|
|
|
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-629 | rfEasyLinkNp example locks up when UART is exercised from script |
| TIDRIVERS-609 | CC13/26xx disables VIMS in IDLE even if CCFG configures VIMS to GPRAM |
| TIDRIVERS-589 | CryptoCC26XX_transact and CryptoCC26XX_transactPolling contain large amounts of duplicate code |
| TIDRIVERS-573 | nRtc1 is reset every time powerup sequence is complete |
| TIDRIVERS-567 | MSP432 UART driver should use ‘tx complete’ interrupt (not tx empty) to work with LPM |
| TIDRIVERS-556 | Move enabling of returnPartial IRQ in SPIDMACC26XX to control function for better logical grouping. |
| TIDRIVERS-554 | Need to reset bYieldPwrDnCancel when switching PHY |
| TIDRIVERS-552 | set the bNoFsPowerUp in the RF_SetupCmd to 0. |
| TIDRIVERS-551 | CryptoCC26XX.h needs better CCM documentation |
| TIDRIVERS-550 | PINCC26XX.h has invalid pin mux macros |
| TIDRIVERS-542 | SPI driver tries to dereference the NULL pointer, need bugfix |
| TIDRIVERS-537 | CryptoCC26XX_loadKey pends transSem with BIOS_NO_WAIT |
| TIDRIVERS-532 | Clear flag and cleanup flag check after a cancelled command callback |
| TIDRIVERS-528 | bPowerChangePhy check in RF_scheduleCmd is not done properly |
| TIDRIVERS-527 | RF driver code cleanup for cancel yield corner cases |
| TIDRIVERS-524 | UDMACC26XX.h generates assignment errors |
| TIDRIVERS-519 | RF driver is getting stuck when Clock.tickPeriod is too high |
| TIDRIVERS-518 | Start using analogCfgMode in powerup to reduce powerup time |
| TIDRIVERS-516 | Accessing RAT when RF Core is powered down |
| TIDRIVERS-510 | Move SysCtrl_DCDC_VoltageConditionalControl() to before entering standby |
| TIDRIVERS-505 | RF_postCmd() cannot cancel RF_yield if there is a pending command |
| TIDRIVERS-495 | RF_RadioSetup missing rfc_CMD_PROP_RADIO_DIV_SETUP_t |
| TIDRIVERS-494 | Possible bug with RF driver calling callback with e = null |
| TIDRIVERS-493 | No need to call RFCRTrim every time we wake up |
| TIDRIVERS-492 | Faulty RF_Stat enum |
| TIDRIVERS-475 | RF driver changed for Power Consumption breaks NPI |
| TIDRIVERS-434 | MSP430 UART driver does not support callback mode |
| TIDRIVERS-427 | Support RF driver integration for SDK03 |
| TIDRIVERS-390 | CC13xx UART HW RX Buffer overrun during TIMAC Cop overnight test |
| TIDRIVERS-384 | Bug in PINCC26XX PIN Driver causes glitches on IO output in given scenarios |
| TIDRIVERS-380 | UART_readCancel() should always turn off receiver even if there’s no active read ongoing |
| TIDRIVERS-372 | Formalize support for overlapping SPI Rx and Tx buffers |
| TIDRIVERS-371 | UARTCC26XX driver incorrectly computes number of bits for clock timeout |
| TIDRIVERS-301 | Enable inactivity timeout feature when RAT channels are also used |
| TIDRIVERS-288 | Create Jenkins job for GCC to be able to run regression for all tests |
| TIDRIVERS-240 | Dual-mode scheduler implementation for RF driver |
| TIDRIVERS-208 | SPICC26XXDMA - higher current draw than necessary when txBuf is NULL |
| TIDRIVERS-178 | UDMACC26XX_close is not thread safe |
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: September 12, 2016 Build Ver: 2.21.00.04