• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 619 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

AWR1243BOOST: SPI Connect RESP TIMEOUT issue in mmWave Studio with a DCA1000EVM

AWR1243BOOST: SPI Connect RESP Timeout Problem

Mohammad
Prodigy 120 points
Part Number: AWR1443BOOST
Other Parts Discussed in Thread: IWR1443, DCA1000EVM, IWR1443BOOST, IWR1243, UNIFLASH

Hi,

I've been using an IWR1443 device with DCA1000EVM for a while, and recently I started running into the issue I mentioned in the title. I follow the procedure to upload BSS/MSS firmware, and when I click SPI Connect in mmWave Studio, I receive the error: RESP TIMEOUT: MSS Power Up async event was not received.

I've tried resetting SFLASH a couple of times, and it does not solve my problem. I'm connecting to device in SOP2 mode (SOP0 and SOP1 has jumpers, SOP2 port hasn't). I also know that my firewall is turned off, and I run mmWave Studio as an administrator.

Lastly, I've also tried flashing a different firmware, vital signs monitor for the device, and it seems that the demo is also working perfectly fine. I did not run into any errors while flashing the demo firmware.

I've also tried other solutions in the forum, but they did not seem to help. I also have a power adapters that are rated at 5V, 3A; thus, they should not be an issue. (Everything was working some time ago anyways).

I've attached the log files 

logs_resp_timeout_error.txt 
GM: Constructor
GM: Thu Feb 20 14:28:16 2020
RSTD.Transmit("/Settings")
[14:28:16]  
[14:28:16]  ### Running Startup script: "C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\Scripts\Startup.lua" ###
[14:28:16]  RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
[14:28:16]  RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")
[14:28:16]  Scripter ignored: Attempt to UnBuild() again or before Build.
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_02_01_00_00\\mmWaveStudio\\Clients\\\\LabClient.dll")
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")
[14:28:16]  RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_02_01_00_00\\mmWaveStudio\\RunTime\\SAL.dll")
[14:28:16]  RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")
[14:28:16]  RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")
[14:28:16]  RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")
[14:28:16]  RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")
[14:28:16]  RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")
[14:28:16]  RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")
[14:28:16]  RSTD.Transmit("/")
[14:28:16]  RSTD.SaveSettings(): Settings saved to "***********\AppData\Roaming\RSTD\config.xml"
[14:28:16]  RSTD.Build()
[14:28:16]  RSTD.SaveSettings(): Settings saved to "***********\AppData\Roaming\RSTD\config.xml"
[14:28:16]  RSTD.Transmit("/")
[14:28:16]  RSTD.AL_Build()
[14:28:16]  RSTD.AL_LoadXml()
[14:28:16]  RSTD.Transmit("/")
[14:28:16]  RSTD.AL_Init()
[14:28:16]  RSTD.Clients_Build()
[14:28:16]  GM: Init
[14:28:16]  GM: Loaded 'C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\Clients\\LabClient.dll'
[14:28:16]  GM: 1 Guest (s) init
[14:28:16]  GM: 1 Module(s) init
[14:28:16]  GM: 2 Tab   (s) init
[14:28:16]  RSTD.Client_LoadXml()
[14:28:17]  [RadarAPI]: ar1.selectRadarMode(0)
[14:28:17]  [RadarAPI]: Status: Passed
[14:28:17]  Matlab Runtime Engine is installed
[14:28:17]  [RadarAPI]: Starting Matlab Engine..
[14:28:18]  [RadarAPI]: Matlab Engine Started!
[14:28:19]  [RadarAPI]: ar1.selectCascadeMode(0)
[14:28:19]  [RadarAPI]: Status: Passed
[14:28:19]  [RadarAPI]: ar1.LoadSettings('***********\AppData\Roaming\RSTD\ar1gui.ini')
[14:28:20]  TESTING = false
[14:28:20]  RstdNet: Port 2777: Listening..
[14:28:20]  
[14:28:20]  ***Script completed successfully.***
[14:28:22]  [RadarAPI]: Opening Gpio Control Port()
[14:28:22]  [RadarAPI]: Status: Passed
[14:28:23]  [RadarAPI]: Opening Board Control Port()
[14:28:23]  [RadarAPI]: Status: Passed
[14:28:24]  [RadarAPI]: ar1.FullReset()
[14:28:24]  [RadarAPI]: Status: Passed
[14:28:25]  [RadarAPI]: Closing Board Control Port()
[14:28:25]  [RadarAPI]: Status: Passed
[14:28:25]  [RadarAPI]: Closing Gpio Control Port()
[14:28:25]  [RadarAPI]: Status: Passed
[14:28:25]  [RadarAPI]: ar1.SOPControl(2)
[14:28:25]  [RadarAPI]: Status: Passed
[14:28:26]  [RadarAPI]: ar1.Connect(4,921600,1000)
[14:28:27]  [RadarAPI]: ar1.Calling_IsConnected()
[14:28:28]  [RadarAPI]: ar1.SelectChipVersion("AR1243")
[14:28:28]  [RadarAPI]: Status: Passed
[14:28:28]  [RadarAPI]: ar1.SelectChipVersion("AR1243")
[14:28:28]  [RadarAPI]: Status: Passed
[14:28:28]  [RadarAPI]: ar1.deviceVariantSelection("XWR1443")
[14:28:28]  [RadarAPI]: Status: Passed
[14:28:28]  [RadarAPI]: ar1.frequencyBandSelection("77G")
[14:28:28]  [RadarAPI]: ar1.SelectChipVersion("XWR1443")
[14:28:28]  [RadarAPI]: Status: Passed
[14:28:28]  Device Status : XWR1443/QM/SOP:2/ES:3
[14:28:28]  [RadarAPI]: ar1.SaveSettings('*********\AppData\Roaming\RSTD\ar1gui.ini')
[14:28:30]  [RadarAPI]: ar1.DownloadBSSFw("C:\\ti\\mmwave_studio_02_01_00_00\\rf_eval_firmware\\radarss\\xwr12xx_xwr14xx_radarss.bin")
[14:28:30]  [RadarAPI]: Downloading BSS Patch RPRC Binary..
[14:28:32]  [RadarAPI]: ar1.GetBSSFwVersion()
[14:28:32]  [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[14:28:33]  [RadarAPI]: ar1.GetBSSPatchFwVersion()
[14:28:33]  [RadarAPI]: BSSPatchFwVersion:(01.02.05.02 (30/04/19))
[14:28:33]  [RadarAPI]: ar1.DownloadMSSFw("C:\\ti\\mmwave_studio_02_01_00_00\\rf_eval_firmware\\masterss\\xwr12xx_xwr14xx_masterss.bin")
[14:28:34]  [RadarAPI]: Downloading MSS RPRC Binary..
[14:28:37]  [RadarAPI]: ar1.GetMSSFwVersion()
[14:28:37]  [RadarAPI]: MSSFwVersion:(01.02.05.01 (12/07/19))
[14:28:43]  [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
[14:28:43]  Status: Failed, Error Type: RESP TIMEOUT
[14:28:47]  MSS Power Up async event was not received!
and I appreciate your help!

Thanks

Ps. I posted this by selecting 'ask a related question' on a forum post that had a similar problem with IWR1243; hence my part number shows up as 1243. I have IWR1443BOOST, as I mentioned in the post.

  • 0
    TI__Guru 50240 points

    Hi Mohammad,

    Have you seen the DCA1000 EVM  training video?

    Cheers,

    Akash

  • 0
    TI__Mastermind 32805 points

    HI, 

    What radar studio version do you use and what is your EVM version?  

    Did you see six COM port in your device manager?

    And here is another notes specially about xwr1243/1443:

    The issue with 1243/1443 is that you need to erase the flash before loading via studio. So that means use Uni-flash first to erase flash then close and change SOP mode and go through normal procedures.

    If you see this error the symptoms are:

    -MSS version reads as 0.0.0.0 etc

    -SPI connect returns time out.

    Best,

    Zigang

  • 0 in reply to zigang Yang
    Prodigy 120 points

    Hi Zigang,

    I am seeing 6 COM ports in my device manager; and as I have noted in my original post, I have erased flash using Uniflash a couple of times, and then tried using mmWave studio to capture data. I've been doing this in the way that you have suggested. (Changing SOP modes etc.). I previously had that MSS version 0.0.0.0 problem (a couple of months ago), but it is not the case here. I think you should be able to see from the log files that MSSFw version gets updated to 01.02.05.01 successfully, but then, in the next step, when I try to do SPI Connect, I receive this RESP TIMEOUT problem.

    I am using mmWave Studio 02.01.00.00, and I have a ES3.0 device. Can you clarify what you are asking by EVM version? In my device manager, I see the DCA1000EVM board as AR-DevPack-EVM-012, but I'm not sure if this is what you are asking.

    @Akash, I have seen the video, and I'm actually trying to do the data collection in the same way.

    Thanks

  • 0 in reply to Mohammad
    TI__Mastermind 23855 points

    Hello,

    If you have a RevB board (it should say RevA or RevB on the front silk screen) you need to set the SPI/CAN selector switch to SPI mode. You can find more information about this switch in section 2.7.4 of the user's guide.

    http://www.ti.com/lit/ug/swru507b/swru507b.pdf

    Regards,

    Adrian

  • 0 in reply to aozer
    Prodigy 120 points

    Hi Adrian,

    I have a REV B board, and I have checked the SPI/CAN selector; but it seems the selector has been switched to SPI mode already. I set up the board a while ago; thus, I totally forgot to check this step. Unfortunately, this does not seem to solve the problem.

    Thanks for the suggestion,

    Mohammad

  • 0 in reply to Mohammad
    TI__Mastermind 32805 points

    Hi, Mohammad:

    Yes, your radar studio version matches with your EVM version.  This information can always be checked at radar studio release notes. 

    So, your system was working and it just stopped working without any change of hardware and software?  

    Is it possible to try another power supply?

    Can you send the pictures of your setup over before and after the error?

    Best,

    Zigang

  • 0 in reply to zigang Yang
    TI__Mastermind 32805 points

    HI, 

    I have not received any reply from you for two weeks. Did your problem solved yet?  

    Best,

    Zigang

  • 0 in reply to zigang Yang
    TI__Mastermind 32805 points

    HI, Mohammad:

    I have not received from you for a long time.  Have you resolved your problem?

    Best,

    Zigang

  • 0 in reply to zigang Yang
    Prodigy 120 points

    Hi Zigang,

    Sorry for the delayed reply. I was looking to purchase some additional power supplies; but in the mean time my device started working perfectly fine. I wanted to wait for some time to see if  I receive the same error again; but it is totally fine now (for the last two weeks).

    I did not change anything on the device, and everything was fine next day in the morning. I do not think this is related to my computer, because I had tried on several computers for a couple of days before posting the problem here. I'm wondering if this indicates any hardware problems, or any compatibility issues.

    Thanks for all the help,

    Mohammad

  • 0 in reply to Mohammad
    TI__Mastermind 32805 points

    Hi, Mohammad:

    Glad that your problem is gone.  This had happened to me as well.   The reason is still unknown to me as well.

    Best,

    Zigang