Other Parts Discussed in Thread: CC2640
Hi Team,
I used the simple central routine of cc2642 to scan the simple peripheral composed of cc2640.
In the SimpleCentral_taskFxn() of 2642, the scan would be started after the GAP_DEVICE_INIT_DONE_EVENT, and the function called is:
GapScan_enable(0, 150, 0);//one-shot scan
(I also tried to change 150 to other values or 0 values for continuous scanning, but the effect of the scanning of those methods was not good or mothing could be scanned.
After it timed out, I would call it again. After multiple calls, it usually took about 10 seconds to scan all 4 target devices (conduct comparison based on the names and scan report event, many other irrelevant devices
would be reported)
Then it would perform connection and service discovery, enable 'notify', send data, receive data, close the connection, and then loop again.
Now my main problem is that the program often crashes during the scan (but not sure if it crashes during other processes). If you suspend the program execution in debug mode, you will find the following picture:
It crashed in a non-debuggable place (a strlen in the rom).
Could you please tell me how to solve this problem? Please note that the simple central routine itself will not actively call the 'scan enable', so it is impossible to use the routine itself to reproduce the problem. I am debugging on our product hardware.
The same thing happened on the official development board: it is easy to crash. Sometimes it scans a few times before crashing, sometimes it crashes quickly, and sometimes it can run for 30 minutes without crashing.
Kind regards,
Katherine
