iSYSTEM, March 2017
41/66
Mictor 38-pin MPC5xxx Nexus 16-bit Cable Adapter
Ordering code
IC50152
IC50152-12
This adapter is used to connect the iC5000 / iC5500 / iC5700 development system to Freescale MPC5xxx or ST
SPC56 based target via Nexus debug interface. It connects between the Debug/Trace module and the target
debug connector. It can be used for targets featuring Mictor 38-pin target debug connector with MPC5xxx Nexus
pinout.
IC50152 features a standard connection length (cca. 24 cm). An adapter with shorter cable length (12 cm) was
introduced (ordering code IC50152-12) for cases when standard length doesn’t work e.g. due to a badly designed
target PCB where reliable Nexus trace capture with the standard 24 cm cable cannot be achieved. In such cases,
shorter cable helps. In practice, IC50152-12 is sometimes used in conjunction with the MPC5646C (3M Bolero)
target device, which internally seems to lack from fast drivers on the Nexus signals.
Jumper J2 (EVTIN)
Under some circumstances it can happen that the debugger cannot find any absolute program counter message in
the analyzed Nexus trace block. Consequentially, trace reconstruction fails and errors or nothing gets displayed
in the trace window. To avoid such situations, the debugger can feed periodic signal to the EVTIN CPU pin
connecting to the on-chip Nexus engine, which then periodically generates and broadcasts program counter
synchronization messages.
In order to use this feature, jumper J2 must be bridged and the ‘Force periodic Nexus SYNC’ option in the
‘Hardware/emulation Options/CPU Setup/Nexus’ tab must be checked. Refer to iSYSTEM ‘Freescale MPC5xxx
& ST SPC56 Family On-Chip Emulation’ technical notes document for more details on the ‘Force periodic
Nexus SYNC’ option use.
Note that the EVTI (Nexus Event In) CPU pin may be shared with other CPU functionalities. For instance, on
MPC5516 the same pin can operate as GPIO, EBI read/write or EVTI. Whenever the CPU pin is configured and
used for EVTI alternate operation, J2 must not be populated in order to prevent electrical conflicts..
Note: In general there is no need to use ‘Force periodic Nexus SYNC’ functionality unless a specific application
code is traced, which does not generate messages containing absolute program counter information. As long as
the user has no problems with the trace use, it is recommended to keep jumper 2 disconnected.
Note: Jumper J2 was introduced with rv: N1, previous versions (rv: M1) do not have this jumper.