SPRUJC6A December 2024 – July 2025 AM2752-Q1 , AM2754-Q1
The EMU1 and EMU0 device pins are used to convey debug boot mode behavior and can also be used as part of a boundary scan compliance sequence to enable boundary scan features.
EMU1 and EMU0 are sampled when MCU_PORz is de-asserted and the decoded value determines the debug boot mode behavior as detailed in the following table:
| Sample Time | EMU1 | EMU0 | Boot Mde | Behavior |
|---|---|---|---|---|
| MCU_PORz dessertion | 0 | 0 | Reserved | Reserved |
| 0 | 1 | Reserved | Reserved | |
| 1 | 0 | Wait-In-Reset (WIR) | Device will remain quiescent until a debug connection is established and the debugger releases WIR. This mode is useful for debugging boot sequences. | |
| 1 | 1 | Normal | Device boots normally. Debug can connect at any time but the context will be post-boot. |
EMU1 and EMU0 are sampled when TRSTn is de-asserted and the decoded value determines the debug boot mode behavior as detailed in the following table:
| Sample Time | EMU1 | EMU0 | Boundary Compliance | Scan | Behavior |
|---|---|---|---|---|---|
| TRSTn deassertion | 0 | 1 | Boundary Enabled | Scan | The devices Boundary Scan TAP is connected to the device's JTAG interface. |
| 0 | 0 | Boundary Disabled | Scan | The device's SWJ-DP is connected to the device's JTAG interface. | |
| 1 | 0 | ||||
| 1 | 1 |