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.

TI MAC for CC2545

Other Parts Discussed in Thread: CC2545, CC2530, CC2541, CC2543, CC2544

we were been facing problems in throughput of  CC2530 as it is TI MAC and Zigbee stack ,typically the data rate is maximum 250Kbps and hardly we are getting a throughput of only 50Kbps as out network involves voice streaming through multiple nodes,so i have seen CC2545 with higher data rate about 2Mbps which could rescue us,but now our problem is TI MAC is only available for CC2530 

what to do if i need a MAC for CC2545 ? are there any thirdparties who are giving MAC needed for CC2545

if a MAC is available we can afford to write our own datalink layer bypassing zigbee,i need some suggestions on this from experts

  • Hello DARAM,

    For the CC2543, CC2544, CC2545 and CC2541 parts we do not have a "proprietary" available MAC layer. But you could consider porting the TIMAC to these devices or create your own. If you want to look further into the previously mentioned proprietary parts I would recommend you to look at the CC2541 (which can also run the BLE stack) which has lower power consumption at 0 dBm output power than the CC2545.

    We also provide devices for higher quality audio called PurePath™.

  • using bluetooth for wireless networks is not that appreciable 

    but are there any other alternatives to improve the through put,

    any alternative MAC suggestions ?which can offer high data rates(as i cant go for 802.15.4 as the data rate is limited to 250Kbps )? that can be ported to CC2545 

    our application typically is a audio streaming mesh network application so an bluetooth or wifi may not help in mesh,and they are quite high power consuming

    any other solutions that you can suggest to serve our purpose ???

  • Hello DARAM,

    That sounds challenging indeed.

    There is an old thread that touches on the subject, but it does not really offer a good solution:

    http://e2e.ti.com/support/wireless_connectivity/f/158/t/134233.aspx