• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 207 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWR1843BOOST: AWR1843BOOST and TM4C1294XL launchpad connection

GAGANDIP SINGH DADHWAL
Prodigy 145 points
Part Number: AWR1843BOOST

Hello, team

I am using AWR 1843BOOST with Medium Range Radar (Lab 007) configuration.

My purpose is to take the detections (TLV) from the RADAR to the booster pins where I can take the data and transfer it over TCP/IP to the client application.

Below mentioned is the approach I have taken:

1) I have removed R136 (AR_MSS_LOGGER) and shorted pin 9 of the J5 connector.

2) I have also removed the R128 (AR_RS232TX) and R129 (AR_RS232RX) and shorted the R169(AR_RS232TX) and R166 (AR_RS232RX) of the J6 connector.
With the above approach, I am assuming that detection data (TLV) should come to the BOOSTER PINS J5 or J6.

And I have the following observations:

Ob1). When I try to read data from pin -9 of J5 (which is connected to AR_MS_Logger), I got some data, there was no magic number (Sent at the starting of every data packet in the header) in the raw data.

Ob2). When I try to read data from AR_RS232TX ( Pin 5 of J6) and AR_RS232RX ( Pin 7 of J6), I don't get any data at all. (both on functional Mode and debug/SOP-2 Mode)

Based on the above observations, I am inferring that the

A) AR_RS232 (Rx/Tx) is used to write only the configuration in the AWR, so this might be the reason I am not getting any Detection Data / Data on the AR_RS232(Rx/Tx) pins. Please correct me if I am wrong.

B) I don’t understand why there was no detection data (magic number) on the J5 connector (AR_MSS_LOGGER) in the AWR1843BOOST. Kindly let me know if I am missing something.

C) Since XDS110 creates two ports on the computer when connected using the serial connecter (J8), I infer that AR_RS232(Rx/Tx) is mapped as “config port” and AR_MSS_LOGGER is mapped as “data port”.
Since now I have depopulated R128 and R129, how the config file would be written if I am using the AR_RS232 RX/TX from the J6 ( Please note that I am using Medium Range Radar lab007).

My final objective is to send/receive both configuration data/Detection Data from J6/J5 over TCP/IP.

  • 0
    TI__Guru*** 138329 points

    Hi,

    Here are some related similar threads

    Since you are using a different physical UART the code would have to be modified to change the UART port being used

    thank you

    Cesar

  • 0 in reply to Cesar
    TI__Mastermind 24955 points

    Gagandip,

    Please review the code segment below to see how the Data UART is configured. This is shown as UART-3. This is where the output TLV data is sent.

        /* Pinmux setting */

    /* Setup the PINMUX to bring out the UART-1 */
    Pinmux_Set_OverrideCtrl(SOC_XWR18XX_PINN5_PADBE, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);    
    Pinmux_Set_FuncSel(SOC_XWR18XX_PINN5_PADBE, SOC_XWR18XX_PINN5_PADBE_MSS_UARTA_TX);
    Pinmux_Set_OverrideCtrl(SOC_XWR18XX_PINN4_PADBD, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);    
    Pinmux_Set_FuncSel(SOC_XWR18XX_PINN4_PADBD, SOC_XWR18XX_PINN4_PADBD_MSS_UARTA_RX);

    /* Setup the PINMUX to bring out the UART-3 */
    Pinmux_Set_OverrideCtrl(SOC_XWR18XX_PINF14_PADAJ, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR18XX_PINF14_PADAJ, SOC_XWR18XX_PINF14_PADAJ_MSS_UARTB_TX);

    /* Setup the PINMUX to bring out the DSS UART */
    Pinmux_Set_OverrideCtrl(SOC_XWR18XX_PINP8_PADBM, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
    Pinmux_Set_FuncSel(SOC_XWR18XX_PINP8_PADBM, SOC_XWR18XX_PINP8_PADBM_DSS_UART_TX);

    Did you attempt to run the MRR demo on an unmodified AWR1843BOOST? Were you able to get that working first before making any hardware modifications?

    In the MRR demo, the chirp configurations are hard coded in the application so the software starts at immediately at bootup. This is shown in the MATLAB GUI where you only need to specify the data UART instead of both the configuration UART and data UART.

    Regards,
    Kyle