Filter
Top Products
5 Using the KD
5.2.5 Limitations on Stop and Wait Modes
To use stop or wait modes in the User Program, start the KD in free-run mode. If you
want to debug, close the RAM, C Watch and ASM Watch Windows before actually
debugging. Furthermore, set a breakpoint or take other necessary measures when
getting out of stop or wait mode in order to ensure that no window operations will be
performed until the program stops at the breakpoint.
5.2.6 Realtime Capability of the User Program
Please be aware that while the Monitor Program is in its “STOP”ed state, the hardware
peripherals will continue to run. Therefore, interrupts may not be serviced properly. Also,
the watchdog timer will not be serviced and will likely timeout if active.
Note: While the Monitor Program is in its “RUN”ning state, there is no overhead on the
User Program,
unless the RAM, C Watch and ASM Watch Windows are open in
KD30/KD3083. These windows require periodic communication with the target
MCU, which suspends normal User Program operation while servicing the
request (approximately 2000 BCLK cycles for each 16 bytes of data displayed in
the window are used per window update). When enabling Realtime Capability in
the User Program, close these windows.
62