Skip to content
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.

Sign up for GitHub

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

Jump to bottom

OTA invalid magic byte (IDFGH-10674) #11903

Closed
3 tasks done
baldhead69 opened this issue Jul 19, 2023 · 32 comments
Closed
3 tasks done

OTA invalid magic byte (IDFGH-10674) #11903

baldhead69 opened this issue Jul 19, 2023 · 32 comments
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally

Comments

@baldhead69
Copy link

baldhead69 commented Jul 19, 2023 •
edited
Loading

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Hi,

I am implementing the example "advanced_https_ota_example" https://github.com/espressif/esp-idf/bl ... _example.c with some particular changes.

After ota app update at new partition( 0x1010000 ), appear this error message, and ESP32-S3 boot from old partition ( 0x20000 ).

E (129) esp_image: image at 0x1010000 has invalid magic byte (nothing flashed here?)
E (137) boot: OTA app partition slot 1 is not bootable

Maybe the size of flash memory with 32MB is not supported ?!

More informations here:
https://www.esp32.com/viewtopic.php?f=13&t=34682&p=117009#p117009

Thank's.
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jul 19, 2023
@github-actions github-actions bot changed the title OTA invalid magic byte OTA invalid magic byte (IDFGH-10674) Jul 19, 2023
@mythbuster5
Copy link
Collaborator

related docs: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/peripherals/spi_flash/spi_flash_optional_feature.html#bit-address-flash-chips

@baldhead69
Copy link
Author

baldhead69 commented Jul 20, 2023 •
edited
Loading

related docs: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/peripherals/spi_flash/spi_flash_optional_feature.html#bit-address-flash-chips

My board use octal flash communication( i configured in this way ), so, i think that docs not apply and my memory chip is different, i think it is MX25UM25645G.
"This option only valid for 4-line flash. Octal flash doesn’t need this."

And i dont have sure if the problem is the memory size ( 32MB ).

@baldhead69
Copy link
Author

baldhead69 commented Jul 21, 2023 •
edited
Loading

The problem, i think, is flash memory size ( 32MB ).

I changed the partition table to address below 16MB and it worked.

How to make it work for addresses above 16MB too ???

Updated answer here:
https://www.esp32.com/viewtopic.php?f=13&t=34682&p=117182#p117182

@ESP32DE
Copy link
Contributor

ESP32DE commented Aug 1, 2023

hi @baldhead69
espressif/esptool#883
best wishes
;-)

@baldhead69
Copy link
Author

hi @ESP32DE,

In my case the ota update by wifi achieves flash the image on flash memory without problems.

When the ota update restart the chip, the message "OTA invalid magic byte" appear and the esp32-s3 use the old firmware to start.

The problem only appears if the address of the new firmware is above 16 MB( specified in the partition file ).

Thank's.

@baldhead69 baldhead69 mentioned this issue Oct 11, 2023
Closed
3 tasks
@mythbuster5
Copy link
Collaborator

ota_32M.txt
Sorry for the late reply. I'm working on other stuff these days... rename it to ota_32M.patch, and apply it. I think this will solve your problem

@baldhead69
Copy link
Author

baldhead69 commented Oct 17, 2023 •
edited
Loading

Hi @mythbuster5,

I applied the patch and errors appeared.
I dont know if i applied the patch correctly.

esp-idf: v5.1

Sem título

@mythbuster5
Copy link
Collaborator

5.1? My version is based on the latest, let me check.

@baldhead69
Copy link
Author

5.1 is the latest stable version, no ?

@baldhead69
Copy link
Author

baldhead69 commented Oct 19, 2023 •
edited
Loading

@mythbuster5 ,

you can change the latest stable version of esp idf.

I download the latest stable version, just tell me what it is, I think it's version 5.1.1 (give me the download link so we can be sure we are working with the same version of esp-idf).

Thank's.

@baldhead69
Copy link
Author

@mythbuster5 ,

you can change the latest stable version of esp idf.

