My customer would need presicion after exchange on below exchange on CC2534:
TI feedback :
The CC2534 was a custom part that we offered for select customers so it wasn’t normally accessible from our website. It was a ROMable device that could only be used with pre-configured firmware from TI. It does not support ZRC2.0. However it can be used as a network layer only device in which case the host processor performs the higher layers and in that case could be used to implement ZRC2.0.
However the CC2533F96 does support ZRC2.0 via RemoTI-1.4.0.
Thanks so much for the info re CC2534 and support for ZRC2.0. We are continuing to explore options to support these Charters RF4CE remotes on our XX CC2534 based boxes. Can you provide additional feedback on these follow-up questions?
1. Is the RF4CE MSO profile actually implemented on the CC2534 or is part of it implemented on the Linux side?
2. Does the CC2534 expose the network layer to the Linux side?
3. Does TI already have a version of ZRC2.0 that runs on Linux? If so, is it possible to use that instead of starting from scratch? If not, what level of support would TI be available for?
Thanks in advance for your help,
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 Toby Pan:
Could you please clarify each point requested by customer ?
It isn't clear from my side
In reply to Maxime ATHEE:
The initial feedback from TI reference in the original post is correct.
1. Yes, there exist a version of firmware for CC2534 which implements RF4CE MSO.
2. Yes, there exist a version of firmware for CC2534 which expose RF4CE network layer API
3. We only have a version of ZRC2.0 that communicates with an embedded implementation of ZRC2.0. If the ZRC2.0 profile is fully ported to Linux that would require some manual work. The APIs are however identical, so it should not be too difficult. No level of support beyond existing documentation can be provided.
Checkout this repository for a host implementation for ZRC2.0, on top of ZRC2.0 profile. This works with RemoTI-1.4.0 on CC2533F96. The above mentioned port is required to use network layer APIs.
In reply to Torbjorn Sorby:
In reply to Ed Bortoni:
ZRC2.0 is primarily improvements regarding pairing. The concept of buttonless pairing, bonding and improved security.
I'm not 100% sure, but simply formatting ZRC2.0 data could probably be accomplished with the older SDKs (and ZRC1.1). However, it wouldn't be compliant since both sides would have to "agree" to secretly support the data format. It could then sort of be viewed as a vendor specific extension of ZRC1.1 (while still using a profile ID < 0xC0)...
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.