-
Notifications
You must be signed in to change notification settings - Fork 130
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
Large .text segments are merged incorrectly? #552
Comments
Hi! The default |
Hello @t-moe, could you try reproducing the behavior with |
Hi @SergioGasquez , I'll answer in two comments. Partiton-table for both:
First bugIf I run I get the following error after boot:
Full Log output for spi autodetect stuff
|
Second BugIf I run I get the following, different error after boot:
Full Log output
Ping me on matrix if you need the elf file. EDIT: removed the |
Regarding trying with esptool, I assume you mean something like the following: Starting with the elf from the previous step:
But this outputs a warning during flashing :
and later
How do I have to adapt my steps to test the thing with esptool? Thank you |
I think the steps would be the following:
You may need adding
|
I've done some investigation. And compared esptool with espflash. Using your elf, I can generate the binary with espflash:
Which we can inspect with esptool:
But, when trying to generate the binary from elf using esptool:
I can still flash the espflash generated bin with esptool:
Also tried flashinig the elf with esptool:
And flashing the elf with espflash:
|
I just did another test, using a freshly generated template (targetting esp32c6 and not using advanced config), I tried using your partition table and flash it with espflash and esptool:
With esptool:
espflash is able to flash and run the project properly using your custom partition table while esptool complains about the magic number of partition 0 |
A small summary with some findings:
Not sure if this is an |
https://github.com/bjoernQ/espsegs might help us debug this issue |
I'm using a esp32c6 here with 8MB of flash and I have a rust program that is around 2 Mb, based on the
esp-idf-*
crates.My partition table:
Output of riscv32-esp-elf-objdump -h
When I run
espflash flash --monitor --partition-table ./partitions.csv <elf>
, I get the following output:Note how the bootloader does not detect the chip size correctly. This is probably a small bug in espflash somewhere.
If I now invoke
espflash flash --monitor --partition-table ./partitions.csv --flash-size 8mb <elf>
I get the following output:Now the bootloader detects the flash size correctly, but cannot load the segments.
Without investigating in detail, to me it looks that we still have some problems with merging the segments.
I'm using espflash from todays master branch (074f8bc)
The text was updated successfully, but these errors were encountered: