problem with uVision4 help me please

Hi everybody,

Issue1:

I am designing an MIL 1553B interface card using LPC2294(from NXP). I am having some source code from old projects which were developed on uVision2 if I try to compile it using uVision4 it is displaying lot of errors while linking like many functions are undefined in .out file(here I am using startup.s file which will get generated automatically at the project creation time because with old start up file it is displaying more errors while linking).

but the .Hex file generated using uVision2 is working fine with my hardware I could load the hex file and I could do all the operations like reset, step wise debug etc..

presently I am using Keil uVision V4. 03q version i.e RL ARM compiler.

can someone tell me what are all the steps to be taken while migrating from uVision2 to uVision4?

Issue 2:
The example code(got installed while installing keil) working fine with simulator i.e allowing all operations like step wise debugging, run, reset etc.. but the same code is not working with my board (keil setting are correct because my old project .hex file is working fine with the same settings).
I tried with a new project with a very simple code it is fine with simulator but not working with board, neither running nor allowing for step wise debugging.

what could be the reason for this? if only startup file issue please suggest me how to get rid of this.
I do not know how to write the startup file please suggest me a link where I can find the required documentation on "how to write the startup file".

Thanks for your help in advance

Parents
  • Note that uVision is just the user interface & "framework" which holds everything together. The actual build is performed by the associated compiler, assembler, linker, etc.

    uVision-2 was superseded by uVision-3 a very long time ago - and uVision-3 itself was superseded by uVision-4 a couple of years ago.

    Therefore, it is likely that your project is waaaaaaaaay out-of-date with the current Keil tools - so it should not come as a surprise that your project does not "just build" with the latest tools!

    "can someone tell me what are all the steps to be taken while migrating from uVision2 to uVision4?"

    For a start, you will need to work through all the reported errors, and fix them.

    You will need to check all the assumptions that your code made about the uVision-2 environment, and check if these still apply to uVision-4 - this will mean careful study of the Manuals for both the old and the new toolsets.

    You could try trawling through all the release notes between your old & new versions - but they're probably too far apart for that to be very helpful. Might be worth a "skim" to look for major changes?

    You will need to do a lot of testing to ensure that everything still works.

    Be sure to keep an installation of the old tools available and in working order - so that you can check whether any problems encountered in this process are new, or did previously exist...

    Note that, just because your code appeared to "work fine" with the old tools, this does not mean that it was actually fine! It is very common indeed that a new tool release will show-up previously undiscovered flaws in your code...

    "I am using Keil uVision V4. 03q version i.e RL ARM compiler"

    RL ARM was not a compiler; it was a set of so-called "middleware" libraries - it is now part of MDK-Professional and not available separately: http://www.keil.com/rl-arm/

Reply
  • Note that uVision is just the user interface & "framework" which holds everything together. The actual build is performed by the associated compiler, assembler, linker, etc.

    uVision-2 was superseded by uVision-3 a very long time ago - and uVision-3 itself was superseded by uVision-4 a couple of years ago.

    Therefore, it is likely that your project is waaaaaaaaay out-of-date with the current Keil tools - so it should not come as a surprise that your project does not "just build" with the latest tools!

    "can someone tell me what are all the steps to be taken while migrating from uVision2 to uVision4?"

    For a start, you will need to work through all the reported errors, and fix them.

    You will need to check all the assumptions that your code made about the uVision-2 environment, and check if these still apply to uVision-4 - this will mean careful study of the Manuals for both the old and the new toolsets.

    You could try trawling through all the release notes between your old & new versions - but they're probably too far apart for that to be very helpful. Might be worth a "skim" to look for major changes?

    You will need to do a lot of testing to ensure that everything still works.

    Be sure to keep an installation of the old tools available and in working order - so that you can check whether any problems encountered in this process are new, or did previously exist...

    Note that, just because your code appeared to "work fine" with the old tools, this does not mean that it was actually fine! It is very common indeed that a new tool release will show-up previously undiscovered flaws in your code...

    "I am using Keil uVision V4. 03q version i.e RL ARM compiler"

    RL ARM was not a compiler; it was a set of so-called "middleware" libraries - it is now part of MDK-Professional and not available separately: http://www.keil.com/rl-arm/

Children
More questions in this forum