Linker file wrong on new V15 IAR SDK for nrf52810 projects

[mjkranz]

Noted that the new V15 SDK for IAR does not have linker config file set correctly on ble_app_blinky_pca10040e_s112 project. The .intvec start location was set to 0x19000 and the memory regions were not correct. Setting .intvec to 0x18000 and rom start to the same at least allowed a debug session to start. The heap and stack sizes are probably also too large for this chip I set mine to 800 and 200 respectively. You still get a hard reset error because the start of your ram is wrong also as it is too small and set to 0x20001c18. I set it to 0x20002000 to give the softdevice enough room but has anyone calculated the real value.

[Vidar Berg]

Hi,

Correct start address should be 0x19000. Are you using s112 v.6.0.0, which is included in SDK 15 (\components\softdevice\s112\hex)? 

[phlb]

hello!

Is there the same problem with s132 soft device (s132_nrf52_5.1.0) and SDK15 ? My application (based on HRS example) not start? In IAR link file the following address is set:

/*-Specials-*/
define symbol __ICFEDIT_intvec_start__ = 0x26000;
/*-Memory Regions-*/
define symbol __ICFEDIT_region_ROM_start__ = 0x26000;
define symbol __ICFEDIT_region_ROM_end__ = 0x7ffff;
define symbol __ICFEDIT_region_RAM_start__ = 0x20002b90;
define symbol __ICFEDIT_region_RAM_end__ = 0x2000ffff;
export symbol __ICFEDIT_region_RAM_start__;
export symbol __ICFEDIT_region_RAM_end__;

Regards, 

[phlb]

When I set with the following values: define symbol __ICFEDIT_intvec_start__ = 0x26000 to 0x23000 and define symbol __ICFEDIT_region_ROM_start__ = 0x23000;

it works (it started, but I still have some issues in init phase at app level).

I replaced s132 nrf52 v5.1.0 with v 6.0.0. and restore previous values in IAR link file, and the application not started. 

[Vidar Berg]

Hello, SDK 15 supports s132 v6.x.x and is not API compatible with version 5.  0x26000 is the correct start address.  

I'd suggest to compare you project configuration with the HRS reference example from SDK 15.0.0, and make sure that you are using s132 v.6.0.0. Have you migrated your project from SDK 14?