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: USB Serial Port;PROTOCOL ERROR.

Part Number: DCA1000EVM
Other Parts Discussed in Thread: AWR1443, UNIFLASH

Tool/software:

Hi sirs,

I am trying to connect the DCA1000EVM with mmWaveStudio 02_01_01_00, but after installing the FTDI device driver, the Device Manager shows the port name as "USB Serial Port" instead of "AR-DevPack-EVM-012" as specified in the manual. The port display is shown in the image below:

I have followed the solutions provided in the manual and other forum posts to update the driver in the path C:\ti\mmwave_studio_02_01_01_00\ftdi. The manual states that after updating the driver, the port names should sequentially change to "AR-DevPack-EVM-012". However, even after reconnecting the USB interface and reinstalling the driver, the port name still appears as "USB Serial Port". Upon checking the properties, the manufacturer and version number are displayed correctly and appear normal.

After connecting to the AWR1443 Boost, mmWaveStudio 02_01_01_00 immediately encounters errors during the initial Reset step:
Status: Failed to open/close GpioControl, Error Type: PROTOCOL ERROR.
Additionally, the system reports "0" for "No. of Devices Detected".
The detailed log from MmWaveStudio is as follows:

 

[09:05:14]  ### Running Startup script: "C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\Scripts\Startup.lua" ###

[09:05:14]  RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")

[09:05:14]  RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")

[09:05:14]  Scripter ignored: Attempt to UnBuild() again or before Build.

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_02_01_01_00\\mmWaveStudio\\Clients\\\\LabClient.dll")

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")

[09:05:14]  RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_02_01_01_00\\mmWaveStudio\\RunTime\\SAL.dll")

[09:05:14]  RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")

[09:05:14]  RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")

[09:05:14]  RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")

[09:05:14]  RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")

[09:05:14]  RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")

[09:05:14]  RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")

[09:05:14]  RSTD.Transmit("/")

[09:05:14]  RSTD.SaveSettings(): Settings saved to "C:\Users\Lenovo\AppData\Roaming\RSTD\config.xml"

[09:05:14]  RSTD.Build()

[09:05:14]  RSTD.SaveSettings(): Settings saved to "C:\Users\Lenovo\AppData\Roaming\RSTD\config.xml"

[09:05:14]  RSTD.Transmit("/")

[09:05:14]  RSTD.AL_Build()

[09:05:14]  RSTD.AL_LoadXml()

[09:05:14]  RSTD.Transmit("/")

[09:05:14]  RSTD.AL_Init()

[09:05:14]  RSTD.Clients_Build()

[09:05:14]  GM: Init

[09:05:14]  GM: Loaded 'C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\Clients\\LabClient.dll'

[09:05:14]  GM: 1 Guest (s) init

[09:05:14]  GM: 1 Module(s) init

[09:05:14]  GM: 2 Tab   (s) init

[09:05:14]  RSTD.Client_LoadXml()

[09:05:14]  [RadarAPI]: ar1.selectRadarMode(0)

[09:05:14]  [RadarAPI]: Status: Passed

[09:05:14]  Matlab Runtime Engine is installed

[09:05:14]  [RadarAPI]: Starting Matlab Engine..

[09:05:18]  [RadarAPI]: Matlab Engine Started!

[09:05:19]  [RadarAPI]: ar1.selectCascadeMode(0)

[09:05:19]  [RadarAPI]: Status: Passed

[09:05:19]  [RadarAPI]: ar1.LoadSettings('C:\Users\Lenovo\AppData\Roaming\RSTD\ar1gui.ini')

[09:05:19]  TESTING = false

[09:05:19]  RstdNet: Port 2777: Listening..

[09:05:19] 

[09:05:19]  ***Script completed successfully.***

[09:05:31]  [RadarAPI]: Opening Gpio Control Port()

[09:05:31]  Status: Failed to open/close GpioControl, Error Type: PROTOCOL ERROR

[09:05:31]  [RadarAPI]: Opening Board Control Port()

[09:05:31]  [RadarAPI]: Status: Failed to open/close BoardControl, Error value: -1

[09:05:32]  [RadarAPI]: ar1.FullReset()

[09:05:32]  [RadarAPI]: Status: Failed To give full reset, Error Value: -7

[09:05:32]  [RadarAPI]: ar1.SOPControl(2)

[09:05:32]  [RadarAPI]: Status: Passed

[09:05:41]  [RadarAPI]: ar1.Connect(9,115200,1000)

[09:05:42]  [RadarAPI]: ar1.Calling_IsConnected()

[09:05:44]  [RadarAPI]: ar1.SelectChipVersion("AR1243")

[09:05:44]  [RadarAPI]: Status: Passed

[09:05:44]  [RadarAPI]: ar1.SelectChipVersion("AR1243")

[09:05:44]  [RadarAPI]: Status: Passed

[09:05:44]  [RadarAPI]: ar1.deviceVariantSelection("XWR1443")

[09:05:44]  [RadarAPI]: Status: Passed

[09:05:44]  [RadarAPI]: ar1.frequencyBandSelection("77G")

[09:05:44]  [RadarAPI]: ar1.SelectChipVersion("XWR1443")

