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

The ARM Linker has stopped working

Hi

I am trying the nRF51822 Evaluation Kit for the first time. I have followed the instructions in the User Guide v1.1. The blinky_example works fine, indicating that the tool-chain should be in place. But, when I am trying to build the heart-rate monitor example, the Linker crashes and I get the Build Output window I get a message:

Build target 'nrf51822_xxaa_s110 (256K)' compiling ble_conn_params.c... compiling ble_stack_handler.c... linking... ._build\ble_app_hrs.axf: error: L6002U: Could not open file ._build\ble_conn_params.o: No such file or directory "._build\ble_app_hrs.axf" - 1 Errors, 0 Warning(s). Target not created

I have not yet installed the PCA-10000 dongle. Below I have pasted in the information from the IDE (I am using Windows8-x64). Any suggestion to how I can proceed?

IDE-Version: µVision V4.72.10.0 Copyright (C) 2013 ARM Ltd and ARM Germany GmbH. All rights reserved.

License Information: Arne Laugstol Sharp Software AS LIC=----

Tool Version Numbers: Toolchain: MDK-Lite Version: 4.72.1.0 Toolchain Path: C:\Keil\ARM\ARMCC\bin
C Compiler: Armcc.Exe V5.03.0.76 [Evaluation] Assembler: Armasm.Exe V5.03.0.76 [Evaluation] Linker/Locator: ArmLink.Exe V5.03.0.76 [Evaluation] Librarian: ArmAr.Exe V5.03.0.76 [Evaluation] Hex Converter: FromElf.Exe V5.03.0.76 [Evaluation] CPU DLL: SARMCM3.DLL V4.72.1.0 Dialog DLL: DARMCM1.DLL V1.11.00.0 Target DLL: Segger\JL2CM3.dll Dialog DLL: TARMCM1.DLL V1.08.00.0

Parents
  • I have updated to the same version that you are running, but I cannot reproduce this on my computer. Checking the KEil forums, it seems that there are other people that have this issue, but no obvious fix has been posted to any of the threads I looked at.

    Can you please .zip the ble_app_hrs project so I can run it on my computer?

    Best regards Håkon

  • I used the exact same version as you have. Have you tried re-installing and choosing "custom install path" (or similar), so that the installation is located in c:\nordic semiconductor? (default) Just in case that the SDK inside keil-path is somehow an older version of the SDK.

    IDE-Version: µVision V4.72.10.0 Copyright (C) 2013 ARM Ltd and ARM Germany GmbH. All rights reserved.

    Tool Version Numbers: Toolchain: MDK-ARM Professional Version: 4.72.1.0 Toolchain Path: C:\Keil\ARM\ARMCC\bin
    C Compiler: Armcc.Exe V5.03.0.76 Assembler: Armasm.Exe V5.03.0.76 Linker/Locator: ArmLink.Exe V5.03.0.76 Librarian: ArmAr.Exe V5.03.0.76 Hex Converter: FromElf.Exe V5.03.0.76
    Target DLL: Segger\JL2CM3.dll Dialog DLL: TARMCM1.DLL V1.08.00.0

Reply
  • I used the exact same version as you have. Have you tried re-installing and choosing "custom install path" (or similar), so that the installation is located in c:\nordic semiconductor? (default) Just in case that the SDK inside keil-path is somehow an older version of the SDK.

    IDE-Version: µVision V4.72.10.0 Copyright (C) 2013 ARM Ltd and ARM Germany GmbH. All rights reserved.

    Tool Version Numbers: Toolchain: MDK-ARM Professional Version: 4.72.1.0 Toolchain Path: C:\Keil\ARM\ARMCC\bin
    C Compiler: Armcc.Exe V5.03.0.76 Assembler: Armasm.Exe V5.03.0.76 Linker/Locator: ArmLink.Exe V5.03.0.76 Librarian: ArmAr.Exe V5.03.0.76 Hex Converter: FromElf.Exe V5.03.0.76
    Target DLL: Segger\JL2CM3.dll Dialog DLL: TARMCM1.DLL V1.08.00.0

Children
No Data
Related