Greetings all,
I recently updated to MDK-ARM V4.22a (because the trusty old version didn't support LPC1788). It's registered version, new PSN, new LIC, all ok so far.
But I cannot compile existing projects anymore (written in uVision3 some years ago, and I prefer the old IDE for various reasons).
Compile a project in uVsion3 isn't possible anymore, with the following error message:
> Compiling xyz > --- Error: failed to execute 'BIN40\ARMcc' > Target not created
uVision3 + uVision4 both correctly show the new toolchain in the about box. But only uVision4 seems to be able to invoke the ARM compiler.
Any ideas why ? Has support for uVision3 been dropped completely (would be very sorry for it).
Then loaded the exising project (*.uv2 !) in uVision4. Compiling works, after the usual modifications in Keil's RTL.H (removal of Keil's TCP/IP stuff because it collides with LwIP). Compiling+linking works with uVision4 (but as usual, the code doesn't work anymore because my custom startup code is incompatible with the current runtime library / kernel.. sigh...).
The tabbed editor windows in uVision4 are quite annoying. I'd prefer to have freely floating windows as in uVision3 so I can place those windows where I want to have them. Any chance to have 'freely floating windows' instead of the tabbed or "split" windows in uVision4 ?
Can the full path (not just the filename) displayed in each of the editor windows, as it was in uVision3 ? (Reason: I have dozens of files with the same name, but a different paths (typically something like 'config.h', which contains project- and/or hardware specific settings) . Ok, I can point the mouse somewhere and uVision4 shows the path in a bubble, but that's not as good as simply having the full path displayed in the editor window's title bar.
All the best, Wolfgang .
If anyone still reading this ... I finally got the new MDK-ARM version (V4.22a) running properly now, and also managed to rewrite my startup (adapted for a custom bootloader via CAN, which resides in external FLASH, shifted interrupt vector table from the CPU's point of view, etc).
The main reason why the old C-startup didn't work was that it called a function written in C to initialize the external memory interface (for ext. FLASH + SDRAM). Now the entire C-startup for the LPC2468 / LPC2478 is written in assembler, based on Keil's recent "LPC2400.s", and works properly (also with my custom bootloader).
BTW After working with the "new" uVision4, I am quite happy with it. It even allows me to continue editing while the debugger/uLink2 JTAG adapter downloads the firmware into the target. Very neat.