AWR2188EVM: Lua example run issue

I apologize for the delay, I have escaped this to apps manager.

This post was reassigned to another engineer to solve it, sorry for the delay.

Hi Dara Ros, 

May i know, whether are you using the ES1 or ES2 Chip ? 

What is the DCA2000 hardware Rev.A or Rev.B board ? 

whether have you modified the DCA2000 hardware ?

Could you please check whether are you able to communicate with DCA2000? by giving the ping cmd. 

ping 192.168.33.30

ping 192.168.33.180

Thank you,

Yogeshwaran Raguraman

Hello Raguraman,

We aren't sure of the Chip ES version number. All the software package version numbers and release date are mentioned in the OP. Following is about the hardware that we currently have in-house.

• AWR2188 EVM - PROC203 - Rev.B (Assy REV: 001; FY24-25/01416000102)
• DCA2000 EVM - PROC202 - Rev.A with no modifications (Assy key: 001; FY24-25/01506000101)
• Both of the addresses could be pinged.

We are looking forward to hearing from you soon.

Best.

Dara Ros

Hi Dara, 

Please take help from our FAE's to find whether are you using the ES1 chip or ES2Chip, 

if it is ES1 chip then we need to use mmWave DFP 4.0.5.0 -- and mmwave_studio_04_05_02_00

if it is ES2 chip then we need to use mmWave DFP 4.0.6.2 -- and mmwave_studio_04_05_03_01

Thank you,

Yogeshwaran Raguraman. 

YOGESHWARAN RAGURAMAN  

The software package pair mentioned below is what we have and use for our initial bring-up. In addition to version number of this two software, the original post also indicated the example release date and the DCA2000 version.

YOGESHWARAN RAGURAMAN said:

mmWave DFP 4.0.5.0 -- and mmwave_studio_04_05_02_00

Hi Dara Ros, 

Step 1: Open Cmd 

Step 2: Go to this path: C:\ti\mmwave_studio_04_05_02_00_External\mmWaveStudio\PostProc> 

Step 3: Give this cmd  "DCA2000_CLI.exe get_status cli_version cf.json" -- tell me what the CLI version is you currently using. 

Step 4: Give this cmd "DCA2000_CLI.exe get_status sw_version cf.json" -- tell me what the SW version is you currently using. 

Could you please send AWR2188 Chip photo ? 

For ES2 -- > XA2188A

Currently, if you are using the ES1 Chip, please migrate it to the ES2 chip 

if you are using the ES1 chip, 

I am just attaching the video here - use the same DFP version and mmwavestudio which is showed in the video to make it work on the ES1 chip. 

tidrive.ext.ti.com/.../1af29517-8cd7-4b8d-8111-f25c91203bf0

Access code : 75sVmy;L

Thank you, 

Yogeshwaran Raguraman. 

Hello Yogeshwaran,

Thanks for suggesting these debug steps. Below is information from our last communication from another thread.

The AWR2188 Chip is XA2188 only. So, according to this and information you mentioned previously, it seems we are using ES1.0 with the correct software package.

{quote}

Below is what we got.

C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>ping 192.168.33.30

Pinging 192.168.33.30 with 32 bytes of data:
Reply from 192.168.33.30: bytes=32 time<1ms TTL=128
Reply from 192.168.33.30: bytes=32 time<1ms TTL=128
Reply from 192.168.33.30: bytes=32 time<1ms TTL=128
Reply from 192.168.33.30: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.33.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>ping 192.168.33.180

Pinging 192.168.33.180 with 32 bytes of data:
Reply from 192.168.33.180: bytes=32 time<1ms TTL=64
Reply from 192.168.33.180: bytes=32 time<1ms TTL=64
Reply from 192.168.33.180: bytes=32 time<1ms TTL=64
Reply from 192.168.33.180: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.33.180:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>DCA2000_CLI.exe get_status hw_version cf.json
HW_VERSION: DCA2000EVM Rev A

C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>DCA2000_CLI.exe get_status sw_version cf.json
SW_VERSION: 0.9.6a

C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>DCA2000_CLI.exe get_status cli_version cf.json
0.9.5
C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>DCA2000_CLI.exe get_status state cf.json
ONLINE

C:\ti\mmwave_studio_04_05_02_00\mmWaveStudio\PostProc>DCA2000_CLI.exe get_status capture_status cf.json
WAITING_FOR_DATA

{quote}

Hi Dara Ros, 

ES1 chip will be no longer to use. requesting you to migrate to board to ES2 chip. 

if you are still using the ES1 chip, please use the mentioned DFP software and mmwavestudio attached in the video. 

tidrive.ext.ti.com/.../1af29517-8cd7-4b8d-8111-f25c91203bf0

Access code : 75sVmy;L

