• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 212 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: chunk packet communication and firmware download overlapping

user6158104
Intellectual 300 points
Part Number: AWR2243

Hello TI Experts,

I am now bringing up a AWR2243 single device module fabricated in our site. Let me ask two questions about communication with the device.

Q1
Do you have a description which guides the way of SPI packet communication with the use of the chunk split?
We are planning to use chunk encoding in SPI packets from a host PC to a device AWR2243. I couldn’t find the detailed description about the way of the communication with the use of the chunk split in the mmWave Radar Interface Control Document. I have tried to transmit some chunks continuously but cannot get good results. It seems that a kind of hand-shake with IRQ is necessary. So, for example, I want to know the hang of ACKREQ in the packet header of each chunk. 

Q2
Let me confirm that the device, AWR2243, has no problems in case that the firmware already existing in the device is downloaded forcibly again to the device. Right?

Your advice is greatly appreciated.

  • +1
    TI__Guru 69960 points

    Hi,

    Q1:  ACKREQ is flag which set the ACK request while you send SPI command to AWR device over SPI, if this is set then AWR device will return the ACK or NACK, next command must send after it  receives response for last command.

    If this is not set then AWR won't respond to any SPI command, but next command must send after AWR device receives and processes last command. It is highly recommended to enable ACKREQ so each command will get the ACK/NACK (response).

    Q2: If firmware file (even one specific chunk) is already loaded the reloading of same chunk of firmware will cause unexpected behavior of the device. So don't reload the FW or chunk to the device if already loaded in the same boot cycle.

    I would recommend you to use mmwavelink library which implements all these SPI command-response sequence or SPI communication protocol so application don't need to bother about SPI communication, it's handshake (CMD/RSP) with AWR device and byte packaging (Header+Payload, chunk) etc.

  • 0 in reply to Jitendra Gupta
    Intellectual 300 points

    Thank you very much for the prompt support. We can go one-step further.