Connector Mictor 38-pin (Debug + Trace signals)
|
Signal
| Pin
| | Pin
| Signal
|
| | | | |
*) | 1 | | | 2 | *) |
*) | 3 | | | 4 | *) |
*) | 5 | | | 6 | *) |
N/C | 7 | | | 8 | *) |
RSTIN- | 9 | | | 10 | EVTI- |
TDO | 11 | | | 12 | VTREF |
*) | 13 | | | 14 | *) |
TCK | 15 | | | 16 | *) |
TMS | 17 | | | 18 | *) |
TDI | 19 | | | 20 | MDO05 |
RST- | 21 | | | 22 | MDO04 |
MDO11 | 23 | | | 24 | MDO03 |
*) | 25 | | | 26 | MDO02 |
*) | 27 | | | 28 | MDO01 |
*) | 29 | | | 30 | MDO00 |
N/C | 31 | | | 32 | EVTO- |
N/C | 33 | | | 34 | MCKO |
*) | 35 | | | 36 | MSEO1- |
N/C | 37 | | | 38 | MSEO0- |
| | | | |
Connect Pin 39,40,41,42 and 43 to GND |
Signal recommendations for Mictor 38-pin
The AVR32 Nexus debugger and trace is based on the Nexus Autofocus Probe (NAF) technology, which supports a wide range of architectures with up to 16 bit MDO AUX port width.
Most pins of the probe are internally connected, but not used for AVR32 debugging and trace. Therefore all pins marked with *) should not be connected at the target connector!
- TDI, TDO, TCK, TMS and RST- should be connected directly to the CPU. Don't connect serial resistors or RC combinations to the lines.
- All trace signals should also be routed straight from CPU to the Mictor connector.
- Avoid routing the JTAG signals close to the NEXUS signals.
- VREF is just a sense input and can be connected directly to target VDD, or optional (recommended) with a serial resistor max. 1kOhm.
Target Connector description and layout
Mictor 38-pin
Order No
TE Connectivity part numbers for suitable receptacles (for target)
TE 2-5767004-2 RoHS compliant
TE 2-767004-2
TE 767054-1 (suggested by Motorola)
TE 767061-1
TE 767044-1 : Board-to-Board Type: Coplanar
TE Connectivity
Probe
|