if you are encountering the issue with "waiting for the data capture" then please repowering all the boards after "waiting for data capture" just onetime.

Thank you, 

Yogeshwaran Raguraman. 

Recycling power doesn't help.

How do we access this tidrive.ext.ti.com? My team and I could not pass the login page.

;

https://tidrive.ext.ti.com/u/jjKhICMyoQ2cMqEG/1af29517-8cd7-4b8d-8111-f25c91203bf0?l

Access code : 1QZ6'vLV

just directly click this link and open it. it will ask for the access code. just enter the above-mentioned access code. 

if you are still facing an issue, please let me know. 

Thank you,

Yogeshwaran Raguraman. 

Thanks YOGESHWARAN RAGURAMAN for the video.

I have a couple of questions:

1. The AWR2188EVM HW we have is revB board which doesn't have SW4 and SW5. According to "AWR2188EVM_documentation_Rev_B/Rev_B/PROC203B_AWR2188LOPEVM.pdf", to my understanding they are always on, aren't they? If not, would we set them on via Lua script?
2. I noticed that on you device manager there wasn't any XDS110 Class Application/User UART Port, and you set both the FTDI_Com_Port and the UART_COM_Port to the same COMPort (the AR-DevPack-EVM-012D). Why is that?

Thanks,

Dara Ros

Hi Dara Ros, 

Dara Ros said:

The AWR2188EVM HW we have is revB board which doesn't have SW4 and SW5. According to "AWR2188EVM_documentation_Rev_B/Rev_B/PROC203B_AWR2188LOPEVM.pdf", to my understanding they are always on, aren't they? If not, would we set them on via Lua script?

I'm not able to understand, what do you mean by the SW4 and SW5 ? 

Dara Ros said:

I noticed that on you device manager there wasn't any XDS110 Class Application/User UART Port, and you set both the FTDI_Com_Port and the UART_COM_Port to the same COMPort (the AR-DevPack-EVM-012D). Why is that?

In that video, i have mistakenly set the COM port to UART, for the running the Lua script UART COM Port is not necessary, so you can ignore setting the UART COM port. 

Ensure that FTDI COM Port is properly set in the Lua script as per the device manager. 

Thank you,

Yogeshwaran Raguraman. 

Hi Dara, 

Dara Ros said:

the revision of our AWR2188EVM board does not include these switches.

Please Ignore those switches which is not present in your board. 

Thank you, 

Yogeshwaran Raguraman. 

Is it possible to directly control the 2188 through the mmwave_studio_04_05_02_00? That way we'd be able to define sensor configuration to see if it's chirping any signal.

I see that the AWR2188EVM also has FTDI-USB and XDS-USB ports.

Thank you,

Dara

Hi Dara, 

Yes you can directly control the AWR2188 from the MmStudio, you can connect the FTDI-USB_1 for primary radar device and FTDI-USB_2 for the secondary radar device to control it. 

But without DCA2000 we will not be able to see the data capture and post processing 

Thank you, 

Yogeshwaran Raguraman.  

Hello Yogeshwaran,

In order to do so, do you have any documentation on how to manage the device directly like setting up radar's configuration and starting the sensor?

I see that the AWR2188 has a mux switch that was set to _HS for DCA2000EVM control. Would we need to set it to the opposite side for controlling the 2188-FTDI-USB1?

On the Board selection, I choose CZ_SINGLE_CHIP for Board Type.

[11:59:55]
[11:59:55] @MWS_API_START
[11:59:55] xw_status = mws.deviceConfiguration(0, 0, 107, "", 10000, 0, 2)
[11:59:55] @MWS_API_END
[11:59:55] -- RS232 is disconnected
[11:59:55] --xw_status = 0
[11:59:56] DeviceIndex:0; FTDI SerialNumber:FTAZ4Q5R; Description:Primary-Radar-FTDI
[11:59:56] --xw_return = 0
[12:00:00]
[12:00:00] @MWS_API_START
[12:00:00] xw_status = mws.selectBDType(1, 0, 0, 1, 0, 0, 0, 29)
[12:00:00] @MWS_API_END
[12:00:00] --xw_status = 0

Best,

Dara

Hi Dara, 

Dara Ros said:

In order to do so, do you have any documentation on how to manage the device directly like setting up radar's configuration and starting the sensor?

You can refer the ICD document for the radar RF / chirp / frame / waveform configuration and starting the sensor. 

Dara Ros said:

I see that the AWR2188 has a mux switch that was set to _HS for DCA2000EVM control. Would we need to set it to the opposite side for controlling the 2188-FTDI-USB1?

Move the mux switch from HS_1 to other side, if you are directly controlling the AWR2188 without using the DCA2000. 

Thank you, 

Yogeshwaran Raguraman.