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.

AWR1243BOOST: Sop mode 4 failed error

Part Number: AWR1243BOOST
Other Parts Discussed in Thread: AWR1243

Hi,

I'm trying to communicate AWR1243boost with TM4C1294 launchpad but I'm getting "SOP 4 mode failed with error -1" message. I have assigned SOP(0,1,2) to PL(1,2,3) of TM4C1294.

Do I need to define only SOP0 mode or all the three SOP modes?

Do I need to call interrupt function for making SOP mode successful? 

  • Hi,

    What are you trying to accomplish?

    What SOP mode are you trying to boot in?

    Thank you

    Cesar

  • Hi,

    SOP mode is working fine now in functional mode. I have connected SOP2, SOP1 and SOP0 pins to PL3, PL2 and PL1 respectively and made PL3 high and PL2 and PL1 pins low. The issue here is if I remove all the jumpers from SOP0, SOP1 and SOP2 (in AWR1243boost board) the SOP mode is successful. Can you give any suggestion on this?  

    I'm trying to download AWR1243 firmware through SPI and I'm trying to boot in functional mode.

    How can I port this data structure in tm4c1294? I need to use this for communication handle object which contains the required information for communication with the AR1243.

    What is does critical section mean?

    typedef struct rlsDevCtx

    {

           UINT8 deviceIndex; /** device index     */

          

           BOOLEAN deviceEnabled; /*** device enable/disable */

          

           BOOLEAN irqMasked; /*** irq mask/unmask */

          

           FT_HANDLE irqI2cHandle; /*** handle to I2C*/

          

           FT_HANDLE spiHandle; /*** handle to SPI */

          

           FT_HANDLE boardControlHandle; /*** handle to Board Control */

          

           FT_HANDLE genericGPIOHandle; /** * handle to Generic GPIO*/

          

           CRITICAL_SECTION cs; /*** critical section */

          

           rlsThreadParam_t hostIntrThread; /*** handle to host interrupt thread */

    }rlsDevCtx_t;

     Regards

    Nithesh

  • Hi,

    Sorry for late reply.

    First you need to make sure that you use the DFP release "mmwave_dfp_01_02_06_03".This is the version that must be used with AWR1243.

    Second, the mmwave link API must be ported to the host tm4c1294.

    There are many threads discussing porting mmwave link to a host.

    Please use google search to find more information as follows:

    site e2e.ti.com mmwave link porting

    Thank you

    Cesar