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

No Software PAcks visible in uVision 5 for nRF52840 (nrf52832)

When trying to build/run the btle throughput demo I get a device not supported error.

When looking in the Options - Device settings for

the project the Software Packs dropdown is greyed out and Vendor, Device and Toolset are set as unknown.

image description

Running uVision V5.24.2.0 
Installed SDK 8.14.1 
Installed Softdevice to dev board 
Can find Nordic devices in File Device Database

image description

If I load other projects in for other devices (e.g. STM32) everything is fine and I can select the device type.


It also shows up in the Pack Installer.

What have I missed??

I've seen issues raised for similar problems but I've tried all the suggested installations of 
SDKs, MDKs and the like and have got nowhere. I'm sure this will be something small. Well I 
hope so.




/** Project  **********************************************************/

"C:\Projects\NORDIC\nrf528xx-ble-throughput-demo-master\ble_app_att_mtu_throughput\pca10056\s140\arm5_no_packs\ble_app_att_mtu_throughput_pca10040_s132.uvprojx"

/**  Error  ************************************************************/

Error: *** Project 'ble_app_att_mtu_throughput_pca10040_s132', Target 'nrf52832_xxaa', Device 'Nordic Semiconductor::nRF52832_xxAA' is not supported by Toolchain ! ***.

/**  uVision  ***************************************************/

IDE-Version:

µVision V5.24.2.0

Copyright (C) 2017 ARM Ltd and ARM Germany GmbH. All rights reserved.





Tool Version Numbers:

Toolchain:        MDK-ARM Cortex-M0/M0+ 256K for ST  Version: 5.24.1

Toolchain Path:    C:\Keil_v5\ARM\ARMCC\Bin

C Compiler:         Armcc.exe        V5.06 update 5 (build 528)

Assembler:          Armasm.exe        V5.06 update 5 (build 528)

Linker/Locator:     ArmLink.exe        V5.06 update 5 (build 528)

Library Manager:    ArmAr.exe        V5.06 update 5 (build 528)

Hex Converter:      FromElf.exe        V5.06 update 5 (build 528)

CPU DLL:               SARMCM3.DLL          V5.24.1

Dialog DLL:         DARMCM1.DLL          V1.18.0.0

Target DLL:             STLink\ST-LINKIII-KEIL_SWO.dll      V3.0.1.0

Dialog DLL:         TARMCM1.DLL          V1.13.0.0


/**  nRF_DeviceFamilyPack  *************************************/

NordicSemiconductor.nRF_DeviceFamilyPack.8.14.1.pack

"C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_DeviceFamilyPack\8.14.1\Device\Source\system_nrf52840.c"

/**  Soft Device  **********************************************/

s140_nrf52840_5.0.0-2.alpha_softdevice.hex

"C:\Projects\NORDIC\nRF5_SDK_14.0.0_3bcc1f7\components\softdevice\s140\hex\s140_nrf52840_5.0.0-2.alpha_softdevice.hex"

/**  Pack Installer  **********************************************/

image description

  • Hi,

    Please download and install the nRF5x Command line tools version 9.7.0 from here, this installer includes the Segger J-Link Software Pack v6.20b.

    Then download SDK 14.0 from here. Unzip, and find the project in the unzipped folder.

    For nRF52832 it will be in the folder SDK_14_folder\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput\pca10040\s132\arm5_no_packs

    For nRF52840 it will be in the folder SDK_14_folder\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput\pca10056\s140\arm5_no_packs

    Also note that CMSIS Pack is deprecated. See this blog post about that.

  • Hi, Thanks for the response.

    I'd already downloaded and installed the latest Command Line Tools and SDK as prompted by other support questions.

    I opened the project as suggested in uVision5 and still have the same issue. "C:\Projects\NORDIC\nRF5_SDK_14.0.0_3bcc1f7\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput\pca10056\s140\arm5_no_packs\ble_app_att_mtu_throughput_pca10056_s140.uvprojx"

    image description

    image description

    image description

    -- UPDATE ----------------------------

    Just for completeness, I decided to follow the suggested installation on my spare Win7 PC.

    I downloaded and installed:

    • MDK524a.EXE
    • nRF5x-Command-Line-Tools_9_7_0_Installer.exe
    • nRF5_SDK_14.0.0_3bcc1f7.zip

    I then opened the throughput project "ble_app_att_mtu_throughput_pca10056_s140.uvprojx" and followed the extra update/installation steps required:

    image description

    image description

    image description

    And lo' the options were there. image description

    BUT ... the build file was too large "._build\nrf52840_xxaa.axf: error: L6050U: The code size of this image (35492 bytes) exceeds the maximum allowed for this version of the linker."

    So ... I registered my product and entered the LIC code

    And ... now I'm back were I was with no option for selecting the device type. "Error: *** Project 'ble_app_att_mtu_throughput_pca10056_s140', Target 'nrf52840_xxaa', Device 'Nordic Semiconductor::nRF52840_xxAA' is not supported by Toolchain ! ***." image description

    Somehow, registering the product has had a negative effect on selecting the device for that project.

    I don't understand how this could have happened.

    Anyone any ideas?

  • Hi,

    Keil have a 32KB code limit, so with a free license you can't compile projects bigger than 32 kB. Looks like you are getting a license that only support Cortex M0 devices, did you sign up for a license here?

    You could test the example by simply flashing the pre-compiled hex found in the folder SDK_folder\examples\ble_central_and_peripheral\experimental\ble_app_att_mtu_throughput\hex. For nRF52840 use the hex file called ble_app_att_mtu_throughput_pca10056_s140.hex.

    Since Keil have this 32KB limit, I would recommend using Segger Embedded Studio instead. You can find a blog post here on how to convert a Keil project to a Segger Embedded Studio Project.

    Let me know if you need me to create the Segger Embedded Studio project for you.

  • Thanks. I had the same thought about the M4 core during my lunchtime walk. didn't realise the hex file was already embedded within the zip so that is a great help. I'll load it in. Looks like I'll have to purchase a Keil licence for development though. *Would flag your answer as "accepted" if I knew how.

  • You can press the grey check mark under the arrows to accepted the answer.

    Again, I would strongly recommend trying out Segger Embedded Studio before buying a Keil license.

Related