ARM Technical Support Knowledge Articles

USING WITH DEVICES WITH EXTERNAL PROGRAM LOCK BITS

Applies to: MON51 Target Monitor

Answer


Information in this article applies to:


SYMPTOMS

I have a problem with Monitor-51 on an Atmel AT89C51CC01 board. I have installed the Monitor according the instructions in Application Note 152: Installing and Using the Keil Monitor-51.

When starting the debug session, the uVision debugger connects to the target but instead of the version number I see only letters displayed. The version number is missing!

My application seems to be downloaded. However, I do not see the correct hex values for my code in the memory window. After I try any code execution command (step or run) the debugger loses communication with the hardware. What can be be reason for this behavior?

CAUSE

The Atmel T89C51CC01 (and several other Atmel parts like the T89C51RD2, T89C51CC02, and T89C51AC01) have security bits that disable external code accesses.

RESOLUTION

You must make sure that the three lock bits in the HARDWARE SECURITY BYTE are inactive (cleared). They must be cleared with a parallel programmer before the chip can execute code from external memory. The lock bits of the HARDWARE SECURITY BYTE cannot be modified with ISP software like the Atmel FLIP utility.

SEE ALSO

Article last edited on: 2004-10-11 09:17:34

Rate this article

[Bad]
|
|
[Good]
Disagree? Move your mouse over the bar and click

Did you find this article helpful? Yes No

How can we improve this article?

Link to this article
Copyright © 2011 ARM Limited. All rights reserved. External (Open), Non-Confidential