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

Keil 4 to Kiel 5 upgrade

I am rebuilding my computer after experiencing a corrupt boot sector and am reinstalling all my apps.  I am moving from Kiel 4 to Kiel 5.  My project loads, but it says that it needs the ARM Tool chain which is not installed. I installed the Toolchain on WIN 10 and it seemed to install smoothly, however in the Project menu, the Options menu item and those below it are all disabled.  Can you guide me through this? 

I notice in the readme.txt in * Architecture options usage * there is a considerable amount ot config options, is this a necessary requirement for the nRF51422 ?  

Thanks,

Brian Fleming

  • Thank you again for your continuing support!

    I copied and pasted the Processor Symbols/Define and the Include Paths from the nrf51422_xxac to the soft device C/C++ and now I am seeing this error:

    Rebuild started: Project: ble_app_uart_pca10028_s130
    *** Using Compiler 'V5.06 update 6 (build 750)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'
    Rebuild target 'flash_s130_nrf51_2.0.1_softdevice'
    compiling main.c...
    linking...
    ..\..\..\..\..\..\components\softdevice\s130\hex\s130_nrf51_2.0.1_softdevice.sct(7): error: L6236E: No section matches selector - no section to be FIRST/LAST.
    Not enough information to list image symbols.
    Not enough information to list load addresses in the image map.
    Finished: 2 information, 0 warning and 1 error messages.
    "..\..\..\..\..\..\components\softdevice\s130\hex\s130_nrf51_2.0.1_softdevice.hex" - 1 Error(s), 0 Warning(s).

  • Hi Brian,

    Did you add startup files, arm_startup_nrf51.s and system_nrf51.c? You can add them into the Device (green) folder under the project or go through Project > Manage > Run Time Environment. 

    You also could try the suggestion in this thread

    --

    You should in general always use the softdevice that comes with the sdk version you are using (check the folder: nRF5_SDK_12.3.0_d7731ad\components\softdevice\s130\hex). You never want to compile the softdevice. 

    If you go back to the softdevice hex file folder, you notice that the softdevice hex file has become a Windows Script component now. Delete all the files that were created in that folder, download the correct softdevice hex file & put it back in that folder.

    Here is a link to the correct softdevice needed:

    s130_nrf51_2.0.1_softdevice.hex

    Once you have done this, erase the nrf51 chip, program the chip with the softdevice hex file (Flash -> Download tab or press F8 instead of F7) & then go back to the application & flash the program to the nrf51.

    -Amanda H.

  • For your first paragraph, the files you described were there.

    Second paragraph, I saved (and deleted) the files in a sub-folder, and copied the .hex file from a backup and placed it in the hex folder.  I can now upload the soft device and the main app to the nRF51 Development Kit and it seems to work.

    Thanks for the tip about not compiling the soft device.

    I think everything has been resolved.

    Thanks, 

    Brian Fleming

  • Hi Brian,

    Good to hear the success and happy to support this case.

    Please kindly verify the answers as the solutions. Thanks.

    -Amanda H.

Related