We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi, We have just bought uVision4 and STM32 dev. suit for new projects. We already have uVision2 and C51 and C166 from some years ago (using printer port dongles) to support older products.
How can I put the old product codes into the new uVision4 system so I can run everything from one Development Environment? It would save me having to run uVision2 and uVision4 on the same PC.
thanks for any help PhilipJ
Thanks for that!
I'm asking here in case anyone else using the system knows how to do it. I thought forums were so we users could have friendly chats with each other.
PhilipJ
I only know how to use old and new uVision when both are for same architecture, in which case the older uVision will reinstall and work with the newer license.
But mixing architectures may not be possible, so you really have to talk with Keil. Using the old uVision for the old system and the new uVision for the newer architecture would probably only require that you keep everything in separate root trees.
I thought forums were so we users could have friendly chats with each other
they are
what is 'unfriendly' about "nobody but Keil marketing will know"?
especially in a case like this where a wrong answer could lead to losing the access to the program.
Erik
OK,
Well it did sound as though I was being accused of trying to get around the licensing arrangements. This is in no way the case, as I said in my first post, my company have bought these tools and the license clearly says that even when they are not renewed for updates and support they are still perfectly legal for use. You may note I did not use the word 'unfriendly' myself, I mentioned friendly chats between us engineers as opposed to officially contacting Keil for a relatively trivial question.
I'm sorry if my comments offended, I will certainly consider more carefully in future my use of this forum.
Meanwhile thanks to Per Westermark for your reply, this is in-fact what the installer gives you since the uVision2 and uVision4 go into seperate folders within the Keil folder.
I have multiple installation directories like c:\Keil_xxx\ where xxx is the version.
This means that I have multiple TOOLS.INI files - one for use with the older ARM compiler and one for the newer ARM compiler. When updating older projects, I continue to use the same tool chain that was used during the original acceptance testing.
The Keil installer on the other hand will do: c:\Keil\xxx\ which means that a newer installation will backup the tool chain directory but overwrite some files. I'm not too fond of getting files overwritten without knowing for sure what the files does.
You may note I did not use the word 'unfriendly' I'm sorry if my comments offended, no offense taken, just wanted to avoid what unfortunately happened I will certainly consider more carefully in future my use of this forum
I hope no Keil user will ever "consider more carefully their use of this forum".