DFU: nRF51822 OTA bootloader jams after reset_prepare()

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Mon, 07 Dec 2015 10:48:24 GMT

Thanks, that clarified a bit!

What I really need is to be able to upload application.zip from nRFTools. If I do the reset, then it doesn't work very well, because user needs to start the upload twice... And if I don't, the bootloader jams into its event loop. :(

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Vidar Berg — Mon, 07 Dec 2015 08:54:03 GMT

The assembly routine in bootloader_util_app_start() does jump from application to bootloader, but it doesn't do a system reset like NVIC_SystemReset, power on reset or a pin reset resulting in the softdevice already being invoked going from application to bootloader. This is the reason for the "app reset" check in ble_stack_init() as SD_MBR_COMMAND_INIT_SD can't be issued when SD is already invoked. In other words, only issue the SD_MBR_COMMAND_INIT_SD command if a system reset has been performed.

Reason for not doing a system reset in the example is to support sharing of bond information between the application and bootlaoder to keep the same encrypted link while doing DFU (bond sharing). If this feature is not needed you can call NVIC_SystemReset(); in your application and always invoke the Softdevice in ble_stack_init().

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Sat, 05 Dec 2015 19:17:50 GMT

Thanks, I will examine those things, too.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Sat, 05 Dec 2015 11:06:24 GMT

I am now using a dirty hack to get rid of bootloader jamming. The modification is at the bootloader's main.c, and it makes the bootloader to reset after it first enters from application, and only after that, it enters the actual bootloader code. However, two upload tries is now needed from nRFTools, so the solution is not optimal.

bool app_reset = (NRF_POWER->GPREGRET == BOOTLOADER_DFU_START);
bool app_reset2 = (NRF_POWER->GPREGRET == ~BOOTLOADER_DFU_START);

if (app_reset)
{
    NRF_POWER->GPREGRET = ~BOOTLOADER_DFU_START;
    NVIC_SystemReset();
}
else if (app_reset2)
{
    NRF_POWER->GPREGRET = 0;
}

In addition, few other changes are needed to support "app_reset2" (several places at main). At least it works now somehow. But it is really a dirty hack as I said...

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Vidar Berg — Fri, 04 Dec 2015 14:49:46 GMT

Hi, are you working with a nRF51 DK kit? Reason I ask is that we have different chip variants in case you're working on a custom board. Some with 16K and 32K of RAM and 128 or 256K of flash (chip variants). DK kit has 256/32 respectively which the examples are based on. So linker settings need to be adjusted accordingly for other variants.

Generally when adding DFU support to an application such as the ble_app_hrs_dfu example you need to follow the instructions given here in the SDK documenation to allow buttonless entry to DFU mode. I guess you have followed those already considering you have implemented at least some of it in the code you posted. Unfortunately, there are two things missing from from these instructions (has been reported internally):

Add loading of service changed flag as shown in the reference example (ble_app_hrs_dfu)
set device_manager_cnfg.h->DEVICE_MANAGER_APP_CONTEXT_SIZE to a multiple of word size. I.e., 4 or more. This is used to store the ATT table changed flag.

I'd suggest to closely compare the ble_app_hrs_dfu example with yours to see if there are any differences releated to DFU implemenation.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Fri, 04 Dec 2015 12:07:17 GMT

Both. Those are in bootloader side. bootloader_util_arm.c is also in application side, but not the bootloader_settings_arm.c.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Fri, 04 Dec 2015 10:04:11 GMT

Do you have bootloader_util_arm.c or bootloader_settings_arm.c or both? And where files are in application or in bootloader.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Fri, 04 Dec 2015 10:01:02 GMT

I agree. And I was mixing-up bootloader_util_arm.c and bootloader_settings_arm.c, although fixing that thing did not help me :(

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Fri, 04 Dec 2015 09:45:19 GMT

yeah i just saw it. the information provided there is not enough.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Fri, 04 Dec 2015 09:44:40 GMT

The application needs it, as it is guided here: developer.nordicsemi.com/.../a00081.html

I think the difference compared to your situation is that I am making an application that can start DFU without any tricks, just using the nRFTools DFU. So that is probably why those bootloader things are needed also in the application side.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Fri, 04 Dec 2015 09:41:13 GMT

The another bootloader_util_arm.c that my app was using was actually from nRF51_SDK_8.0.0_5fc2c3a\examples\dfu\experimental_ant_bootloader by mistake. I replaced it with the one used by bootloader, but it did not change anything. However, there's now nowhere the line UICR you were discussing about. I can try to add it into the bootloader.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Fri, 04 Dec 2015 09:37:39 GMT

My chip is nrf51822, and sdk is 8. bootloader_settings_arm.c is only required in bootloader, and why do you use it in your application?? UICR line must be in bootloader_settings_arm.c, which must be present in bootloader, and not in application.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Fri, 04 Dec 2015 09:29:24 GMT

Well, I had it in my application.I have two quire different bootloader_util_arm.c -files and the another one used by dual-bank bootloader doesn't have the UICR line there, at all. What is the exact version of your bootloader, i.e. from what folder in sdk you found it?

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Fri, 04 Dec 2015 09:01:10 GMT

Make sure "uint32_t m_uicr_bootloader_start_address..." is only in bootloader, and also UICR registers should only be used in bootloader and not in application. using nrfgo studio, use eraseall.

burn softdevice, burn application, burn bootloader. if this doesn't work try eraseall, program softdevice, burn botloader, burn application.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Fri, 04 Dec 2015 07:38:06 GMT

Yeah, I noted that it does not work if I comment the line away. Then I erased the whole chip nRFGo studio. But it did not help, when I try to flash my application having that line uncommented, the errors:

No Algorithm found for: 10001014H - 10001017H

Partial Erase Done (areas with no algorithms skipped!)

No Algorithm found for: 10001014H - 10001017H

Partial Programming Done (areas with no algorithms skipped!)

are still there. I am now stuck on this. What the heck happened, this problem didn't exist two days ago :-o

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Fri, 04 Dec 2015 04:34:31 GMT

Uncomment that line which you have commented out, otherwise bootloader will nerver get flashed. You just have to erase whole nrf chip, or just write, nrfjprog --eraseall --program filename.hex --reset --verify. It will definitely work. and always use given above command for flashing. It is because you can't overwrite UICR registers without erasing them, and those can only be erased by eerasing whole chip.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Thu, 03 Dec 2015 22:33:55 GMT

Actually, I had to comment the line "uint32_t m_uicr_bootloader_start_address..." away to get rid of the error message. And the older project was working because it did not have that file at all, yet. However, now I am back at the starting point: I cannot DFU if my own application is there. I will look your instructions carefully, let's see if I can manage to get it working. Thanks again!

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Thu, 03 Dec 2015 22:15:31 GMT

Well, they were already there. When I try to flash the bootloader, the error message is as follows:

nrfjprog.exe --reset --program "C:\Nordic Semiconductor\nRF51_SDK_8.0.0_5fc2c3a_backup\nRF51_SDK_8.0.0_5fc2c3a\examples\dfu\bootloader\pca10028\dual_bank_ble_s110\arm4_build\nrf51422_xxac.HEX"

Parsing hex file(s).

Checking that there is no data to be written in region 0.

Checking that there are no UICR conflicts.

ERROR: The device has data in the UICR area, and there is a conflict with the hex to download. No program command will automatically erase UICR area. Erase the UICR area and download the hex(s) files again.

And on the other hand, I have two versions of the application project (not the bootloader). Another one does flash OK, while the other fails with the "No Algorithm ..." -error. This just does not make any sense... :( I cannot find the difference even with using WinMerge. AAARRRGGH :(

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Thu, 03 Dec 2015 22:00:51 GMT

in bootloader_settings_arm.c file add "uint32_t m_uicr_bootloader_start_address attribute((at(NRF_UICR_BOOT_START_ADDRESS))) = BOOTLOADER_REGION_START;", #define NRF_UICR_BOOT_START_ADDRESS (NRF_UICR_BASE + 0x14) and #define DFU_BL_IMAGE_MAX_SIZE (BOOTLOADER_SETTINGS_ADDRESS - BOOTLOADER_REGION_START)

it will be there just uncomment it, the error is because of the absence of this line, this line is used to write uicr registers. or use nrfjrog.exe to write image on nrf. else follow given links: developer.nordicsemi.com/.../a00098.html and infocenter.nordicsemi.com/index.jsp

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Thu, 03 Dec 2015 21:44:47 GMT

Thanks for very comprehensive answer! I think my application enters bootloader correctly, but the bootloader might get mad because of our hardware peripherals and their interrupts. Would like to test that, but my project (Keil) corrupted somehow. I get errors:

No Algorithm found for: 10001014H - 10001017H Partial Erase Done (areas with no algorithms skipped!) No Algorithm found for: 10001014H - 10001017H Partial Programming Done (areas with no algorithms skipped!) Partial Verify OK (areas with no algorithms skipped!)

And the application fails to run. I have compared all the settings with an older copy of the project, and everything seems to be similar. But it just continues to give that error! So irritating and frustrating... :(

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Thu, 03 Dec 2015 13:39:40 GMT

I think there is issue with the method of sending nrf into bootloader. I have successfully done ota for application, bootloader and also softdevice. So let me tell you what have i done. In your application code, go where bluetooth messages are recieved. there u can make a function which parses the message. in that function check if (say) 0th byte is 0x1 then just set NRF_POWER->GPREGRET to BOOTLOADER_DFU_START, that's a macro, you can assign whatever value you want, just make sure define it in both application and bootloader. in bootloader in main function just check NRF_POWER->GPREGRET, if it is equal to BOOTLOADER_DFU_START be in bootloader mode.

How to go in bootloader mode from application? go to nrf master control panel app(android), connect to it, dicover services, bond it, enable services.

Let's say my device's name is 1234, as shown in image. select it and connect it.

2.You get 2nd screen, there on topright corner tap to settings near Disconnect, a popup will open shown in second image. select Refresh services. 3.and then again go to settings and select bond. Your screen would be like: 4. now your device is bonded, now goto settings "status:connected, bonded" tab, from popup select "enable services". 5. Goto Unknown Service. in that goto Unkwnown Characteristics with UUID 0000900a... ahead of it you will see a 2 icon of upload, tap on it. 6.this will look like: change "byte array" to "byte" write 01 to new value then send. again tap on it and again select byte and write "1". as decided above. written above in bold.

Now nrf will advertise as "DfuTarg".

Now use nrf toolbox for ota

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Thu, 03 Dec 2015 10:48:24 GMT

Yes, but not directly, because I just link with the code provided by Nordic Semiconductor. Bootloader is started when nRFTool at the phone side is requesting it. I followed the instructions from here to enable DFU for my application: developer.nordicsemi.com/.../a00081.html

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Thu, 03 Dec 2015 10:35:48 GMT

How do you enter in bootloader mode from application?? Is it using NRF_POWER->GPREGRET??

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

Jarmo — Thu, 03 Dec 2015 10:31:42 GMT

Yes, I added the indication function after noticing the system hangs up. So it's not definitely the cause of the problem. And the reset_prepare is in my application, as it needs to be.

RE: DFU: nRF51822 OTA bootloader jams after reset_prepare()

shubham — Thu, 03 Dec 2015 10:03:05 GMT

reset_prepare function is in application or in bootloader?