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.

IWR1642BOOST: Connect to IWR1642 BOOST with uart

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642

Hi


I designed a board to communicate with IWR1642 Boost Rev B radar. I used UART and j6,j5 for this connection.


Confige and "done" are sent and received through RS232 ? Is the output data received via MSS_logger? If that's true I'm not getting anything from either RS232 or MSS_logger. where is the problem from?

I removed R129 and replaced R166 and R169 with 0 ohm resistors.


Baud rate is 115200 for RS232 and 921600 for MSS.


Thanks

  • Hi Meisam!

    Thanks for your question! 

    It looks like you are trying to route the UART signal away from the XDS110 and towards the booster pack header connectors. Is there a particular reason why? UART connection to the device is available across the XDS110 interface. 

    Based on your report, R128 is still populated. This means the AR_RS232TX net is connected to the XDS110 and the booster pack connectors at the same time. I would recommend removing it.

    Let me know if you have any more questions. 

    Very Respectfully, 

    Blake

  • Hi Blake

    Thanks for your response.

    We want to communicate with the radar using LAN connection, so we designed a board in which the micro stm32f107 is used. The settings are sent to the interface board through LAN and sent to the radar through UART in the interface board.
    As you said, we removed R128, but the problem still exists.
    We used interrupt for UART communication.

    Please give me a solution


    Thanks

    Meisam

  • Do you have some kind of USB2UART interpreter? I would recommend directly connecting to the mmIC from your PC across this interpreter. Use a terminal software such as TeraTerm or PuTTY to test that you can communicate to the MMIC. 

    If this works than you may have an issue with your interface board.