I download the latest stable version, just tell me what it is, I think it's version 5.1.1 (give me the download link so we can be sure we are working with the same version of esp-idf).

@mythbuster5 ,

Completed ?

@baldhead69
Copy link
Author

please reopen this issue

@baldhead69 baldhead69 mentioned this issue Oct 30, 2023
Closed
@mythbuster5
Copy link
Collaborator

Please pick this commit to your branch 6cea72b The backport on 5.1 has not been arrived.

@baldhead69
Copy link
Author

Work on latest stable version ?

I think latest stable version is v5.1.1

@baldhead69
Copy link
Author

@mythbuster5,

I updated esp-idf to v5.2-dev-3775-gb4268c874a and got errors yet.

@igrr, could you help me with this issue ?

buggy_yet

espressif-bot pushed a commit that referenced this issue Nov 8, 2023
@mythbuster5
fix(ota): Fixed OTA fail on octal flash with 32MB memory,
643b0ab 
Closes #11903
@baldhead69
Copy link
Author

Hi,

Someone can open this issue again, since this hasn't been solved yet.

espressif-bot pushed a commit that referenced this issue Nov 14, 2023
@mythbuster5
fix(ota): Fixed OTA fail on octal flash with 32MB memory,
f5e80b6 
Closes #11903
@baldhead69
Copy link
Author

?????????

@ginkgm
Copy link
Collaborator

ginkgm commented Nov 15, 2023

Hi @baldhead69

5.1.2 is going to be released soon, you may wait for that.

igrr pushed a commit that referenced this issue Nov 16, 2023
@mythbuster5
fix(ota): Fixed OTA fail on octal flash with 32MB memory,
bb7544e 
Closes #11903
@baldhead69
Copy link
Author

baldhead69 commented Nov 23, 2023 •
edited
Loading

@mythbuster5 and @igrr and @ginkgm ,

I want to know why this issue was not reopened ???

Open this issue again, please.

This issue is not solved yet.

I have already asked to reopen this issue several times, I don't know why espressif team closed this issue

Close the issue when i confirm that the solution worked.

I downloaded esp-idf v5.1.2 and the SAME problem persists.

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40379c47
0x40379c47: esp_restart_noos_dig at C:/esp-idf/components/esp_system/port/esp_system_chip.c:57 (discriminator 1)

SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fce3818,len:0x17fc
load:0x403c9700,len:0x4
load:0x403c9704,len:0xcb4
load:0x403cc700,len:0x3008
entry 0x403c9984
I (38) boot: ESP-IDF v5.1.2 2nd stage bootloader
I (38) boot: compile time Nov 23 2023 19:31:29
I (38) boot: Multicore bootloader
I (41) boot: chip revision: v0.1
I (45) boot.esp32s3: Boot SPI Speed : 80MHz
I (49) boot.esp32s3: SPI Mode       : SLOW READ
I (55) boot.esp32s3: SPI Flash Size : 32MB
I (59) boot: Enabling RNG early entropy source...
I (65) boot: Partition Table:
I (68) boot: ## Label            Usage          Type ST Offset   Length
I (76) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (83) boot:  1 otadata          OTA data         01 00 0000f000 00002000
I (91) boot:  2 ota_0            OTA app          00 10 00020000 00fe7000
I (98) boot:  3 ota_1            OTA app          00 11 01010000 00fe7000
I (106) boot: End of partition table
E (110) esp_image: image at 0x1010000 has invalid magic byte (nothing flashed here?)
E (118) boot: OTA app partition slot 1 is not bootable
I (124) esp_image: segment 0: paddr=00020020 vaddr=3c0c0020 size=86c20h (551968) map
I (257) esp_image: segment 1: paddr=000a6c48 vaddr=3fc9d000 size=05678h ( 22136) load
I (263) esp_image: segment 2: paddr=000ac2c8 vaddr=40378000 size=03d50h ( 15696) load
I (267) esp_image: segment 3: paddr=000b0020 vaddr=42000020 size=bb358h (766808) map
I (444) esp_image: segment 4: paddr=0016b380 vaddr=4037bd50 size=11290h ( 70288) load
I (470) boot: Loaded app from partition at offset 0x20000

