![NXP Semiconductors LPC43Sxx Скачать руководство пользователя страница 1376](http://html1.mh-extra.com/html/nxp-semiconductors/lpc43sxx/lpc43sxx_user-manual_17218271376.webp)
UM10503
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2015. All rights reserved.
User manual
Rev. 2.1 — 10 December 2015
1376 of 1441
NXP Semiconductors
UM10503
Chapter 51: LPC43xx/LPC43Sxx JTAG, Serial Wire Debug (SWD), and
51.7 Debug Notes
The following limitations apply during debugging:
•
Due to limitations of the Cortex-M4 integration, the LPC43xx cannot wake up in the
usual manner from Deep Sleep and Power-down modes. Do not use these modes
during debug.
•
The debug mode changes the way in which reduced power modes are handled by the
Cortex-M4 CPU. This causes power modes at the device level to be different from
normal mode operation. These differences mean that power measurements should
not be made while debugging because the results will be higher than during normal
operation in an application.
•
During a debugging session, the System Tick Timer and the Repetitive Interrupt
Timers are automatically stopped whenever the CPU is stopped. Other peripherals
are not affected. If the Repetitive Interrupt Timer is configured such that its clock rate
is lower than the CPU clock rate, the RIT may not increment predictably during some
debug operations, such as single stepping.
•
Debugging is disabled if code read protection of the flash memory is enabled.
51.8 Debug memory re-mapping
Following chip reset, a portion of the Boot ROM is mapped to address 0 so that it will be
automatically executed. The Boot ROM switches the map to point to 0x1000 0000 or
0x1C00 0000 (when booting from EMC) or 0x8000 0000 (when booting from SPIFI). Code
execution can start from address 0x0000 0000 using the M4 memory mapping register
(
).
The register mapping is normally not transparent to the user. However, when a debugger
halts CPU execution immediately following reset, the Boot ROM is still mapped to address
0 and the IRC calibration value has not been loaded, which may cause the IRC frequency
to be outside of the specified 12 MHz. Ideally, the debugger should correct the mapping
automatically in this case.
51.9 JTAG TAP Identification
The JTAG TAP controller contains device ID that can be used by debugging software to
identify the general type of device.
Debug and trace functions are integrated into the ARM Cortex-M4. Serial wire debug and
trace functions are supported in addition to a standard JTAG debug and parallel trace
functions. The ARM Cortex-M4 is configured to support up to eight breakpoints and four
watch points.
Table 1174.JTAG TAP identification
Mode
ID code
JTAG mode
0x4BA0 0477
SWD mode
0x2BA0 1477
Cortex-M0 co-processor
0x0BA0 1477