ICS MON08 Interface Connection
Connection Procedure
357
Microcontrollers Debugger Manual
check was successfully passed. If a break character is not received from the
processor, this flag returns an ‘N’. Reasons for this include:
– The baud rate specified was incorrect.
– The processor was not reset properly. Check the
Target Hardware Type
. If you
are connecting to a class II board, check the
MON08 cable communication
connections type
in the
Advanced Settings
dialog box.
•
4 – Device entered monitor mode:
Once the software receives, or fails to receive, a break character from the processor,
it attempts to communicate with the monitor running on the M68HC08 processor. It
tries to read the monitor version number by issuing a monitor mode read. If the
processor fails to respond properly to this command, this flag returns an ‘N’.
•
5 – Reset was Power-On Reset:
If the device properly entered monitor mode (4), the software reads the reset status
register (RSR). This read does not affect the security sequence, and occurs purely for
diagnostic reasons. The RSR indicates the conditions under which the processor
underwent the last reset. For the software to pass the security check properly, it
MUST first cause the processor to undergo a Power-On Reset. The software reads
the RSR to determine if the last reset was indeed caused by power-on. The result of
the RSR read is indicated in parentheses after the flag value. If the highest bit is not
set then the reset was not a power-on reset, and the flag indicates an ‘N’. Reasons for
this include:
– The processor did not power all the way down because power was being supplied
to the processor through either the port pins, IRQ line, RESET line, or power
pins.
– The voltage driven on the power pin of the processor did not go below 0.1 volts.
– The processor was not reset properly. Check the
Target Hardware Type
. If you
are connecting to a class II board, check the
MON08 cable communication
connections type
in the
Advanced Settings
dialog box.
•
6 – ROM is accessible (un-secured):
If the device properly entered monitor mode (4), the software reads locations $FFF6-
$FFFF to determine if the processor passes the security check. Memory locations
which are invalid or protected read back from the device as $AD. If all bytes from
$FFF6-$FFFF read a value of $AD, it is assumed the device is secure, and the flag
value is an ‘N’. If all flags 0-5 register a value of ‘Y’ and flag 6 register a value of
‘N,’ then the reset process has gone correctly except that the security code used to
pass security was incorrect. Specify the correct security code and try again, or
IGNORE the security failure and erase the device. Once you erase a secured device,
you must exit the software and restart it in order to pass security.
Summary of Contents for Microcontrollers
Page 1: ...Microcontrollers Debugger Manual Revised 22 October 2007 ...
Page 20: ...Table of Contents 20 Microcontrollers Debugger Manual ...
Page 24: ...Book I Contents 24 Microcontrollers Debugger Manual ...
Page 60: ...Debugger Interface Highlights of the User Interface 60 Microcontrollers Debugger Manual ...
Page 156: ...Debugger Components Visualization Utilities 156 Microcontrollers Debugger Manual ...
Page 198: ...Real Time Kernel Awareness OSEK Kernel Awareness 198 Microcontrollers Debugger Manual ...
Page 236: ...Synchronized Debugging Through DA C IDE Troubleshooting 236 Microcontrollers Debugger Manual ...
Page 238: ...Book II Contents 238 Microcontrollers Debugger Manual ...
Page 332: ...HC08 Full Chip Simulation Configuration Procedure 332 Microcontrollers Debugger Manual ...
Page 348: ...MON08 Interface Connection Device Class Description 348 Microcontrollers Debugger Manual ...
Page 364: ...ICS MON08 Interface Connection Device Class Description 364 Microcontrollers Debugger Manual ...
Page 428: ...HC08 FSICEBASE Emulator Bus State Analyzer BSA 428 Microcontrollers Debugger Manual ...
Page 430: ...Book III Contents 430 Microcontrollers Debugger Manual ...
Page 466: ...HCS08 Full Chip Simulation Peripheral Modules Commands 466 Microcontrollers Debugger Manual ...
Page 544: ...HCS08 On Chip DBG Module HCS08 DBG V3 New Features 544 Microcontrollers Debugger Manual ...
Page 546: ...Book IV Contents 546 Microcontrollers Debugger Manual ...
Page 576: ...Book V Contents 576 Microcontrollers Debugger Manual ...
Page 698: ...Book VI Contents 698 Microcontrollers Debugger Manual ...
Page 714: ...Flash Programming NVMC Commands 714 Microcontrollers Debugger Manual ...
Page 730: ...Book VII Contents 730 Microcontrollers Debugger Manual ...
Page 840: ...Book VIII Contents 840 Microcontrollers Debugger Manual ...
Page 864: ...Book IX Contents 864 Microcontrollers Debugger Manual ...
Page 868: ...Legacy Target Interfaces Removed 868 Microcontrollers Debugger Manual ...