Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.
NPI RF4CE SubSystem
RF4CE Network Processor Interface SubSystem
This page describes how to use the Network Processor Interface to interface with the RF4CE stack. RemoTI is the implementation of RF4CE for CC2xxx.
There are two sub system IDs that can be used to interface with the RF4CE stack:
|0x0B||RemoTI Network Layer (RCN) API|
Command ID to RemoTI API mapping
The APIs listed in the tables below are ordered by functionality, rather than ID.
- Most APIs are asynchronous requests made by host that have an asynchronous confirmation.
- They are typically called requests and confirmations.
- Requests end with
- Confirmations end with
- Some APIs to host do not require a request. Some of those APIs require a response.
- They are typically called indications and responses.
- Indications end with
- Responses end with
Initiated by Host
Initiated by Host, with response
|Command ID||APIs with return value|
Initiated by RemoTI Network Processor
|Command ID||Indications||Command ID||Responses/Confirmations|
Detailed RemoTI API over NPI
A detailed list of full serialization of all the APIs can be found here.