• State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 72 subscribers
  • Views 9635 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 240800
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
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

MDK uVision SDK 16.0 keil Family Pack Installation

Andrew_Engineer

hello,

we are in process migrating to SDK 16.0 and service pack 8.27 or higher. While performing an upgrade we encourage few problems and would like you expert advise.

We have upgrade Keil MDK uVision to V5.29 version,

We also installed all the latest service packs such as V8.27.1 V8.28 V8.29.

Once we try to open any of the example projects we are getting follow message:

Once we click "Yes" Leil pack installer starting .

In Keil pack Installer we already have all the latest service packs:

Now , when Keil pack installer is starting up we getting follow error message

Obviously pack installer is looking for "NordicSimiconductornRF_DeviceFamilyPack_NordicLicense"

"Nordic License " is bit confusing and we are not sure how to address  this. While searching over the devzone we find two similar 

 posts:

https://devzone.nordicsemi.com/f/nordic-q-a/54703/cannot-install-pack-nordicsemiconductor-nrf_devicefamilypack_nordiclicense-8-27-0-pack-not-found

and

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf5-sdk-v-16-0-flashing-nrf52833-in-keil-uvision

We tried recommendations from both topics but it didnt help.

Could you please advise what would be appropriate way to address this problem.

Thank you,

Andrew.

  • +2

    Hi,

    Update:

    Workaround for updating MDK in Keil 5 project based on nRF5 SDK 16.0.0 and earlier

    After updating to the new version of MDK (Device Familty Pack) a project fails to compile. The reason for that is that project contains include paths to MDK within current SDK and path to MDK include files in Keil Pack folder. Because SDK path has higher priority, project fails to compile if new MDK source files are incompatible with MDK header files in version delivered with SDK. Include path to MDK within the SDK is redundant and should be removed to allow MDK (Device Family Pack) upgrades.

    Perform following steps to update MDK (Device Family Pack):

    • use "Pack installer" to install new Device Family Pack
    • open "Select Software Packs" and select new version of nRF_DeviceFamilyPack and close the window
    • right click on "Device" component in the project explorer and open "Options for Component Class 'Device'"
    • select new version of the component from the drop down list and close the window

    Perform following steps to remove redundant include path:

    • open "Options for target"
    • go to "C/C++" pane
    • open "Include Paths" dialog box (press "..." button located on the right hand sight of include paths entry)
    • find relative path which contains "modules\nrfx\mdk" entry (e.g. ..\..\..\..\..\..\modules\nrfx\mdk) and remove it
    • recompile the project

    6404.Some screenshot to help on the description here.pdf

    Best regards,
    Kenneth

  • 0

    Hi Kenneth,

    Thank you for your replay all good

    andrew

  • 0

    I understand that back when this question was originally posed, the solution recommended below would have been a good one.

    But I am running into this situation now and find this workaround to be quite frustrating to have to deploy across a development team.
    We use SDK 15.3.0 with the PCA10040 (a custom variant) and nRF52832 and as of early 2021, the KEIL pack is at version 8.35.0

    I mean, how important is it for our team to worry about nrf_erratas.h when all we are interested in building is the DFU example?
    Wouldn't it be simpler to just add a blank "nrf_erratas.h" file somewhere in the include path(s) and be done with it?

    Alternatively, could we not download this file from Nordic website and save it in one of the folders in the include path and be done with it?

    RMV

Related