• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 634 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.

Original question:

AWR1642: DCA1000+AWR1642,spi connect

AWR1642: SPI Connect using lua script with mmWaveStudio (and DCA1000EVM)

John Lee35
Prodigy 70 points
Part Number: AWR1642
Other Parts Discussed in Thread: DCA1000EVM, UNIFLASH,

Hi,

I have been having trouble with the "SPI Connect" step with my AWR1642 + DCA1000EVM when I try to do so from the lua shell or a lua script. The line that has been giving me trouble has been ar1.PowerOn(0, 1000, 0, 0). The thing that has been confusing me is that clicking "SPI Connect" on the graphical interface works. I've tried erasing the sFlash using uniflash, but that hasn't made a difference either.

Is there something that the "SPI Connect" button does under the hood other than ar1.PowerOn(0, 1000, 0, 0)? I cannot figure out why there is a difference between the graphical interface and the lua shell. Thanks!

  • 0
    TI__Guru 69970 points

    Hi John,

    Did you try the LUA script provided in the Studio installation?

    C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\Scripts\DataCaptureDemo_xWR.lua

    Make sure that device is being set in developoment mode (jumpers on AWR1642BOOT SOP0:1, SOP1:1).

    On top of that in the LUA script, you need ar1.FullReset() & ar1.SOPControl(2) line which does a device reset or click Reset button on GUI.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 70 points

    Hi Jitendra,

    Yes, I've tried the LUA script provided in the Studio installation. (Although I'm using mmwave_studio_01_00_00). Still getting stuck at the SPI connect (RESP timeout). The device is set to development mode (jumpers on AWR1642BOOST SOP0:1, SOP1:1).

    What seems to have resolved the issue for me is sending ar1.SOPControl(5) instead of ar1.SOPControl(2) even though the jumpers on the AWR1642BOOST is set to SOP 2 (i.e. jumpers on SOP0 and SOP1). I was perplexed that it wasn't working earlier, and I'm equally perplexed now that it is working. 

    Any insights on why this might be the case?

    Regards,

    John

  • 0 in reply to John Lee35
    TI__Guru 69970 points

    Hi John,

    I am not sure what can cause this issue at your end. Are you able to do all the API calls (along with SPI connect) when you configure SOPControl(5)? Ideally, this mode sets the device in flashing mode where SPI connection is not available.

    I would suggest you proceed with this workaround to unblock yourself, meanwhile, you can try mmWave Studio v2.1 version if that may help here.

    Regards,

    Jitendra