Other Parts Discussed in Thread: CC2640R2F
Tool/software: TI-RTOS
Hello,
My project is based on simple_peripheral_oad_onchip project and running on custom board.
My SDK version is 1_35_00_33.
CC2640R2F is used in the custom board.
Custom board is nearly same with TI Reference design and there is a button in the custom board.
The custom board operates on a coin cell battery.
The button has two use cases which are waking up the board from shutdown state and starting sending of the connectable packet.
After the loading the code into the custom board, the custom board will be in shutdown state.
Here is the brief story of my problem;
1) I pressed the button to wake-up the custom board.
2) After the pressing the button, the board will be awake and the SimpleBLEPeripheral_taskFxn task will run. At the same time, the custom board will send connectable beacon packets to connect our mobile application to exchange data.
3) After the communication between the mobile application and the custom board ends, The custom board will send non-connectable beacon message at a fixed interval.
(I checked that there is no problem sending non-connectable beacon messages)
4) After a while (like 10 days), I pressed to button to make the custom board connectable.
5) The custom board started to send connectable beacon message and I verified by using the packet sniffer.
6) When I attempt to connect to the tag by using the mobile application, the connection takes so much time. Because of the lots of RETRY packet.
According to packet sniffer logs, Master device (mobile phone) tried to send a request and it seemed that slave device did not respond to the request.
I attached the packet sniffer log to check what's going on.
Here is the list of what I did to address the problem;
1) I checked the voltage on batteries and it seemed normal.
2) I checked RSSI value and rate of CRC and FEC errors. It seemed normal.
3) I tried to recreate the problem in another custom board, I did not run into the problem.
I think the problem occurs when the tag operates so much time.
I woke up the custom board by pressing the button. I sent the configuration to the custom board by using mobile application. After 20 hours, I pressed the button to reconnect to tag. The connection was successful.
I measured the elapsed time to connect to the custom board and sending the configuration;
The custom board that has difficulties to connect-> It took nearly 26 seconds to send configuration.
The custom board that has not difficulties to connect -> It took nearly 4 seconds to send configuration.
Any help would be appreciated.
Have a nice day.
Best Regards.
