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.
Part Number: CC1310
Our project is based off LAUNCHXL-CC1310. 1. When both collector and sensor are flashed, the sensor is able to join the network and sends data on it's poll interval.2. After the sensor sends it's data, we erase and re-flash the same sensor binary3. We can see the PA an PC, and 6 attempts to rejoin the network, but all were unsuccessful and sensor data is never sent or received by the collector. ( We ran multiple test on different boards and the rejoin is unsuccessful 80% of the time.Note:If we perform #1 and ONLY cycle power on the sensor, the sensor rejoins every time.
We recompile the code with `#define CONFIG_SECURE false` and performed the same test. It rejoins and sends data every time.
If you re-flash sensor binary (even it's the same), it's recommended to join sensor again from scratch.
If my post answers your question, please click on "This Resolved my issue" button to benefit others who have the same issue.
Comparision on Zigbee, Z-Wave, and Z-Wave Long range.
Build OpenThread Sleepy End Device doorlock prototype to test with Rasperry Pi OpenThread Border Router
How to use two UARTs in CC26x2 and CC13x2
SwitchBot DIY using LPSTK-CC1352R , SG90 servo motor, and ProjectZero to away from COVID-19.
How to use two endpoints in SIMPLELINK-CC13X2-26X2-SDK Z-Stack.
How to create a periodic event to toggle BLE Advertising in CC26xx simple_peripheral example
How to use indication in simple_peripheral example and use Btool to enable indication
How to detect button hold in CC26x2, CC13x0, CC13x2 SDK.
660 Zigbee devices in the same Zigbee network!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to YiKai Chen:
Yes, the sensor is trying to rejoin the network. It performs the PA, PC, and Association successful/unsuccessful attempts.What we are trying to understand is the why is the setup with encryption is 80% unsuccessful.Step 1-3 is performed with encryption. Rejoin fails 80%.Step 1-3 is performed with no encryption. Rejoin is 100% successful.These are the same code for both the collector and sensor. Only the #define CONFIG_SECURE is changed.
Please keep the flash in the same state on the sensor and collector. I.e. when you erase and re-flash the sensor, please do the same on the collector.
Cheers, Marie H.
In reply to Marie H:
Yes, I noted that in step 1. We are trying to get clarification/understanding of why the security builds behave differently with respect to the reflash/rejoining.We are need a deeper explanation of the mechanics involved with the security enable than what was provide in the TI 15.4-Stack Software Developers Guide.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.