Hi,
a customer using the RM57L843 is in need of changing from the MIPI-60 connector to a connector with less pins for their board.
The following thread was useful:
https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/528218/1941694#pi320995=1
The customers goal is to use the CoreSight-20 connector with the pin-out described in
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0499b/BEHEIHCE.html
Table 14. CoreSight 20 interface pinout table
| Pin | Signal name | I/O diagram | Voltage domain |
|---|---|---|---|
| 1 | VTREF | G | A |
| 2 | TMS/SWDIO | B/C | A |
| 3 | GND | H | NA |
| 4 | TCK/SWCLK | B | A |
| 5 | GND | H | NA |
| 6 | TDO/SWO | A | A |
| 7 | KEY (NC) | NA | NA |
| 8 | TDI | B | A |
| 9 | GND | H | NA |
| 10 | nSRST | E | A |
| 11 | NC | I | NA |
| 12 | RTCK/TRACECLK | A | A |
| 13 | NC | I | NA |
| 14 | SWO/TraceD0 | E | A |
| 15 | GND | H | NA |
| 16 | nTRST/TraceD1 | E | A |
| 17 | GND | H | NA |
| 18 | DBGRQ/TraceD2 | A | A |
| 19 | GND | H | NA |
| 20 | DBGACK /TraceD3 | A | A |
In the above e2e post, the attempt was made with it seems a Mictor-38 connector, where the Hercules ETM signals mapped pretty well.
Table 4. Mictor 38 interface pinout table
| Pin | ETMv3/TPIU | ETMv2 | ETMv1 | I/O diagram | Voltage domain |
|---|---|---|---|---|---|
| 1 | NC | NC | NC | NA | NA |
| 2 | NC | NC | NC | NA | NA |
| 3 | NC | NC | NC | NA | NA |
| 4 | NC | NC | NC | NA | NA |
| 5 | GND | GND | GND | H | NA |
| 6 | TRACECLK | TRACECLK | TRACECLK | A | B |
| 7 | DBGRQ | DBGRQ | DBGRQ | B | B |
| 8 | DBGACK | DBGACK | DBGACK | A | B |
| 9 | nSRST | nSRST | nSRST | E | B |
| 10 | EXTTRIG | EXTTRIG | EXTTRIG | B | B |
| 11 | TDO | TDO | TDO | A | B |
| 12 | VTREF | VTREF | VTREF | F | B |
| 13 | RTCK | RTCK | RTCK | B | B |
| 14 | VSUPPLY | VSUPPLY | VSUPPLY | Reserved | NA |
| 15 | TCK | TCK | TCK | B | B |
| 16 | TRACEDATA[7] | TRACEPKT[7] | TRACEPKT[7] | A | B |
| 17 | TMS | TMS | TMS | B | B |
| 18 | TRACEDATA[6] | TRACEPKT[6] | TRACEPKT[6] | A | B |
| 19 | TDI | TDI | TDI | B | B |
| 20 | TRACEDATA[5] | TRACEPKT[5] | TRACEPKT[5] | A | B |
| 21 | nTRST | nTRST | nTRST | D | B |
| 22 | TRACEDATA[4] | TRACEPKT[4] | TRACEPKT[4] | A | B |
| 23 | TRACEDATA[15] | TRACEPKT[15] | TRACEPKT[15] | A | B |
| 24 | TRACEDATA[3] | TRACEPKT[3] | TRACEPKT[3] | A | B |
| 25 | TRACEDATA[14] | TRACEPKT[14] | TRACEPKT[14] | A | B |
| 26 | TRACEDATA[2] | TRACEPKT[2] | TRACEPKT[2] | A | B |
| 27 | TRACEDATA[13] | TRACEPKT[13] | TRACEPKT[13] | A | B |
| 28 | TRACEDATA[1] | TRACEPKT[1] | TRACEPKT[1] | A | B |
| 29 | TRACEDATA[12] | TRACEPKT[12] | TRACEPKT[12] | A | B |
| 30 | Logic 0 | TRACEPKT[0] | TRACEPKT[0] | A | B |
| 31 | TRACEDATA[11] | TRACEPKT[11] | TRACEPKT[11] | A | B |
| 32 | Logic 0 | PIPESTAT[3] | TRACESYNC | A | B |
| 33 | TRACEDATA[10] | TRACEPKT[10] | A | B | |
| 34 | Logic 1 | PIPESTAT[2] | PIPESTAT[2] | A | B |
| 35 | TRACEDATA[9] | TRACEPKT[9] | TRACEPKT[9] | A | B |
| 36 | TRACECTL | PIPESTAT[1] | PIPESTAT[1] | A | B |
| 37 | TRACEDATA[8] | TRACEPKT[8] | TRACEPKT[8] | A | B |
| 38 | TRACEDATA[0] | PIPESTAT[0] | PIPESTAT[0] | A |
B |
Questions:
Has anyone been able to successfully use ETM trace with a Coresight-20 connector with any toolset? Should this work with the above signal connections?
Has the Mictor-38 been proven to work for ETM trace?
Do we know if a JLINK with CCS would work to enable ETM trace?
Thanks!
--Gunter
