This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Converting gazell dynamic pairing library to SES

I am trying to use the gzp_dynamic_pairing example in SDK version 16 with Segger Embedded Studio and the PCA10040 dev board.  There is no project for SES so I copied what I could from the gzll_ack_payload project.  This consisted of the folder structure and two files, the Embedded Studio project file and the flash placement file.

Compilation if ok but there is a linker error.

1> Remove C:\nordic\examples\proprietary_rf\gzll\gzp_dynamic_pairing\host\pca10040\blank\ses\Output\gzll_dynamic_pairing_host_pca10040 Debug\Obj\gzll_dynamic_pairing_host_pca10040.ind
1> Remove C:\nordic\examples\proprietary_rf\gzll\gzp_dynamic_pairing\host\pca10040\blank\ses\Output\gzll_dynamic_pairing_host_pca10040 Debug\Obj\gzll_dynamic_pairing_host_pca10040.ld
1> Generating linker script ‘gzll_dynamic_pairing_host_pca10040.ld’
1> Linking gzll_dynamic_pairing_host_pca10040.elf
1> C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.52c/gcc/arm-none-eabi/bin/ld: Output/Debug/Exe/gzll_dynamic_pairing_host_pca10040.elf section `.gzll_paring' will not fit in region `UNPLACED_SECTIONS'
1> C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.52c/gcc/arm-none-eabi/bin/ld: region `UNPLACED_SECTIONS' overflowed by 4096 bytes
Build failed


I am concerned about the spelling typo for one thing.  It lists ".gzll_paring" but the word pairing is mis-spelled.

Is there a better process for adapting the project to Segger Embedded Studio than copying a similar project using the same library and same board?

Parents Reply Children
No Data
Related