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
%r is a Codewright macro which returns the name of the working file (the one in your edit window). %e delivers the extension of this file. This results in a filename without any path information. %b%e gives you the complete name including the path. Maybe this works better. The name you listed does not show any extension. Is none specified ? How do you make sure that the compiler finds include files which are referencend in your source file ? HHK
the full file address is; Keil\C166\INC\REGST10F269.h It contains register locations. I'm not sure how to let the compiler include referenced files. Matthew
I no longer have the tools, but I set up Codewrite and C166 before. There are several issues I had to solve that you may want to look into. 1. If Keil's AMAKE is involved, turn it off because it embeds include paths in the object modules as part of it's dependency checking. The problem is that the first build doesn't know where the includes are, and if move the project between computers individual machines may use different directories for the tools and source files. 2. Look into the include command line switch for the compiler so you can tell it where the include files are. 3. Look into using command files because the command lines will soon outgrow the length limit when you start using options. 4. Beware of the #pragma SRC option. Experts in make files may know how to do it, but I found it confusing to include dependencies for a file that won't exist until the c file has been compiled. I wrote a short console app that I called translate. It called the compiler, then looked to see if a .src file was present by the same name and assembled it. 5. You can also use something like perl to parse the project file and generate a make file. I wrote a makmak application to do this in C. 6. You will have to modify the parsing of error messages in the CodeWrite IDE so that it understands how to take you to the offending line.
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.
The uVision command-line options are discussed in chapter 12 of the "Getting Started with µVision2" manual; GS51.pdf.
Thanks for the info. Unfortunatly I can't find the file on the Keil website or the program directory. Where can I download this from? Thanks Matthew
Sorry, for C166 the file is GS166.pdf!! Oops! You should find it in Keil\c166\hlp\ (on the CD or in your installation) Or on the 'Books' tab in the uVision Project window.
Found the file. Thanks very much for your help MGL