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]

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.

[Wasil]

I just put the blinky right at the top of my main() and it works. Now what that would be?

[Wasil]

i have put blinky in while(1) therefore size of my file is much smaller around 6k

[Hung Bui]

Next step is to try stepping into the code and check why it doesn't work. I assume your app works fine without the bootloader ? 

You can try to add a break point in your main() (test first with the blinky modified code you have, then test again with the blinky part removed). Just debug it as normal application. If the bootloader works as it should, you should be able to step into the code. Make sure you removed code optimization. 

[Wasil]

Correct app works fine without dfu bootloader. 

I have noticed that it stuck after sd_power_dcdc_mode_set. 

It works when I comment dcdc_mode. Then when I move blinky code further down it then stuck to  sd_power_reset_reason_clr(0xffffffff); 

I have also commented out sd_power_reset_reason_clr(0xffffffff); And then app stuck in ble_ant_stack_init(). 

without dfu bootloader application works 100%.

Looks like dfu bootloader preventing bluetooth and ANT+ to start?

[Wasil]

Hi Hung

  Any thoughts?

[Hung Bui]

Hi Stark, 

I don't see any softdevice enable before sd_power_dcdc_mode_set(). You can't call softdevice API before you enable the softdevice. 

I attached here the ble_app_hrs for S332 (unmodified from the SDK). Please try using the bootloader I sent you earlier. It worked fine here for me. 

package_hrs.zip

[Wasil]

I have just checked your package file and bootloader. It uploads package OTA but then I see it stuck. LED stays on all the time also cannot find on nrf connect app :-(

[Wasil]

((I don't see any softdevice enable before sd_power_dcdc_mode_set(). You can't call softdevice API before you enable the softdevice)..... how to enable it? I thought preprocessor directives enabling it. )

I know what you mean now. 

it stuck in SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL); routine. I have check the XTAL settings and it looks fine to me.