• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 16 subscribers
  • Views 396 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.

CC2640R2F-Q1: Standyby mode operation based on startTime and startTrigger

Chris Lande
Expert 6565 points
Part Number: CC2640R2F-Q1

Please will you confirm where I can find details about the radio going into standby when

RF_pCmdTxR2HS->startTrigger.triggerType = TRIG_ABSTIME

and the RF_pCmdTxR2HS->startTime is set to a value greater than the standby limit?

Thanks.

  • 0
    TI__Guru* 86241 points
    Hi Chris

    Please see the RF Driver documentation in the SDK. We do not have any other documentation of this available:

    dev.ti.com/.../_r_f_8h.html

    BR

    Siri
  • 0 in reply to Siri
    TI__Expert 6565 points

    Hi Siri,

    I have reviewed this file RF.h.  I have copied below the section from this document and added my questions below it.

     

    Deferred dispatching of commands with absolute timing

    When dispatching a radio operation command with an absolute start trigger that is ahead in the future, the RF driver defers the execution and powers the RF core down until the command is due. It does that only, when:

     

        cmd.startTrigger.triggerType is set to TRIG_ABSTIME

        The difference between RF_getCurrentTime() and cmd.startTime is at not more than 3/4 of a full RAT cycle. Otherwise the driver assumes that cmd.startTime is in the past.

        There is enough time to run a full power cycle before cmd.startTime is due. That includes:

            the power-down time (fixed value, 1 ms) if the RF core is already powered up,

           the measured power-up duration or the value specified by RF_Params::nPowerUpDuration,

            the power-up safety margin RF_Params::nPowerUpDurationMargin (the default is 282 microseconds).

     

    If one of the conditions are not fulfilled, the RF core is kept up and running and the command is dispatched immediately. This ensures, that the command will execute on-time and not miss the configured start trigger.

     

    Question:

    1) So does this means that the RF core will power down if the startTime is > current RAT time by (1ms + RF_Params::nPowerUpDuration + 282 µs)?

    2) What is the value RF_Params::nPowerUpDuration,?

  • 0 in reply to Chris Lande
    TI__Guru* 86241 points
    Hi Chris

    1) Yes
    2) How long time this will take depends on both startup time of the crystal you are using , and also on what PHY you are using (different PHYs use different patches, and this will affect the startup time). I do not have numbers for the CC2640R2, but I know that on our CC13x0 devices, running the 50 kbps genfsk PHY the startup time from Standby to active RX or TX is around 1.6 ms. That means that if you set the startTrigger to be less than 1.6 ms into the future, the device will not enter standby when waiting to execute the command.

    BR
    Siri