-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
info sections (like .defmt) are downloaded instead of discarded on the esp8266 #471
Comments
How did you add defmt support? The official template marks the |
I also find it a bit strange.
Is this maybe a problem of the (gcc) linker used with the esp8266? (using |
Hmm actually it appears |
Yes it is strange that even if I use the official template As for the discarding: I think for the esp8266 the address space is not checked? |
At that would be it. Sorry its been a long long time since I looked at the esp8266 stuff. Would you mind sending a PR to check the address space when merging sections? |
Actually, also on the esp32c3 the https://github.com/esp-rs/no_std-training/tree/main/intro/hello-world, but with defmt added
The only difference is, that addr=0 and on the esp8266 addr=1. An addr=0 will cause the segment to be discarded (elf.rs) Regarding the implementation: How do we fix this? |
Hmm, I guess understanding why it's assigned an address of 1, when on every other chip the defmt section has an address of 0, is how we solve this. Of the top of my head though, I don't have any idea why this would be the case :( |
We've decided to drop support for the ESP8266 (see #576), so closing this issue. |
I'm using the esp8266 with defmt.
defmt uses a linker script
defmt.x.in
that adds a custom section:As a result the elf file looks like this (
xtensa-lx106-elf-readelf -S mytarget
):(not sure why the info flag is not set on
.defmt
)The current code of espflash, does not discard that
.defmt
section and instead downloads it.As a result the chip won't boot up.
Hacky patch, to get it working:
The text was updated successfully, but these errors were encountered: