I have two computers, one for office use, one for going to clients.
Both are Win10 machines running licensed versions of V5.34.0.0 of MDK ARM Essential.
I wanted to re-sync the office computer to the travel computer yesterday, so I copied the entire folder from the travel to office computer.
When I open the IDE either from the desktop shortcut, or by clicking on the project file, the IDE opens, I can see the files, but before I can do anything, the IDE closes without any error message.
This happens for only one project. If I open a different project, that opens and builds fine. I then close that project, and open the other project, and the IDE disappears.
Both folder on the two computers are identical.
I tried restarting the computer several times with out success.
I finally uninstall Keil, re-installed and licensed it again. I then opened the project and it built without any problems.
I then closed Keil, and when I tried to reopen Keil, it immediately closes again.
This is making working on that project impossible right now, so any help would be appreciated.
It is not supported to just copy the MDK Installation folder to a different PC, as data created is not just existing at that folder only.
Instead:
- install and register Keil MDK from scratch on both PC's
- install the required Device Family Packs on each PC
- and just copy your project.
I didn't copy the MDK folder.
I have licensed copies of Keil on both computers.
The only thing I copied over was the project folder.
And this arrangement has been working for over a year.
Thanks for clarifying.
In this case I recommend to re-install Keil MDK to C:\Keil_V5
In case the problem persists you are, as registered user, entitled to open a Support case:
https://www.arm.com/support/contact-support
(attach your project to allow a replication, and confirm the MDK version in use, pls)
Actually, that is what I did.
I uninstalled Keil. Deleted the old folder.
I downloaded the latest Keil version, MDK-ARM Essential V5.34.0.0 and installed it to the default directory, and got the license setup again.