Nexus Development Interface (NDI)
31-4
Freescale Semiconductor
PXR40 Microcontroller Reference Manual, Rev. 1
— FlexRay Nexus trace via data write messaging (DWM) and data read messaging (DRM). This
allows the development tool to trace FlexRay generated reads and/or writes to selected address
ranges in the device’s memory map.
— Watchpoint messaging (WPM) via the auxiliary port.
— Watchpoint trigger enable/disable of data trace messaging.
•
eTPU development support features (NDEDI)
— IEEE-ISTO 5001-2002 standard Class 3 compliant for the eTPU engines.
— Data trace via data write messaging and data read messaging. This allows the development tool
to trace reads and writes to selected shared parameter RAM (SPRAM) address ranges. Four
data trace windows are shared by the two eTPU engines.
— Ownership trace via ownership trace messaging (OTM). OTM facilitates ownership trace by
providing visibility of which channel is being serviced. An ownership trace message is
transmitted to indicate when a new channel service request is scheduled, allowing the
development tools to trace task flow. A special OTM is sent when the engine enters in idle state,
meaning that all requests were serviced and no new requests are yet scheduled.
— Program trace via branch trace messaging. BTM displays program flow discontinuities (start,
jumps, return, etc.), allowing the development tool to interpolate what transpires between the
discontinuities. Thus static code can be traced. The branch trace messaging method uses the
branch/predicate method to reduce the number of generated messages.
— Watchpoint messaging via the auxiliary port. WPM provides visibility of the occurrence of the
eTPU’s’ watchpoints and breakpoints.
— Nexus based breakpoint/watchpoint configuration and single step support.
•
Run-time access to the on-chip memory map via the Nexus read/write access protocol. This feature
supports accesses for run-time internal visibility, calibration variable acquisition, calibration
constant tuning, and external rapid prototyping for powertrain automotive development systems.
•
All features are independently configurable and controllable via the IEEE 1149.1 I/O port.
•
The NDI block reset is controlled with JCOMP, power-on reset, and the TAP state machine. These
sources are independent of system reset.
31.1.3
Modes of Operation
The NDI block is in reset when the TAP controller state machine is in the TEST-LOGIC-RESET state. The
TEST-LOGIC-RESET state is entered on the assertion of the power-on reset signal, negation of JCOMP,
or through state machine transitions controlled by TMS. Assertion of JCOMP allows the NDI to move out
of the reset state, and is a prerequisite to grant Nexus clients control of the TAP. Ownership of the TAP is
achieved by loading the appropriate enable instruction for the desired Nexus client in the JTAGC controller
(JTAGC) block when JCOMP is asserted.
Following negation of power-on reset, the NPC remains in reset until the system clock achieves lock. In
PLL bypass mode, the NDI can transition out of the reset state immediately following negation of
power-on reset. See
Summary of Contents for PXR4030
Page 1: ...PXR40 Microcontroller Reference Manual Devices Supported PXR4030 PXR4040 PXR40RM Rev 1 06 2011...
Page 30: ...PXR40 Microcontroller Reference Manual Rev 1 Freescale Semiconductor xxx...
Page 40: ...PXR40 Microcontroller Reference Manual Rev 1 xl Freescale Semiconductor...
Page 66: ...Memory Map PXR40 Microcontroller Reference Manual Rev 1 2 4 Freescale Semiconductor...
Page 120: ...Signal Descriptions 3 54 Freescale Semiconductor PXR40 Microcontroller Reference Manual Rev 1...
Page 860: ...FlexCAN Module 24 50 Freescale Semiconductor PXR40 Microcontroller Reference Manual Rev 1...
Page 1167: ...Decimation Filter Freescale Semiconductor 28 53 PXR40 Microcontroller Reference Manual Rev 1...
Page 1168: ...Decimation Filter 28 54 Freescale Semiconductor PXR40 Microcontroller Reference Manual Rev 1...