• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 422 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.

DCA1000EVM: DCA1000EVM + IWR1443 data acquisition

Annie Liu
Genius 10295 points
Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR1443BOOST,

Hi Team,

The customer wants to know that he sets the parameters like this, targets around 40 to 50 meters are not shown. 

May I ask which parameter setting is unreasonabl？

Why can't Duty Cycle be set to 100%?

Best regards,

Annie

  • 0
    TI__Genius 10295 points

    GM: Constructor
    GM: Thu Apr 16 13:29:52 2020
    RSTD.Transmit("/Settings")
    [13:29:52]
    [13:29:52] ### Running Startup script: "C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Scripts\Startup.lua" ###
    [13:29:52] RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    [13:29:52] RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")
    [13:29:52] Scripter ignored: Attempt to UnBuild() again or before Build.
    [13:29:52] RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Clients\\\\LabClient.dll")
    [13:29:53] RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")
    [13:29:53] RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")
    [13:29:53] RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")
    [13:29:53] RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")
    [13:29:53] RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")
    [13:29:53] RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\RunTime\\SAL.dll")
    [13:29:53] RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")
    [13:29:53] RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")
    [13:29:53] RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")
    [13:29:53] RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")
    [13:29:53] RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")
    [13:29:53] RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")
    [13:29:53] RSTD.Transmit("/")
    [13:29:53] RSTD.SaveSettings(): Settings saved to "C:\Users\Zhaoy\AppData\Roaming\RSTD\config.xml"
    [13:29:53] RSTD.Build()
    [13:29:53] RSTD.SaveSettings(): Settings saved to "C:\Users\Zhaoy\AppData\Roaming\RSTD\config.xml"
    [13:29:53] RSTD.Transmit("/")
    [13:29:53] RSTD.AL_Build()
    [13:29:53] RSTD.AL_LoadXml()
    [13:29:53] RSTD.Transmit("/")
    [13:29:53] RSTD.AL_Init()
    [13:29:53] RSTD.Clients_Build()
    [13:29:53] GM: Init
    [13:29:53] GM: Loaded 'C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Clients\\LabClient.dll'
    [13:29:53] GM: 1 Guest (s) init
    [13:29:53] GM: 1 Module(s) init
    [13:29:53] GM: 2 Tab (s) init
    [13:29:53] RSTD.Client_LoadXml()
    [13:29:53] [RadarAPI]: Starting Matlab Engine..
    [13:29:57] [RadarAPI]: Matlab Engine Started!
    [13:30:00] [RadarAPI]: ar1.LoadSettings('C:\Users\Zhaoy\AppData\Roaming\RSTD\ar1gui.ini')
    [13:30:00] TESTING = false
    [13:30:00]
    [13:30:00] ***Script completed successfully.***
    [13:30:14] [RadarAPI]: Opening Gpio Control Port()
    [13:30:14] [RadarAPI]: Status: Passed
    [13:30:15] [RadarAPI]: Opening Board Control Port()
    [13:30:15] [RadarAPI]: Status: Passed
    [13:30:16] [RadarAPI]: ar1.FullReset()
    [13:30:16] [RadarAPI]: Status: Passed
    [13:30:16] [RadarAPI]: Closing Board Control Port()
    [13:30:16] [RadarAPI]: Status: Passed
    [13:30:16] [RadarAPI]: Closing Gpio Control Port()
    [13:30:16] [RadarAPI]: Status: Passed
    [13:30:16] [RadarAPI]: ar1.SOPControl(2)
    [13:30:16] [RadarAPI]: Status: Passed
    [13:30:18] [RadarAPI]: ar1.Connect(3,115200,1000)
    [13:30:19] [RadarAPI]: ar1.Calling_IsConnected()
    [13:30:20] [RadarAPI]: ar1.SelectChipVersion("AR1243")
    [13:30:20] [RadarAPI]: Status: Passed
    [13:30:20] [RadarAPI]: RS232 is not connected ..!!!!
    [13:30:20] [RadarAPI]: ar1.frequencyBandSelection("77G")
    [13:30:20] [RadarAPI]: ar1.SelectChipVersion("XWR1443")
    [13:30:20] [RadarAPI]: Status: Passed
    [13:30:20] Device Status : XWR1443/QM/SOP:2/ES:3
    [13:30:21] [RadarAPI]: ar1.SelectChipVersion("AR1243")
    [13:30:21] [RadarAPI]: Status: Passed
    [13:30:21] [RadarAPI]: ar1.SelectChipVersion("XWR1443")
    [13:30:21] [RadarAPI]: Status: Passed
    [13:30:21] Device Status : XWR1443/QM/SOP:2/ES:3
    [13:30:21] [RadarAPI]: ar1.SaveSettings('C:\Users\Zhaoy\AppData\Roaming\RSTD\ar1gui.ini')
    [13:30:22] [RadarAPI]: ar1.DownloadBSSFw("C:\\ti\\mmwave_studio_02_00_00_02\\rf_eval_firmware\\radarss\\xwr12xx_xwr14xx_radarss.bin")
    [13:30:23] [RadarAPI]: Downloading BSS Patch RPRC Binary..
    [13:30:30] [RadarAPI]: ar1.GetBSSFwVersion()
    [13:30:30] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
    [13:30:31] [RadarAPI]: ar1.GetBSSPatchFwVersion()
    [13:30:31] [RadarAPI]: BSSPatchFwVersion:(01.02.00.03 (24/10/18))
    [13:32:31] [RadarAPI]: ar1.DownloadMSSFw("C:\\ti\\mmwave_studio_02_00_00_02\\rf_eval_firmware\\masterss\\xwr12xx_xwr14xx_masterss.bin")
    [13:32:31] [RadarAPI]: Downloading MSS RPRC Binary..
    [13:32:51] [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
    [13:32:51] [RadarAPI]: Status: Passed
    [13:32:51] MSS power up done async event received!
    [13:32:59] [RadarAPI]: ar1.RfEnable()
    [13:32:59] BSS power up done async event received!
    [13:32:59] [RadarAPI]: Status: Passed
    [13:33:00] [RadarAPI]: ar1.GetBSSFwVersion()
    [13:33:00] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
    [13:33:01] [RadarAPI]: ar1.GetBSSPatchFwVersion()
    [13:33:01] [RadarAPI]: BSSPatchFwVersion:(01.02.00.03 (24/10/18))
    [13:33:15] [RadarAPI]: ar1.ChanNAdcConfig(1, 1, 0, 1, 1, 1, 1, 2, 2, 0)
    [13:33:15] [RadarAPI]: Status: Passed
    [13:33:25] [RadarAPI]: ar1.LPModConfig(0, 0)
    [13:33:25] [RadarAPI]: Status: Passed
    [13:33:28] [RadarAPI]: ar1.RfInit()
    [13:33:28] MSS RF Error status Async event recieved(0x1)
    [13:33:28] BSS CPU Fault error status Async event recieved(0x3)
    [13:33:28] Reserved(0x0)
    [13:33:28] LineNum(0x4D6)
    [13:33:28] FaultLR(0x2A8AE)
    [13:33:28] FaultPrevLR(0x0)
    [13:33:28] FaultSPSR(0x6000011F)
    [13:33:28] FaultSP(0x800FB68)
    [13:33:28] FaultCauseAddress(0x0)
    [13:33:28] FaultErrorStatus(0xFFFF)
    [13:33:28] FaultErrorSourced(0xFF)
    [13:33:28] FaultAXIErrorType(0xFF)
    [13:33:28] FaultAccessType(0xFF)
    [13:33:28] FaultRecoveryType(0xFF)
    [13:33:28] Reserved2(0x0)
    [13:33:28] BSS ESM Fault error status Async event recieved(0x0)
    [13:33:28] Analog fault Async event recieved(0x0)
    [13:33:28] Reserved(0x0)
    [13:33:28] Reserved2(0x0)
    [13:33:28] FaultSig(0x0)
    [13:33:28] Reserved3(0x0)
    [13:33:31] [RadarAPI]: Status: Passed
    [13:33:34] [RadarAPI]: ar1.DataPathConfig(513, 1216644097, 0)
    [13:33:34] [RadarAPI]: Status: Passed
    [13:33:38] [RadarAPI]: ar1.LvdsClkConfig(1, 1)
    [13:33:42] [RadarAPI]: Status: Failed, Error Type: RESP TIMEOUT
    [13:33:45] [RadarAPI]: ar1.LVDSLaneConfig(0, 1, 1, 1, 1, 1, 0, 0)
    [13:33:48] Status: Failed, Error Type: RESP TIMEOUT

  • 0 in reply to Annie Liu
    TI__Mastermind 25835 points

    Hello,

       From the logs it appears that you are using older version of mmWave studio, Please use the latest version of the mmWave studio.  If you still find the error post the studio screenshots and logs. 

    For the the chirp configuration you could refer to the Chirp database in the TI resource explorer folder in the below link.

    http://dev.ti.com/tirex/explore/node?node=ALYHkY2xyhq2-EgWIUuw-Q__VLyFKFf__LATEST

    This provides pointer for various application chirp configuration. This could be adapted and modified depending upon customer needs.

    100% duty-cycle is not realistic mainly due to:

     1) One need to perform data processing from the mmWave sensor i.e. Doppler FFT,  Angle of arrival processing, detection and few more post processing functions depending upon customer use case requirements, these elements needs certain time allocation between frame and chirp intervals. In real time embedded system these data need to be processed and consumed hence at higher percent duty-cycled (50+%) cases you may not get sufficient time for processing. Hence 100% duty-cycle is not realistic.

    2) At higher duty-cycles sensor also dissipates higher power, This would be concern from reliability perspective for prolonged period of operation without thermal protection for the device. 

    Thanks and regards,

    CHETHAN KUMAR Y.B. 

  • 0 in reply to CHETHAN KUMAR Y.B.
    TI__Mastermind 24955 points

    Annie,

    The customer needs to set the CAN/SPI switch on the IWR1443BOOST to the "SPI" position. The switch is currently set in the middle. This is why the SPI Connect step is failing every time. 

    Please also relay the importance of using a second power supply for the DCA1000EVM. This point has been reiterated several times now yet this suggestion has not been taken into advisement.

    Please take these two steps immediately and there should be no issue with using mmWave Studio with the IWR1443BOOST EVM.

    Regards,

    Kyle