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.

DCA1000EVM: AWR1642: mmwave studio : FPGA version is 0.0.0.0 , Data capture issues, adc_data.bin file is empty

Part Number: DCA1000EVM
Other Parts Discussed in Thread: AWR1642, MMWAVE-STUDIO, AWR1642BOOST

We are using DCA1000 EVM with AWR1642BOOST ES1.0 and mmwave Studio v 1.0.0.0 running on Window 10. We followed the exact steps in the DCA1000 quick user guide when connecting both the DCA1000 and the AWE1642 EVM and the mmwave studio was used to configure and control the devices to capture the raw ADC data. We faced similar issues posted in  previous forums

- Unable to identify the FPGA version: FPGA version is 0.0.0.0,

- Ethernet connectivity issues: Ethernet Cable is disconnected Please check......!!!”

- Data Capture related issues.

Based on the recommendations given in the forums and going through the DCA1000 Debug Handbook: the following steps were taken to resolve these problems.

  • A USB 3.0 Gigabit Ethernet Network Adapter was purchased to resolve the connectivity issues with PC over the Ethernet when direct Ethernet connection from PC to the DCA1000 was initially used. The static IP address was reconfigured correctly.
  • The windows Firewall was disabled, and the ports were enabled in both outbound and inbound rules
  • Two separate power supplies (5V/4A) for the DCA1000 and the AWR1642 EVMs were used all the time.
  • Wireshark tool was installed, and the connection was shown between both the PC and the DCA1000 board.
  • Re-flashed the FPGA to the latest version 2.8 using lattice programmer software.

 As shown in previous forums, the issue was resolved by using either one of the steps or a combination of steps shown above. However, in our case the problem is still not resolved, and the FPGA version is still not identified.

-  Again, when using the mmwave Studio, in the ‘setup DCA 1000'  the FPGA is still shown as version 0.0.0.0., and when we tried to "Connect, Reset and Configure" the RFDataCaptrurecard, the following error message appeared:

“ConnectRFDCCard Status: RFDCCARD_UDP_WRITE_ERR

Ethernet Cable is disconnected Please check......!!!”  . We also tried to increase the packet delay to 100 µs, and we still have the same error message.

-  In addition, after running the DataCaptureDemo_xWR.lua, the Data_Trans_PRG LED on the top left corner of the DCA1000 board is turned on and the Wireshark showed a transfer of UDP packets from the DCA 1000 to PC (please see  the figures below). However, Ethernet connectivity error was shown and the generated adc_data.bin is empty. An error message was also shown after post processing step with MATLAB since the .bin files were empty. The output log file is also attached.

08_mmwave_output_log_demolua.txt
Fullscreen
1
2
3
4
5
6
GM: Constructor
GM: Thu Aug 27 10:58:51 2020
RSTD.Transmit("/Settings")
[10:58:51]
[10:58:51] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
[10:58:51] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Since the Wireshark tool confirmed the Ethernet connection between the DCA1000 and the PC, yet no data was transferred. Based on this along with the other observations we ask the following questions:

-   The version of DCA1000 FPGA is shown as V.0.0.0.0; How to resolve that, what should it be? Is there any issue that can arise by using a newer version of the DCA1000 Kit (Purchased date 08/22/19) with the older AWR1642 ES 1.0 version?

-  We are using the older mmwave-studio version 1.0.0 because it supports our ES1.0 AWR1642. We have a body of work done with this device and do not want to reflash it to use a later version of the mmwave studio. Therefore, if it comes to this, can we instead reflash the DCA1000 with an older FPGA version (v2.5) that is found in the mmwave_studio_01_00_00_00\mmWaveStudio\DCA1000FPGA folder to solve the problem?

We spent a lot of time trying to figure out how to resolve these problems with no luck so far and your help is greatly appreciated.

