Using nRF52DK with custom board 51822

[Glenn]

Hi, would like to know if anyone has some experience and advise how to get an external 51822 based board programmed and working via the nRF52DK. All the wiring works, I can flash the softdevice but compiling SDK examples are a struggle. I'm importing the SDK beacon example into Segger Studio, defined a custom board to which I reference in the preprocessor definitions, also indicated it's a 51822, deleted the arm startup file and replaced it with ses_nrf51_startup and also added system_nrf51 as internal files, imported the flash_placement file and set the correct FLASH_START/SRAM_START adresses etc. When I debug I get a 'Stopped by vector catch'. Is there anything obvious I overlooked or can anyone point me into some direction ? THANKS !

[FormerMember]

For setting up the project, did you follow this blog post?

Raphael found a solution to the "Stopped by vector catch" problem in an older version the blog (here):

Found a solution for the "Stopped by vector catch" problem. Apparently I was using the wrong flash and RAM starts

Setting the Section Placement Macros to FLASH_START=0x1b000 RAM_START=0x20001f00 based on the linker file included in the armgcc directory worked for me.

Note that I was using S130 with PCA10028 and SDK v11-alpha2. I did not change the flash_placement.xml. I believe the start values for flash and RAM there should remain what they are and not be the same as the section placement macros, i.e. not factor in the SoftDevice. Correct me if I am wrong, but that is what I used and it worked for me.

[Glenn]

Thanks Kristin, yes, I must have read that tutorial at least a hundred times :) It's a very important reference when getting started with SES. I noticed that Raphael's reference to section placement is "RAM_START" while the tutorial correctly refers to SRAM_START. I got my section info from the SDK example ARMGCC folder (.ld) file and used exactly that as it should be I guess, origin 0x1b000 for FLASH and 0x20001870 for SRAM.

[FormerMember]

Yes, I would think that "RAM_START" actually should be "SRAM_START". Did you were able to get rid of the error?