Hi,
Currently I am exploring the simple peripheral example on a custom board with the CC1352R chip. When running the example, Android devices detect its presence. However, iPhone does not.
Any ideas?
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.
Hi,
Currently I am exploring the simple peripheral example on a custom board with the CC1352R chip. When running the example, Android devices detect its presence. However, iPhone does not.
Any ideas?
I just test simple_peripheral of SimpleLink™ CC13x2 and CC26x2 SDK, version 3.20.00.68 running on my LAUNCHXL-CC1352R1 and my iphone 7 running TI SimpleLink Starter App can scan and connect to LAUNCHXL-CC1352R1 without problem.
You should use TI SimpleLink Starter App to scan and connect to LAUNCHXL-CC1352R1
Thank you. The iPhone now indeed scans the device.
However, we can not connect to it. Neither the Android nor the iPhone devices. I also tried using auto connect, but to no avail. Am I missing something else?
Also, what are the A and B groups in auto connect?
If there is any documentation on the functioning of the Simple Peripheral, besides the demonstrations, that would help.
The SimpleLink Starter app shows a pop up while connecting to the device, in which it shows Retries: 0 of 4.. Retries 1 of 4.. etc. Eventually it goes through all 4 retries and decides it is unsuccessfull in setting up the connection.
I suspect there is something wrong on your custom HW especially on 48M Hz crystal. I suggest you to refer to and check your HW first.
Thank you for your insight. Indeed, we are actually not using a 32 kHz crystal, but instead we are using the internal RC oscillator. I am currently looking into how to configure everything to support this.
RF part uses 48M Hz crystal not 32K so I suggest you to check 48 MHZ crystal first.
Thank you for your guidance and insights. The problem is solved, so the device is now connectable and readable from both Android and iOS phones.
It has been simply solved by adding USE_RCOSC to the predefined symbols of the project, which informs the processor to use the RC oscillator instead of the 32 kHz crystal, which is not provided in our case.