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?
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