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: Turning Radio off and device getting stuck in PER receive mode

Part Number: CC1310


I am trying to integrate 2 different TI-RTOS examples to one test firmware. The goal is to accept commands via UART and verify certain functionalities.

Getting started with EasyLink AT Network Processor TI-RTOS Example mentions about turning the radio ON by :

AT+i – Used to initialize the radio.

1. Is there a way to turn the radio off as well. The API documentation says "EasyLink_init() : Inits and opens the RF driver", but nothing about closing or turning it OFF. 

2. I am running "Exchanging Data between a Device and SmartRF Studio" and trying to send packets between two devices Dev1(connected to SmartRF studio) , Dev2(connected to UART). everything works well if the transmission is successful, when its not the device connected to UART gets stuck and the only way to get out of it is a reset. How should I deal with this scenario?

3. When I merge two examples and try to put "static void atnpFxn(UArg arg0, UArg arg1)" to sleep upon receiving a certain command it works well but our client is looking for something where they are able to make the device enter and come out of standby mode via entering some command via UART. I can make the device enter in stanby mode by calling Task_sleep(standbyDurationUs / Clock_tickPeriod); but thats for a specific amount of time, can we make it command driven. 

e.g. command1 device enters standby mode

e.g command2 device comes back to active mode.

I understand when I put "static void atnpFxn(UArg arg0, UArg arg1)" UART will be dysfunctional, any inputs are appreciated.

Note: I am using a custom cc1310 with no buttons or LED's available. 

  • Hi aditya,

    1. There is no need to explicitly close the EasyLink driver, you only need to stop any running commands. The underlying RF driver will automatically turn of the radio when there no running commands.
    2. This is probably a logic error in your own code. I cannot really help you much on this unless you tell me more how your code is implemented.
    3. I'm not entirely sure I understand what you are saying. In order for your task to go to standby, it will have to block. In a TI-RTOS context, usually this is done by pending on either a semaphore, event or mailbox.