• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 56 subscribers
  • Views 153 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.

CC1354R10: Help diagnosing Proprietary Rx Adv command returning 0x0804 (ERROR_POINTER)

Alon Levy
Prodigy 80 points

Part Number: CC1354R10

Tool/software:

Hi,

 I am trying to port an easylink 6.20 SDK based example from CC1352R1 to the CC1354R10 using the newer version 8.31.0.11 that does not have easylink.

I have managed to use the Rx & Tx commands. Now I'm trying to use the RxAdv command which requires a queue and am receiving status 0x804 after the RF_runCmd call.

What is the canonical example for using the RF_cmdPropRxAdv (command 0x3804) command?

Is it rxPacketErrorRate?

Is there any simpler example?

I don't mind which modulation / carrier frequency or other parameters it will have - I'll take any starting point.

Thanks in advance,

Alon

  • 0
    Prodigy 80 points

    ok, I figured it out, for eternity, my problem was that despite pNextOp being NULL I was getting 0x0804 and I couldn't figure out why - turns out when condition.rule is 0 then NULL is an invalid value and the error the RFC returns is 0x0804. Would be nice to have a separate error, but still it makes sense - condition.rule = 0 means "always run the next command" and that cannot be done if the next command is missing, i.e. the pointer is NULL. Fixed by changing to the default (and what is in most examples - I made a mistake copy pasting because I started from an existing project) 1, which means "never run the next command".

    For reference:

    software-dl.ti.com/.../radio-operation-commands.html