• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 2053 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR1443: Custom design / Removing XDS110

Koos Habte
Prodigy 210 points
Part Number: IWR1443
Other Parts Discussed in Thread: TIDEP-0091, , TMDSEMU110-U, SEGGER, UNIFLASH

I know there are a lot of posts on this subject, but not everything is clear to me yet. 

I have a few questions on designing a custom board without the TM4C microcontroller. I want to be able to program the Flash memory over UART, and also to program/debug using CCS. 

(1) I plan to put a JTAG connector on the board. So if I flash the 'xwr14xx_ccsdebug_mss.bin' to the flash memory, is the JTAG connector the only necessary connector to be able to develop/program with CCS?

(2) The UART pins will be used for flashing the flash memory. After flashing and switching to Functional mode, can the UART pins be used for communication with an external MCU? (In about the same way as the use of SPI in TIDEP-0091)

(3) Is there any common use case for the SOP1 pin? The manual states that it is used to enter Debug mode, however, I've never needed to use this mode because of the CCS debug capabilities. 

Thank you for your time,

Koos

  • 0
    TI__Mastermind 37500 points

    Hello Koos,

    1) XDS110 - I would suggest using the sprui94 XDS110 External Probe document, to accomodate:

        JTAG - CCS access

        Control UART -  device control

        Master Logger Tx Uart - data UART

    I would copy the connectivity from the XDS110 pages to the mmwave U2 Sensor.

    2) the BP/LP connectors and mechanical structure would allow you to connect the MSP432R401 EVM to your card.  In this case, the TIDEP-0091 Level Sensing code can be used for your card.   

    3) SOP1 is not normally used it can be connected to GND.

    There is a hardware checklist, attached for the IWR1443, you also need to follow the hardware guide, they are attached.

    It is important for the pin muxing and use case, to describe what interfaces you need.

    Note: if you retain the Control UART, and MSS Data Logger - you might be able to recode the Visualizer as a GUI interface.

    Regards,

    Joe Quintal1565.HardwareDesignChecklist_V0p7fix_IWR1443_SWRR150.xlsx 

     

     

  • 0 in reply to Radio-Joe
    Prodigy 210 points
    Hi Joe,

    Thank you for your quick response, it helped a lot.
    The XDS100 debugger seems like a very useful option considering it offers both JTAG and UART. I would have to buy the TMDSEMU110-U then, right?

    However, to finish up my board design I would like to test the JTAG right now. We have a Segger J-Link laying around, but I couldn't get it to work. Is there anything I need to know about connecting it? I connected the four JTAG pins from the IWR1443, the NRST, Ground and 3V3.

    Thanks again.
    Kind regards,
    Koos
  • 0 in reply to Koos Habte
    TI__Mastermind 37500 points
    Hello Koos,
    I can only think if the JTAG items, TMS must be '1' when the board is taken out of Reset. Check the TCLK is toggling when you request to read a memory location at bootime. There is a memory map in the datasheet. I have only used the XDS110 with the IWr1443.
    Regards,
    Joe Quintal
  • 0 in reply to Radio-Joe
    Prodigy 210 points

    Hi Joe,

    It appeared that SEGGER just doesn't have support for the IWR1443 in their software. When using the J-Link with OpenOCD I could verify that it was working.

    Thank you for your time.

    Kind regards,

    Koos

  • 0 in reply to Radio-Joe
    Prodigy 210 points
    Hi Joe,

    Two more questions, just to verify.

    1) I got the TMDSEMU110-U, I will need to use the 30-pin expansion header to connect both UART instances, right?

    2) Regarding TIDEP-0091, what I meant to ask is: would it be possible to get the same functionality but over UART instead of SPI? Since the UART isn't used for configuration anyway.

    Kind regards,
    Koos
  • 0 in reply to Koos Habte
    TI__Mastermind 37500 points
    Hello Koos,
    related to question 1 - If you follow the xds110 debug probe, sprui94, Table 2 on page 11 has the 30 pin connector.
    you need to compare the IWr1443 EVM XDS110 pin#
    25, AR_MSS_LOGGER, UART (XDS side) Rx
    33, AR_RS232TX, UART (XDS side) Rx
    34, AR_RS232RX, UART (XDS side) Tx
    35, XDSET_TCK, JTAG ClkOut IEEE1149
    36, XDSET_TMS, JTAG Mode Out IEEE1149
    37, XDSET_TDO, JTAG Serial Data IEEE1149
    38, XDSET_TDI, JTAG Serial Data IEEE1149
    40. AR_NRST_XDS, Reset Out (active low)

    You also need to control SOP0 = '1', SOP2 = (0 operational, 1 flashing)

    Note: you will need to post in the Embedded Processor Forum for XDS110 Probe tool, to determine how Uniflash will work with the mmwave IWR1443, with a passive XDS110. I don't have a working example.

    Note: the OOB Demo visualizer, is expecting a PC - USB connection, you will also need to ask if the XDS110 probe to PC USB, acts the same as the CDS110 embedded as far as USB streams (JTAG, Control UART Tx,Rx, Aux Data UART).

    related to question 2, you could follow the Out of Box demo (UART), and TIDEP 0091 (SPI), for the command side. On the data return,
    you could either send the results over a Control UART, or MSS Data UART.

    Regards,
    Joe Quintal
  • 0 in reply to Radio-Joe
    Prodigy 210 points
    Hi Joe,

    Thanks a lot!

    Kind regards,
    Koos