External target NRF51422 with BLE problems

[ShadowAdu]

Hello everyone,

I know that there are many similiar questions on the DevZone but i am not able to get it work and i dont uderstand it yet. 

For example: https://devzone.nordicsemi.com/f/nordic-q-a/24922/ble-example-not-working-on-external-target

I have similiar problem -  with BLE example on the NRF51422 processor (custom board). Namely, after uploading SoftDevice (s130 / s110), and uploading the program to launch Bluetooth (eg ble_app_template), I can not make a connection.

I would like to add that as a programmer I use nrf52 DK which contains the processor NRF52832 on which after uploading s132 and the above program, the connection was established without difficulty.

Below I put in a few screenshots showing the settings in Keil.

What can be the issue ?

[ShadowAdu]

Okey Jared,

I launched ble_app_blinky and SoftDevice S130 from the SDK11 packages.
I used "board_custom" with following LFCLKSRC:

#define NRF_CLOCK_LFCLKSRC      {.source       = NRF_CLOCK_LF_SRC_XTAL,            \
							    .rc_ctiv       = 0,                                \
							    .rc_temp_ctiv  = 0,                                \
							    .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM}

I chose the NRF51422_XXAB board in Keil, I set ROM1 (screen under the first post) and XTAL to 32 Mhz (For lower values, it does not turn on BLE).

After uploading the program, in nrfConnect i found the board as "n/a", and after clicking "Connect", it immediately breaks the connection.

Is there a problem with clock settings ?

[Jared]

The softdevice is enabled by the function call sd_ble_enable() in the softdevice_enable() call that is done in ble_stack_init(). One of the parameters that is passed to sd_ble_enable() is a pointer to the address that sets the amount of memory the ble stack needs. Could you run the program in debug mode and see what value &app_ram_base is pointing to? Also, could you print the err_code that is returned from sd_ ble_enable()?

[ShadowAdu]

I hope I have read your instructions correctly.
app_ram_base(0x0001CB44 ) and err_code(0x0001CB46). (screen)

In memory view (decimal):
0x0001CB44 = 001
0x0001CB46 = 000

[Jared]

Hi. Sorry for the late response. It doesn't seem that you have turned off optimizations while debugging. You should redo it with optimizations turned off. Check this post for more info regarding optimizations: You can also try to change the IRAM1 configuration to:

START:0x20002080

SIZE: 0x5F80

Best regards

Jared