PK-HCS08GB60 SofTec Microsystems SRL, PK-HCS08GB60 Datasheet - Page 28

• Manufacturer Part Number: PK-HCS08GB60
• Description: KIT STARTER USB FOR MC9S08GB60
• Manufacturer: SofTec Microsystems SRL
• Type: MCUr

Specifications of PK-HCS08GB60

• Contents: Board, Cable, Software, Datasheets and User Manual
• Silicon Manufacturer: Freescale
• Core Architecture: HCS08
• Kit Contents: Emulator/Programmer
• Mc9s08gb60 Evaluation Board: Silicon Family Name
• Silicon Core Number: MC9S08GB60
• Core Sub-architecture: HCS08
• Silicon Family Name: S08GB
• Rohs Compliant: No
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• For Use With/related Products: Freescale MC9S08GB60 (USB)
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant, Contains lead / RoHS non-compliant
• Other names: 520-1014

PK-HCS08GB60 User's Manual
Note: the Single Step command (in a C source code) and the Step Over and Step Out
commands (both in a C and Assembly source code) use one hardware breakpoint.
Notes and Tips
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 is automatically calculated and programmed (to the location suggested by Motorola).
4
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.
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.
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.
Page 27