Hi out there,
I'm new to ARM-Controllers and KEIL uVision.
I'm using the trial version (restricted version), with Keil tool-chain
on a WIN2000-PC
Compiling works, also loading into LPC2103 (with ULINK).
The compiler tells me that I use 12% of code limit of the trial version.
BUT: When I want to start my program on the LPC2103 by the debugger I
get the following message:
MISSING DEVICE (R003: SECURITY KEY NOT FOUND)
Runnunig in Eval Mode.
What' wrong ?
Thank you for help
Otto
uVision3 error message: "Missing Device (R003....)"
Started by ●September 7, 2006
Reply by ●September 7, 20062006-09-07
Reply by ●September 7, 20062006-09-07
At 13:39 07.09.2006 +0000, you wrote:
>Hi out there,
>
>I'm new to ARM-Controllers and KEIL uVision.
>I'm using the trial version (restricted version), with Keil tool-chain
>on a WIN2000-PC
>Compiling works, also loading into LPC2103 (with ULINK).
>The compiler tells me that I use 12% of code limit of the trial version.
>
>BUT: When I want to start my program on the LPC2103 by the debugger I
>get the following message:
>
>MISSING DEVICE (R003: SECURITY KEY NOT FOUND)
>Runnunig in Eval Mode.
>
>What' wrong ?
Nothing, you can ignore this message as long as you do not want to debug
more than 16k (or 24k, I'm not quite sure about the current limitation of
the debugger). Debugging is still fully available as long as you do not
exceed the given code size (you will get a different message when you do so).
Regards
Herbert
>Hi out there,
>
>I'm new to ARM-Controllers and KEIL uVision.
>I'm using the trial version (restricted version), with Keil tool-chain
>on a WIN2000-PC
>Compiling works, also loading into LPC2103 (with ULINK).
>The compiler tells me that I use 12% of code limit of the trial version.
>
>BUT: When I want to start my program on the LPC2103 by the debugger I
>get the following message:
>
>MISSING DEVICE (R003: SECURITY KEY NOT FOUND)
>Runnunig in Eval Mode.
>
>What' wrong ?
Nothing, you can ignore this message as long as you do not want to debug
more than 16k (or 24k, I'm not quite sure about the current limitation of
the debugger). Debugging is still fully available as long as you do not
exceed the given code size (you will get a different message when you do so).
Regards
Herbert