-
Notifications
You must be signed in to change notification settings - Fork 1.1k
#2082 breaks user firmware update #2219
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
Comments
Sorry Luke - I might need some guidance on this. |
I think this was fixed in #2116 - with that fix the |
Nope, it gets inlined into pico-sdk/src/rp2_common/hardware_flash/flash.c Lines 288 to 296 in 3d746b3
pico-sdk/src/rp2_common/hardware_flash/flash.c Lines 305 to 310 in 3d746b3
declaring
Didn't take a look at the other functions, so there might be some others needing this massage. |
fix merged into develop |
We have a firmware update in which we copy a new image onto an older image (erase, write), then reset. We've been running this with SDK 2.0.0 in evb-pico2-alike boards.
With #2082 in SDK 2.1.0,
flash_range_erase()
adds this:pico-sdk/src/rp2_common/hardware_flash/flash.c
Lines 141 to 143 in 389dc03
Here,
flash_rp2350_restore_qmi_cs1()
callsflash_devinfo_get_cs_size()
, which callsflash_devinfo_ptr()
, function that is not declared as__no_inline_not_in_flash_func
and hence is in flash.Should this function somehow not have been erased, yet, it will call
rom_data_lookup()
, also resident in flash.Is this change actually necessary when one is going to erase everything ?
Is there a workaround that I can easily apply ? (instead of patching
flash_range_erase()
or writing our own version of it, of course)Regards
The text was updated successfully, but these errors were encountered: