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.

IWR6843AOPEVM: SPI connectivity issue in mmwaveStudio and RESP timeout when I try SPI Connect

Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: MMWAVEICBOOST

Tool/software:

Referencing this thread: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1275979/awr6843isk-mss-power-up-async-event-was-not-recieved

I have a REV G 6843 AOP and its ES2 and hitting these errors:

[15:13:19] Status: Failed, Error Type: RESP TIMEOUT
[15:13:23] MSS Power Up async event was not received!

Also I was never able to use mmwaveStudio 4.3.1.0 (64 bit one) but the 32bit one (mmwveStudio 2.1.0.1) works so far but never was successful to bring up the SPI for data capture.

I also tried rawDataCaptureGUI_DCA1000CLI.exe in radar_tool_box but that didn't work either. I guess without the SPI connect it cannot capture. Could you please help me unblock? Thank you!

Here's a screenshot of the studio window:

  • Though not specifically mentioned in this thread I am using DCA1000 without a MMWAVEICBOOST as Rev G supports that. Hoping to see some raw ADC data with your expert help. Thanks!

  • Was able to get past the SPI connectivity with BSS, MSS binaries loaded. Then switched to running the rawDataCaptureGUI_DCA1000CLI.exe but hitting this error:


    Reset AR Device command : Success

    ans =

    0


    FPGA Configuration command : Success

    ans =

    0


    Configure Record command : Success

    Start Record command : Success
    Serial port is already open. Power cycle the device and re-run the application...
    Sending configuration from <snip>AOP_6m_staticRetention_modified.cfg file ...
    Unrecognized function or variable 'configureTerminator'.

    Error in sendconfiguration>writelineslow (line 83)

    Error in sendconfiguration (line 46)

    Error in rawDataCaptureGUI_DCA1000CLI (line 38)

    MATLAB:UndefinedFunction
    PS C:\ti\radar_toolbox_2_20_00_05\tools\Adc_Data_Capture_Tool_DCA1000_CLI>

  • With the help of this: https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.12.1&node=A__AGTrhNYW8jE6cMxbovlfaA__com.ti.mmwave_industrial_toolbox__VLyFKFf__4.12.1

    I went a step further but still not able to capture the ADC data.

    When I tried "start Frame" it fails:

    [08:20:47] [RadarAPI]: ar1.CaptureCardConfig_StartRecord("C:\\ti\\mmwave_studio_02_01_01_00\\mmWaveStudio\\PostProc\\adc_data.bin", 1)
    [08:20:47] [RadarAPI]: Sending start_record command to DCA1000
    [08:20:57] [RadarAPI]:
    [08:20:57] Start Record :
    [08:20:57] Timeout Error! System disconnected
    [08:20:58] [RadarAPI]: ar1.StartFrame()
    [08:21:02] Status: Failed, Error Type: RESP TIMEOUT
    [08:21:13] [RadarAPI]: ar1.StartFrame()
    [08:21:17] Status: Failed, Error Type: RESP TIMEOUT
    [08:22:01] [RadarAPI]: ar1.CaptureCardConfig_StartRecord("C:\\ti\\mmwave_studio_02_01_01_00\\mmWaveStudio\\PostProc\\adc_data.bin", 1)
    [08:22:01] [RadarAPI]: Sending start_record command to DCA1000
    [08:22:09] [RadarAPI]: ar1.StartFrame()
    [08:22:13] Status: Failed, Error Type: RESP TIMEOUT
    [08:22:23] [RadarAPI]: ar1.StopFrame()
    [08:22:35] [RadarAPI]: ar1.StartMatlabPostProc("C:\\ti\\mmwave_studio_02_01_01_00\\mmWaveStudio\\PostProc\\adc_data.bin")
    [08:22:35] [RadarAPI]: No of files Captured: 0, Total no of frames for each device : 8
    [08:22:35] Error : The number of files captured is zero!

  • Hello Surya,

    So it seems that you are no longer getting the "MSS Power Up async event was not received!" parameter is that correct? You are able to power up, and get DCA1000's FPGA information, but when you go to start the sensor via DCA1000 ARM and Trigger Frame the .bin is empty correct?



    What this means is that similar to when you run our example projects, when a profile/chirp configuration is invalid due to one or more parameters, the front end is unable to start. Have you verified that the settings you are putting for mmWaveStudio's Sensor Configuration tab is at least valid when inputted into the mmWaveSensingEstimator? Try using a default configuration to try to get it working at least once. The settings seen in the above screenshot should work as far as I am aware.

    Best Regards,

    Pedrhom

  • Hello Pedrhom,

      Thank you for your reply. Yes I went past the SPI connectivity issue (apologies for the title of this post) but yes the issue is with getting the data. I do not see the .bin file at all. Start Frame fails with that error I mentioned. I am following this (https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.12.1&node=A__AGTrhNYW8jE6cMxbovlfaA__com.ti.mmwave_industrial_toolbox__VLyFKFf__4.12.1) from one of your responses on E2E and used the exact values.

    I am using 3D people tracking firmware. Hope that is not an issue. I am trying just the default config for now (the ones from the above link).

    Here's a snapshot of the sensorConfig tab (the only difference I notice in my case is that under Frame "Active-Ramp Duty Cycle" is 19.2% and "Duty Cycle" is 51.2% whereas the guide shows "Duty Cycle" as 0%)

  • I did use the mmWaveSensingEstimator and here's where it fails for frameconfig. profile and chirp config set were fine:

    [16:14:41] [RadarAPI]: ar1.FrameConfig(0, 2, 18, 48, 55, 0, 0, 1)
    [16:14:45] Status: Failed, Error Type: RESP TIMEOUT
    [16:14:45] [RadarAPI]: MatlabProc Status: Failed

  • Any help is greatly appreciated. I am back to the SPI connectivity issue again Disappointed Have been trying it for over a day with different cables but nothing seems to be working.

    [08:55:42] ***Script completed successfully.***
    [08:55:54] [RadarAPI]: Opening Gpio Control Port()
    [08:55:54] [RadarAPI]: Status: Passed
    [08:55:54] [RadarAPI]: Opening Board Control Port()
    [08:55:54] [RadarAPI]: Status: Passed
    [08:55:55] [RadarAPI]: ar1.FullReset()
    [08:55:55] [RadarAPI]: Status: Passed
    [08:55:56] [RadarAPI]: Closing Board Control Port()
    [08:55:56] [RadarAPI]: Status: Passed
    [08:55:56] [RadarAPI]: Closing Gpio Control Port()
    [08:55:56] [RadarAPI]: Status: Passed
    [08:55:56] [RadarAPI]: ar1.SOPControl(2)
    [08:55:56] [RadarAPI]: Status: Passed
    [08:55:59] [RadarAPI]: ar1.Connect(22,115200,1000)
    [08:56:00] [RadarAPI]: ar1.Calling_IsConnected()
    [08:56:01] Device Status : UnDetDe/QM/SOP:2/ES:2
    [08:56:01] [RadarAPI]: ar1.SaveSettings('C:\<snip>AppData\Roaming\RSTD\ar1gui.ini')
    [08:56:05] [RadarAPI]: ar1.frequencyBandSelection("60G")
    [08:57:13] [RadarAPI]: ar1.DownloadBSSFw("C:\\ti\\mmwave_studio_02_01_01_00\\rf_eval_firmware\\radarss\\xwr68xx_radarss.bin")
    [08:57:13] [RadarAPI]: Downloading BSS ROM RPRC Binary..
    [08:58:01] [RadarAPI]: ar1.GetBSSFwVersion()
    [08:58:01] [RadarAPI]: BSSFwVersion:(06.01.01.00 (08/04/19))
    [08:58:04] [RadarAPI]: ar1.DownloadMSSFw("C:\\ti\\mmwave_studio_02_01_01_00\\rf_eval_firmware\\masterss\\xwr68xx_masterss.bin")
    [08:58:04] [RadarAPI]: Downloading MSS RPRC Binary..
    [08:58:23] [RadarAPI]: ar1.GetMSSFwVersion()
    [08:58:23] [RadarAPI]: MSSFwVersion:(02.00.00.03 (27/08/19))
    [08:58:44] [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
    [08:58:44] Status: Failed, Error Type: RESP TIMEOUT
    [08:58:49] MSS Power Up async event was not received

  • After changing all the cables as suggested by Pedrhom in a different post the SPI interface came up and I was able to get SPI interface up and capture raw data. I specifically got GOLD plated micro USB cables and GOLD plated ethernet cable - perhaps a good investment. I will close this thread now. Thanks!