DFU not working on S332 2.0 SDK12 . Help me setting Target IROM1 and IRAM1?

[Wasil]

Hi 

   I am trying to implement DFU to my project. I have done all the steps to generate packages,  private and public keys etc. My program now starts at dfu and I can upload the package to nrf52 but it then get stuck to (Jump to 0x0029000).

Can anyone help me target setting on keil? Thanks

 

[Hung Bui]

Hi Stark,

Could you try to test updating an example in our SDK (you need to configure it so it works with S332) instead of your application, just to make sure that DFU works properly ?  You can also start with testing with a simple application to blink an LED. 

I assume your app works if you don't flash the bootloader ? 

[Wasil]

Hi Hung,

             I got successful in running dfu on s132 but struggling on s332. I think its IROM1 and IRAM1 settings for dfu bootloader. Currently settings are

IROM1: 0x75000 and size: 0xB000

IRAM1: 0x20002E00 and size: 0xD370 

I am working on nrf52832 512k chip. 

Is there any way to find out the correct IRAM1?

[Wasil]

Hi Hung, Did you get a chance checking files I sent you?

[Hung Bui]

Hi Stark, 

I have been testing here and actually found a bug in the bootloader (after 4 hours :( ). We used wrong size of data when doing nrf_dfu_flash_store() inside nrf_dfu_app_continue() in nrf_dfu_utils.c. It should be like this: 

ret_val = nrf_dfu_flash_store((uint32_t*)target_addr, (uint32_t*)src_addr, cur_len/sizeof(uint32_t), NULL);

It may not be related to the issue you are having now, but it's worth to try again. 

Could you please do the same test (reading out hex files) with the following images. Please flash the softdevice and bootloader that's included in this .zip file and update blinky and then update hrs. 

0572.DFU_TEST.zip

[Wasil]

Thanks for your time Hung. Much appreciated.

I have attached the tests for you. Also I have tried my app on this SD + bootloader and it actually initialise the ble and ant but it restarted after pStorage init and then jump back to dfu bootloader. Definitely improvement :-)

New blinky package works fine and when I restart the device it jump straight to app again unlike before it start again from dfu bootloader.

New hrs package didn't work.

test1-1.zip

[Wasil]

Hi I have just checked the hrs_package again and its running ok. I have attached the flash read for this again. Both Packages you sent working ok. 

test3-1.hex

[Hung Bui]

Glad to hear Wasil, this meant a normal application should work fine. 

Could you try to update one of the application (for S332) in the SDK with your own bootloader ?  (with the fix I proposed)

Or you can use the image of the hrs example that I attached here. 

If that works with your bootloader we would need to look into your application to check why it crashed at pstorage init. 

Do you do any flash operation that modify the application firmware ? Can you step into the code and check why pstorage init crashed ?

If you can't get to pstorage init and it's stuck at DFU bootloader, you can check and send me the RTT log of the bootloader. 

[Wasil]

If I use fresh sdk12 just for bootloader and current one for my app, you think that would help?  

[Hung Bui]

Hi Wasil, 

Yes, you can do that. But it's better to figure out what caused the issue.

In addition, even with my bootloader you still can't update your application ? You can try to debug your application (with the bootloader ) and check what throwing the error.  

[Wasil]

Hi Hung,

I have changed the target settings of app and now its running ok. 

One thing I have noticed that when I restart my device it start from dfu again. (I am using your bootloader and when I restart hrs or blink app then it start at app not dfu) This shows some thing is missing in my app. Where should I look at? Thanks

[Wasil]

I did try the memory read and got different number. 

nrfjprog -f nrf52 --memrd 0x7f020
Got: 

Expected: 0x0007F020: 00000001                              |....|

[Hung Bui]

In your app do you have any flash operation ? 

It looks like you are editing the bootloader setting page in your app. 

Please make sure fstorage has the location of flash located bellow the bootloader. This is defined in FS_PAGE_END_ADDR that we used in fs_init(). To make sure the if we have a bootloader we relocated the flash area for application under the bootloader, not to mess up with the bootloader data.