SDK 12: dfu/bootloader questions

RE: SDK 12: dfu/bootloader questions

Mario Ribeiro — Tue, 29 Nov 2016 15:49:34 GMT

Ok, got it working with a .bat script. Basically, you just need to merge all the .hex you wat to write into memory.

nrfutil settings generate --family NRF51 --application %app_hex% --application-version 0xFFFFFFFF --bootloader-version 0xFFFFFFFF --bl-settings-version 1 bootloader_settings.hex

mergehex -m %bootloader_hex% %app_hex% bootloader_settings.hex -o nrf_bootloader_and_app.hex

nrfjprog --reset --program %sd_hex% -f nrf51 --chiperase 
nrfjprog --reset --program nrf_bootloader_and_app.hex -f nrf51

One question still persists though. Is serial DFU planned for a future SDK?

RE: SDK 12: dfu/bootloader questions

Mario Ribeiro — Tue, 29 Nov 2016 15:01:25 GMT

Thanks but that doesn't answer any of my questions.

RE: SDK 12: dfu/bootloader questions

AlekseyJ — Mon, 28 Nov 2016 23:13:07 GMT

Bootloader it just a 'switch' between the DFU application and your application. You need tell to bootloader run your application first instead DFU. To do this bootloader need to know CRC32 of your application and then it will jump immediattely to your application. You need use nrfutil to create bootloader setting.hex file and then upload (with j-link) bootloader setting hex file with your bootloader hex file and with your application and softdevice hex files.

To generate bootloader setting hex file:

nrfutil settings generate --family NRF52 --yourapplication.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 bootloader_settings.hex