Porting S130 bootloader to NRF51822

RE: Porting S130 bootloader to NRF51822

bjorn-spockeli — Thu, 22 Sep 2016 12:48:45 GMT

You could also try using nrfjprog to program the chip. If you're nt able to program the chip with nrfjprog, then you can try to recover the chip using nrfjprog --recover.

RE: Porting S130 bootloader to NRF51822

Roger Clark — Wed, 21 Sep 2016 10:35:45 GMT

Is the MCU locked ?

See www.rogerclark.net/.../

RE: Porting S130 bootloader to NRF51822

Andy — Wed, 21 Sep 2016 10:30:07 GMT

When I try to download the code I get:

Failed to prepare for programming.
Failed to download RAMCode!

RE: Porting S130 bootloader to NRF51822

Andy — Wed, 21 Sep 2016 10:19:41 GMT

I'm currently using a JLink programmer and I download the code using JLinkExe. However, when I try to download the code onto the board it just doesn't download. And yes, my board has an external 32.768kHz crystal.

RE: Porting S130 bootloader to NRF51822

Vidar Berg — Wed, 21 Sep 2016 10:14:07 GMT

Please try to call 'nrfjprog --readregs' while the bootloader is running and post the output in order to confirm that the hardfault exception hasn't been triggered.

Also, does your board have a LF crystal like the dev boards? If not you will need to change the clock source to the internal RC in the stack init routine.

RE: Porting S130 bootloader to NRF51822

Andy — Wed, 21 Sep 2016 10:03:10 GMT

Ok, thanks. I did that but I still cannot download the .bin to the board. It just gets stuck there... Any idea what could be happening?

RE: Porting S130 bootloader to NRF51822

Vidar Berg — Wed, 21 Sep 2016 09:55:26 GMT

As Roger said, you need to adjust the linker settings to limit RAM usage to the 16K boundary. The linker file (*.ld) is located in the bootloader directory and can be changed as follows:

/** RAM Region for bootloader. This setting is suitable when used with s110, s120, s130, s310. */
RAM (rwx) :  ORIGIN = 0x20002C00, LENGTH = 0x1380

/** Location of non initialized RAM. Non initialized RAM is used for exchanging bond information
*  from application to bootloader when using buttonluss DFU OTA. 
*/
NOINIT (rwx) :  ORIGIN = 0x20003F80, LENGTH = 0x80

RE: Porting S130 bootloader to NRF51822

Andy — Wed, 21 Sep 2016 09:55:10 GMT

This is what I see in the linker file (some comments removed):

MEMORY
{
  FLASH (rx) : ORIGIN = 0x3C000, LENGTH = 0x3C00

  /** RAM Region for bootloader. This setting is suitable when used with s110, s120, s130, s310. */
  RAM (rwx) :  ORIGIN = 0x20002C00, LENGTH = 0x5380

  /** Location of non initialized RAM. Non initialized RAM is used for exchanging bond information
   *  from application to bootloader when using buttonluss DFU OTA. 
   */
  NOINIT (rwx) :  ORIGIN = 0x20007F80, LENGTH = 0x80
  BOOTLOADER_SETTINGS (rw) : ORIGIN = 0x0003FC00, LENGTH = 0x0400
  UICR_BOOTLOADER (r) : ORIGIN = 0x10001014, LENGTH = 0x04
}

RE: Porting S130 bootloader to NRF51822

Roger Clark — Wed, 21 Sep 2016 09:43:50 GMT

QFAA has 16k less RAM than the QFAC, so normally you need to change the RAM size setting in the linker and reduce it by 0x4000

However I don't know what value IRAM is in your linker file.