nRF DFU works only in using SES, not after nrfjprog programming

RE: nRF DFU works only in using SES, not after nrfjprog programming

bjorn-spockeli — Wed, 27 Mar 2019 15:53:38 GMT

Didnt see your first comment when I wrote my reply.

Yes, a reference to printf with the logging module disabled could lead to unwanted behaviour, so I would remove it/comment it out and then see if it helps. However, then you should see the nRF asserting in the debug session as well I would think.

You can flash the Softdevice first with the --chiperase option and then you should only have to use --sectorerase when flashing the bootloader mergerd with the settings hex using sectorerase(which isnt strictly needed since you have run a chiperase when flashing the SD).

RE: nRF DFU works only in using SES, not after nrfjprog programming

sbu — Wed, 27 Mar 2019 15:30:25 GMT

"How do you program the setting.hex in the first scenario if you're not using nrfjprog?" => You're right, I was using nrfjprog for this step, but without merging with the bootloader.

"Do you mean that you start a debug session?" => Yes, but in release build.

First I only use --sectorerase, but return a warning for the UIC segment that require to be rewritten (i guess to update the start address). In both case, the bootloader does not answer after the first command. What do you think about the printf I forgot to remove ? can it explain the problem ?

I will change nRFGo for nRF Connect.

RE: nRF DFU works only in using SES, not after nrfjprog programming

bjorn-spockeli — Wed, 27 Mar 2019 15:04:34 GMT

Hi Stephane,

I strongly recommend that you use nrfjprog directly or the new Programmer app in our nRF Connect for Desktop to program the application and SoftDevice. nRFGo Studio is deprecated for the nRF52 series.

How do you program the setting.hex in the first scenario if you're not using nrfjprog?

Also you state:

[quote user=""]Then I launch the bootloader using SES.[/quote]

Do you mean that you start a debug session?

I cant see any issues with the nrfjprog commands,

Can you try to flash the softdevice and appplication using nrfjprog before you flash the bootloader and also replace the --sectoranduicrerase with --sectorerase?

Best regards

Bjørn

RE: nRF DFU works only in using SES, not after nrfjprog programming

sbu — Wed, 27 Mar 2019 14:41:14 GMT

I am unsure, i still need to do more testing, but is it possible that a printf in the code can cause the crash of the bootloader ? I add a printf in one of the uart driver function that was previously blocking and I needed to monitor its result but forgot to remove it.NRF_LOG is disabled in release mode and cannot enable it as there is not enough space for it.

It seems that after removing this, it works. If you think this could be link, I would like to understand the reason and if there is a way to properly disable printf output in suc case, but if you don't, let me know as it will happen again. regards