Hi,
I am trying to migrate my device from s132 7.2.0 to s332 7.0.1, for adding ANT.
I have no more access to the SWD.
I know it is not tested :
docs.nordicsemi.com/.../lib_bootloader_dfu_validation.html
"Updating between different SoftDevice families"
As proposed, I commented :
// else if (SD_PRESENT && (SD_ID_GET(MBR_SIZE) != SD_ID_GET(sd_start_addr)))
// {
// NRF_LOG_ERROR("The new SoftDevice is of a different family than the present SoftDevice. Compatibility cannot be guaranteed.");
// result = false;
// }
And changed "is_major_softdevice_update" to respond true.
it is not 7=>7, but I thought it is even worse and it is used to : "Invalidating app because it is incompatible with the SoftDevice"
I have added RTT log to see what is going on.
I have made a pkg having : bootloader, s332, and working app with s332. (for testing : flashing with SWD on a simple kit works, it is running)
Log shows it is taking data from ble, and writhing in flash at 0x26000, about 215kb (seems to be s332 + bootloader ?)
But after I do not understand, it is copying the s332 :
<W> app: Copying 0x26000 to 0x1000, size: 0x2F000 (why 0x1000 ?)
But nothing after. It seems to be blocked.
I do not understand how it is supposed to work ? It is replacing the SD it is using. Or eaven less how bootloader update is done ? (ram execution ? I can not find any ...)
But it should be the same probleme while doing (a major) sdk update ? Or it is using only for BLE, not for flash copy ?
It seem to be possible :
devzone.nordicsemi.com/.../migrate-softdevice-from-s132-to-s332
"The first one update the SoftDevice. If your bootloader depends on the SoftDevice, this update also need to include a new bootloader."
"After that update, the application is invalidated. The bootloader will enter DFU mode waiting for the application update, which will be the second update."
Thank you in advance for any help.
