• State Verified Answer
  • Replies 10 replies
  • Subscribers 67 subscribers
  • Views 9650 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104427
Options
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

jt

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

  • 0 in reply to Sebastian

    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.

  • 0 in reply to Asbjørn

    Thanks for your help. I confirmed that my settings did match both images and unfortunately I get the same error. I just realized I can probably save a lot of time by just starting from a uVision 5 project and importing my c files and headers from the uVision 4 project's directory 1 by 1 manually.

  • 0

    This is a workaround, not a root cause solution, but to save time/resources I decided to start with a uVision 5 project, and manually import the source/header files over from the uVision 4 projects of interest. That seems to work.

    Thanks Asbjorn and Sesbastian for your time looking into this. I have to say, all in all, porting from "another BLE company"'s SoC to Nordic has been quite pleasant due to the documentation & high level of support, among other things.

  • 0

    I think that safest way is to do what you have planned - just create new project in uprojx format. The MDK from nRF51 SDK v7.0.1 should not collide with older SDK, so if you have more projects in old format you may still try to use it. On my PC I have nRF51 SDK v6.0.0 installed and also SDK v7.0.1 in PACK format and can compile both uvjproj and uvprojx projects.

  • 0 in reply to jt

    I'm a bit surprised that we didn't figure out what was wrong with your project. The workaround isn't ideal as you say, but we haven't gotten any similar feedback so I'm not sure what's actually gone wrong in your setup. Hopefully you'll get your development on the road however and let us know here is you should have any other questions and feedback. Good luck:)

Related