[09:05:44]  [RadarAPI]: Status: Passed

[09:05:44]  Device Status : XWR1443/QM/SOP:2/ES:3

[09:05:44]  [RadarAPI]: ar1.SaveSettings('C:\Users\Lenovo\AppData\Roaming\RSTD\ar1gui.ini')

 

Both the DCA1000EVM and AWR1443 Boost were configured according to the manual. The FPGA connection is functioning properly, and I even attempted to refresh the 1443 Boost using Uniflash before restarting mmWaveStudio. However, the previously mentioned errors persist.
      After replacing the original DCA1000EVM with another unit, the system operates normally. Could the engineers help identify what might be wrong with this specific DCA1000EVM unit?

 

Your assistance is appreciated.

Regards,

Wang

  • Hi,

    When you show hidden devices (Device Manager>View>Show hidden devices), do any AR-DevPack-EVM-012 ports show up?

    Could you try deleting all instances of the USB Serial COM port driver that show up when you connect to FTDI, then reconnect and show me the COM ports?

    Thank you,

    Jin

  • Hi Jin,

    First of all, thank you for your response. After enabling the display of hidden devices, I did see the port records (AR-DevPack-EVM-012) previously connected to other DCA1000EVM devices.

    I then removed all of them. After reconnecting the device, it showed the following (as below)

    but even after updating the drivers, the port name AR-DevPack-EVM-012 still did not appear.

    Thank you!

  • Hi,

    Great, this is expected. Now could you try updating the driver again, on those USB serial ports? 

    Thank you,

    Jin

  • Hi Jin,
    I have updated the drivers again on those USB serial ports, but the port name AR-DevPack-EVM-012 still does not appear. I’m wondering if my FTDI driver version is too outdated and whether I need to download a new version of the FTDI driver—and if so, where can I download it from?
    Thank you!

  • Hi, 

    I've tried to recreate the setup shown in your first screenshot:

    1. Connect to the DCA1000EVM FTDI and power it on. Delete the all instances of the USB serial ports/AR-DevPack-EVM from Ports (COMP & LPT) and Universal Serial Bus controllers section (If they are present on both).

    2. Disconnect and reconnect the DCA1000EVM. (Please try the next steps even if the devices show up as USB Serial Port for you)

    3. Update the driver using the FTDI driver in the Studio package:

    (Right-click) device > Update Driver > Browse my computer for drivers > Search for drivers in this location: <mmwave studio directory>\ftdi:

    After clicking Next:

    4. It should now show up under Universal Serial Bus controllers:

    Do this for each device.

    5. Now, the AR-DevPack-EVM-012 A~D should show up under Universal Serial Bus controllers. There will also be unidentified USB Serial Port devices under Other devices.

    6. Update the drivers for each USB Serial Port device again, as explained in Step 3.

    Then, all 4 AR-DevPacks should show up under Ports (COM & LPT) and be good to use. 

    Please give this a try and let me know at which step it is failing.

    Thank you,

    Jin

  • Hi Jin

    Here are the results I obtained by following your instructions:

    1. I deleted all instances under both Ports and Universal Serial Bus controllers (previously I only removed instances under Ports, while there were still numerous instances remaining under Universal Serial Bus controllers).
    2. Reconnected the DCA1000EVM. (Without any manual intervention, the device initially displayed as "Quad RS232-HS", then after a moment showed "USB Serial Port". Following a loading period, the Ports section displayed "USB Serial Port A~D", while Universal Serial Bus controllers showed "USB Serial Converter A~D")
    3. During the previous step, the Universal Serial Bus controllers already displayed "USB Serial Converter A~D" without driver updates. After updating the drivers, the device names remained displayed as "USB Serial Converter A~D".

    Thank you!

     

  • Hi,

    The "Quad RS232-HS" briefly showing up suggests that the FTDI chip is detected, but the driver isn't able to take control as expected. Could you try the following to narrow down the issue:

    • Try the same steps with MMWAVE-STUDIO-2G and see if you get this same behavior
    • Try the same steps on a different PC.

    Thank you,

    Jin

  • Hi Jin:
    I apologize for the late response. I used the mmWstudio – 2G (03.00.00.14) version, but during the reset step, I still encountered the error: "Failed to open/close GpioControl, Error Type: PROTOCOL ERROR". I then switched to a different computer and tried connecting again, but the port name still appeared abnormal, and the same error occurred when connecting to Studio.
    Thank you!

  • Hi,

    Could you refer to the following threads and try out the debugging steps described there:

    Could you confirm what power supply you are using for the DCA1000?

    Thank you,

    Jin

  • Hi Jin:
    I followed the steps to power the DCA1000 separately (using a 5V/3A power supply input) and connected only the Radar_FTDI port, but the issue still persists.
    I also checked the DCA1000 Debugging manual and noticed that similar problems are typically caused by firmware and chip version mismatches. However, I’m now completely stuck and have no further leads.
    Thank you!

  • Hi,

    Sorry for the delayed response. At this point, we are not sure what could be causing the issue either, and do not have the know-how to debug the FTDI firmware. Please work with the Customer Service Center or your distributor to coordinate a return.

    Thank you,

    Jin