IWR1642: Minimum required signals for XDS110

Hello
If the customer is going to use an external XDS110, and they want to have a custom connector footprint (they will make their
Own adapter cable).

It depends on what functions are needed from the XDS110
JTAG - needed for debugging
TMS
TDI
TDO
TCK
XDS110_nRST (has to be tied into board nRESET logic)
GND
Note: having the PMIC_PGOOD signal in the custom connector would be a good indicate the DC power is ready
This is an open drain signal, requires a pullup to 3.3v.

Note2: if the customer has a CCS project for loading the flash, and uses SPI or CAN for communication, the Control UART is not required, but suggested.

If the customer is trying to use the XDS110 for flashing
Control Uart Tx
Control Uart Rx
SOP2 with light pulldown on board, 3.3v pullup for flashing, SOP2 not pulled up for operation
GND
Note: SOP0 on main board is pulled up, SOP1 is pulled down.

If the customer is trying to use the XDS110 connection with a modified Visualizer the Emulation – MSS Logger
UART is also needed.

Regards,
Joe Quintal

Hello,
PMIC_PGOOD is not a standard signal, it would have to use a spare pin, and have some customer monitoring. For power monitoring there are also the LDO power quality concerns. If the open-drain IO structure is used for th LDO power supervision, one signal can be used for Power OK. Note: the 1.8v LDO output goes out of regulation at the end of the chirp / frame, this is a momentary condition.

If this is an engineering environment, SOP2 jumper is OK, if this is a manufacturing environment, is the jumper accessible?

The MSS Logger UART is used for data export for Out of Box demo applications. On the IWR1642 BOOST schematic, the signal name is AR_MSS_LOGGER, pin F14. If you trace the signal name you will see it goes to the XDS110.

The Visualizer software sends control commands over the Control UART / USB port, The Visualizer software receives data from the mmwave sensor over the MSS Logger UART / USB port.

The Visualizer software if the customer used it for engineering evaluation would need to be modified for the XDS 110 implementation, if its not a USB port. If Uniflash can be used for flashing, customized with remote SOP2 if needed, then the Visualizer can be modified by customer (custom Visualizer) to test their product. Note: the data export of the MSS Logger data, or if SPI is used, is the customization.

The customer will have to make a custom cable to distribute the signals to the standard XDS110 external pod connections. This way the customer board can have a minimal connector.

Using the sprui94 document, for external XDS110 Debug Probe,
JTAG
TMS - with onboard pull down
TDI
TDO
TCK
TnRST - to onboard Reset logic

additional for flashing QSPI
PMIC_PGOOD
SOP2- force if jumper is not available
Control UART - Tx
Control UART - Rx

if Out of Box demo is supported
MSS_Logger UART - Tx

Regards,
Joe Quintal

Hello Katsuhiro,
The PMIC_GOOD can be optional, the customer might consider an LED to a pullup resistor, for engineering test.
Can be removed for production.

The MSS_LOGGER_UART Tx is an Emulation UART, I think this would be EMU1.
The Control UART Tx, Rx - is needed
The SOP2 pullup connection is needed for flashing.
The nRESET (nRST) needs to be controlled by XDS110 - low for reset.

The Visualizer would need to be customized to get the data from the PC-XDS110 instead of USB.

Regards,
Joe Quintal

Hello,
The XDS110 Debug Probe, sprui94 shows the available signal connections

The customer should consider making a customer adapter cable from a smaller foot print, than the 3 connections.

2.3 CTI-20
supports
1 - TMS
2(15) - NTRST or nRESET
3 - TDI
7 - TDO
8 - GND
11 - TCK
13 - GPIOOUT0 - if SOP2 is pulled up over XDS110 interface
17 - GPIOIN0 - PMICGOOD or POWER GOOD (optional)

2.4 Aux - 14pin
5 - GND
12 - UARTTx (need to check which end is specified)
14 - UARTRx (need to check which end is specified)

2.5 Probe Expansion Header
9 - GND
17 - UART7 Rx (this is connected to MSS_Logger_TxUart

Questions about customizing the Visualizer, need a separate E2E. The source is available. The customer should consider
making a hardware interface to the PC where the (Control UART) Aux-12, Aux-14 are the Control Port, and PEH-17 MSS_Logger_UART
is the data UART over an RS232 to USB interface.
Please make Visualizer questions a separate E2E.

Thank you
Joe Quintal

Hello, The signal names for the mmwave sensor are related to the mmwave sensor end.
At the other end Rx <-> Tx.
Regards,
Joe Quintal

yes for a UART, like the SPI communication the source and destination ends of serial communication get reversed
mmwave sensor Tx ----> Host Processor (XDS110) Rx
mmwave sensor Rx <----- Host Processor (XDS110) Tx
REgards,
Joe Quintal