nRF5340: Forbid BT-DFU when only app_update.bin is uploaded

Question

Hi there 
 
 My costumer was not able to update the cpunet on a nRF5340. 
 A lot of troubleshooting now led to the insight, that the costumer used only the app_update.bin file and not the complete .zip folder. 
 
 Is there a way to forbid the update on the nRF5340 when the net_core_app_update.bin is missing (so when the app is not using the .zip-folder)? 
 
 SDK: v2.6.1 
 
 Thank you and best regards 
 Chris

Einar Thorsrud · Accepted Answer

Hi, 
 ChriglSEI said: Okay, but here NCS 2.5.0: MCUBOOT_IMGTOOL_SIGN_VERSION any way to set this from the content of the new VERSION file? it says, that CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION is also set by the VERSION file. 
 Yes, with recent SDK versions it is. 
 ChriglSEI said: Could you give an example based on e.g. https://github.com/NordicDeveloperAcademy/ncs-inter/tree/main/lesson8/inter_less8_exer3_solution with SDK 2.6.1? 
 I tested this combination on my end now, with the only change being the addition of this in prj.conf: 
 CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION="4.0.0+0"
CONFIG_NRF53_ENFORCE_IMAGE_VERSION_EQUALITY=y 
 and I also modified the printout on line 189 (the first printk in main()), to show the version. And with this I see that without CONFIG_NRF53_ENFORCE_IMAGE_VERSION_EQUALITY=y I am allowed to update only the app core (using app_update.bin), but with CONFIG_NRF53_ENFORCE_IMAGE_VERSION_EQUALITY=y I need to update both (using dfu_application.zip). So from what I can see this works as expected. Do you not see the same? One issue though is that the nRF Connect application does not do this validation, it is done by MCUboot, so it will indicate success even if MCUboot did not do the update due to version mismatch. By printing the version in the log you can see that the update did not happen.

nRF5340: Forbid BT-DFU when only app_update.bin is uploaded

Top Replies