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.

CC2650RC: Using CC2650 as the Coordinator, Recipent as the Dongle in the RC application, based on cc2650rc in Remoti-2.0.0.13 or Remoti-2.0.1.15

Part Number: CC2650RC
Other Parts Discussed in Thread: CC2650, , REMOTI

Our final goal is to use CC2650 as the Zigbee radio on our own board. The CC2650 will be the Coordinator to setup the network, and allow other devices (two) to join. The CC2650 will be the Recipient like the dongle, responding to the other devices. It will also periodically send queries to the other devices for their status.

We are using the CC2650RC project as our baseline. Currently, we are able to compiled the cc2650rc_app and download to our custom board, allowing it to pair and send key presses over to the dongle, as if it were the remote control.

Our implementation requires us to change the project from a originator to a recipient. I see that in the cc2650rc_stack, the GDP and ZRC source have the needed .c and .h files for recipient configuration. And from the looks of it, I need to rewrite almost the whole cc2650rc_app, since it was written as a originator.

My questions/obstacles are:

1. The Remoti-2.0.0 documents and the actual codes in the projects have some discrepancies, i.e. RTI_PollInd vs RTI_PollRsp, the documents have both, while the code base only have RTI_PollRsp, so I ended up with unresolved symbol at compile time. Both function have different parameters. I have tried both the 2.0.0.13 and 2.0.1.15, same result.

2. I know the dongle code is provided only in binary form. Is there some application notes or sample code similar to it? Like with step to be a coordinator role, setup network, response to Discovery Req., and wait for pairing req.... etc

  • Hi Ronald,

    Is your goal to create a Recipient on any CC2650, or specifically turn CC2650RC into a Recipient? There's another thread which is discussing the same, e2e.ti.com/.../547996.

  • Torbjorn Sorby said:

    Hi Ronald,

    Is your goal to create a Recipient on any CC2650, or specifically turn CC2650RC into a Recipient? There's another thread which is discussing the same, e2e.ti.com/.../547996.

    It does not HAVE to be CC2650RC. I just choose CC2650RC since we have it working as originator running on our hardware. The goal is then to turn our hardware into recipient, and use another one as originator.

    Getting them to pair and send data back and forth. I took a look at the thread you referred, it is concern running rnp needed a host or host MCU to control the NP. I think I am more less a single chip solution. Please correct me if I am wrong about this.

    I have FEATURE_RECIPIENT defined in cc2650rc_stack, brought in the needed source files, such as zrc_binding_recipient.c, and gdp_discovery_recipient.c .... compiled and build okay.

    Now, I am working in cc2650rc_app, and looks like it is totally written as a remote control (originator), I assume I have to rewrite most if not all of it? unless there is a more direct code / app leavel example?

  • Hi Torbjorn,

    I also tried to get the LaunchPad to work per the other thread you mentioned.

    I downloaded the "~/hex/cc2650lp_rnp_rti_originator_stack.hex" and "~/hex/cc2650lp_rnp_rti_originator_app.hex"

    as well as "~/hex/cc2650lp_rnp_rti_originator_uart_super.hex" to the LaunchPad.

    Both of them gave me error message similar to below, when using Target Emulator v1.4.3 talking to it. We set the COM port at 115200, 8 N 1.

    ----------------------------------------------------------------

    RemoTI Target Emulator - v1.4.3
    --------------------------------------------------------------------
    Initialize User's Components...
    Done
    --------------------------------------------------------------------
    Starting The Emulator...
    Initialize RTI Library...COM20...
    Done
    --------------------------------------------------------------------
    Getting Startup Info...
    --------------------------------------------------------------------
    <Tx> - RTI_ReadItemEx
    ProfileId = 0xFF (255) (RTI)
    ItemNumber = 0xA0 (160) (RTI_CP_ITEM_STARTUP_CTRL)
    ItemLength = 0x01 (1)
    --------------------------------------------------------------------
    <Rx> - RTI_ReadItemEx
    Status = 0xFF (255) (Synchronous Npi Timeout)
    <Error> - Error Reading ReadItemEx
    <Error> - No Device Was Found On The Selected Port
    SetupSerialPortTarget ReadItemEx RTI_CP_ITEM_STARTUP_CTRL Failed
    Error 0xFF (255)
    Synchronous Npi Timeout
    <Warning> - Failed Starting The Emulator
    --------------------------------------------------------------------
    Starting The Emulator...
    Initialize RTI Library...COM19...
    Done
    --------------------------------------------------------------------
    Getting Startup Info...
    --------------------------------------------------------------------
    <Tx> - RTI_ReadItemEx
    ProfileId = 0xFF (255) (RTI)
    ItemNumber = 0xA0 (160) (RTI_CP_ITEM_STARTUP_CTRL)
    ItemLength = 0x01 (1)
    --------------------------------------------------------------------
    <Rx> - RTI_ReadItemEx
    Status = 0xFF (255) (Synchronous Npi Timeout)
    <Error> - Error Reading ReadItemEx
    <Error> - No Device Was Found On The Selected Port
    SetupSerialPortTarget ReadItemEx RTI_CP_ITEM_STARTUP_CTRL Failed
    Error 0xFF (255)
    Synchronous Npi Timeout
    <Warning> - Failed Starting The Emulator

    --------------------------------------------------------------

    Can you or anyone share a successful communication between the LaunchPad and the PC (Target Emulator v 1.4.3)? Thanks!