• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 450 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:

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

AWR2243: Concerns about IRQ and command issue

KenF
Expert 7150 points
Part Number: AWR2243


Hello Jitendra,

We have some concerns about IRQ and command as follows.

1. Does the IRQ state change while the command is being sent? What should we do if it can change?

2. What happens when IRQ = H and a command are issued at the same time?
In our system, IRQ is checked by polling instead of interrupt processing, so it takes some time between IRQ status check and command issue. Depending on the timing, the command may be issued with IRQ = H. What should we do?

Regards,
Ken

  • 0
    TI__Mastermind 31680 points

    Hello Ken,

    I've forwarded your query to Jiten. Please expect a response on this next week.

    Regards,

    Ishita

  • +1
    TI__Guru 70090 points

    Hi Ken,

    There is max of two scenario of communication b/w Host & AWR device over SPI.

    1. Host sends CMD; AWR processes it & send back ACK/NACK (response) to Host over SPI.

    2. AWR device sends Asynchronous Event message whenever it needs to send some message to Host; It can be Boot status, monitor/calibration reports or any other device generated data.

    * There can be only one command at time which Host can send, after receiving ACK/NACK for that command Host is eligible to send next CMD to AWR.

    * AWR can send Async-event message any time, so it may possible that while Host is about to send it got HostIRQ high for some async-event message from AWR.   THIS case has been handled by mmwavelink, if there is no ongoing CMD then that hostIRQ will be treated as async-event message and to read that mmwavelink spawn a different task.

    Now in your case, even though you have polling mode of HostIRQ line instead of interrupt mode, mmwavelink will able to distinguish b/w async-event or response message (when HostIRQ come at time of CMD send). Header field of SPI data b/w Host and AWR contains a field which says if it is CMD/RESPONSE or ASYNC_EVENT.  [header->opcode.b2MsgType]

    Are you facing any currently with your implementation?