Updating to MSK-ARM version 4.70

It looks like you did not really fully update your MDK.
When i open "About µVision", it states µVision V4.70.0.0 on the top and in the toolchain-line we have MDK-ARM Standard: 4 user Version 4.70.0.0, and the compiler is V5.03.0.24.

Maybe try to reinstall again, or make a complete uninstall before you install the new version.
(The code completion configuration is where you expected it to be on my version, Edit->Configuration->Text Completion.

Hope this helps in any way...

Yes, you were right, it seems I haven't finished installation process...I have tried to reinstall it again and now I see uVision V4.70.0.0.

Text Completion is also working :)

Thank you!

I started using the new editor in V4.70a today, hapily typing away for a couple of hours, then uVision crashed, lost an hour of work. I had not done any compilation, just code writing - so be sure to save regularly (as of course, we all do except when we need to).

Editing in uVision crash has never happened in the many years I have been using uVision editor (ok i have had a couple of compile crashes but not while just editing).

- Phil.

I tried 4.7 about a week ago, found it to be very unstable. Crashes, and problems compiling.
Went back to an old version, which was much faster. The new features were not worth the headaches.

did anyone else experience problems with the preprocessor symbols in the options tab?

i have defined 2 symbols DEBUG1, DEBUG2

in 4.60 everthing was fine.

4.70: i did not change anything and try to compile:
if i compile sometimes i get and error during linking: could not open file DEBUG2

than i have to compile again and everthing is working fine and my hex file is created. i did not recognize a system behind this behaviour. sometimes it is working fine sometimes not..

sorry but i'm so pissed at the moment. it is not like uVision costs 100$
KEIL gets a serious amount of money and everytime you have to strugglewith such stupi errors

I recently upgraded to 4.70a

I found I had to clear out the target directory and remove all the project related files apart from the *.uvproj

Until I did this the builds were unstable, debugging was all over the place, the size of the output wasnt what I was expecting.

afterwards dont forget to set up the ulink2 to use the correct programming routines and the SW interface ( if you use it )

This what I was told to do previously after a upgrade from the distributor

Even though I am sure I upgraded to 4.70a
the info from the IDE is this

IDE-Version:
µVision V4.70.0.0
Copyright (C) 2013 ARM Ltd and ARM Germany GmbH. All rights reserved.

License Information:
XXXXXXXXXXXXXX
CCCCCCCCCCCCC
LIC=BLAH-BLAH-BLAH-BLAH-BLAH-BLAH-BLAH-BLAH

Tool Version Numbers:
Toolchain: MDK-ARM Professional Version: 4.70.0.0
Toolchain Path: C:\Keil\ARM\ARMCC\bin\
C Compiler: Armcc.Exe V5.03.0.24
Assembler: Armasm.Exe V5.03.0.24
Linker/Locator: ArmLink.Exe V5.03.0.24
Librarian: ArmAr.Exe V5.03.0.24
Hex Converter: FromElf.Exe V5.03.0.24
CPU DLL: SARMCM3.DLL V4.70.0.0
Dialog DLL: DCM.DLL V1.9.0.0
Target DLL: UL2CM3.DLL V1.146.0.0
Dialog DLL: TCM.DLL V1.12.0.0

and if I click on help/check for upgrade its suggests I get 4.70a
anyone else seeing this

hey,

thanks for the info. i did what you said and it seems better. linker errors are gone for now.

I havent had a problem since clearing out the old project settings.

Dont forget to turn on the periodic updates on the debugger if you want to see vairables update

Do you still have your 'old' project files which show the strange behavior?
If yes, please send this project to support.intl@keil.com. If we can duplicate a problem, we will fix it.