@Spritetm Spritetm reopened this Nov 24, 2023
@Spritetm
Copy link
Member

Reopened as apparently this is not fixed yet.

@baldhead69
Copy link
Author

baldhead69 commented Nov 28, 2023 •
edited
Loading

Considering that my idea is to divide the 32 MB memory into two 16 MB partitions and that for accessing the first 16 MB only need 3 bytes of address ( 2^24 = 16.777.216 -> 0 to 16.777.215 ), 16.777.215 = 11111111 11111111 11111111 and for acessing 32 MB only need 25 bits ( 2^25 = 33.554.432 -> 0 to 33.554.431 ), 33.554.431 = 0001 11111111 11111111 11111111, means that only bit 24 changes the value when accessing the two partitions.

For performance reasons, wouldn't there be a way (command on flash memory) informing the memory that which partition will be accessed in that moment, ie: 0 - 16MB or 16MB-32MB ?

This way only need to send 3 bytes of address to memory instead of 4 bytes.

movsb pushed a commit to movsb/esp-idf that referenced this issue Dec 1, 2023
@mythbuster5 @movsb
fix(ota): Fixed OTA fail on octal flash with 32MB memory,
bc420c9 
Closes espressif#11903
@baldhead69
Copy link
Author

@Spritetm ,

Do you have some position on this ?

Thanks.

@igrr
Copy link
Member

igrr commented Dec 20, 2023

The fix on release/v5.1 branch is linked above — bb7544e. This commit is not in v5.1.2 release, it will be included in v5.1.3.

@baldhead69
Copy link
Author

baldhead69 commented Dec 20, 2023 •
edited
Loading

@igrr

I have version 5.1.2.

How do I use this commit in version 5.1.2 ?

"c:\esp-idf>git cherry-pick -n bb7544e"    ???

"c:\esp-idf>git cherry-pick bb7544e65aba750aad7dfd641a2b166b9e0a2ffe"    ???

@huming2207 huming2207 mentioned this issue Dec 21, 2023
Closed
3 tasks
@baldhead69
Copy link
Author

????

@baldhead69
Copy link
Author

@igrr

@igrr
Copy link
Member

igrr commented Jan 4, 2024

@baldhead69 Please try this:

git cherry-pick bb7544e
git cherry-pick 8f6213c9

(the 2nd commit is the fix for the compilation issue reported in #12850, linked above)

@baldhead69
Copy link
Author

baldhead69 commented Jan 10, 2024 •
edited
Loading

@igrr

bad_revision

@baldhead69
Copy link
Author

The fix on release/v5.1 branch is linked above — bb7544e. This commit is not in v5.1.2 release, it will be included in v5.1.3.

Is esp_idf v5.1.3 already available ?

@baldhead69
Copy link
Author

fetch.txt

I tried this:
fatal: bad revision while cherry-picking a commit!
This happens when your local git remains oblivious of the existence of the commit. To fix this, fetch all the branches, and then cherry-pick again.

From here:
https://blog.mayadata.io/openebs/avoiding-git-panic-part-i-novice#:~:text=fatal%3A%20bad%20revision%20while%20cherry,and%20then%20cherry%2Dpick%20again.

But not worked.

@baldhead69
Copy link
Author

The ota is working now.

Solution here:
https://www.esp32.com/viewtopic.php?f=13&t=37734

@espressif-bot espressif-bot added Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: Opened Issue is new labels Feb 8, 2024
@Alvin1Zhang
Copy link
Collaborator

Thanks for sharing the feedback, feel free to reopen.

hathach pushed a commit to adafruit/esp-idf that referenced this issue Mar 27, 2024
@mythbuster5 @hathach
fix(ota): Fixed OTA fail on octal flash with 32MB memory,
9a9874d 
Closes espressif#11903
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@igrr @Spritetm @ESP32DE @baldhead69 @ginkgm @mythbuster5 @Alvin1Zhang @espressif-bot