CC1310 EasylinkRF switch in code from TX to RX -> EasyLink_abort()

Anyway ... turns out the concentrator example uses easylink but still the issue is there that the abort function does not seem to work.

Any reply from TI ?

There will be an new TI-RTOS version in a couple of days. In that release, the EasyLink_abort function has been re-written:

EasyLink_Status EasyLink_abort(void)
{
    EasyLink_Status status = EasyLink_Status_Cmd_Error;

    if(!configured)
    {
        return EasyLink_Status_Config_Error;
    }
    //check an Async command is running, if not return success
    if(asyncCmdHndl == NULL)
    {
        return EasyLink_Status_Success;
    }

    //force abort (gracefull param set to 0)
    if(RF_cancelCmd(rfHandle, asyncCmdHndl, 0) == RF_StatSuccess)
    {
       /* Wait for Command to complete */
       RF_EventMask result = RF_pendCmd(rfHandle, asyncCmdHndl, (RF_EventLastCmdDone | RF_EventCmdError |
               RF_EventCmdAborted | RF_EventCmdCancelled | RF_EventCmdStopped));

       if (result & RF_EventLastCmdDone)
       {
           status = EasyLink_Status_Success;
       }
    }
    else
    {
       status = EasyLink_Status_Cmd_Error;
    }

    return status;
}

BR

Siri

You should not call driver API's from an HWI or SWI, you should always post and event or semaphore and have your task call the driver API's.

Can you illiterate on the issue / work around you mentioned?

Hello,

I am fairly new to CC1310 and I am trying to get Easylink TX and RX task to work together. I have merged both tasks together and they work just fine independently.

However, when I have both running with my custom semaphores, nothing runs.

 Is there an example code for CC1310 where we have txTask_init(ledPinHandle) and rxTask_init(ledPinHandle) working together on the CC1310 Launchpad?

I am trying to have a code that enters the rxTask, waits there until it receives a packet, then blocks the rxTask starts the TX task and transmits a message.

Any help is truly appreciated.