We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
We get the following errors (8 out of 10 times) when trying to compile (the samplecode) Error C3397E - System clock has been set back or Error L0589E - System clock has been set back or Error A0594E - System clock has been set back
We installed the same version
<mdk304.exe size: 68.130.552 byte> IDE-Version: µVision3 V3.50 Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2007
on a second (identical!) computer There the problem does not occur.
Unfortunately i need the second machine for other tasks, so i need to run the µVision3 compiler on the one not working :-( Does anybody has a clue how to get rid of those "System clock has been set back" messages?
- Arndt
p.s. We only use local file system and no network drive.
This sounds like the kind of thing you get with time-limited evaluation versions when you've tried to cheat by setting your PC's date back a few days to gain extra evaluation time...
Is Keil's ARM evaluation time-limited?
Did you fiddle with the PC's clock (ie, its date & time setting)?
yes the Eval Versions have a long term time bomb to avoid that people are using them even in 10 years. It causes quite a bit of support work to find out versions that Eval users are using (especially when they want to use the newest devices with the oldest tool version).
"the Eval Versions have a long term time bomb"
Is this true of all Eval versions, or just the ARM tools?
Could this be the cause of the message that the OP is seeing?
First of all: Many thanks for the quick and good support. Yes, there were files (somewhere) in the Windows Directory which had a "creation time stamp" set to the 5th May 2007. That caused the problem. I just wrote a tool to set the actual system time to all files have a future timestamp and now it is working.
Thanks again.