"SYStem.Up" does not work |
||
![]() |
![]() |
The installation is ok, but when trying "SYStem.Up" the debugger responds with the error message "emulation debug port time-out". |
|
See chapter "Trouble-Shooting" in the "ICD Targets" guide in the online help. |
|
Debugging in Idle Mode |
||
![]() |
![]() |
Why does the debugger switch to 'DOWN' mode when idle mode is entered by the processor? |
|
When the processor enters the idle mode the communication channel to the debugger will be cut off. Debugging is not possible in this mode. |
|
Single Step on Extended Sequence |
||
![]() |
![]() |
Why does extended register, page or segment commands overstep the next commands? |
|
For execution of a single step a debug trap is used. During the execution of these extended sequences the software trap is locked. Affected commands are EXTR, EXTP, EXTPR, EXTS, EXTSR. |
|
Software Breakpoint on extended Sequence |
||
![]() |
![]() |
Why do I get wrong program behavior when setting a software breakpoint on an extended sequence? |
|
A software breakpoint within an extended sequence aborts the extended sequence. Therefore do not use a software breakpoint within the extended sequence or use a hardware breakpoint instead. Affected commands are EXTR, EXTP, EXTPR, EXTS, EXTSR. |
|


|
Copyright © 2008 Lauterbach Datentechnik GmbH, Fichtenstr. 27, D-85649 Hofolding, Germany Impressum The information presented is intended to give overview information only. Changes and technical enhancements or modifications can be made without notice. Last generated/modified: Aug-27-2008 |