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
I am looking to implement the collector example code based on cc1312R (TIDA-010024). I wanted to port this example code to the CC1310. I tried a few different solutions I found on the forums but was not able to build the project correctly.
How do I go about this, if I use the CC1310, 15.4 stack collector example as a base and want to include the 6lowpan and DTLS part from the TIDA-010024?
How do I go about this, if I use a CC1310 empty project and port the entire CC1312 project to the cc1310?
Are there any other solutions to the problem? Please suggest me some way this can be achieved.
I do see a related post here: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/876810. To reiterate some comments there, a main concern here by using the CC1310 is a memory limitation, as this limits your network size.
Sabin JohnHow do I go about this, if I use the CC1310, 15.4 stack collector example as a base and want to include the 6lowpan and DTLS part from the TIDA-010024?
You can start here, however I'm not sure it will work. You will likely have to strip out a lot of features to get the barebones operation to work.. As listed in Table 1 of TIDA-010024, the remaining flash after implementing the end node on the CC1310 (using TIDA-010003) is 5KB, so you may not have enough memory for a collector role.
Sabin JohnHow do I go about this, if I use a CC1310 empty project and port the entire CC1312 project to the cc1310?
I wouldn't suggest starting from an empty project and porting the entire CC1312 project over to the CC1310. The ROM layout is different on these devices, and this will likely not work/be the best approach.
Please click the "This Resolved My Issue" button on this post if it answers your question
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 Ammar N:
Thank you very much for the input. I will decide further keeping these points in mind.
As per your inputs we have decided to go ahead with the CC1312R. However I have a few concerns..
1. Does the launchpad for the 1312R support 433Mhz?
2. We have our custom boards based on the cc1310. Are the cc1312r and cc1310 pin to pin compatible? Can we directly change the controllers and work on it?
3. Will there be any changes required at RF side if we swap the controllers, (our boards are designed for 433mhz)?
In reply to Sabin John:
Sabin John1. Does the launchpad for the 1312R support 433Mhz?
The launchpad can support this PHY, however, we are working on characterizing this PHY currently have not released support for this PHY. See: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/710070/2618320#2618320.
Sabin John2. We have our custom boards based on the cc1310. Are the cc1312r and cc1310 pin to pin compatible? Can we directly change the controllers and work on it?
The devices are pin to pin compatible, there's more information here: http://www.ti.com/lit/an/swra587/swra587.pdf.
Sabin John3. Will there be any changes required at RF side if we swap the controllers, (our boards are designed for 433mhz)?
Although I'm not familiar in this area, here is some insight I can provide. After taking a look at our launchpad schematics, the RF front ends look very similar, so your devices should still work with the CC1312. If you have any follow up questions, I'll try to loop in the appropriate expert in this area.
It would be good if you can loop in one of the RF experts. I wanted to clarify if the LC parameters of the RF balloon circuit need to be changed from what they were in CC1310 for 433 MHz.
Thanks and Regards,
The same circuit can be used for CC1312.
Please refer to SWRA640 for more info. The following is the link.
In reply to PM:
Thank you for the confirmation!
As per your suggestion, I am trying the ti15.4 stack example on our cc1312r custom boards. I am trying to modify the code for 433 MHz, but the sysconfig is overwriting any settings I am trying to make in the files during build. How do I prevent the sysconfig from overwriting my changes.
The characterization for 433 Mhz on the CC1312R is not completed, see https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/708238#pi320995=2.
You'll have to port over the RF settings from SmartRF Studio or try porting over the settings from our CC1352P1 examples. I believe you've started this process, but I just want to make sure you are aware. As we have not released support for 433 Mhz, please note we can't guarantee full functionality at this PHY. That being said, it should have similar performance compared to the CC1310.
See here for some instructions on disabling sysconfig (you may have to remove unused include paths after following these steps):
If you have any follow up questions, please create a new thread by hitting the "Ask a related question" as this question diverges from the original question asked.
Okay thank you Ammar. I will try disabling the sysconfig approach.
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.