I have just installed Keil UVision2 and are trying out the included example rtx_ex1. I want to run it on the simulator for an Infineon C167CR-LM processor. When I build the project, i get FATAL ERROR L210: I/O ERROR ON INPUT FILE: EXCEPTION 0021H: PATH OR FILE NOT FOUND FILE: Rtx_ex1.obj I have not done any changes to the project, other than changing to the correct processor "device for target..." Should'nt uvision2 create this file when it is not there? What to do? Regards, Ray
If it's a purchased copy of C166, you should follow installation instructions carefully (serial number, dongle, etc.). Otherwise the compiler will not generate code which will lead to the error message you are getting. Or you can try installing evaluation version of the C166 toolset. - mike
Hi, and thanks for the answer. I have an Infineon SK167 starter kit with hitex debugger and a uvision2 evaluation version, and I also have a licensed full version of uvision2. When I run the example rtx_ex1 in the evaluation version it works fine, but when i try it in the full version, I get the above mentioned error. The installation is done according to the books. I also get a warning in the full version, saying: RTX_EX1.C(1): warning C500: MISSING DEVICE (SECURITY KEY NOT FOUND) I dont know what this security is, but it dont like the sound of that warning. Do you know what this warning is?
If I'm not mistaken, security key means the dongle that plugs into the parallel port. Again, I might be wrong, but I think the dongle requires a software driver on NT/2K/XP systems. The option to install the driver should be presented during the installation of the C166 toolkit.
Yes - the installation does ask if you want to install the security key driver - but it doesn't always work. And when it fails, it doesn't tell you. You need to search this site for the NT dongle driver, download the file and install it seperately. (There is a special version of the driver for people with Toshiba Satellite Pro laptops, as I found after many days of trying to get the damned thing to work!)
I got it. Something must have gone wrong on the installation of the security key driver. I uninstalled and reinstalled the driver, and now it works like a charm. Thanks a lot, both of you. Regards, Ray