Thank you 

  • Hello Aya,

    Thankyou for providing such a detailed summary of your debug actions. This will definitely help us resolve your issue at the earliest. I have forwarded your query to our DCA expert, please expect a response shortly. 

    Thankyou for your patience.

    Regards,

    Ishita

  •  Hi Ishita,

    Thank you for your reply. Any updates from the DCA expert?

    Looking forward to hearing back from him soon.

    Thank you

  • Hi Ishita ,

    Any news regarding our problem? we need to resolve the problem as soon as possible, our project is on hold and we can't move forward until we resolve these issues. 

    I hope we can figure out how to fix these issues soon  with the help of TI expertise.  

    Will wait for your feedback and suggestions.

    Thank you

  • Hello Aya,

    Extremely sorry for the delay. There was a long weekend due to holidays in the US and hence the responses are delayed. I understand your concerns and urgency and I assure you our team will get back to you before the end of this week.

    Thank you for your patience again.

    Regards,

    Ishita

  • Aya,

    Is there a reason that you chose to use a USB to Ethernet adapter over the PC Ethernet connection?

    Regards,
    Kyle

  • Aya,

    Can you provide screenshots of your "Network Connections" screen from the Windows Control Panel? Specifically, the connections for the USB adapter but also the main screen so the other connections are viewable.

    Regards,
    Kyle

  • Aya,

    I see no issue with attempting to reflash the FPGA with the v2.5 file that is included in mmWave Studio v1.0. You can try that and see if that resolves your issue.

    Regards,
    Kyle

  • Thank you so much for your response I appreciate it 

  • Hi Kyle ,

    Thank you for your response. it is greatly appreciated.

    Regarding your first reply:

    - I initially used a direct PC Ethernet connection and correctly configured the IP address but I was getting that error message all the time   "RFDCCARD_UDP_WRITE_ERR  Ethernet Cable is disconnected Please check.....!!!".

    In addition I always had zero received bytes when I checked the direct Ethernet status connection in the Control panel window . so I thought there might be a problem with the Ethernet cable. I used another cable but still got the same error.  When I went through similar issues in the forum I found that it was resolved by using USB Gigabit Ethernet Network Adapter. That was the reason I chose to use the adapter for connection. After using the adapter I can see some bytes received as well as UDB packets transferred in the Wireshark window. But still the problem was not resolved.

    - I am attaching the screen shots for my network connections and the USB adapter connection after I ran the data capture demo as you requested hopefully you see some issue I don't see.

    Please advice if there is an issue before attempting to re-flash the FPGA with the 2.5 version.

    Thank you very much

  • Aya,

    Upon reviewing your mmWave Studio log, I noticed that you are using a baud rate of 115200 instead of 961200. Please change to the faster baud rate.

    Regards,
    Kyle

  • Hi Kyle ,

    I changed the baud rate to 961200. I still have the same problem when I ran the demo and also when i tried to click on setup DCA1000

    I am attaching both logs to show the details. Please take a look at them and let me know where to go from there. 

    2020_09_08_mmwave_output_log_demo_921600.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    GM: Constructor
    GM: Tue Sep 08 15:19:52 2020
    RSTD.Transmit("/Settings")
    [15:19:52]
    [15:19:52] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [15:19:52] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    2020_09_08_mmwave_output_log_setupdca_921600.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    GM: Constructor
    GM: Tue Sep 08 15:53:30 2020
    RSTD.Transmit("/Settings")
    [15:53:30]
    [15:53:30] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [15:53:30] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Thank you 

  • Hi Kyle ,

    I changed the baud rate to 961200. I still have the same problem when I ran the demo and also when i tried to click on setup DCA1000

    I am attaching both logs to show the details. Please take a look at them and let me know where to go from there. 

    5314.2020_09_08_mmwave_output_log_demo_921600.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    GM: Constructor
    GM: Tue Sep 08 15:19:52 2020
    RSTD.Transmit("/Settings")
    [15:19:52]
    [15:19:52] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [15:19:52] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    4300.2020_09_08_mmwave_output_log_setupdca_921600.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    GM: Constructor
    GM: Tue Sep 08 15:53:30 2020
    RSTD.Transmit("/Settings")
    [15:53:30]
    [15:53:30] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [15:53:30] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Thank you

  • Hi Kyle ,

    I changed the baud rate to 961200. I still have the same problem when I ran the demo and also when i tried to click on setup DCA1000

    I am attaching both logs to show the details. Please take a look at them and let me know where to go from there. 

    5670.2020_09_08_mmwave_output_log_demo_921600.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    GM: Constructor
    GM: Tue Sep 08 15:19:52 2020
    RSTD.Transmit("/Settings")
    [15:19:52]
    [15:19:52] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [15:19:52] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    0572.2020_09_08_mmwave_output_log_setupdca_921600.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    GM: Constructor
    GM: Tue Sep 08 15:53:30 2020
    RSTD.Transmit("/Settings")
    [15:53:30]
    [15:53:30] ### Running Startup script: "C:\workspace\TI\07_mmwave_studio\MMWAVE_STUDIO_01_00_00_00\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [15:53:30] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Thank you

  • Hi Kyle,

    - Did you check my log with the faster baud rate I sent earlier after you suggestion? I still have the same problem it did not resolve the issue. Should I go back to using baud rate 115200 or the problem is not related to that?

    - Also , Is there anything wrong with my Network connection status from the screen shot I sent earlier?

    Please advice what needs to be done next to make this work.

    We still don't know what is the main cause of our issue. 

    Thank you

  • Unfortunately this did not resolve my issue . After reflashing  with the 2.5 version and running the demo or trying to capture data still the .bin file is empty and the fpga version is still 0.0.0.0 .

    I tried everything I could think of based on previous forums and your previous suggestions with no luck again. We spent a lot of time trying to figure out how to resolve these problems and eventually be able to capture raw data and  would really need the help of TI experts to get to the root cause of this issue and let us know how to resolve it.

    Thank you

  • Any further suggestions or advice to resolve that?  I am still stuck with the same problem.

    Do you think it is a compatibility problem between the DCA1000 and  our AWR1642 EVM .

    Please advise. 

  • Aya,

    Has this issue been resolved?

    Regards,
    Kyle

  • Unfortunately the issue was not resolved and we are still stuck. 

    Please let us know where to go from there.

  • Aya,

    Unfortunately, there are no additional suggestions that we can provide at this time. You are using an older revision of the AWR1642 EVM that we no longer support along with an older version of mmWave Studio. All devices currently in production for AWR1642 are ES 2.0 devices and you are using an ES 1.0 device.

    I have provided all of the workarounds known on the TI side. This is difficult to debug as I (nor anyone else on my team) do not have an ES 1.0 AWR1642BOOST EVM. So we are unable to replicate your setup to try to recreate your issue. All I can do at this point is make suggestions, which I have provided in my many previous responses.

    Ultimately, the recommendation is to move to our latest release of the AWR1642BOOST EVM and use the latest version of mmWave Studio. I am sure that this is not the answer you are looking for, but no additional support with regards to your specific configuration can be provided at this time.

    Please feel free to respond if you have any additional questions.

    Regards,
    Kyle

  • Hi Kyle,

    Thank you for your reply,

    I have one more question :

    Has the DCA1000 worked before with the ES1.0 version of the AWR1642 earlier? In other words was the DCA1000 expected and confirmed  to work with the older version of the AWR1642?

    Thank you

  • Aya,

    Yes, the DCA1000 and AWR1642 have worked in their earlier revisions. However, as I mentioned in my previous post, both of these EVMs have gone through hardware revisions and silicon updates and we do not have the ability to replicate and debug this issue now.

    Regards,
    Kyle