search

ARMmbed / mbed-os

Arm Mbed OS is a platform operating system designed for the internet of things
https://mbed.com
Other
4.64k stars 2.97k forks source link

Add support for uVision 5 #1651

Closed janjongboom closed 7 years ago

janjongboom commented 8 years ago

It's no longer possible to open old uVision 4 projects in uVision 5 (see f.e. https://devzone.nordicsemi.com/question/31201/nrf51822-error-in-keil-device-not-found/), this now means that we're no longer compatible with latest uVision stable. We should fix that.

0xc0170 commented 8 years ago

It's no longer possible to open old uVision 4 projects in uVision 5

It is. There's legacy pack, but not valid for nrf51. You need to copy manually those files from nordic SDK (or they add those automatically, I recall I had to do it manually) to get device support in uvision5.

Progen supports uvision5, even new uvision5 device packs for targets. There should be a migration path for this. We could add uvision5 support. People could use uvision4 or uvision5 (5 would default to new device packs, not the legacy device support). I can easily add this, however not many devices are in the progen definitions at the moment.

Or another option is to have uvision5 by default if target is supported there (progen has all data required), generates .uvprojx (=uvision5), otherwise tries to generate .uvproj.

I am inclined do go with new uvision5 exporter, start with small number of devices, and expand by the time.

janjongboom commented 8 years ago

@0xc0170 So opening a FRDM-K64F export to uVision 4 in uVision 5 ends with uVision crashing. (uVision IDE has stopped working, bla bla bla)...

0xc0170 commented 8 years ago

That never happened to me, it should not crash I assume.. I am using by default uvision5. Current version 5.17.0.0.

I'll do a cleanup for the template project (I noticed there are some leftovers left), I added already exporter yaml file to get info about exporters, should be on master. Please try to generate blinky example for k64f, it should contain yaml file with more information about exporters. Share that with us, also uvision5 version. I can have a look why a project crashes uvision5

toyowata commented 8 years ago

@janjongboom @0xc0170

You can also contact to Keil support team about IDE crash issue which is possibly a bug in the uvision.

I had an IDE crash case with latest version of uvision 5 IDE which worked fine with previous update version. That was a clearly a bug in the IDE and Keil support team quickly sent me a fixed version for it.

janjongboom commented 8 years ago

@toyowata Thanks. I opened an issue with Keil.

janjongboom commented 8 years ago

FRDM-K64F issue has been resolved with latest patch from uVision.

0xc0170 commented 8 years ago

FRDM-K64F issue has been resolved with latest patch from uVision.

Patch? U received something or just updated uvision? What was the cause?

We should either create a new feature request for uvision5 here in mbed, or rename this one. To get nrf51 for uvision5, we need to add uvision5 exporter to mbed exporters first.

janjongboom commented 8 years ago

It was fixed in 5.18a, I was on 5.18.

ciarmcom commented 7 years ago

ARM Internal Ref: IOTMORF-209

sg- commented 7 years ago

Closing all older exporter related issues. Please reopen if still valid. https://developer.mbed.org/blog/entry/Fixed-exporters-in-the-mbed-Online-Compi/