nrfutil generate incorrect bootloader settings (for nRF52840)

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Chibi — Mon, 30 Mar 2020 15:22:57 GMT

That's a good idea, I'll open a new case. Thanks.

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Edvin — Mon, 30 Mar 2020 14:13:02 GMT

I think we should take it in a new case, because it may be helpful for other users as well. And it is certainly easier to find if it is related to the title of the case 🙂

Best regards,

Edvin

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Chibi — Mon, 30 Mar 2020 13:13:25 GMT

Hi Edvin,

Thanks for the URL link - it was very informative.

I may have also solved my original issue concerning the hard fault (in my main application) - at least I'm no longer seeing it for the time being.

I have another unrelated question - do you mind if I ask it here or should I create another case? My new issue concern the usage of the RTC (Real Time Counter) peripheral.

Thanks again.

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Edvin — Mon, 30 Mar 2020 09:06:47 GMT

Hello,

The GPIOs are reset by a soft reset (sd_nvic_SystemReset). You can see the reset behavior for different peripherals based on different reset reasons in this table.

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Chibi — Fri, 27 Mar 2020 16:44:18 GMT

Hi Edvin,

The hardfault is happening in my main application (which uses SoftDevice S140 7.0.1) on my custom hardware. It was reported by my IAR debugger.

Actually, I have tried the DFU bootloader a while ago and confirmed its correct operation on the dev kit.

Perhaps you can help me with a slightly different question? If I called sd_nvic_SystemReset (e.g. to enter the secure bootloader from my main application, after setting the GPREGRET register with 0xB1), does it preserve the GPIO settings or will they get reset as well?

Thanks.

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Edvin — Fri, 27 Mar 2020 15:07:19 GMT

Are you sure it is a hardfault?

Did you do any changes to the bootloader project? If so, can you try to unzip an unmodified version of the SDK, and check if it behaves the same. If so, try the ..._debug project for the bootloader (if you use pca10056_ble now, use pca10056_ble_debug instead) and monitor the RTT log output. What does it say?

Perhaps the bootloader is working, but the application crashes before it has time to do anything sensible (that you can see in the log/LEDs)?

If not, the bootloader log should reveal some information.

Best regards,

Edvin

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Chibi — Fri, 27 Mar 2020 13:46:40 GMT

Hi Edvin,

I am having some issues with a hard fault when used in conjunction with the secure bootloader and the bootloader settings. Whilst debugging, I spotted the oddity with the bootloader settings.

I don't think that is the cause of the issue I am seeing but I just wanted to understand that the settings I have created is valid because the documentation is perhaps not 100% clear (or more likely I failed to read it properly).

Thanks.

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Edvin — Fri, 27 Mar 2020 13:09:07 GMT

Hello Chibi,

I don't know exactly what is written where (you would have to look at the implementation of nrfutil for that), but I get the same output as you when I use the settings display command, the "Bad access" message. It has been around for a while, but I don't think it actually does any harm. You can check the nrfutil implementation for why it is printed. However, the settings file works just fine (also tested with the same version that you use).

Do you experience any issues with the settings file? If so, can you please describe the symptoms? In my opinion, everything looks good.

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Chibi — Fri, 27 Mar 2020 11:50:34 GMT

Hi Edvin,

Thanks for your reply but I am still a bit confused. I agree with your observation but that is not what I'm seeing (I think) from the generated bootloader settings image.

From what I can see in the bootloader settings hex image, the settings is written to flash starting from address 0x000FE000 and ends at address 0x000FE320. There is an additional block which is written between address 0x000FF000 and 0x000FF320.

Is this the backup page (0x000FE000 - 0x000FE320) - the contents and size looks identical to the second block? As per your observation, this memory is reserved for the MBR parameter storage.

Cheers,

Chibi

RE: nrfutil generate incorrect bootloader settings (for nRF52840)

Edvin — Fri, 27 Mar 2020 10:53:16 GMT

Hello,

The bootloader settings doesn't actually start before 0x000FF000, but the MBR parameters are stored from 0x000FE000, as it says in the memory range table that you have posted.

So this is expected.

Best regards,

Edvin