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.

MMWCAS-DSP-EVM: RS232 connection

Part Number: MMWCAS-DSP-EVM
Other Parts Discussed in Thread: TDA2, MMWCAS-RF-EVM,

Hello,

We are using RF cascaded EVM radar together with MMW-DSP-EVM. 

We are at the begining phase.

We have a problem of RS232 connectivity. We installed all the drivers in the manual and we saw the two PCB ports in the device manager (com10 and com9) in PC (as shown below).

The mmwave 2.1.0.0 didn't see RS232 connection (see below).

Could you please also show us a training video for the mmwave studio cascaded (like the one of mmwave studio single board)? 

Thanks in advance.

Best,

Zijian 

  • Hi,

    Lua scripts are provided to make the configuration easier.

    Are you able to run the Lua scripts are described in the documentation?

    thank you

    Cesar

  • Hello,

    Thank you for the support. It gave the same issue of Connectivity. When i run the “Cascade_Configuration_TestSource.lua", i have the same error message, please find the pictures attached.

    Best regards,

    Khaldoun

  • I have the same problem. Have you solved it? How was it solved?

  • Hello,

    The problem of RS232 connection did not solve yet, but it does not afftect on data acquisition !

    Other errors are solved by using the 2nd-generation firmware package (DFP) meta image 'xwr22xx_metaImage.bin' file in .Lua script. 

    For the version of meta image, you need to read the marking on the chips (it should be xAWR2243P or equivalent for using 'xwr22xx_metaImage.bin' file).

    Best regards,

    Khaldoun

  • Hello,

     The problem of RS232 connection did not solve yet,  as well as the data acquisition. How did you do that?  I have load the  2nd-generation firmware package (DFP) meta image 'xwr22xx_metaImage.bin'。 How to config the radar device 2-4?   After click on the RF Power-up, I load the lua commands file  'cascade_capture.lua' , and it has the output of 'Frame Periodicity Response from Capture Card time out !!'   So did I miss any steps? I look forward to your detailed explanation

  • Hello,

    Configuration of radar devices 2-4 manuelly is quite complex. The easiest way is to use .Lua scripte 'Cascade_Configuration_TestSource' which you can find in Cascade script. 

    Please check the path of meta image Inside .Lua scripte, which it must be 'xwr22xx_metaImage.bin'. I attached where you need to modify and the expected working device interface.

    For data acquestion, click on “TDAxx ARM” with any one of the device selected. This should be done only once for a capture session.  By default, the framing status (refer the below screenshot) is “NOT FRAMING” for all the devices.  Click on Trigger frame for all the enabled slave devices (one device at a time). The framing status will be updated to “WAITING FOR TRIGGER” once the frame start async event is obtained for the respective devices.  Choose the master (device 1) and click on Trigger frame. Once the frame start async event for the master is received, the framing status is updated.

    Then you need to move the data from SSD card to the C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\PostProc by using WinSCP program.

  • Hello,

          I have  used .Lua scripte 'Cascade_Configuration_TestSource' and  checked the path of meta image Inside .Lua scripte. But the SPI  of radar devices 2-4  is  still showed 'Disconnected'. 

     When  I click on “TDAxx ARM” with any one of the device selected, the output still presents 'Frame Periodicity Response from Capture Card time out !!'  It seems  no difference  afrer loading  the  **.lua scripte.   I havenot changed the IP Address for the TDA2 Host Board.  Is it necessary ?

  • Hello, 

    SPI must be connected to be able to capture data, please find the hardware connected statues. You can check manuelly SPI connection. The 

    IP address is 192.168.33.180, which different from the static Ethernet IP address 192.168.33.30.

    Best regards,

    Khaldoun

  • Hi Zijian, 

    The mmWave Studio tool does not use a UART/RS232 connection for mastering the AWR devices on the MMWCAS-RF-EVM. So the status of RS232 being disconnected is normal for MMWCAS-RF-EVM operation. 

    The mmWave Studio tool connectivity is only between the MMWCAS-DSP-EVM and host PC over Ethernet. The TDA2 host processor on the MMWCAS-DSP-EVM runs an application which acts as a bridge between the mmWave Studio Ethernet connection and 2 SPI ports on the TDA2. The TDA2 directly masters the 4 AWR devices over these SPI ports. 

    I hope that helps. 

    Thank you,

    -Randy