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

Running uVision 4 examples in uVision5

I'm uising the NRF51822 PCA100001 eval kit. I'm trying to open a couple uVision 4 projects in uVision 5. Unfortunately, it keeps telling me to install the software pack. I've already done this and confirmed the NRF51x software family pack is current. I've also installed the legacy pack from the keil website. I've also uninstalled and reinstalled everything a couple times.

Is there any way to use Vision 4 stuff in uVision 5? A lot of the forum posts provide uVision4 examples. Thanks. I looked at other forum posts but none have resolved my issue. image description

image description

image description

image description

Parents
  • jt,

    1. I think the easiest way is to install nRF51 SDK v6.1 - this should add support for Nordic chips in non PACK format. However I see that you already have Nordic folders inside KEIL what could suggest you already done it - so you may want to try second method.

    2. Try to download newest nRF51 SDK v7.0.1 zip and run nRF51_mdk_6_1_0_installer.msi from it.

    PACKs are only for MDK 5.12 or newer for projects in KEIL 5 format (uvprojx) - does not work in KEIL 4 projects.

    Hope that will help.

  • Thanks Sebastian. Yeah I have v6.1. I looked at the SDK v7.0.1 release notes and I'm using the NRF51822 silicon on the PCA10001 ref design, which hasn't been qualified with these drivers apparently. They recommend sticking to v6 if you're using that chip/board. Is that a cause for concern or do you think it's 'OK' to give it a shot anyways? I think I just figured out a more labor intensive workaround though - I'll try by starting with a uVision 5 project, and then manually import the source files / headers from the uVision 4 project.

Reply
  • Thanks Sebastian. Yeah I have v6.1. I looked at the SDK v7.0.1 release notes and I'm using the NRF51822 silicon on the PCA10001 ref design, which hasn't been qualified with these drivers apparently. They recommend sticking to v6 if you're using that chip/board. Is that a cause for concern or do you think it's 'OK' to give it a shot anyways? I think I just figured out a more labor intensive workaround though - I'll try by starting with a uVision 5 project, and then manually import the source files / headers from the uVision 4 project.

Children
No Data
Related