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]

You are right. I have comment it out for now. Also when I select MicroLib under Target (keil) for my application then dfu counter display jumping to 0x0029000 and when I unselect microLib then it jumps to "Dbg("After real nrf_dfu_init\r\n");" .Should it be checked? it was originally unchecked. 

[Hung Bui]

I don't think unchecked it would cause a problem. But as in most of our examples, we use MicroLib. Have you managed to update a minimum application, for example blinking LED  ?

[Wasil]

I did try blinking LED and same result. Do I need to do any clock settings?

[Wasil]

Also do you have any working example on SDk12 S332v2.0 that I can get hold of?

[Hung Bui]

Have you made sure when you build the .zip file you choose the correct sd_req code ? for s332_nrf52_2.0.1 it is 0x8E

Also made sure you have changed the bootloader so that it use the S332 header files, not the S132 header files. 

I attached here the public, private keys, the bootloader project and the .zip package file that you can test. It's tested on SDK v12.3 S332 v2.0.1.

The application to update is simply a blinky example (not the BLE one)

07Mar.zip

[Wasil]

just to confirm size of bootloader package after compile is roughly 34k?

[Wasil]

I have tried the version you sent me. its working ok

I then tried my application (created new public and private keys etc) and generated the dfu package but its not working. For creating dfu package I have used the following command:

nrfutil pkg generate --hw-version 52 --application-version 1 --application nrf52832_xxaa.hex --sd-req 0x8E --key-file private.key dkm_fast.zip

Is this correct?

[Wasil]

It looks like after dfu upload the start address of application is not correct. I can see it says Jumping to : 0x0029000 but it stuck right there. It is not even entering in to "nrf_bootloader_app_start(uint32_t start_addr)" routine. 

[Wasil]

When I upload blinky example it works fine and when I upload my app it just stuck just before calling routine (nrf_bootloader_app_start(uint32_t start_addr). I think it could be start address is not 0x0029000? or clock settings or target settings(screenshot below)?

[Hung Bui]

I'm not sure it would stuck at nrf_bootloader_app_start(). The bootloader treat your application and the blinky application exactly the same. I assume the blinky application you also set the start address to 0x29000 ? 

If you step into bootloader code and step the function nrf_bootloader_app_start() what do you have  ? 

You can also try to put a break point at the beginning of your application to see if it jumped there. 

You can try to modify your application to do blinky, just to test if the bootloader actually jumped to application.