Skip to content

Conversation

tannewt
Copy link
Member

@tannewt tannewt commented Aug 26, 2025

Only minor changes needed. Should hopefully fix things along with better support for newer hardware.

Copy link
Collaborator

@dhalbert dhalbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry to say:

Metro ESP32-S2 and ESP32-S3 UF2's load but don't come up. /dev/ttyACM0 appears but not responsive, and no MSC shown.

Feather ESP32 V2 does not come up. No response on serial.

Espressif C3 DevKit board bootloops

Espressif C6 DevKit board shows boot log and then stops.

@tannewt
Copy link
Member Author

tannewt commented Aug 27, 2025

Thanks for the testing! I saw similar issues on the C5 and assumed it was a C5 issue. So I moved on. I see similar issues on the C6 and ESP32 so I'm hunting it down. I'm hopeful it'll fix all of the different variants and the C5. They added support for picolibc instead of newlib and that may have messed up some of the linking. I'm not sure, and still looking into it. I'll undraft after I've smoke tested successfully on a number of chips.

@@ -156,11 +157,13 @@ REGISTRATION_FUNCTIONS = \
-u __ubsan_include \
-u esp_system_include_startup_funcs \
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that both this and bt pull in coex now. Not sure if coex is worth including for everything but just a heads up since h2 and p4 chips have wifi disabled. I just OR'd the configs in my branch to make sure when testing just bluetooth without wifi that everything gets linked but either way I think it will require some additional casing to handle the p4 which lacks both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants