• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 62 subscribers
  • Views 1669 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 127419
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

eddystone example link error due to code size

nezhad

I am trying to use the eddystone example I found in the ble_prepheral/ble_app_eddystone/pca10040 folder in SDK14.2 with my nRF52832 development board but I get the following link error.

._build\nrf52832_xxaa.axf: error: L6050U: The code size of this image (36056 bytes) exceeds the maximum allowed for this version of the linker.

What do I need to do? Upgrade the linker? How? Thanks

Parents
  • 0

    Thank you Sigurd. Segger successfully built the project. How do I download to the board though? It was so easy in Keil but in Segger I am a little confused. I see "Download file" option under Target menue but then there are multiple options for Elf, binary and Hex files but none of them find any files in the Win2k, x64 or x86 folders under USBDrivers or in the codecs.

    Update: When I try ""Build and Run", it complains that ...\nRF_SDK14\components\softdevice\s132\hex\s132_nrf52_5.0.0_softdevice.hex does not exist when in fact it does. New Update: I managed to locate and download the hex file from ..\nRF_SDK14\examples\ble_peripheral\ble_app_eddystone\pca10040\s132\ses\Output\Debug\Exe\ble_app_eddystone_pca10040_s132.hex and now I have an Eddystone beacon:)

Reply
  • 0

    Thank you Sigurd. Segger successfully built the project. How do I download to the board though? It was so easy in Keil but in Segger I am a little confused. I see "Download file" option under Target menue but then there are multiple options for Elf, binary and Hex files but none of them find any files in the Win2k, x64 or x86 folders under USBDrivers or in the codecs.

    Update: When I try ""Build and Run", it complains that ...\nRF_SDK14\components\softdevice\s132\hex\s132_nrf52_5.0.0_softdevice.hex does not exist when in fact it does. New Update: I managed to locate and download the hex file from ..\nRF_SDK14\examples\ble_peripheral\ble_app_eddystone\pca10040\s132\ses\Output\Debug\Exe\ble_app_eddystone_pca10040_s132.hex and now I have an Eddystone beacon:)

Children
No Data
Related