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.

CC1310: Boot up time from shut down

Part Number: CC1310

Hi,

Could you please help answer a question from my customer?

  • Is there a minimum time after booting up (from shut down mode) or bringing up the RF core of the cc1310, that should be considered before sending/receiving radio telegrams?
  • What is a typical time for the synthesizer to be successfully calibrated after boot up?
  • Are there any constraints we have to  respect before starting radio communication on the cc1310?

After walking up the device from shut down mode and waiting for 50 ms before sending out a radio request telegram, the receiving responder device does not receive the request.

For further test cases, please let me know and i will give you updates.

Thanks!

Best regards,
Needhu

  • Hi Needhu,

    There is no such specific time. From the point the device has booted you should be able to bring up and use the RF code. The synth do not start and calibrate during the boot process, this is done when the RF core is started. I would expect the frequency/synth calibration should take 100-200us.

    If you are using the RF Driver, you should not need to address any software constraints as these are handled by the driver.

    Could you maybe elaborate on the test you/your costumer are trying to run (maybe even share the code)?

  • Hi,

    Thank you very much for the quick feedback. The test performed was as follows,

    1. We wake up the cc1310 from shut down mode.
    2. Within 50ms to 70ms after booting up from shut down, we send out a radio request telegram (recorded by sniffing tool

        1. Sometimes (approx.. 1 out of 10) it happens, that a “steady on air” listening responder device does not receive the request
        2. Sometimes (approx. 1 out of 10) it happens, that a “steady on air” listening responder device does respond to the request (recorded by sniffing tool), but the response does not seem to be received by the requesting device.
    • We do not observe the behavior of 2.a and 2.b  during any following communication sessions except the first one after waking up.

    If you need the codes, could we take it offline?

    Thanks,
    Needhu

  • Hi Needhu,

    Are you testing this out on TI LaunchPads or custom hardware? Having a look at the code would help, if you can't share it here feel free to reach out to me offline. I will be out of office for a few days so any responds from my side will be a bit delay, sorry for the inconvenience.

  • Hi,

    Could you please send me an email? you can find me with 'Needhu'.

    Thanks,

    Needhu

  • Hi Needhu,

    As this has moved offline, i will close the thread for now until any additional information surfaces.