Peer Manager and GCC

[Andrew]

I have attempted to migrate over a couple of nRF52 projects built around device manager to the new peer manager in SDK 11 that are built with eclipse and GCC. However, I am seeing the exact same behavior after each attempt. I am following the migration tutorial and everything to builds just fine but running in debug shows the application getting hung up at flash address 0x10 and disassembly shows the following:

          fs_config:
00000000:   beq.n   0xee
00000002:   movs    r1, r0
00000004:   movs    r0, r0
00000006:   movs    r0, r0
00000008:   movs    r0, r0
0000000a:   movs    r0, r0
0000000c:   movs    r3, r0
0000000e:   movs    r0, r0
00000010:           ; <UNDEFINED> instruction: 0xffffffff

The undefined instruction continues until address 0x1000, or one block of flash.

I also tried creating a new project around the example relay project that uses the peer manager but again, same result.

It seems that the fs_config is ignoring the flash start address in the linker script is wiping out the Softdevice flash for storage space (this is just a guess). I'm not sure how to fix this quickly or correctly.

[Håkon Alseth]

Hi,

EDIT : This shall be fixed from nRF5_SDK_11.0.0_89a8197 and upwards

Fix for nRF5_SDK_11 alpha:

Had to re-order our common linker file, and for now; everything is included into one .ld file, due to ordering of the .data/.fs_data/.bss sections for initialization.

ble_app_hrs_rscs_relay_gcc_nrf52.ld

sector_vars.h

Best regards, Håkon

[Håkon Alseth]

Hi Andrew, I've edited my response for a proper workaround. I was able to connect and run the example properly now.

Cheers, Håkon