• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 580 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.

AWR2243: Issuing the next command during the SPI IRQ = H

KenF
Expert 7150 points
Part Number: AWR2243

Hi Experts,

Is it okay to issue the next command during the SPI IRQ = H period? If so, what is the output of the IRQ signal in that case? (Always H?, Return to L once after receiving CNYS?)

Best regards,
Ken

  • 0
    TI__Guru*** 147894 points

    Hi,

    Please give us some time to review your question and get back to you

    thank you

    cesar

  • +1
    TI__Guru 69960 points

    Hello Ken,

    AWR device supports only one command at a time, it won't take next command till last CMD-> ACK session is completed.

    1. Host sends cmd to AWR over SPI

    2. Host waits for ACK from AWR

    3. AWR receives CMD over SPI, parse and process (by MSS or BSS) then generate ACK/NACK for that CMD

    4. Raises HostIRQ to notify Host that ACK/NACK is ready with AWR which it needs to read over SPI

    5. Host sees HostIRQ (via interrupt mechanism), then it write CNYS pattern to AWR

    6. AWR takes HostIRQ down as soon as it reads CNYS pattern and copied the ACK/NACK to SPI buttfer

    7. Host then reads the ACK/NACK header+CRC

    So Host needs to complete this whole cycle before sending next command. And even mmwavelink library doesn't honor next CMD if it is already under first CMD process. Next CMD call will be blocked by mutex.

    Regards,

    Jitendra