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.
Replies: 17
Views: 35152
With the introduction of CC1310 die Rev B Texas Instruments is announcing several important enhancements increasing the versatility and usability of all CC1310 part numbers going forward. The changes and updates are summarized as follows:
1) Removed limitation on usage of on-chip 32 kHz RC oscillator. On die Rev B the built in 32 kHz RC oscillator (RCOSC_LF) can be used as the system low frequency oscillator to clock the RTC. The accuracy of the RTC when using this oscillator is within +/- 500 ppm when calibrated 1x per second. For radio networks that have more relaxed timing accuracy than the above, it is now possible to run the CC1310 die Rev B with only 1x crystal on the PCB (24 MHz).
2) Removed limitation on frequency bands supported in CC1310. New frequency bands are supported for the CC1310 from die Rev B and onwards, starting with support for frequency bands in the 430-510 MHz range. This will allow customers to use the same device in a number of markets worldwide. Note that current die Rev A material will still be limited to 863-930 MHz only. SmartRF Studio 2.4.3 or later will detect die Rev A devices and issue an appropriate warning as to the applicable frequency range. Please remember to update SmartRF Studio accordingly.
3) Removed limitation on Brown-out detector (BOD). The brown-out detector (BOD) has been improved from die Rev A to die Rev B and the CC1310 datasheet restrictions regarding the BOD no longer apply. Restrictions do still apply for die Rev A material. More details regarding this item is found in section 6.7 – Power management in the CC1310 datasheet (SWRS181 update C, footnote 2).
4) ESD correction. The ESD HBM and ESD CDM levels are corrected to ±3000V and ±500V respectively in the CC1310 datasheet. Note the following:
5) DEVICE ID change. The DEVICE ID will be stepped between die Rev A (2B9BE02F) and die Rev B (3B9BE02F). The Device Identification Register, abbreviated TAPID and holding the DEVICE ID, is a register within the ICEPick status and control registers. This register is accessed via JTAG. Reading DEVICE ID can also be done in software, using the ICEPICK_DEVICE_ID or the USER_ID registers. Please refer to the CC13xx, CC26xx SimpleLink™ Wireless MCU Technical Reference Manual for details on these registers. For FLASH-PROGRAMMER-2 version 1.7.2 or later no updates are required, while for earlier versions the software running on the tool must be updated. Else die Rev B will not be recognized. For the Uniflash Standalone Flash Tool die Rev B support is provided by using the application «Update»-feature. For third party Flash programmers please refer to the companies providing these flash programmers.
6) Mandatory Software update. It is mandatory that the software is updated to TI-RTOS version 2.16.01.14 or later in order to maintain compatibility between die revisions. Please refer to the guidelines on the TI-RTOS web page for more details. Register settings supporting both die Rev A and die Rev B are generated using SmartRF Studio 2.4.3 or later. Emphasis: Without applying the new software, correct operation of the CC1310 die Rev B device cannot be guaranteed!
For more info on the PCN please refer to the following Wiki: http://processors.wiki.ti.com/index.php/CC1310_rev_B_PCN_information
In reply to Alain Guelzec:
hi:
in the datasheet of cc1310 ,it's described as following:
6.3 RF Core
Wide range of data rates:
– From 625 bps (offering long range and high robustness) to as high as 4 Mbps
it's true?
In reply to xuji zhao:
If my post answers your question, please click on "This Resolved my issue" button to benefit others who have the same issue.
YK Chen
CC13xx TRX WOR project.
How to change CC26xx/CC13xx UART baudrate dynamically in your application.
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 check APS ack in TI Z-Stack
How to detect button hold in CC26x2, CC13x0, CC13x2 SDK.
660 Zigbee devices in the same Zigbee network!
How to setup Mosquitto on Raspberry Pi and make Contiki/Contiki-NG cc26xx-web-demo do mqtt publish to it.
In reply to YiKai Chen:
In reply to TER:
Hello,
Could you give some details about data rate limitation ? It is characterized only at 50kbps maximum, and errata indicates that it supports up to 100kbps, much less than the 4mbps expected in maximum.
What is the current characterisation status of the rev B die ?
Any idea of sensitivity at 250kbps, 500kbps and 1Mbps @ 868MHz ?
When will be the docs updated ?
What happen and what are the risks if I use 500kbps on this chip now ?
I have ordered the CC1310DK (but not started yet), is it possible with smartRFstudio to set that data rates and make range tests ?
Aurelien
In reply to aurelienr:
We have done a characterization of 500 kbps. Performance figures will be added to the data sheet. This PHY will also be included in the next release of SmartRF Studio.
In the meantime please refer to the following Wiki:
In reply to Sverre: