Respected Colleagues,
will you be so kind to give me some opinion about situation I have:
If I compile some code and make HEX file for the NXP LPC2148 with a Keil uVision3 and BIN30 tools, Keil MCB2140 evaluation board work fine as expected, but if I compile the same code and make HEX file for the NXP LPC2148 with a Keil uVision4 and BIN40 tools, the same Keil MCB2140 evaluation board do not work at all.
To clarify, the code is trivial - just switching one LED on the Keil MCB2140 board. Startup file, device configuration and all settings are standard. Of course compilation and linking is with 0 errors and 0 warnings.
With other MCU's, like LPC2929 (Keil MCB2900 Evaluation board) and LPC2939 (Hitex LPC2939 Evaluation board) very complex and demanding programs are working fine with uVision 4 and BIN40 tools.
Furthermore, all very complex and demanding programs which I wrote in the past with uVision3 and BIN30 tools are working fine on the Keil MCB2140 board.
Any suggestions?
Is that "early" uVision-3 or "late" uVision-3?
It's several years since the last uVision-3 was replaced by uVision-4 - and there have been many further updates since then.
http://www.keil.com/forum/21895/
It should, therefore, come as no surprise that code written for uVision-3 (and associated other tools) does not "just work" with the latest tools.
You could start by doing some basic debugging to see where, exactly it is failing - the information content of "do not work at all" tends to zero...
Respected Andrew Neil,
versions are µVision3 V3.90 and µVision V4.50.
It doesn't matter where the code is written (uVision3 or uVision4). The code is not written for the uVision3 and tested with the uVision4. The point is that MCU doesn't work when I download generated HEX file from the new simple project for the LPC2148 in the uVision4 (which only have to turn on one LED, or just to send "Hello" on the serial port).
I have found that:
A) New project created in the Keil uVision4 for the LPC2148 MCU compiled and linked with that same version of Keil uVision4 does not work on the Keil MCB2140 Evaluation board with LPC2148.
B) New project created in the Keil uVision3 for the LPC2148 MCU compiled and linked with that same version of the Keil uVision3 work fine on the Keil MCB2140 Evaluation board with LPC2148.
C) New project created in the Keil uVision4 for an other type of MCU's like LPC2929 (on the Keil MCB2929 Evaluation Board) work fine.
I have checked mentioned with my colleague who have both Real View 3.0 and 4.0 and devices other than MCB2140, and result is that LPC2148 work OK with HEX files generated under Real View 3.0, but doesn't under Real View 4.0.
Regarding your debugging suggestion, I think that Keil have to debug this, because it is a Keil's compiler and a Keil's Evaluation board.
If you don't believe that mentioned above is true, please take one MCB2140 evaluation board and check it yourself. Maybe Keil had some reason to remove Blinky project only from the folder for the MCB2140 evaluation board with the LPC2148 (C:\Keil\ARM\Boards\Keil\MCB2140).
Best regards.
Then you had better submit a bug report to Keil
"If you don't believe that mentioned above is true"
I didn't question whether it may be true; in fact, I stated that it is not uncommon for stuff which "works fine" (sic) when built with an old(er) toolset to fail when built with a new(er) toolset.
You probably need more evidence to support that it is actually a bug in uVision 4 - at least, a more detailed description of the failure than just, "it doesn't work"
www.catb.org/.../smart-questions.html
lpc 2148 device is not found in the device tool (data base of ) keil u4 what to do??