SDK 12: dfu/bootloader questions

[Mario Ribeiro]

Hi,

With the latest SDK (12) there isn't an UART bootloader example available. Am I right?

I'm trying to understand what are the options to program the nRF51 during production. I'll use a JLink to program the bootloader but then I need to upload the app through it. I'd prefer a solution that doesn't require a smartphone nor a nRF kit for uploading so I think that having the UART bootloader would be a good ideia. However since it's not available:

1. Do you plan to release (again) a UART bootloader on newer SDKs? Or, any pointers on how to implement it with current SDK?

2. Do you plan to support uploading through BLE bootloader without requiring an nRF5 kit? (ie, using a simple BLE dongle, as I'm already using to test the PCB after production)

3. Is it possible to program both the bootloader and the app code with JLink?

Thanks!

[AlekseyJ]

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

[Mario Ribeiro]

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