Other Parts Discussed in Thread: CC2650, CC2652R
Hello, we are migrating from a CC2650 based design to a new one, based on the CC2652RB. We made some of the porting on the CC2652RB LaunchPad and after that we designed the new pcb and we had all the involved components assembled into the new boards, including all the peripherals, in order to complete and verify the porting in the full working final board. Our system was designed to operate in two mutual exclusive ways: BLE and proprietary protocol. The BLE mode works fine and we concluded all the related activities. Some days ago we started the porting of the proprietary protocol to the new platform and we found, astounded, that syscfg does not support such mode for the RB variant despite also the last released data sheet (Rev. D - Feb 2021) and all related documents clearly state that this protocol was supported !!!
After this unbelievable surprise, we read numerous posts about this topic and we have seen that other people are in the same situation.
Do we have to redesign our PCB and rebuild all the boards ??? Who pays for that and the time waste ??? The system has very stringent space constraints and the RB variant would be a perfect solution.
How can we proceed ? Do you have planned to enable the proprietary protocol for the RB variant and/or do you have a beta release, maybe, of the SDK that allows for proprietary protocol that you can share?
Many thanks
