• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 438 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.

Original question:

AWR1843: How to flash the mmwave automotive labs in a custom board

AWR1843: SRR lab - GUI only shows target detected points when "advFrameCfg" and "sensorStart" commands are sent - custom board

Jairo Gallardo
Expert 1640 points
Part Number: AWR1843

Hi, I am testing the SRR lab in a custom AWR1843 board but the GUI does not starts, but the MRR lab works ok. I do the same test with the AWR1843BOOST EVK and both labs runs ok, I am using the original code from tirex, I only have changed the data UART pins for the tests in my custom board

changes in pins respect to awr1843boost evk:

UARTB TX

pin F14 to pin P10

CAN

TX: E14  to   F14

RX: D13  to  H14

we are not using the TM4C1294NCPDTT3

error detected in custom board: we left the pin SOP1 unconnected

where could I find info about the messages interchange between GUI and awr1843?, I need to understand what are the requirements that need the GUI to send the commands automatically, I also dont understand why the MRR lab works ok but the SRR labs does not works

thanks

  • 0
    TI__Guru*** 138349 points

    Hi

    Sorry for the confusion.

    On the AWR1843BOOST, the SRR and MRR demos in Automotive Toolbox 3.2 start in different ways.

    Here is the expected behavior for the demos on AWR1843BOOST EVM with Automotive Toolbox 3.2

    1) SRR demo

    The demo will start after receiving the following two comands: advFrameCfg; sensorStart

    Please see

    mmwave_automotive_toolbox_3_2_0__win\mmwave_automotive_toolbox_3_2_0\labs\lab0002_short_range_radar\gui\load_config.m

    Please see SRR_MSS_CLISensorStart() in

    mmwave_automotive_toolbox_3_2_0\labs\lab0002_short_range_radar\src\mss\mss_srr_cli.c

    2) MRR demo

    The demo will start upon boot up.

    Please see

    mmwave_automotive_toolbox_3_2_0\labs\lab0007_medium_range_radar\src\mss\mss_srr_cli.c

    You will notice in this file, that the two commands are hardcoded in the code and will execute upon bootup.

        MRR_MSS_CLIAdvancedFrameCfg(1, dummy);
         
        MRR_MSS_CLISensorStart(2, dummy);

    Note that in future releases of the Automotive Toolbox we plan to implement for MRR the same start up sequence as SRR. We came to the conclusion that this will be less confusing.

  • 0 in reply to Cesar
    Expert 1640 points

    Ok you say that both labs starts in different ways, but both starts automatically right?, I mean, when I load any of those labs to the awr1843boost evk the GUI starts by itself when I open it, I dont have to send manually any command, with my custom board the MRR lab GUI starts automatically when I open it but the SRR lab needs to manually enter both commands to start, here I want to explain something in detail:

    we have 2 UARTs:

    UART 1 (user):

    pins N4 and N5 (same as texas evk)

    UART 2 (data)

    changed from pin F14 to pin P10

    So in the tests we have 2 of this uart-usb converters and we open a terminal to see dat from the user UART, here we see the "SrrTIDesign:/>" and from that terminal we send the "advFrameCfg" and "sensorStart" commands to start the GUI, once done we see some points in it.

    the query is, If in the texas evk everything works ok why in the custom work I have this issue?, I would understand that, for example, in the custom board none of the labs works, but MRR works and SRR does not works, could be something relationated with the pin SOP1 that I have mentioned in the post or maybe the fact that we have 2 UARTs separated?

  • 0 in reply to Jairo Gallardo
    TI__Guru*** 138349 points

    Hi,

    If I understand correctly, if you don't open the terminal but you only run the GUI executable, then you don't see any detection points on the GUI. Is this correct?

    If this is correct, it means that the matlab GUI can't send the commands through the UART but the terminal can send them.

    This would be a matlab serial port problem

    thank you

    Cesar

  • 0 in reply to Cesar
    Expert 1640 points

    Hi, sorry if I was not clear, yes, if I don´t send the commands from the terminal the GUI opens but no points are shown, when I send the commands I can see a higher current consumption and the GUI works normally

  • 0 in reply to Jairo Gallardo
    TI__Guru*** 138349 points

    Hi,

    Based on your behavior, it means that for SRR the Matlab GUI can't send the commands. Do you see any errors from Matlab?

    In order to further debug you will need to run the gui from matlab and set breakpoints in the matlab code

    In order to run the matlab gui  with matlab you need to run as follows:

    srr_ti_design_visualization()

    The matlab code you should check

    mmwave_automotive_toolbox_3_2_0\labs\lab0002_short_range_radar\gui\load_config.m

    Thank you

    Cesar

  • 0 in reply to Cesar
    Expert 1640 points

    I have included these lines in the SRR code and now works

      SRR_MSS_CLIAdvancedFrameCfg(1, dummy);
      SRR_MSS_CLISensorStart(2, dummy);

    thanks

  • 0 in reply to Jairo Gallardo
    TI__Guru*** 138349 points

    Hi,

    This code update will send the commands when the code executes at boot up without waiting on the matlab gui to send them.

    I will close this thread now. If there are new questions please start a new thread.

    Thank you

    Cesar