|
|
|
TI-Drivers is a software component that includes device drivers for the assorted peripherals on a given device (i.e., UART, SPI, I2C, etc.).
These device drivers are also included in the TI-RTOS product. They are provided here as a separate component so that they can be used as a stand-alone library in non-TI-RTOS environments. To avoid duplication, TI-RTOS includes this versioned component in the tirtos/products directory.
The following documentation is provided with this release.
NOTE: Please view the Device Specific driver implementations as they may contain or exclude certain features that are defined in the top level interfaces.
License and manifest.
Release notes from previous releases are also available in the release notes archive directory.
| TIDRIVERS JIRA Identifier | Summary |
|---|---|
| TIDRIVERS-404 | PDM driver decimationFilterInRAM too big |
| TIDRIVERS-383 | Bug in SPICC26XXDMA SSI Driver breaks hardware chip handling in given scenarios |
| TIDRIVERS-381 | Move include of HwiP.h from CC3200_LAUNCHXL.c, into UDMACC3200.h |
| TIDRIVERS-373 | Incorrect RAT timer count after waking up from RF_yield |
| TIDRIVERS-364 | BLE PM Timing Problem When Using CCS |
| TIDRIVERS-362 | LMAC TX stuck during the ASYNC message |
| TIDRIVERS-359 | RAT timer callback is missing sometimes |
| TIDRIVERS-357 | Remove the call to PRCMPeripheralClkEnable() in GPIOCC3200.c |
| TIDRIVERS-350 | PIN_init should ignore PIN_UNASSIGNED |
| TIDRIVERS-349 | g_hwiInt in crypto API should be declared as volatile |
| TIDRIVERS-340 | BLE Advertising Appears to Stop Working When PM Is Used |
| TIDRIVERS-338 | TIMAC assert on ‘RAT negative channel’ on beacon mode coordinator or end device |
| TIDRIVERS-337 | Radio driver failed to wakeup in TIMAC beacon mode |
| TIDRIVERS-325 | PowerCC3200_initPolicy() should no longer check Clock_tickPeriod |
| TIDRIVERS-324 | Call to RF_getCurrentTime Can Cause a System Fault and Hang |
| TIDRIVERS-323 | RF_getRssi stuck (wait forever) |
| TIDRIVERS-317 | Improperly power down in RF_yield() while current command is not completed |
| TIDRIVERS-314 | Radio failed to wake up after 40 to 80 minutes |
| TIDRIVERS-311 | RF_getCurrentTime() is accessing RAT register while it is not available |
| TIDRIVERS-308 | Sometimes RF_postCmd() gets stuck |
| TIDRIVERS-193 | Posting Commands Rapidly When Using nInactivityTimeout of Zero Causes Hang |
| TIDRIVERS-192 | Second transaction fails if first fails because of Address NACK |
| TIDRIVERS-191 | RCOSC_HF calibration check should have hysteresis to avoid likelihood of 2 TDC measurements |
| TIDRIVERS-185 | RF driver should not while(1) on error, but rather call fault handler |
| TIDRIVERS-184 | Incorrect RAT timer count after waking up from RF_yield() |
| TIDRIVERS-181 | crypto API is stuck at forever loop |
| TIDRIVERS-172 | Need to update existing PWM drivers to the new “PWM2” API |
| TIDRIVERS-168 | Add support for IO retention groups during shutdown (ti.drivers.power.PowerCC3200) |
Supported Operating Systems:
This release requires the following software components and tools versions to successfully function:
This release was validated using the following components:
All releases have 4 digits (M.mm.pp.bb). This includes GA and pre-releases (engineering, alpha/EA, beta, etc.). Pre-releases are denoted with a suffix (e.g. 6.30.00.00-eng or 6.30.00.10-beta).
This product’s version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and bb is an unrestricted set of digits used as an incrementing build counter.
To support multiple side-by-side installations of the product, the product version is encoded in the top level directory.
Subsequent releases of patch upgrades will be identified by the patch number. Typically, these patches only include critical bug fixes.
Last updated: June 22, 2016 Build Ver: 2.20.00.08