• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 197 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:

IWRL6432AOPEVM: Raw ADC Streaming DCA1000 + 6432AOP

IWRL6432AOPEVM: DCA1000 Capture Card + AWRL6432AOP

Tobias Brandl
Prodigy 100 points
Part Number: IWRL6432AOPEVM
Other Parts Discussed in Thread: AWRL6432AOP, AWRL6432, IWRL6432

Tool/software:

Hello Ti Team,

i am trying to capture RawData with DCA1000 Capture Card and AWRL6432AOP Device. Regarding to your last reply, i tried to use the LUA Scripts you provided (i changed the firmware directory and the RS232 Ports in the script). Unfortunatly i am still getting an Error (see picture). Regarding to TIREX  it is recommended to use an older Version of mmwave Studio for AOP devices. With this older Version, the detection of the Board is different comparing to newer mmwave studio (see picture,device typ). I am also not able to load the second firmware file, as described in my previous post.

-I am using both firmware files from the newest SDK. Would it be possible, that i have to use different Firmware files, because my Radarboard is an older Device (EG?)?

-In both cases the firmware version ist not fully shown in the GUI after flashing it.

-is it recommended to use the LUA Script also for the newer mmwaveStudio Version? Its only a optional way of configuring the device correct?

-is there a recommended demo to flash on the AWRL6432 for testing? Currently i am using TrueGroundSpeed Demo. I also tried the motion and presence demo.

-How can i check which EG(1.0/2.0?) Version i have?

-How can I ensure that I select the correct firmware files and the correct demo+.cfg? There are also appimages+chirp profiles stored in the respective tools' folders. This is a bit confusing.

In the end, I want to be able to configure the frontend, send a chirp frame, and have data visualization. I have tried using mmWave Studio, Studio CLI Tool, and DCA1000 CLI. The 6432AOP always seems to have a special status and is either not listed in the programs/scripts or needs to be configured differently compared to the other boards. Unfortunately, the information from the user guides did not help me further. 

As far as I understand, mmWave Studio offers the most extensive functionality for evaluating the frontend. That's why I would be particularly interested in this solution.I would be very grateful for further assistance. 

Thank you very much. Best regards Tobias.

  • 0
    TI__Genius 9180 points

    Hi

    Thanks for your query. Please allow us a couple of days to respond

    Regards

  • 0 in reply to Abhishek Karkisaval
    Prodigy 100 points

    Hello Abhishek,

    i think i have made some progress, but i still have some problems getting a succesful chirp frame sent.

    I flashed the FPGA with a new Firmware using Lattice Programmer. Then i used LUA Scripts to config DCA1000 (using mmwave studio 4.1.0.6.) with this result: I can see the APIs are accepted and i am getting all of the information about Firmware Version etc. 

    When i take a closer look to the output log, i can see that there are still some functions/steps which are causing an error, like:

    i have to deactivate the step for postproc information in the luascript,otherwise the script is not running.

    -- Check that Matlab Postproc is at least version 5.02
local postproc_version = tonumber(mws.GetPostProcVersion())
if (postproc_version < 5.02) then
error("ERROR: Matlab Postproc must be at least version 5.02")
end
    ...getting FPGA Version still not working...
    [21:38:25]  mws.ftdiResetAllDevices()
[21:38:25]  --xw_status = 0
[21:38:25]  xw_status = mws.selectBDType(0, 0, 1, 0)
[21:38:25]  --xw_status = 0
[21:38:25]  xw_status = mws.selectComIfType(1, 1000, 0, 2, 0)
[21:38:25]  --xw_status = 0
[21:38:25]  [RadarAPI]: mws.SelectCaptureDevice("DCA1000")
[21:38:25]  [RadarAPI]: Status: Passed
[21:38:25]  xw_status = mws.captureCardCfgResetFPGA()
[21:38:25]  [RadarAPI]: Sending reset_fpga command to DCA1000
[21:38:35]  [RadarAPI]: 
[21:38:35]  Reset FPGA : 
[21:38:35]  Timeout Error! System disconnected
[21:38:35]  --xw_status=0
[21:38:35]  xw_status = mws.captureCardEthernetCfg("192.168.33.30", "192.168.33.180", "12.34.56.78.90.12", 4096, 4098, 1)
[21:38:35]  [RadarAPI]: Sending eeprom command to DCA1000
[21:38:46]  [RadarAPI]: 
[21:38:46]  EEPROM Configuration : 
[21:38:46]  Timeout Error! System disconnected
[21:38:46]  --xw_status=0
[21:38:46]  xw_status = mws.captureCardModeCfg(1,1,1,2, 1, 25)
[21:38:46]  [RadarAPI]: Sending fpga command to DCA1000
[21:38:56]  [RadarAPI]: 
[21:38:56]  FPGA Configuration : 
[21:38:56]  Timeout Error! System disconnected
[21:38:56]  [RadarAPI]: Sending record command to DCA1000
[21:39:06]  [RadarAPI]: 
[21:39:06]  Configure Record : 
[21:39:06]  Timeout Error! System disconnected
[21:39:06]  --xw_status=0
[21:39:06]  xw_status, s_version, s_dllVersion = mws.getCaptureCardFPGAVersion()
[21:39:06]  [RadarAPI]: Sending fpga_version command to DCA1000
[21:39:16]  [RadarAPI]: 
[21:39:16]  
[21:39:16]  Unable to read FPGA Version. [error -5]
[21:39:16]
    nevertheless, the script runs till the end.
    When i send the 2nd LUA script :4188.IWRL6432_capture.lua the scripts ends with:
    [21:56:55]  Waiting for data capture to complete or timeout
[21:56:55]  Calling mws.GetDCAStartRecordStatus()
[21:57:04]  [RadarAPI]: 
[21:57:04]  Start Record : 
[21:57:04]  Timeout Error! System disconnected
[21:57:04]  
[21:57:04]  &&&&&&&&&&&&&&&&&&&&
[21:57:04]  ***Script FAILED!***
[21:57:04]  &&&&&&&&&&&&&&&&&&&&
[21:57:04]  Exception message is:
[21:57:04]  ...KAD\BEMTT\TI\DCA1000\email\4188.IWRL6432_capture.lua:124: ERROR: mws.GetDCAStartRecordStatus() API failed
    All of the previous steps from the script seem to be ok/completed sucessful. Do you have an idea? Thank you very much!
  • +1 in reply to Tobias Brandl
    Prodigy 100 points

    i re-installed the FTDI Drivers and deactivated Firewall. It is working now :). I still have to deactivate the postproc Command in LUA script. But its working without...