• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 277 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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:

IWRL6432BOOST: Firware files

IWRL6432BOOST: Data capture with IWRL6432BOOST and DCA1000

Barghavi Parthiban
Prodigy 30 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432

Tool/software:

I am using the script from the radar toolbox \radar_toolbox_3_10_00_05\radar_toolbox_3_10_00_05\tools\scripts\mmWaveStudio_lua_examples\xWRLx432\IWRL6432_capture.lua for adc data capture using IWRL6432BOOST ES1.0 with DCA1000. 

My mmwave studio version : 4.1.0.6

mmwavesdk version : 5.3.0.2

I am facing the below error. Please help me to resolve this

I have used the default parameter value given for start frequency and slope in the script.

[17:36:18] -----------fecRfPwrOnOff-----------
[17:36:18]
[17:36:18] [DFP API]xw_status=mws.fecRfPwrOnOff(0,{h_RxChCtrlBitMask=7,h_TxChCtrlBitMask=3,c_Reserved=0,c_MiscCtrl=1,h_Reserved1=0,w_Reserved2=0})
[17:36:18] --xw_status: 0 (SUCCESS)
[17:36:18]
[17:36:18] xw_status, w_freqCode = mws.sensConvFreqToCode(0, 1, 0, 60000)
[17:36:18] xw_status = 0
[17:36:18] w_freqCode = 13107200
[17:36:18] xw_status, w_slopeCode = mws.sensConvSlopeToCode(0,1,40)
[17:36:18] xw_status = 0
[17:36:18] w_slopeCode = 1049
[17:36:18]
[17:36:18] &&&&&&&&&&&&&&&&&&&&
[17:36:18] ***Script FAILED!***
[17:36:18] &&&&&&&&&&&&&&&&&&&&
[17:36:18] Exception message is:
[17:36:18] Value was either too large or too small for a UInt16.


  • +1
    TI__Mastermind 23177 points

    Hello,

    The scripts in the Radar Toolbox were made for ES2 silicon, while the scripts seen within mmWaveStudio itself should be for ES1 (C:\ti\mmwave_studio_04_01_00_06\mmWaveStudio\Scripts\MatlabExamples\LUA_examples)

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 30 points

    Thank you. Using the script inside mmwave studio solved my error. 

    After starting the data capture, I am getting a timeout error repeatedly. Is the issue related to DCA1000? I referred to the DCA1000 debugging handbook and mentioned there might be a version disconnect between mmwave studio and the firmware. I have mentioned my mmwavestudio and SDK version above, please let me know if it's correct or if there might be other issues 

    [09:16:59] xw_status=mws.captureCardStartRecord("C:\\ti\\mmwave_studio_04_01_00_06\\mmWaveStudio\\RunTime\\..\\PostProc\\adc_data1.bin",1,1,4096)
    [09:16:59] [RadarAPI]: Sending start_record command to DCA1000
    [09:17:00] -----------sensorStart-----------
    [09:17:00]
    [09:17:00] [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})
    [09:17:00] --xw_status: 0 (SUCCESS)
    [09:17:00]
    [09:17:00] Waiting 4 sec
    [09:17:04] xw_status = mws.StartMatlabPostProc("C:\\ti\\mmwave_studio_04_01_00_06\\mmWaveStudio\\RunTime\\..\\PostProc\\adc_data1.bin",0)
    [09:17:09] [RadarAPI]:
    [09:17:09] Start Record :
    [09:17:09] Timeout Error! System disconnected
    [09:17:13]
    [09:17:13] ***Script completed successfully.***

    I also just noticed my log for the device setup and the API calls related to the DCA1000 show the system is disconnected

    [14:22:27] [RadarAPI]: mws.SelectCaptureDevice("DCA1000")
    [14:22:27] [RadarAPI]: Status: Passed
    [14:22:27] xw_status = mws.captureCardCfgResetFPGA()
    [14:22:27] [RadarAPI]: Sending reset_fpga command to DCA1000
    [14:22:37] [RadarAPI]:
    [14:22:37] Reset FPGA :
    [14:22:37] Timeout Error! System disconnected
    [14:22:37] --xw_status=0
    [14:22:38] xw_status = mws.captureCardEthernetCfg("192.168.33.30", "192.168.33.180", "12.34.56.78.90.12", 4096, 4098, 1)
    [14:22:38] [RadarAPI]: Sending eeprom command to DCA1000
    [14:22:48] [RadarAPI]:
    [14:22:48] EEPROM Configuration :
    [14:22:48] Timeout Error! System disconnected
    [14:22:48] --xw_status=0
    [14:22:48] xw_status = mws.captureCardModeCfg(1,1,1,2, 1, 25)
    [14:22:48] [RadarAPI]: Sending fpga command to DCA1000
    [14:22:58] [RadarAPI]:
    [14:22:58] FPGA Configuration :
    [14:22:58] Timeout Error! System disconnected
    [14:22:58] [RadarAPI]: Sending record command to DCA1000
    [14:23:08] [RadarAPI]:
    [14:23:08] Configure Record :
    [14:23:08] Timeout Error! System disconnected
    [14:23:08] --xw_status=0
    [14:23:08] xw_status, s_version, s_dllVersion = mws.getCaptureCardFPGAVersion()
    [14:23:08] [RadarAPI]: Sending fpga_version command to DCA1000
    [14:23:18] [RadarAPI]:
    [14:23:18]
    [14:23:18] Unable to read FPGA Version. [error -5]
    [14:23:18]
    [14:23:18] [RadarAPI]: Sending dll_version command to DCA1000
    [14:23:18] [RadarAPI]:
    [14:23:18] DLL Version : 1.0

  • 0 in reply to Barghavi Parthiban
    TI__Mastermind 23177 points

    Hello,

    Unable to Read FPGA Version -5 is one of the most common DCA1000 errors. It is exclusively the connection between DCA1000 and computer via Ethernet not connecting properly. The DCA1000 FAQ E2E Post covers the possible solutions which ill also post below

    • Computer's ethernet adapter must be Gigabit (>1Gbps). If using a Ethernet to USB dongle, ensure the dongle hardware supports >1Gbps.
    • Firewall is blocking mmWaveStudio, will be specifically DCA1000_EVM_CLI_Control.exe and DCA1000_EVM_CLI_Record.exe. Within your firewall settings, ensure all permissions are checked for these two executables found in C:\ti\<MMWAVE_STUDIO_VER>\mmWaveStudio\PostProc



    • FPGA is corrupted and needs to be reflashed with Lattice Tool
    • Bad Ethernet Cable, FTDI chip doesn't like the USB cable used and thus must be switched out
    • 5V 3A power supply is not being used
    • Packet delay needs to be increased. mmWaveStudio attempts to connect by increasing the packet delay several times but may need to go past mmWaveStudio's "last attempt"

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 30 points

    Thanks for the detailed reply. I will check them one by one. Do you have any guide to follow to flash FPGA with Lattice tool? 

  • 0 in reply to Barghavi Parthiban
    TI__Mastermind 23177 points

    It can be found here

    DCA1000 User Guide PDF

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 30 points

    I downloaded the lattice tool, but it doesn't recognise my device. I have configured the switch settings as given in the DCA1000 user guide chapter 9 (Attached images) and followed the steps. But I get the below error

  • 0 in reply to Barghavi Parthiban
    TI__Mastermind 23177 points

    Hello,

    Do you see the four DevPack ports in Device Manager? If not ensure the FTDI drivers are installed.

    Make sure all the switches are correct and you have a 5V 3A power supply, cable to the FTDI port of the DCA1000, ethernet port of the DCA1000, and XDS port of the mmWaveSensor

    https://dev.ti.com/tirex/explore/node?node=A__AZpB296-3QEz48rsFnFiOw__radar_toolbox__1AslXXD__LATEST

    https://dev.ti.com/tirex/explore/node?node=A__Ab2zfideDkWxrpN2-140Vw__radar_toolbox__1AslXXD__LATEST

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 30 points

    Yes, I can see the four devpack ports. I have the switches as shown in the picture. I have a 5V 3A  adaptor to the DCA1000 and a 5V 2A adaptor to the sensor. Will that be an issue?
      

  • 0 in reply to Barghavi Parthiban
    TI__Mastermind 23177 points

    If the four DevPack drivers are appearing, then the FTDI drivers are installed and is detecting the DCA1000. Detecting is different than full communication, but is a good start. Do you set your static IP to 192.168.33.30 as well?

    Also, in your picture I do not see a USB cable connected to the mmWave sensor itself. You need two USB cables, one from DCA1000's FTDI USB port and one from 6432's XDS USB port.

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 30 points

    I have set the static IP address and also used two USB cables. But still facing the same problem. I have a 5V 3A  adapter for the DCA1000 and a 5V 2A adapter for the sensor. Will that be an issue?

  • 0 in reply to Barghavi Parthiban
    TI__Mastermind 23177 points

    Hello,

    Could you try different USB and Ethernet cables? And to be certain you added the two .exe's listed prior to your firewall list correct?

    Best Regards,

    Pedrhom