Hi,
I have just discovered that calling ApiMac_mcpsPurgeReq() also call pDataCnfCb() which I can't find to be correct as per 802.15.4. It seems against the standard to have a mac api call result in the calling back of two different callbacks: pPurgeCnfCb() and pDataCnfCb().
I have now changed my code around this unexpected functionality so I'm hoping it is to standard and it won't get changed and missed by me in a future stack release. If you can confirm if this behaviour is not to standard, I will rewrite my application to futureproof against Ti changing this functionality.
Thanks,
Andy
simplelink_cc13x2_26x2_sdk_4_30_00_54
collector/sensor examples
no FH
non-beacon
TiRTOS