nRF52 app plus bootloader

RE: nRF52 app plus bootloader

bjorn-spockeli — Mon, 11 Jul 2016 13:57:43 GMT

Glad to hear that you got it working using the Rigado Modules!

RE: nRF52 app plus bootloader

ejg2putt — Thu, 30 Jun 2016 19:06:28 GMT

It did not, but then we switched our hardware to the Rigado nrf52 module, which has its own bootloader and app integration library. I believe the issues we were having were related to the ROM/RAM settings, but never had a chance to debug. Appreciate all the help regardless, it kept us moving along at the time.

RE: nRF52 app plus bootloader

bjorn-spockeli — Thu, 30 Jun 2016 13:15:01 GMT

@andreas_wickstrom: See this page on our Infocenter to see how you switch to bootloader mode and initiate the DFU process.

@ejg2putt: Did the memory settings that I gave you fix the issue?

RE: nRF52 app plus bootloader

ejg2putt — Sun, 19 Jun 2016 21:32:06 GMT

The SDK handles the firmware update automatically when the DFUServiceInitiator is started. Just give it the file name of the zip file.

RE: nRF52 app plus bootloader

Andreas_Wickström — Fri, 17 Jun 2016 07:41:47 GMT

Hi When bootloading from app. Do you set the bootloadersetting to BANK_INVALID_APP from the application and then start the bootloader or how do you let the bootloader know when to update the firmware?

RE: nRF52 app plus bootloader

bjorn-spockeli — Mon, 30 May 2016 08:12:57 GMT

Great, keep me posted :)

RE: nRF52 app plus bootloader

ejg2putt — Sun, 15 May 2016 21:58:09 GMT

Thanks Bjorn, Haven't had a chance to try this yet, been working on our hardware. Will post results once I get back to this.

RE: nRF52 app plus bootloader

bjorn-spockeli — Thu, 28 Apr 2016 11:32:50 GMT

The correct ROM/RAM settings for the bootloader(S132 v1.0.0-3.alpha and SDK v0.9.2) are:

IROM1: Start 0x7B000 Size: 0x4C00
IRAM1: Start 0x20002C00 Size: 0x5380
IRAM2: Start 0x20007F80 Size: 0x80

RE: nRF52 app plus bootloader

ejg2putt — Fri, 22 Apr 2016 19:47:33 GMT

Bjorn or anyone else. Any ideas or suggestions about the linking errors? I can not seem to find the proper settings for the ROM load regions as mentioned above.

Thanks Ed

RE: nRF52 app plus bootloader

ejg2putt — Wed, 20 Apr 2016 18:16:58 GMT

I've not been able to find any definitive documentation on setting the IROM1/2 settings to eliminate the linker errors. I need 0x50E0 space according to the linker:

Load region LR_IROM1 size 20704 Execution region ER_IROM1 20480

If I expand IROM1 by this amount, nrfprog complains about invalid addresses, I could not find an nRF52 version of this post:

devzone.nordicsemi.com/.../

but playing around with various values for IROM1/2 start and size did not produce anything that works.

If I need a total of 0x50E0 bytes can you tell me the proper IROM1/2 settings, assuming that is indeed my problem.

Thanks Ed

RE: nRF52 app plus bootloader

ejg2putt — Wed, 20 Apr 2016 11:58:59 GMT

Thanks Bjorn, I've made the code change in bootloader_settings.c, getting a couple linker errors about LR_IROM1 size exceeding limits. I'm in meetings all day, I'll troubleshoot those problems later today.

RE: nRF52 app plus bootloader

bjorn-spockeli — Tue, 19 Apr 2016 12:56:55 GMT

I recommend setting the BANK_VALID_APP flag in the bootloader code instead of merging in a spearate hex file. You just have to alter one line in in bootloader_settings.c from

uint8_t  m_boot_settings[CODE_PAGE_SIZE]    __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used));

to the following

uint8_t  m_boot_settings[CODE_PAGE_SIZE]    __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used)) = {BANK_VALID_APP};

RE: nRF52 app plus bootloader

ejg2putt — Tue, 19 Apr 2016 11:16:50 GMT

Yes, the application runs fine if I don't try to extend with DFU support. The example code also runs fine, can do an OTA with no problem - the firmware is properly downloaded and the app restarts with the downloaded code with no problem. I've successfully done this with a downloaded image of our own code using the dfu boot loader example.

I was seeing the same problem when I merge the bootloader with the mergehex command in the first line of my script.

But I was seeing some other strange behavior with our dev system yesterday (some sort of weird JLink logging behavior on our non-OTA/bootloader version of the code), I'm going to switch systems later today, and will retry everything. I'll let you know what I find, thanks for your help so far.

Just for reference, is either one of the app_valid_setting_apply.hex files that I used correct? Is one preferred over the other?

Thanks Ed

RE: nRF52 app plus bootloader

bjorn-spockeli — Tue, 19 Apr 2016 07:03:13 GMT

Does the application run on the PCA10040 if you do not extend the application with DFU support?

Looking at one of your previous comments:

mergehex -m s132_nrf52_1.0.0-3.alpha_softdevice.hex appIn.hex app_valid_setting_apply.hex -o appOut.hex

nrfjprog.exe --family NRF52 --eraseall

nrfjprog.exe --family NRF52 --program appOut.hex

nrfjprog.exe --family NRF52 --verify appOut.hex

nrfjprog.exe --family NRF52 --reset

In the first step(mergehex) it would appear that you're only merging the SoftDevice and the Application. Is the bootloader hex already merged with the application or softdevice?

RE: nRF52 app plus bootloader

ejg2putt — Mon, 18 Apr 2016 23:14:27 GMT

Here's two I tried:

:020000040003F7 :10FC00000100000000000000FE000000FFFFFFFFF9 :00000001FF

:020000040003F7 :08FC00000100000000000000FB :00000001FF

If I do not merge either hex file above, the device appears to be non-operable - I don't get anything on the console, nor can I see any dfu advertising, etc. So it really doesn't seem to matter if one of the above files are merged or not, device seems to be dead. Any suggestions are debugging further, troubleshooting, etc. are appreciated.

RE: nRF52 app plus bootloader

bjorn-spockeli — Mon, 18 Apr 2016 10:27:47 GMT

Could you upload the app_valid_setting_apply.hex? Does the device start in bootloader mode if you do not merge in the app_valid_setting_apply.hex?

RE: nRF52 app plus bootloader

ejg2putt — Mon, 18 Apr 2016 09:38:42 GMT

Yes, that appears to be the case. Neither the debugger nor various printfs I've added show anything - I've see various posts on debugging this, but none have really worked for me.

Here's my script:

mergehex -m s132_nrf52_1.0.0-3.alpha_softdevice.hex appIn.hex app_valid_setting_apply.hex -o appOut.hex nrfjprog.exe --family NRF52 --eraseall nrfjprog.exe --family NRF52 --program appOut.hex nrfjprog.exe --family NRF52 --verify appOut.hex nrfjprog.exe --family NRF52 --reset

After I run the script, I can see the app, softdevice, and bootloader at the proper addresses in nRFgo Studio.

RE: nRF52 app plus bootloader

bjorn-spockeli — Mon, 18 Apr 2016 09:23:20 GMT

So if you flash the application with DFU support together with the Bootloader and Softdevice, then neither the Bootloader or the application wills start?