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

• 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

5
5. Troubleshooting
3. Make sure you are working with the correct hardware model. To view/change the
4. If the SofTec-HCS08 menu is not present in the CodeWarrior HC(S)08 debugger’s main
Stepping Execution is Slow
When the Memory window is open, step commands may execute slower, since the Memory
window contents need to be refreshed after every step.
STOP Assembly Instruction Causes a Microcontroller Reset
If the STOPE bit in the SOPT register is not set, the STOP instruction is recognized as an
illegal opcode, causing the microcontroller to reset. The SOPT register can be written only
once after reset.
Communication Lost During Debugging
This problem may occur because:
1.
2.
Getting Technical Support
Technical assistance is provided free to all customers. For technical assistance,
documentation and information about products and services, please refer to your local
SofTec Microsystems partner.
Page 34
hardware model in use, choose SofTec-HCS08 > MCU Configuration from the
CodeWarrior HC(S)08 debugger’s main menu.
menu, this is because the target has not been recognized by CodeWarrior (“No link to
Target” appears in the status bar). In this case, from the GDI menu, choose MCU
Configuration and verify that the hardware code is set correctly.
The BKGDPE bit in the SOPT (System Option Register) register has been set to 0,
configuring the BKGD pin as a generic I/O pin. The BKGD pin must be reserved for the
BDM communication (BKGDPE = 1).
A microcontroller reset has occurred. Among other things, this may be caused by the
COP peripheral. After reset, the COP is enabled, so your program must either disable
it or reset its timer.