Hello I am getting very serious problem, The code written for phillips 89V51RD2 , after some days the code written in keil will not work on the same hardware .If i write same code once again without copy/paste it will work . Please any body have solution for this.
Regards Santosh Hegde.
I don't know anything about the C51 tools, but with the ARM tools, I have on three occations had projects that have totally died on me. The first two times, I had to create new projects and then add all source files unchanged.
The second and third times, I could verify that the project file had switched to a completely different processor - not even correct manufacturer.
I have not been able to find out exactly what trigged the change of processor in the project.
Per; I have had the same unscheduled changes occur in my projects. It appears that tools.ini is changed. There is one possible cause for me. I sometimes open more than one version of uVision. In one, I may be working in PK51(moving programs from 8051 to ARM) while I have MDK running in a different window. I can never predict which version of tools.ini will show up. Probably the last project to open will leave tools.ini modified. Also, I often have two uVision MDK projects open. I assume the same results are changing my tools.ini file. I hope to spend a little more time playing with different configurations to possibly identify a true cause. In the next release, I plan to build a completely different path for the two sets of Keil tools with different uV3 and different tools.ini. Bradford
I totally missed my point. The corrupted files are frequently older files pathed by the corrupted tools.ini rather than newer files changed. Re-loading the files repairs the broken paths. Bradford
Interesting. I will take a closer look the next time I get the problem.