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.

CCS/CC2650RC: RemoTI 1.4.0 Bi-directional Communication vs 2.0.0 Remote Finder

Part Number: CC2650RC
Other Parts Discussed in Thread: CC2650, CC2531EMK, CC2531

Tool/software: Code Composer Studio

Hello TI gurus,

While investigating the possibility of debugging Bi-directional Communication in the CCS imported cc2650rc project C:\ti\simplelink\rti_sdk_2_00_01_15\examples\cc2650rc\remote_control\ccs\app and C:\ti\simplelink\rti_sdk_2_00_01_15\examples\cc2650rc\remote_control\ccs\stack

I noticed in RemoTI-1.4.0 Developer's Guide (Section 9 ZRC Features), the very extensive treatment of Bi-directional Communication which dives into the gdp_poll_client.c/gdp_poll_server.c mechanisms, whereas that section in the RemoTI-2.0.0 Developer's Guide has now become the very abbreviated and very specific Remote Finder function. This function is tightly coupled with the Target Emulator, which I believe is only available via the CC2531EMK. Could you provide guidance to have this Target Emulator implemented on a CC2650 Launchpad or SmartRF06+CC2650EM?

I read this here blog e2e.ti.com/.../547996, but I think there's more to it than that.

Thanks in advance.

Manuel 

  • Hi,

    The CC2650  Launch Pad can be used as a recipient with Target Emulator, just like CC2531 USB Dongle.

    The section about bi-directional communication has not changed between RemoTI-1.4.1 and RemoTI-2.0.1. They are both based on ZRC2.0 (and GDP2.0). Please find the section here.

  • Program the following image to use the launchpad as recipient:

    C:\ti\simplelink\rti_sdk_2_00_01_15\examples\hex\cc2650lp_rnp_rti_recipient_uart_super.hex

    You can communicate with it using the CC2650RC, or any other ZRC2.0 compatible originator.

    By the way, we will soon release an updated driver for Linux with sample applications. This is much like Target Emulator, without the GUI. Difference is that it's delivered in source, and you can as such much more easily use the Originator image for the Launch Pad to pair two launch pads with each other.

    Note that all APIs that are used on the host side are identical to those embedded. So, if you want to remove the host, then simply call the same APIs, in the same order in an embedded application. The most recent ZRC2.0 host application can be found here.