• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 1074 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:

DCA1000EVM: AWR1642 problem with mmwave studio 2.0.0.2

DCA1000EVM: ETH cable is disconnected

radar just
Prodigy 70 points
Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR1642

Hi,

I have issues with configuring the board to connected through Ethernet. I followed the necessary steps.

Configured IP to static. 192.168.33.30

SOP0,SOP1

DCA1000 switches configured

SW1: 

16BIT_ON and the other two are off

SW2

6.7.8 --> SW1,2,3

5: SW_CONFI

4: RAW_DATA

3: 1243_MODe

2: ETH

1:LVDS

GM: Constructor
GM: Tue Dec 18 11:36:54 2018
RSTD.Transmit("/Settings")
[11:36:55]
[11:36:55] ### Running Startup script: "C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Scripts\Startup.lua" ###
[11:36:55] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
[11:36:55] RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")
[11:36:55] Scripter ignored: Attempt to UnBuild() again or before Build.
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Clients\\\\LabClient.dll")
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")
[11:36:55] RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\RunTime\\SAL.dll")
[11:36:55] RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")
[11:36:55] RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")
[11:36:55] RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")
[11:36:55] RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")
[11:36:55] RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")
[11:36:55] RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")
[11:36:55] RSTD.Transmit("/")
[11:36:55] RSTD.SaveSettings(): Settings saved to "C:\Users\abe_mhamdan\AppData\Roaming\RSTD\config.xml"
[11:36:56] RSTD.Build()
[11:36:56] RSTD.SaveSettings(): Settings saved to "C:\Users\abe_mhamdan\AppData\Roaming\RSTD\config.xml"
[11:36:56] RSTD.Transmit("/")
[11:36:56] RSTD.AL_Build()
[11:36:56] RSTD.AL_LoadXml()
[11:36:56] RSTD.Transmit("/")
[11:36:56] RSTD.AL_Init()
[11:36:56] RSTD.Clients_Build()
[11:36:56] GM: Init
[11:36:56] GM: Loaded 'C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Clients\\LabClient.dll'
[11:36:56] GM: 1 Guest (s) init
[11:36:56] GM: 1 Module(s) init
[11:36:56] GM: 2 Tab (s) init
[11:36:56] RSTD.Client_LoadXml()
[11:36:56] [RadarAPI]: Starting Matlab Engine..
[11:37:15] [RadarAPI]: Matlab Engine Started!
[11:37:18] [RadarAPI]: ar1.LoadSettings('C:\Users\abe_mhamdan\AppData\Roaming\RSTD\ar1gui.ini')
[11:37:18] TESTING = false
[11:37:18]
[11:37:18] ***Script completed successfully.***
[11:37:25] [RadarAPI]: Opening Gpio Control Port()
[11:37:25] [RadarAPI]: Status: Passed
[11:37:25] [RadarAPI]: Opening Board Control Port()
[11:37:25] [RadarAPI]: Status: Passed
[11:37:26] [RadarAPI]: ar1.FullReset()
[11:37:26] [RadarAPI]: Status: Passed
[11:37:27] [RadarAPI]: Closing Board Control Port()
[11:37:27] [RadarAPI]: Status: Passed
[11:37:27] [RadarAPI]: Closing Gpio Control Port()
[11:37:27] [RadarAPI]: Status: Passed
[11:37:27] [RadarAPI]: ar1.SOPControl(2)
[11:37:27] [RadarAPI]: Status: Passed
[11:37:28] [RadarAPI]: ar1.Connect(5,115200,1000)
[11:37:29] [RadarAPI]: ar1.Calling_IsConnected()
[11:37:31] [RadarAPI]: ar1.SelectChipVersion("AR1642")
[11:37:31] [RadarAPI]: Status: Passed
[11:37:31] [RadarAPI]: RS232 is not connected ..!!!!
[11:37:31] [RadarAPI]: ar1.frequencyBandSelection("77G")
[11:37:31] [RadarAPI]: ar1.SelectChipVersion("XWR1642")
[11:37:31] [RadarAPI]: Status: Passed
[11:37:31] Device Status : XWR1642/QM/SOP:2/ES:2
[11:37:32] [RadarAPI]: ar1.SelectChipVersion("AR1642")
[11:37:32] [RadarAPI]: Status: Passed
[11:37:32] [RadarAPI]: ar1.SelectChipVersion("XWR1642")
[11:37:32] [RadarAPI]: Status: Passed
[11:37:32] Device Status : XWR1642/QM/SOP:2/ES:2
[11:37:32] [RadarAPI]: ar1.SaveSettings('C:\Users\abe_mhamdan\AppData\Roaming\RSTD\ar1gui.ini')
[11:39:01] [RadarAPI]: ar1.ReadRegister(0xffffe214, 0, 31)
[11:39:01] [RadarAPI]: ar1.ReadRegister(0xffffe210, 0, 31)
[11:39:01] [RadarAPI]: ar1.ReadRegister(0xffffe218, 0, 31)
[11:39:01] [RadarAPI]: ar1.DownloadBSSFw("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\..\\rf_eval_firmware\\radarss\\xwr16xx_radarss.bin")
[11:39:02] [RadarAPI]: Downloading BSS Patch RPRC Binary..
[11:39:09] [RadarAPI]: ar1.GetBSSFwVersion()
[11:39:09] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[11:39:10] [RadarAPI]: ar1.GetBSSPatchFwVersion()
[11:39:10] [RadarAPI]: BSSPatchFwVersion:(01.02.00.03 (24/10/18))
[11:39:10] BSS FW Download Success
[11:39:12] [RadarAPI]: ar1.DownloadMSSFw("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\..\\rf_eval_firmware\\masterss\\xwr16xx_masterss.bin")
[11:39:12] [RadarAPI]: Downloading MSS RPRC Binary..
[11:39:23] MSS FW Download Success
[11:39:25] [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
[11:39:25] [RadarAPI]: Status: Passed
[11:39:25] MSS power up done async event received!
[11:39:25] Power On Success
[11:39:26] [RadarAPI]: ar1.RfEnable()
[11:39:26] [RadarAPI]: Status: Passed
[11:39:26] BSS power up done async event received!
[11:39:27] [RadarAPI]: ar1.GetBSSFwVersion()
[11:39:27] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[11:39:28] [RadarAPI]: ar1.GetBSSPatchFwVersion()
[11:39:28] [RadarAPI]: BSSPatchFwVersion:(01.02.00.03 (24/10/18))
[11:39:28] RF Enable Success
[11:39:29] [RadarAPI]: ar1.ChanNAdcConfig(1, 1, 0, 1, 1, 1, 1, 2, 1, 0)
[11:39:29] [RadarAPI]: Status: Passed
[11:39:29] ChanNAdcConfig Success
[11:39:30] [RadarAPI]: ar1.LPModConfig(0, 1)
[11:39:30] [RadarAPI]: Status: Passed
[11:39:30] LPModConfig Success
[11:39:32] [RadarAPI]: ar1.RfInit()
[11:39:32] RF Init async event received!
[11:39:32] [RadarAPI]: Time stamp, Temperture: 5843,41; APLL Status, Update: 1, 0; SynthVCO1 Status, Update: 1, 1; SynthVCO2 Status, Update: 1, 1; LODist Status, Update: 1, 1; RxADCDC Status, Update: 1, 1; HPFcutoff Status, Update: 1, 1; LPFcutoff Status, Update: 1, 1; PeakDetector Status, Update: 1, 1; TxPower Status, Update: 1, 1; RxGain Status, Update: 1, 1; TxPhase Status, Update: 0, 0; RxIQMM Status, Update: 1, 1;
[11:39:32] [RadarAPI]: Status: Passed
[11:39:32] RfInit Success
[11:39:33] [RadarAPI]: ar1.DataPathConfig(1, 1, 0)
[11:39:33] [RadarAPI]: Status: Passed
[11:39:33] DataPathConfig Success
[11:39:34] [RadarAPI]: ar1.LvdsClkConfig(1, 1)
[11:39:34] [RadarAPI]: Status: Passed
[11:39:34] LvdsClkConfig Success
[11:39:35] [RadarAPI]: ar1.LVDSLaneConfig(0, 1, 1, 0, 0, 1, 0, 0)
[11:39:36] [RadarAPI]: Status: Passed
[11:39:36] LVDSLaneConfig Success
[11:39:37] [RadarAPI]: ar1.ProfileConfig(0, 77, 100, 6, 60, 0, 0, 0, 0, 0, 0, 29.982, 0, 256, 5000, 0, 0, 30)
[11:39:37] [RadarAPI]: Status: Passed
[11:39:37] ProfileConfig Success
[11:39:38] [RadarAPI]: ar1.ChirpConfig(0, 0, 0, 0, 0, 0, 0, 1, 1, 0)
[11:39:38] [RadarAPI]: Status: Passed
[11:39:38] ChirpConfig Success
[11:39:39] Test Source Already Disabled...!!!
[11:39:39] [RadarAPI]: Status: Passed
[11:39:39] [RadarAPI]: ar1.FrameConfig(0, 0, 8, 128, 40, 0, 1)
[11:39:39] [RadarAPI]: Status: Passed
[11:39:39] FrameConfig Success
[11:39:40] [RadarAPI]: ar1.SelectCaptureDevice("DCA1000")
[11:39:40] [RadarAPI]: passed
[11:39:40] SelectCaptureDevice Success
[11:39:41] [RadarAPI]: StatusDCCard Event Registered
[11:39:41] [RadarAPI]: Status: Passed
[11:39:41] [RadarAPI]: ar1.CaptureCardConfig_EthInit("192.168.33.30", "192.168.33.180", "12:34:56:78:90:12", 4096, 4098)
[11:39:41] [RadarAPI]: Status: Passed
[11:39:43] Ethernet Cable is disconnected Please check.....!!!
[11:39:43] CaptureCardConfig_EthInit Success
[11:39:44] [RadarAPI]: ar1.ConfigureRFDCCardMode(1, 2, 1, 2, 3, 30)
[11:39:44] [RadarAPI]: Status: Passed
[11:39:44] CaptureCardConfig_Mode Success
[11:39:45] [RadarAPI]: ar1.CaptureCardConfig_PacketDelay(25)
[11:39:45] [RadarAPI]: Status: Passed
[11:39:45] CaptureCardConfig_PacketDelay Success
[11:39:46] [RadarAPI]: ar1.CaptureCardConfig_StartRecord("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data.bin", 1)
[11:39:46] [RadarAPI]: Status: Passed
[11:39:47] [RadarAPI]: ar1.StartFrame()
[11:39:47] [RadarAPI]: Status: Passed
[11:39:47] Frame start async event received!
[11:39:48] Frame End async event received!
[11:39:48] [RadarAPI]: Frame Ended
[11:39:49] Please wait for a few seconds for Packet reorder utility processing .....!!!!
[11:39:49] [RadarAPI]: Packet Reorder Utility Started...please wait...
[11:39:49] [RadarAPI]: ar1.PacketReorderZeroFill("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data_Raw_0.bin", "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data.bin", "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\pktlogfile.txt")
[11:39:54] [RadarAPI]: Packet Reorder Utility process completed!
[11:40:04] Packet reorder utility processing done.....!!!!
[11:40:04] Please wait for a few seconds for matlab post processing .....!!!!
[11:40:04] [RadarAPI]: ar1.StartMatlabPostProc("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data.bin")
[11:40:05] [RadarAPI]: Error:
[11:40:05]
[11:40:05] ... MWMCR::EvaluateFunction error ...
[11:40:05] 18-Dec-2018 11:40:05: The file C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Scripts\..\PostProc\adc_data.bin is empty. Please capture more data.,1,
[11:40:05] Error in => process_adc_data.m at line 52.
[11:40:05]
[11:40:05] ... Matlab M-code Stack Trace ...
[11:40:05] at
[11:40:05] file C:\Users\ABE_MH~1\AppData\Local\Temp\abe_mhamdan\mcrCache8.5.1\Matlab0\Logging\log_status.m, name log_status, line 32.
[11:40:05] at
[11:40:05] file C:\Users\ABE_MH~1\AppData\Local\Temp\abe_mhamdan\mcrCache8.5.1\Matlab0\Processing_functions\read_adc_data.m, name read_adc_data, line 28.
[11:40:05] at
[11:40:05] file C:\Users\ABE_MH~1\AppData\Local\Temp\abe_mhamdan\mcrCache8.5.1\Matlab0\MatlabPostPr\process_adc_data.m, name process_adc_data, line 52.
[11:40:05]
[11:40:05]
[11:40:05] Trace:
[11:40:05] at MathWorks.MATLAB.NET.Utility.MWMCR.EvaluateFunction(String functionName, Int32 numArgsOut, Int32 numArgsIn, MWArray[] argsIn)
[11:40:05] at MathWorks.MATLAB.NET.Utility.MWMCR.EvaluateFunction(Int32 numArgsOut, String functionName, MWArray[] argsIn)
[11:40:05] at MatlabPostProcGui.MatlabPostProcGUIClass.process_adc_data(MWArray adc_file_name, MWArray force_cont_stream_mode)
[11:40:05] at AR1xController.frmAR1Main.iStartMtlabPostProc()
[11:40:14]
[11:40:14] ***Script completed successfully.***

  • 0
    TI__Intellectual 2885 points

    Hi,

    Your setting on SW2 should be like the table below.

    position name
    SW2.8 OFF USER_SW1
    SW2.7 OFF USER_SW2
    SW2.6 OFF USER_SW3
    SW2.5 ON CONFIG_VIA_SW
    SW2.4 OFF RAW_MODE
    SW2.3 ON AR1642_MODE
    SW2.2 ON ETH_STREAM
    SW2.1 OFF LVDS_CAPTURE

    On the ethernet disconected issue, you need to make sure that your PC says that its connected, see image below.

    another check is ping the address 192.168.33.180 from the command promt type: ping 192.168.33.180, you will get a timeouts because the DCA1000 will not respond and you will see that all data packets are lost, but you should see the LED on the DCA blink.

    Also use wireshark to see communication from the PC to DCA.

    hope this helps

    Alex

  • 0 in reply to Alex Rivera
    Prodigy 70 points
    Hi Alex,
    thank you that kind of resolved the problem as I am able to connect to the FPGA now but I still get the error when testings the DataCaptureDemo.


    The DatacaptureDemo, only worked when I just started up the mmWaveStudio, and After I redo the steps to attempt to connect to FPGa after testing DatacaptureDemo, FPGA won't connect. Going back to the ethernet problem again.

    It is more like I cannot do both one after another through mmWave?
  • 0 in reply to radar just
    TI__Intellectual 2885 points
    hi,

    redo the steps? you only need to set up the DCA1000 once, after that you can:
    1) DCA1000 ARM
    2) Trigger Frame
    3) PostProc

    several times, no need to re-set up the DCA1000.

    I would recommend you do all steps manually and see if you get any errors that way.

    Alex
  • 0 in reply to Alex Rivera
    Prodigy 70 points
    Hi Alex,
    What is the difference between SW2.6 set to EEPROM or hardcoded FPGA? and which one ensures that configurations are saved without having to reconfigure after a power cycle? , I actually tried both and non worked for me.

    I configured the board to capture data through software, but every time I wanted to capture data after power-cycling the board, I had to do all the communication steps in the mmWAVE studio
    1- Reset 2-COM connection 3- BSS download 4-MSS download 5- SPI connection 6- RF power up
    then apply all configuration then connect to FPGA before I able to
    1) DCA1000 ARM
    2) Trigger Frame
    3) PostProc

    Indeed, I have an application that requires RAW data streaming and I want to achieve that through configuring the DCA1000EVM one time or whenever needed and then perform all data capturing based on that configuration.

    For example, I want to configure the board then deploy it then turn it off and then run it again and have it ready to start capturing either through a software/hardware command.

    Could you please explain to me how can I achieve this?
  • 0 in reply to radar just
    TI__Intellectual 2885 points

    Hi,

    I think this post will have what you need in order to change the settings in the FPGA LINK

    Unfortunately there is currently no way to achieve what you want with out mmWave Studio, perhaps at a later time.

    Thanks
    Alex

  • 0 in reply to Alex Rivera
    Prodigy 70 points

    Hi Alex,

    What I really would like to know is this,

    Do I have to configure the DCA1000, everytime I power it up? and do I always need to establish all the 6 connection steps to issue a software trigger? 

    1- Reset 2-COM connection 3- BSS download 4-MSS download 5- SPI connection 6- RF power up ?

    And, What is the difference between SW2.6 set to EEPROM or hardcoded FPGA? and which one ensures that configurations are saved without having to reconfigure after a power cycle?

  • 0 in reply to radar just
    TI__Intellectual 2885 points

    Do I have to configure the DCA1000, everytime I power it up?

    Yes


    Do I always need to establish all the 6 connection steps to issue a software trigger?

    No, you can just do DCA1000 ARM and Trigger Frame, optionally PostProc

    If you decide to not do the PostProc then you need to do the packet reorder manually.

    What is the difference between SW2.6 set to EEPROM or hardcoded FPGA?

    With the FPGA you cannot change the settings, on the EEPROM you can change the default values and keep them after powercycle.

    Hope this was helpful

    Alex

  • 0 in reply to Alex Rivera
    Prodigy 70 points

    What I mean by the 6 connection steps is this:

    And Configuration is --> 

    I think if I do not establish a connection in mmWAVE studio, I won't be able to configure the board? However, I attempted to configure and resulted in error! 

    I am confused now. 

    Further, why there is not a way to hard-code specific configurations and only change them when I decide to? 

    I did not quite understand the difference between FPGa and EEPROM?   what is hardcoded on FPGA? 

    I thought I can store the configuration on either and when I use the board again, I'd be just ready to trigger data-capture!

  • 0 in reply to radar just
    TI__Intellectual 2885 points

    Hi,

    There is currently no way of setting up the device without mmWave studio.

    why there is not a way to hard-code specific configurations and only change them when I decide to?

    The firmware that gets loaded with mmWave studio cannot be hard-coded, unless you create your own binary file similar to the Labs or demos in the industrial toolbox.

    I did not quite understand the difference between FPGa and EEPROM?   what is hardcoded on FPGA?

    the FPGA you cannot modify the settings (IP addresses, ports),  on the EEPROM you can edit said settings

    I thought I can store the configuration on either and when I use the board again, I'd be just ready to trigger data-capture!

    you can create your own binary file similar to the Labs/demos in the industrial toolbox.

    Alex

  • 0 in reply to Alex Rivera
    Prodigy 50 points

    Hi Alex -- I'm an engineer/data scientist working on this project as well.  We spend >$800 to get the IWR1642 demo board and DCA1000 with the hope of capturing raw data to explore using this for commercial product development AND research work.  I had very high hopes for the TI hardware, but Moe (the OP) is still having trouble getting this reliable enough to even consider handing off to data collection teams.  He's tried to follow your latest suggestions and is getting an error when trying to avoid the full configuration and connection steps every time (which should be possible????).  Under what circumstances can we actually get an engineer on the phone?  

  • 0 in reply to John Just
    TI__Intellectual 2885 points
    John,

    Thank you for considering TI for your project, I'm sorry to hear that you are still having issues and i did not convey my message correctly.

    Currently, the only way to capture RAW ADC data is with the DCA1000 and mmWave Studio, no way around it. This is because the EVM and the DCA1000 needs to be configured.

    To avoid the configuration you would need to create your own binary file, similar to the Labs or demos in the industrial toolbox, then send the data trough UART, SPI, I2C or LVDS lines of the EVM, that being said UART, SPI and I2C bandwidth is too low to support the RAW ADC data rate.

    The IWR1642 device has an ARM R4F processor and full floating-point DSP processor in the device for processing the ADC data so the typical use-case is to output post-processed, lower bandwidth data instead of the raw ADC data.

    There are UART, SPI and I2C drivers included with the mmWave SDK. They are documented in the mmWave SDK (after downloading and installing it) in mmwave_sdk_<ver>\docs\mmwave_sdk_module_documentation.html. There are also example driver tests for each driver located in the "test" directory inside each driver directory. Please see the mmWave SDK user guide for more details on the location of the drivers/tests and instructions for building the driver tests.


    Alex