IWRL6432: IWRL6432Boost + DCA1000

Right now we are following this URL to configure DCA1000 and IWRL6432 to capture raw data.

I have changed the LUA script accordingly and ran it. I can see the following,

1) RS232 connectiviti status => SUCCESS

2) APPSS FW Download => SUCCESS

but it seems like the mmwavestudio is failing when it tries to download the FEC file

i have checked the location of the file which the mmwave studio is searching for and i don't see that file.

is the file is in a  different location? or do we need to download that file from somewhere else in the TI website?

since i see some patchfiles.. do i need to change the LUA script to use those files instead of what it's looking for? if yes.. which file we should choose?

Hello,

Paths are as shown below. You do not need to load all of these for basic raw ADC data capture, but just for reference these are locations.

We are going to be updating the LUA script to be used for mmWaveStudio 6432 in our next toolbox release. I have attached it to this reply for your convenience.
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/3324.IWRL6432_5F00_common_5F00_device_5F00_setup.lua

Best Regards,

Pedrhom

Just t o be sure we directly copy pasted the LUA script you provided and made sure that the "firmware_directory_base" is accordingly changed to our PC. (also changed the COM port number according to our device enumeration)

Still we get the same error as yesterday.  COM port get successfully connected. APPSS firmware gets successfully uploaded. But the mmwave studio cannot be seem to find the "rfs_firmware". 

we are using "MMWAVE_L_SDK_05_04_00_01" but there are no "mmwave_rfs_rprc.bin" inside "rfsfirmware\xWRL6432" directory.

Is there a possibility when you made the SDK public your internal system missed that file? 

Because we downloaded the SDK on a different PC on a different region of the world and it still is missing.

Thanks

Hello,

rfs_firmware should just be the patch one for ES2 devices. rfs_firmware without the patch is for older silicon (ES1). If you comment out that line can you do raw data capture all the same?

Best Regards,

Pedrhom

As you suggested we first tried commenting out the line that contains "rfs_firmware" and it resulted with following error on the mmWave Studio

Then we tried changing the binary file to mmwave_rfs_patch.bin since that is the file that is not being used by the LUA script. But it resulted in following error.

Any idea what else we can try? 

Hello,

You are not loading the right file for line 59 of the script. It needs to be mmwave_rfs_patch_rprc.bin not mmwave_rfs_patch.bin

Best regards,

Pedrhom

So what you are saying is, 

