• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 15 subscribers
  • Views 1641 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help with compiling in codewright

Matthew Lickess

Hi All

I'm trying to integrate uVision so that it compiles code written in codewright. I have set up the following command line in codewright to use the compiler

c:\keil\c166\bin\c166.exe %r%e

it returns messages saying invalid base address and unidentified identifier in the following file REGST10F269.

I'm fairly new to this and would appreciate any help.

Thanks in advance
Matthew

Parents
  • 0

    Hi,

    we usually develop code under CodeWright and build/debug the application with uVision2 (when it's for Infineon CPUs!). To do this, we prepare one project file for CodeWright (*.pjt, *.psp) and one project for uVision2 (*.uv2) and from inside CodeWright we launch uVision2 in batch mode with different options to build, rebuild, download or simulate the application. This is easily done by entering the right commands under CodeWright's "Project Properties / Tools". As an example:

    C:\KEIL\UV2\UV2.EXE -b "%x\PROJNAME.UV2" -t "Target Name" -o %x\PROJ.ERR

    is for "build". See the manual of uVision2 for other commandline options.

    If this is not enaught clear, I could try to prepare a brief appnote about the matter and publish it in our web site at http://www.bluewind.it.

Reply
  • 0

    Hi,

    we usually develop code under CodeWright and build/debug the application with uVision2 (when it's for Infineon CPUs!). To do this, we prepare one project file for CodeWright (*.pjt, *.psp) and one project for uVision2 (*.uv2) and from inside CodeWright we launch uVision2 in batch mode with different options to build, rebuild, download or simulate the application. This is easily done by entering the right commands under CodeWright's "Project Properties / Tools". As an example:

    C:\KEIL\UV2\UV2.EXE -b "%x\PROJNAME.UV2" -t "Target Name" -o %x\PROJ.ERR

    is for "build". See the manual of uVision2 for other commandline options.

    If this is not enaught clear, I could try to prepare a brief appnote about the matter and publish it in our web site at http://www.bluewind.it.

Children