CC2650MODA: TI-provided BLE Stack does not meet NPI communication specifications

Hi Sakai,

Thank you for the details provided. Please note the timings provided in the referenced document are based on testing. These do not represent absolute values but instead are values that were tested and shown to be functional.

The SRDY signal is actually handled by the file npi_tl.c.
In order to move further, I would recommend to identify the line of code responsible to set and then reset the SRDY signal when you encounter the behavior reported.
=> Looking at the code, I assume line "SRDY_ENABLE();" in NPITL_handleMrdyEvent is responsible to set SRDY when "(npiTxActive && mrdyPktStamp == txPktCount )" is true.

void NPITL_handleMrdyEvent(void)
{
    ICall_CSState key;
    key = ICall_enterCriticalSection();

    // Check to make sure this event is not occurring during the next packet
    // transmission
    if ( PIN_getInputValue(MRDY_PIN) == 0 ||
        (npiTxActive && mrdyPktStamp == txPktCount ) )
    {
        transportMrdyEvent();
        SRDY_ENABLE();
    }

    ICall_leaveCriticalSection(key);
}

After this, SRDY is reset within NPITL_transmissionCallBack (using the line "SRDY_DISABLE();").

Please double check when executing the code on your device.

Assuming you can confirm my assumption, you can slightly modify the code in order to set a flag when setting the SRDY signal under the conditions identified. Then, when the mentioned flag is set, instead of resetting the SRDY signal in NPITL_transmissionCallBack, you start a timer and reset it after its expiration.

I hope this will help,

Best regards,