NRF52832-QFAB-R loader script

[sboudaud]

Hello,
I modified the ble_app_blinky example to work on our board (removed leds and buttons) and modified the board pca10040.h
the new application worked on the devkit but not in our board.
As the chip in the devkit is not the same used on our board (NRF52832-QFAB-R) is there any thing that I need to modify? like ble_app_blinky_gcc_nrf52.ld?

Thanks.

[Edvin]

Hello,

You should probably adjust the memory settings to match the chip variant that you have. Check this table:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcomp_matrix_nrf52832%2FCOMP%2Fnrf52832%2Fic_revision_overview.html

So if your device has 256kb/32kB Flash/RAM, you need to change the ble_app_blinky_gcc_nrf52.ld

Now it probably says something like:

FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0x5a000
RAM (rwx) : ORIGIN = 0x20002a98, LENGTH = 0xd568

This means that the application can use:

The flash from address 0x26000 to 0x80000 ( = 0x26000+0x5a000)

The RAM from address 0x2000 2a98 to 0x2001 0000.

The Flash is mapped from 0x00000000 to 0x0008 0000, and the RAM is mapped from 0x2000 0000 to 0x2001 0000. on the 512/64 kB devices.

The reason the origins are not on 0x0000 0000 and 0x2000 0000 is because some of it is reserved for the softdevice. 

On the 256/32 kB version, the Flash is mapped from 0x0000 0000 to 0x0004 0000, and the RAM from 0x2000 0000 to 0x2000 8000.

So adjust the LENGTH so that ORIGIN + LENGTH equals 0x40000 in Flash and 0x2000 8000 in RAM.

Now, this is probably not the issue that you see in ble_app_blinky, because this application doesn't use particularly much flash or RAM.

What you probably will see is if you run e.g. the blinky example from SDK\examples\peripheral\blinky, it will work, but the examples from SDK\examples\ble_peripheral will not work. If that is the case, it is probably because your custom board doesn't have an external LFXTAL. Do you have that? If you don't have it, you need to set the softdevice to use the RC Oscillator instead of the external XTAL. I don't know what SDK you use, but in SDK15.3.0, look for NRF_SDH_CLOCK_LF_SRC, and set it to 0. There are some more defines you should adjust. You can start with these:

#define NRF_SDH_CLOCK_LF_SRC 0
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#define NRF_SDH_CLOCK_LF_ACCURACY 1

Try these configs, and see if you can see the advertisements. If not, have you tried debugging the application on the custom PCB?

Best regards,

Edvin

[sboudaud]

I tried to debug the app with ozone but the connection fail, I'm using leopard geko EFM32 development kit to connect to the BLE.