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]

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. 

[Wasil]

You are correct.  FS_PAGE_END_ADDR was 0x80000. So I have moved it to away from bootloader region. Its working ok. Thanks For your help. 

Also for bottonless dfu for sdk12 I have read your blog and just want  to confirm when setting GPREGRET register and after soft restart, do I need to read same register in bootloader dfu aswell? 

[Hung Bui]

I'm glad that it worked for you. 

In my blog I wrote: 

Note that on SDK v12 we write to bootloader setting, instead of write to GPREGRET register. I think writing to GPREGRET is a cleaner way of doing this.

In SDK 13 we used GPREGRET not in SDK v12 (in SDK 12 we write to bootloader setting in flash). But if you want to use GPREGRET instead, it's not too hard to modify the bootloader code to check for that, please have a look at  nrf_dfu_enter_check() function in nrf_dfu.c 

[Wasil]

When I write 0x01 to GPREGRET register and do NVIC_SystemReset(); It restarts from the app again.

(WDT is enabled during this process) 

[Wasil]

Hi Hung,

           It does get in to dfu loader. I have confirmed this by blinking LEDs in DFU. I have made the changes to check GPREGRET but it is not reading GPREGRET. 

[Wasil]

i have noticed that when I restart the device it then restart again due to WDT enabled in app. So I have enabled it in DFU. After restarting back to dfu it won't do the serial printing on RTT. Any idea?