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

Hi,

If I understand correctly your description,

• developed a custom board with AWR1843
• not using TM4C1294NCPDTT3 on the custom board.
• modified the MRR demo (lab007) to export the data through CAN
• tried several demos, the GUI does not work

I am not clear if you have modified all the demos to export the data through CAN. Please note that the demos export the data through UART and that the GUIs require the use of UART. You would need to develop a new GUI to be used with CAN

thank you
Cesar

Hi, all this is correct

• developed a custom board with AWR1843
• not using TM4C1294NCPDTT3 on the custom board.

except this:

- modified the MRR demo (lab007) to export the data through CAN

because I modified this lab to export data through CAN and UART

and this:

- tried several demos, the GUI does not work

because the GUI works with the MRR lab and the CAN too

" I am not clear if you have modified all the demos to export the data through CAN. Please note that the demos export the data through UART and that the GUIs require the use of UART. You would need to develop a new GUI to be used with CAN "

sorry if I was not clear, I know that the GUI uses the UART, that is why I modified the UART pins in my custom board and in the MRR lab which is the only one that is working for me I see data through the GUI and CAN at same time with no problem, in the other labs I cant see data throught UART or CAN but all the labs are flashed ok

thanks

Hi, I forget to mention something else:

we are using MX25L3233F flash instead MX25V1635FZNQ, we use this guide to choose a compatible flash "Flash Variants Supported by the mmWave Sensor"

Hi,

If you are able to run the MRR demo this means that the flashing process, Uart mapping is correct.

So, there should be no problem running the Parking Assistance demo.

Could you perform the following steps:

1) Flash the Parking Assistance Demo on the custom board

2) Power on the board to run the demo

3) Start a serial console such as Tera Term

4) In Tera Term,  connect to the User Uart COM Port at 115200 Baud Rate

5) Type Enter.

6) If the demo runs correctly, you should see the following in Tera Term terminal:

PaTIDesign:/>

Do you see this prompt?

thank you

Cesar

Hi, yes, I can see that message in both boards, the AWR1843BOOST and in my custom board, in the AWR1843BOOST the GUI works but in the custom board I start the GUI but does not works, what could be the issue?

thanks

Hi, you say:

" At the "PaTIDesign:/>" prompt send following commands: "advFrameCfg" and "sensorStart" "

Where can I find more info (docs or videos) about this interchange of messages between the EVK and the GUI?

Now the automated parking lab works in my custom EVK, we were connecting the data UART after starting the GUI so in the terminal we could see a timeout warning and the GUI did not work, so we started the GUI after connect the data UART and works, but, for example, the SRR lab shows us the "PaTIDesign:/>" via terminal but the GUI does not work

thanks

Hi, I will try to do that test but I still don't understand why do I need to send those commands to some labs but other labs run automatically

labs that run ok in both boards (custom and awr1843boost evk):

- MRR beamsteering

- MRR

- parking assitance

labs that does not work: ("PaTIDesign:/>" message is shown)

- ODS

- SRR

- ODD

any suggestion?, thanks

Hi,

I think there is some confusion,

The fact that you are seeing "PaTIDesign:/>" tells me that the evm (Board) is running the Parking Assistance demo.

This would explain why the MRR and PA demos are running.

If you want to run the SRR demo, you will need to flash the SRR binaries on the board first as described in the SRR demo documentation. After that you will need to run the SRR GUI

Thank you

Cesar

Hi, when I send the "advFrameCfg" and "sensorStart" commnads the GUI starts but the detection of the targets are not so good, what coould be wrong with the SRR lab that needs this commands to start?, any suggestions to debug this issue or a doc where explains the messages interchange between the GUI and AWR1843?

thanks

But if is not an issue between GUI and AWR1843 why do I need to send the commands "advFrameCfg" and "sensorStart" in my custom board?, in the texas EVK the labs run automatically, I dont need to introduce this commands, should I open a new thread?