From"""

Hello,

I went back and grabbed the 3324.IWRL6432_common_device_setup.lua that I linked and ran it. I changed nothing except the rs232 port and it worked fine. You can see below the two files it uses is mmwave_plt_rfeval_rprc.bin for APPSS Fw Download and mmwave_rfs_patch_rprc.bin for FECSS Fw Download. For a reason I'm not sure about, in the log you are showing me it is grabbing "mmwave_rfs_patch.bin" for FECSS Fw Download which is incorrect. It needs to be mmwave_rfs_patch_rprc.bin as mentioned in my prior reply.

Best Regards,

Pedrhom

So since you mentioned that it worked on your end. what we tried was. completely reinstalling the mmWave SDK related to IWRL6432 and mmwave studio related to IWRL6432 from scratch. 

Suprisingly that newly installed versions had all the files required. So just changing the COM port in t he RS232 was enough to make it work. 

But we are now ran into a a another issue. As you know we are trying to collect raw ADC data from IWRL6432 using the DCA1000 (https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.10.00.13&node=A__AGTrhNYW8jE6cMxbovlfaA__radar_toolbox__1AslXXD__1.10.00.13) by following above descriptions. 

In there it says,

1) Provide a binary file to record the data
2) Press DCA START RECORD

3) Press START on Trigger mode dropdown (We are using the SW_TRIG option)

4) Once the Data is recorded press PostProc button. 

But in the output we see it's saying NO LVDS data. 

When we searched in the internet we saw multiple unresolved threads related to DCA100 and IWRL6432. Does that means this is a known issue on the software stack? that we can't use DCA1000 to record raw data from the IWRL6432? or is this something completely different. 

Just FYI. we didn't do anything extra on the configs. Only the steps shown in the screenshots of the above toolbox link. 

Following images shows the power supply and our setup. Just in case you need to see them.

Just in case you need to look into the LOG of the mmwave studio. i will copy paste the LOG here too.

GM: Constructor
GM: Tue Jul 23 11:30:50 2024
RSTD.Transmit("/Settings")
[11:30:50]
[11:30:50] ### Running Startup script: "C:\ti\mmwave_studio_04_01_00_06\mmWaveStudio\Scripts\Startup.lua" ###
[11:30:50] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
[11:30:50] RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")
[11:30:50] Scripter ignored: Attempt to UnBuild() again or before Build.
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_04_01_00_06\\mmWaveStudio\\Clients\\\\LabClient.dll")
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")
[11:30:50] RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_04_01_00_06\\mmWaveStudio\\RunTime\\SAL.dll")
[11:30:50] RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")
[11:30:50] RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")
[11:30:50] RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")
[11:30:50] RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")
[11:30:50] RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")
[11:30:50] RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")
[11:30:50] RSTD.Transmit("/")
[11:30:50] RSTD.SaveSettings(): Settings saved to "C:\Users\nitin\AppData\Roaming\RSTD\config.xml"
[11:30:50] RSTD.Build()
[11:30:50] RSTD.SaveSettings(): Settings saved to "C:\Users\nitin\AppData\Roaming\RSTD\config.xml"
[11:30:50] RSTD.Transmit("/")
[11:30:50] RSTD.AL_Build()
[11:30:50] RSTD.AL_LoadXml()
[11:30:50] RSTD.Transmit("/")
[11:30:50] RSTD.AL_Init()
[11:30:50] RSTD.Clients_Build()
[11:30:50] GM: Init
[11:30:50] GM: Loaded 'C:\ti\mmwave_studio_04_01_00_06\mmWaveStudio\Clients\\LabClient.dll'
[11:30:50] GM: 1 Guest (s) init
[11:30:50] GM: 1 Module(s) init
[11:30:50] GM: 2 Tab (s) init
[11:30:50] RSTD.Client_LoadXml()
[11:30:50] xw_status = mws.GuiVersion()
[11:30:50] --GuiVersion = 4.1.0.6
[11:30:51] Matlab Runtime Engine is installed
[11:30:51] [RadarAPI]: Starting Matlab Engine..
[11:30:54] [RadarAPI]: Matlab Engine Started!
[11:30:54] xw_status = mws.RadarlinkVersion()
[11:30:54] --RadarlinkVersion = 1.0.1.3(11/7/22)
[11:30:54] xw_status = mws.StudiolinkVersion()
[11:30:54] --StudiolinkVersion = 1.1.0.2(8/2/23)
[11:30:54] xw_status = mws.GuiVersion()
[11:30:54] --GuiVersion = 4.1.0.6
[11:30:54] s_version = mws.GetPostProcVersion()
[11:30:55] [RadarAPI]: mws.LoadSettings('C:\Users\nitin\AppData\Roaming\RSTD\ar1gui.ini')
[11:30:55] xw_status, deviceMapInfo = mws.getFtdiDeviceInfo()
[11:30:55] TESTING = false
[11:30:55] DeviceIndex:0; SerialNumber:FT8CY22D; Description:AR-DevPack-EVM-012
[11:30:55] --xw_status = 0
[11:30:55] RstdNet: Port 2777: Listening..
[11:30:55] --(getNumDevices): xw_return = 0; numFtdiDevices = 1
[11:30:55]
[11:30:55] ***Script completed successfully.***
[11:30:57] s_version = mws.GetPostProcVersion()
[11:30:57] mws.ftdiResetAllDevices()
[11:30:57] --xw_status = 0
[11:30:57] xw_status = mws.selectBDType(0, 0, 1, 0)
[11:30:57] --xw_status = 0
[11:30:57] xw_status = mws.selectComIfType(1, 1000, 0, 2, 0)
[11:30:57] --xw_status = 0
[11:30:57] [RadarAPI]: mws.SelectCaptureDevice("DCA1000")
[11:30:57] [RadarAPI]: Status: Passed
[11:30:57] xw_status = mws.captureCardCfgResetFPGA()
[11:30:57] [RadarAPI]: Sending reset_fpga command to DCA1000
[11:30:57] [RadarAPI]:
[11:30:57] Reset FPGA command : Success
[11:30:57] --xw_status=0
[11:30:58] xw_status = mws.captureCardEthernetCfg("192.168.33.30", "192.168.33.180", "12.34.56.78.90.12", 4096, 4098, 1)
[11:30:58] [RadarAPI]: Sending eeprom command to DCA1000
[11:30:58] [RadarAPI]:
[11:30:58] EEPROM Configuration command : Success
[11:30:58] --xw_status=0
[11:30:58] xw_status = mws.captureCardModeCfg(1,1,1,2, 1, 25)
[11:30:58] [RadarAPI]: Sending fpga command to DCA1000
[11:30:58] [RadarAPI]:
[11:30:58] FPGA Configuration command : Success
[11:30:58] [RadarAPI]: Sending record command to DCA1000
[11:30:58] [RadarAPI]:
[11:30:58] Configure Record command : Success
[11:30:58] --xw_status=0
[11:30:58] xw_status, s_version, s_dllVersion = mws.getCaptureCardFPGAVersion()
[11:30:58] [RadarAPI]: Sending fpga_version command to DCA1000
[11:30:58] [RadarAPI]:
[11:30:58]
[11:30:58] FPGA Version : 2.9 [Record]
[11:30:58]
[11:30:58] [RadarAPI]: Sending dll_version command to DCA1000
[11:30:58] [RadarAPI]:
[11:30:58] DLL Version : 1.0
[11:30:58] --xw_status=0
[11:30:58] xw_status = mws.sopControl(0, 3)
[11:30:58] --xw_status = 0
[11:30:58] xw_status = mws.nReset(0)
[11:30:59] --xw_status = 0
[11:31:00] xw_status = mws.rs232Config(0, 6, 0, 0)
[11:31:01] xw_status, lot, wafer, devX, devY = mws.decodeDieId(3986246656, 1610666180)
[11:31:01] DeviceType:4114x
[11:31:01] SafetyType:0
[11:31:01] ES_PG_Version2
[11:31:01] SOP_MODE:3
[11:31:01] DieId:1073752740.1474789376.3986246656.1610666180
[11:31:01] XTAL_Type:1
[11:31:01] --xw_status = 0
[11:31:01] xw_status = mws.sopDebugFwPreBootCfg(0, 1, 0, 0)
[11:31:02] --xw_status = 0
[11:31:02] xw_status = mws.fwRprcDownload(0, 2, "C:\\ti\\MMWAVE_L_SDK_05_01_00_03\\firmware\\mmwave_dfp\\rfevalfirmware\\appss\\mmwave_plt_rfeval_rprc.bin")
[11:31:13] --xw_status = 0
[11:31:13] xw_status = mws.sopDebugFwPostBootCfg(0, 0, 0, 0, 0, 0)
[11:31:13] --xw_status = 0
[11:31:13] xw_status = mws.fwRprcDownload(0, 0, "C:\\ti\\MMWAVE_L_SDK_05_01_00_03\\firmware\\mmwave_dfp\\rfsfirmware\\xWRL6432\\mmwave_rfs_rprc.bin")
[11:31:21] --xw_status = 0
[11:31:21] xw_status = mws.fwRprcDownload(0, 1, "C:\\ti\\MMWAVE_L_SDK_05_01_00_03\\firmware\\mmwave_dfp\\rfevalfirmware\\rfsatecal\\xWRL6432\\mmwave_rfs_atecal_rprc.bin")
[11:31:22] --xw_status = 0
[11:31:22] xw_status, t_deviceStatus = mws.devicePowerup(0, 0, 0, 0)
[11:31:23] -----------rfEvalDevAppStsGet-----------
[11:31:23]
[11:31:23] [DFP API]xw_status, response=mws.rfEvalDevAppStsGet(0)
[11:31:23] --[[ Response
[11:31:23] c_GenVerNum = 3
[11:31:23] c_MajorVerNum = 0
[11:31:23] c_MinorVerNum = 8
[11:31:23] c_BuildVerNum = 8
[11:31:23] c_Year = 22
[11:31:23] c_Month = 11
[11:31:23] c_Date = 14
[11:31:23] c_Reserved = 0
[11:31:23] h_FwState = 32776
[11:31:23] c_XtalType = 1
[11:31:23] c_DigPllStatus = 1
[11:31:23] c_AppCoreClockType = 3
[11:31:23] c_SafetyType = 0
[11:31:23] h_CoreFreqFcount = 3210
[11:31:23] c_PlatformId = 0
[11:31:23] c_RfType = 0
[11:31:23] c_TestTarget = 0
[11:31:23] c_TestStatus = 255
[11:31:23] w_reserved1 = 0
[11:31:23] ]]
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23] Boot Successful; FwState:0x8008
[11:31:23] --xw_status = 0
[11:31:23] -----------fecDevicePowerOn-----------
[11:31:23]
[11:31:23] [DFP API]xw_status=mws.fecDevicePowerOn(0,{h_XtalClkFreq=10240,c_ClkSourceSel=10,c_PowerMode=0,c_ChirpTimerResol=0,c_FecBootCfg=0,h_Reserved2=0,w_Reserved3=0})
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23] -----------fecDfpVerGet-----------
[11:31:23]
[11:31:23] [DFP API]xw_status, response=mws.fecDfpVerGet(0)
[11:31:23] --[[ Response
[11:31:23] c_MmwlGenVerNum = 3
[11:31:23] c_MmwlMajorVerNum = 0
[11:31:23] c_MmwlMinorVerNum = 8
[11:31:23] c_MmwlBuildVerNum = 8
[11:31:23] c_MmwlYear = 22
[11:31:23] c_MmwlMonth = 11
[11:31:23] c_MmwlDate = 14
[11:31:23] c_MmwlReserved = 0
[11:31:23] c_FecGenVerNum = 3
[11:31:23] c_FecMajorVerNum = 0
[11:31:23] c_FecMinorVerNum = 8
[11:31:23] c_FecBuildVerNum = 8
[11:31:23] c_FecYear = 22
[11:31:23] c_FecMonth = 11
[11:31:23] c_FecDate = 14
[11:31:23] c_FecReserved = 0
[11:31:23] c_RfsRomGenVerNum = 7
[11:31:23] c_RfsRomMajorVerNum = 0
[11:31:23] c_RfsRomMinorVerNum = 8
[11:31:23] c_RfsRomBuildVerNum = 15
[11:31:23] c_RfsRomYear = 22
[11:31:23] c_RfsRomMonth = 11
[11:31:23] c_RfsRomDate = 15
[11:31:23] c_RfsRomReserved = 0
[11:31:23] c_RfsPatchGenVerNum = 0
[11:31:23] c_RfsPatchMajorVerNum = 0
[11:31:23] c_RfsPatchMinorVerNum = 0
[11:31:23] c_RfsPatchBuildVerNum = 0
[11:31:23] c_RfsPatchYear = 0
[11:31:23] c_RfsPatchMonth = 0
[11:31:23] c_RfsPatchDate = 0
[11:31:23] c_RfsPatchReserved = 0
[11:31:23] ]]
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23] -----------fecDieIdGet-----------
[11:31:23]
[11:31:23] [DFP API]xw_status, response=mws.fecDieIdGet(0)
[11:31:23] --[[ Response
[11:31:23] w_DieIdData0 = 1073752740
[11:31:23] w_DieIdData1 = 1474789376
[11:31:23] w_DieIdData2 = 3986246656
[11:31:23] w_DieIdData3 = 1610666180
[11:31:23] Reserved0 = 0
[11:31:23] Reserved1 = 0
[11:31:23] Reserved2 = 0
[11:31:23] Reserved3 = 0
[11:31:23] ]]
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23] -----------rfEvalAteInit-----------
[11:31:23]
[11:31:23] [DFP API]xw_status, response=mws.rfEvalAteInit(0,{c_AteInitAddress=2129856,w_Reserved=0})
[11:31:23] --[[ Response
[11:31:23] c_GenVerNum = 7
[11:31:23] c_MajorVerNum = 0
[11:31:23] c_MinorVerNum = 8
[11:31:23] c_BuildVerNum = 8
[11:31:23] c_Year = 22
[11:31:23] c_Month = 11
[11:31:23] c_Date = 10
[11:31:23] c_Reserved = 0
[11:31:23] ]]
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23] -----------fecRfsDbgCtrl-----------
[11:31:23]
[11:31:23] [DFP API]xw_status=mws.fecRfsDbgCtrl(0,{w_RfsDbgLogAddress=575029248,w_Reserved0=0,w_Reserved1=0})
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23] -----------fecDevClkctrl-----------
[11:31:23]
[11:31:23] [DFP API]xw_status=mws.fecDevClkctrl(0,{c_DevClkCtrl=10,c_FtClkCtrl=0,c_ApllClkCtrl=170,c_Reserved1=0,w_Reserved2=0})
[11:31:23] --xw_status: 0 (SUCCESS)
[11:31:23]
[11:31:23]
[11:31:23] ***Script completed successfully.***
[11:31:41] xw_status=mws.captureCardStartRecord("C:\\ti\\mmwave_studio_04_01_00_06\\mmWaveStudio\\PostProc\\adc_data.bin",1,0,4096)
[11:31:41] [RadarAPI]: Sending start_record command to DCA1000
[11:31:44] -----------sensorStart-----------
[11:31:44]
[11:31:44] [DFP API]xw_status=mws.sensorStart(0,{c_FrameTrigMode=0,c_ChirpStartSigLbEn=0,c_FrameLivMonEn=0,c_Reserved=0,w_FrameTrigTimerVal=0,w_Reserved1=0})
[11:31:44] --xw_status: 0 (SUCCESS)
[11:31:44]
[11:32:11] [RadarAPI]:
[11:32:11] Start Record command : Success
[11:32:11]
[11:32:11] No LVDS data
[11:32:11]
[11:32:11] Record stop is done successfully

Hello,

No LVDS data is a common error, and going to Google and searching "site:e2e.ti.com No LVDS data" will bring up a lot of potential solutions. No LVDS data is pretty much never related to a chirp configuration, and is again related to DCA1000 + mmWaveStudio communication. One thing I see right off the bat is the power supply you are using is rated too low. It seems you are using a 5V 2A supply where we suggest a 5V 3A one, and it could be that the DCA1000 has enough current to start but not enough to support device chirping as needed.

Best Regards,

Pedrhom

Hi Pedrhom,

We already tried almost all the solutions for "NO LVDS DATA" related to DCA1000+IWRL6432. Nothing worked on our case. 

Just to clarify, We are providing DCA1000 with a 3A power adapter and we were using 2A power supply to power the IWRL6432 board. Even with that mmWaveStudio says NO LVDS Data. So what you are asking is to use 3A power adapter on DCA1000 and 3A power supply on IWRL6432? Or just 3A power adapter on DCA1000. (Because we are already provinding DCA1000 with 3A power adapter)

Doesn't our OUTPUT log give any information about what's the root cause of the No LVDS Data? Also is there any video guides related to using IWRL6432 + DCA1000 using mmwavestudio 4.X ? Because the mmwavetoolbox related to IWRL6432 + DCA1000 is like 2 chapters and doesn't give us lot of details. 

Thanks

Hello,

Could you try using this capture script below's settings? No LVDS data could possibly mean that the device is not starting, so there is nothing to capture. Nothing in your output screams out to me as an issue, but it's possible that the overall design of the chirp could have a timing issue. As an FYI this script and the one sent prior will be a part of the next Radar Toolbox update coming out next week.

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/chirp_5F00_mode_5F00_capture.lua

Best Regards,

Pedrhom

Hi, Where should I load this lua script on the mmWave studio? I don’t see a place to put this capture script Can you tell me where to load this up? Thanks

Hello,

Browse for the script then run

Thanks Pedrohm, we have made this script work. But one problem still persisits that DCA1000 and IWRL6432boost work in Windows 10.

But as soon we use a Windows 11 machine it starts giving a Timeout error. I looked at this forum question https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/928145/dca1000evm-mmwave-studio-unable-to-read-the-fpga-version-of-dca1000

is this the only way. can you please advise if this is taken care of in any new version. As this is quite hard to find Windows10 machine. We only have a ddsktop and we need to make it work on laptop which is Windows 11. 

Also one more question - the capture script you shared is it for 77Ghz as IWRL6432 is 60Ghz, as when we load it shows Start frequency in GUI as 77GHz and end frequency as 81Ghz. Please share a 60Ghz version of it. 

Please advise soon. Thanks for your helps so far

Ok Pedhrom, scripts are working now we have 2 issues. In windows 10 mmwave studio is closing every time Post processing starts. Complete mmwave studio closes. This wasn't happening earlier but now its like every time. We need answer to this asap. As we need to demo this to clients.

Do we need to delete some files every time or some thing before we launch the post processing.

Is there a way we can launch the runtime matlab standalone. so it can capture the bin file and process it. Or from Matlab. We need answers soon pls. this case is going on for so long now.   

Windows11, nothing works, we disabled firewall still no success. Have you tried it yourself. Can you share a video its working. 

Hello,

My own computer is Windows 11 and works fine, nor does mmWaveStudio crash after every post proc.

Remind me, you guys are just looking for raw data collection correct? Nothing too custom nor anything that pushes the device past its intended purposes?

You should try the DCA1000 CLI Data Capture Tool. It is significantly simpler, lighter weight, more consistent functionally, and is what we are now pushing to users who are looking for raw data capture. The only con is there not as many knobs and it is gated by SDK firmware limits so some techniques such as CW mode still needs mmWaveStudio.

https://dev.ti.com/tirex/explore/node?a=1AslXXD__2.20.00.05&node=A__ACcj5qsn5G-kyhEttWYAjg__radar_toolbox__1AslXXD__2.20.00.05

Best Regards,

Pedrhom

Hi 

We have bought a new equipment with windows 11. will test and reply.

One thing we want is when we get it i want to test your true ground spedd example on it.

Now we used true ground speed example .cfg file in mmwave estimator. is there a tool which can convert .cfg file into data capture Lua script in mmwavestudio. what i want is to see SNR and velocity distribution curve of raw data we get back. also 1D and 2D fft results in post processing. THat is why post process is impotant to us, any suggestions

thanks 

Hello,

Just so things are clear, the DCA1000 allows for raw IQ radar data to be dumped straight from the ADC buffer. This means no processing of any kind including FFTs are done on this data, and this data is useful for those who are developing their own processing algorithms. True Ground Speed example has multiple FFTs, CFAR, RANSAC-LSQ, etc. To run the true ground speed example you do not need a DCA1000. Unless you are stating that you want to recreate all the processing done in our True Ground Speed example to create a custom processing chain that fits your need.

Best Regards,

Pedrhom