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.
Part Number: CC1352R
Hi TI expert,
I was wondering if there is any alternative proprietary command to the CMD_IEEE_RX_ACK? CMD_IEEE_RX_ACK is very useful to check the ACK message timeout, but I couldn't figure out a good approach to deal with the similar situation in sub-1 mode.
Some posts suggest to use "RF_cmdPropTx.pNextOp = (RF_Op*) &RF_cmdPropRx;" but it assumes the ACK is the piggybacked (the ACK is the next received message after transit). This hypothesis is not always true in the real situations.
Could you give some suggestions on what is the practical methods to deal with the auto-ACK situation in Proprietary mode.
Thank you very much in advance,
Since prop can be used to implement a wide selection of standards, prop doesn't have a 'ACK' command.
Hence your best option is to chain commands as shown in http://dev.ti.com/tirex/explore/node?node=AMWGQAr.6MV9a9rMY8cU-A__pTTHBmu__LATEST&search=debug
If you are writing your own protocol you have full control over when you send and ack and when you have to listen for one meaning that this method should give you the flexibility you need.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to TER:
Sorry to late response. I checked the sample (regarding auto-ack in prop mode) that uses command chain to receive 'ACK' after transmit. But it a little confuses me that the RF_cmdPropRx has to be called again after RF_cmdPropTx command executes.
Chapter 25.5.4 in TRM mentioned "In IEEE 802.15.4 mode, the radio CPU accepts two levels of radio operation commands. Operations can run in the background level or in the foreground level.", the Tx command is able to run in front of Rx command, so that the Rx command can be execute only one time.
I assume the prop does not support combinations of Foreground and Background Level Operations? So Rx command has to be chained after Tx? Also, whenever I want to send a packet using TX command I have to abort the running Rx command first?
Thank you very much for your support, as always!
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.