iSYSTEM, October 2016
37/69
Jumper J2 (EVTIN)
Note: It was introduced with rv: C1, some previous versions (rv: A1, A2, B1, D1) do not have this jumper.
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 J2 disconnected.
The adapter connects to the target via a 14-pin 2.54 mm connector (for example Yamaichi: FAS-1401-2101-2-
0BF). A target should feature a matching part (for example WÜRTH ELEKTRONIK: 612 014 216 21).