INDART-ONE/FSL SofTec Microsystems SRL, INDART-ONE/FSL Datasheet - Page 42

• Manufacturer Part Number: INDART-ONE/FSL
• Description: PROG/DEBUG FOR HC08/HCS08/HCS12
• Manufacturer: SofTec Microsystems SRL
• Series: inDARTr
• Type: In-Circuit, Real-Time Debugger/Programmerr

Specifications of INDART-ONE/FSL

• Contents: In-circuit debugger/programmer unit, Cables, Evaluation Board and Software
• For Use With/related Products: Freescale HC08/S08/RS08/S12/S12X
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 520-1038; INDART-ONE

3
Debugging
3.4 HCS08, RS08 and S12(X) Notes and Tips
3.4.1 Entering Debug Session with CodeWarrior
When entering a debug session, the target microcontroller’s FLASH memory
is automatically erased, unsecured, programmed with the user application,
and the trimming value (if trimming is available for the selected
microcontroller) is automatically calculated and programmed (in the location
suggested by Freescale).
3.4.2 Reading Peripheral Status
Care must be taken when reading some peripheral’s status/data registers,
since a reading operation may cause the clearing of flags. This may happen
when the “Memory” window or the “Data” window is open, since these
windows read microcontroller’s resources during refresh operations.
3.4.3 Breakpoints and BGND Instruction
The BGND Assembly instruction forces the target microcontroller to enter the
Active Background Debug mode, stopping program execution. CodeWarrior
recognizes this event as a breakpoint and updates the contents of registers,
memory, etc. Successive commands (Start/Continue, Single Step, etc.) will
continue the execution of the program from the next instruction.
3.4.4 Real-Time Memory Update
During program execution, it is possible to view/edit the contents of the
“Memory” window and “Data” window in real time (edit operations are only
40
i
Note: When programming the microcontroller with the user
application (after having unsecured the device),
CodeWarrior ignores (doesn’t program) the security bits. As
a result, when entering a debug session, the device is
always unsecured, regardless of other user settings.