sd_ble_enable causing hang if application is jumped to from bootloader

RE: sd_ble_enable causing hang if application is jumped to from bootloader

MichaelVPI — Tue, 12 Aug 2014 22:26:54 GMT

ONE MORE UPDATE: I later found that NVIC_SystemReset() isn't a good strategy since this should continuously boot you into the bootloader (I think) as opposed to the application. I found that calling JumpToApplication() works with no problems if, from the application, you initialize softdevice (using mbr_command) and set up the vector table directly after this.

I think this is because there is some initialization that has to happen in SD before calling sd_ble_enable(), and since this function sets the vector table's address to SD's vector table (maybe it's needed for initialization), you have to set it back to the application. Some of this was spelled out in the bootlaoder example code, I just wasn't sure if the same would apply to the application that the bootloader is jumping to.

So in other words, if the application is jumped to from the bootloader instead of directly from the mbr/SD, then the application also must initialize SD and set the vector table to the application vector table directly after.

RE: sd_ble_enable causing hang if application is jumped to from bootloader

John — Tue, 12 Aug 2014 12:36:30 GMT

Glad to hear you have it working.

RE: sd_ble_enable causing hang if application is jumped to from bootloader

MichaelVPI — Mon, 11 Aug 2014 21:31:57 GMT

UPDATE: I was able to get it to work by setting the vector table address to the start of SD 7.0.0 (0x1000) instead of the application and calling NVIC_SystemReset(). Thanks for the help!

RE: sd_ble_enable causing hang if application is jumped to from bootloader

MichaelVPI — Mon, 11 Aug 2014 17:48:00 GMT

I just tried NVIC_SystemReset() in place of JumpToApplication() with no success unfortunately.

RE: sd_ble_enable causing hang if application is jumped to from bootloader

John — Mon, 11 Aug 2014 14:29:16 GMT

I have not yet done the upgrade to use the SD 7.0.0 so I am not very familiar with the MBR stuff yet. However, after perusing the documentation a bit one line from the details section on the sd_mbr_command_vector_table_base_set_t caught my eye:

"Once this function has been called, this address is where the MBR will start to forward interrupts to after a reset."

So perhaps a reset is required rather than jumping to the application?