Other Parts Discussed in Thread: CC2650, REMOTI, CC2592, SMARTRFTM-STUDIO, LAUNCHXL-CC2650
We are using RemoTI v2.0.1 with a CC2650 and have the RNP stack/application working on the CC2650 Launchpads, and are able to bind/pair and send/receive data. However, the PA signal does not get asserted (and LNA de-asserted) when sending an acknowledgement (ACK) after receiving data on the target/recipient (see attached waveforms showing DATA_REQ from both the target and contoller). Therefore, when testing on a custom board with a CC2592 range extender, the controller/originator sending the data does not receive the ACK and continually resends the packet until it times out. Note that the behavior of the PA/LNA signals does look correct on the device sending the data request, and during the bind/pair process. It also works correctly for the ACKs on the controller/originator version of the stack. Can someone confirm if this is a bug in the stack code (assuming in rcnsuper-cc2620.a), or if something else needs to be configured differently?
rnp_app and rnp_stack examples from rti_sdk_2_00_01_15 using RTI interface.
Built with MODULE_CC26XX_5X5 and PA_LNA_CC2592 defined. Configured IO pins 7 and 13 for GPO0 and GPO1 functionality.
Seeing same behavior on CC2650 Launchpad and on custom board with CC2650F128RHBT and CC2592 range extender.
Target sending a DATA_REQ to Controller and seeing an ACT from the Controller
Controller Sending a DATA_REQ and not seeing an ACK from the Target