Firmware update not working with MBOOT on a PyBoard with expanded internal file system #15193
Unanswered
saraverbeecke
asked this question in
STM32 / Pyboard
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I hope someone can help me out...
I am not able to perform a firmware update using a new firmware file placed on the internal file system using a genuine PyBoard.
mpconfigboard.h
,mpconfigboard.mk
andstm32f405.ld
(and alsoflashbdev.c
) files in order to obtain more file system space. (384kB for FLASH_TEXT, 368kB for FLASH_FS in total; see files contents below for reference)ports/stm32/mboot
dirmpremote
or via USB (MSC drag and drop)fwupdate.py
to the boardOutcome: board goes into bootloader, red LED flashes a few times, then stays on for a few seconds and the board returns to old firmware. (also tried the non-gzip of the .dfu, but same result). The gzip or non-gzip new firmware file can fit in the 384kB on to the filesystem and in the FLASH_TEXT available space.
Questions
fwupdate.update_mpy('/flash/firmware.dfu.gz', 0x80A00000, 3 * 128 * 1024)
0x80A00000 is the right start address for the internal FLASH_TEXT, 3 * 128 * 1024 equals 384kB the LENGTH of the FLASH_TEXT section. Or do I need to call something else since the docs use this call for a SPI flash update...
Thanks for helping out!
stm32f405.ld
mpconfigboard.h
(is te same as default for PYBV11 except the lines below were added)mpconfigboard.mk
(complete for reference, check TEXT1_ADDR pointing to the correct start address of the FLASH_TEXT startin at sector 9)flashbdev.c
(the same except added the necessary lines for handling extra sectors see below)Beta Was this translation helpful? Give feedback.
All reactions