SYS/BIOS 6.40.01.15 is a GA release of SYS/BIOS
6.40.00. CCS users must use CCSv6.0.0 or higher. This
release also has support for GCC (for Cortex-M) and IAR (for Cortex-M
and MSP430).
Please read the SYS/BIOS User's Guide for help installing and setting
up your environment to use SYS/BIOS 6.40.01.15.
This release is identical to 6.40.00.13 except for a minor installation fix.
Repackaging for use in CCSv6.
The 'target' and 'platform' packages have been moved to the SYS/BIOS
package and removed from XDC 3.30.00 tools. SYS/BIOS 6.40.0x
requires XDC 3.30.00 and CCSv6.0 or later.
Changed
'timeout' parameter in Semaphore, Mailbox, and Event from UInt to
UInt32. This will affect compatiblity for MSP430 and C2000
devices where and UInt and UInt32 are not the same size.
Added support for the TMS320F2837xD devices.
Added support for the Cortex-A15 for the TCI6636K2H device.
Added configuration paremeters to help minimize code and data size and updated the User's Guide "sizing" appendix.
Miscellaneous bug fixes.
Defects Fixed in
SYS/BIOS
6.40.01.15 GA (Fixes since SYS/BIOS 6.37.02):
ID
Headline
SDOCM00106892 MSP430's
TaskSupport_buildTaskStack() IAR asm implementation does not read task
function address correctly SDOCM00106341 Device support documentation for F28377 missing SDOCM00106340 Timer64 chained mode does not work for periods that require more than 32-bits SDOCM00106243 Update the data types of timeouts to be UInt32 SDOCM00105758
Cortex-A15 MMU module's setFirstLevelDesc/setFirstLevelDescMeta
functions have a bug when attrs.type is TABLE SDOCM00105683
update "minimizing size" appendix to reflect latest and greatest (add
device specific sections as well) SDOCM00105635 Add m3.Hwi.resetVectorTableAddress and m3.Hwi.vectorTableAddress to xgconf page. SDOCM00105596 Unnecessary re-links of CCS SYS/BIOS applications SDOCM00105376 Improper reference to params in setPeriodMicroSecs() in family/arm/m3/Timer.xs SDOCM00105129
Rework functionality of Task check stacks, hooks, and logging so that a
single ISR context on a task stack can be supported. SDOCM00105096 Update m3 Hwi code to copy vector table only when Hwi_nvic.VTOR != Hwi_resetVectors. SDOCM00105082
Add warnings to Mailbox_create/construct/post docs - message size and
possible memory corruption of receive buffer too small SDOCM00104987 IAR ARM applications contain two vector tables SDOCM00104968 hal Hwi_construct() and Timer_construct() call their delegate XXX_create() functions. SDOCM00104778 update benchloop to use "TimestampProvider_get16()" (or Timestamp_get16()) for MSP430 target SDOCM00104723
use Hwi_switchAndRun() instead of separate switchTo/From functions,
optimize the extra headroom from stack SDOCM00104630
Add TRex example support for Cortex-A9 and Cortex-A15 (requires updates
.xml files and filters from CCS) SDOCM00104586 Hwi, Task, Swi (and maybe more) need to support construct with STATIC_POLICY SDOCM00104463 Configuring user hook for FatFS gettime function causes warning in user build SDOCM00104417 The Clock Module's Timer Proxy should be made configurable SDOCM00104386 remove need for HeapMin and minimal heap. consider providing custom atexit()/exit() SDOCM00104294
Fix Timer example code in SYS/BIOS user's guide to not show two
arguments passed to the tick function SDOCM00104273 add support for single-core A15 on TCI6636K2H SDOCM00104199 Need to better document system stack reclamation during SYS/BIOS startup SDOCM00103795 Typo in Section 8.5.3 of SYS/BIOS User Guide SDOCM00103734 Clock timerId field in ROV is not always correct. Can show '0' when it should be '2'. SDOCM00103539 ROV needs to show Mod_constructed tasks and semaphores, etc. SDOCM00103472
If an M3/M4 core is re-started (without a reset) while in handler mode,
Hwi_initStacks() fails to split the stacks SDOCM00103344 Redesign M3/M4 Hwi module to eliminate dispatch table SDOCM00103312 SYS/BIOS heap modules need better documentation for alloc() alignment requirements SDOCM00103110 update SYS/BIOS documenation to say "TI-RTOS Kernel" SDOCM00103099 Revisit benchmarks to see if footprints can be improved. SDOCM00102777
A15 Timer's startup function is not called during BIOS startup if this
timer is not the default hal/Timer delegate SDOCM00102776 Need a Power module for ti.sysbios.family.arm.m3 SDOCM00102041
AM3505/AM3517 devices are shown in the supported device list but CCS A8
projects do not build for evmAM3505/AM3517 platforms SDOCM00101967 all Module__prologue/epilogue.h files should be protected with #ifdef __cplusplus SDOCM00101934 DMTimer timerSettings config param should allow changing eventId. SDOCM00101017 814x and 816x show up under ARM9 and M3 in TI Resource explorer SDOCM00100886 Update cdoc for intFreqs config parameter in timer64 module SDOCM00100610 Enhance Timer_setNextTick interface to include the number of ticks to be skipped SDOCM00100244
Modify the "typical" example to exit upon completion, so
System_printf() output is flushed to the CCS console
Binary compatible for all targets except MSP430 and C2000.
MSP430
and C2000 users must recompile all source files that use the Semaphore,
Mailbox, or Event modules. The timeout parameter was changed from
UInt to UInt32 which are different sizes.
All other users can use libraries built with 6.35.0x and 6.37.0x with 6.40.00.
SYS/BIOS 6.34 and older
Source compatible. All APIs are supported but all source files must be recompiled.
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 b
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 (e.g. bios_6_30_00_00).
Subsequent
releases of patch upgrades will be identified by the patch number, ex.
SYS/BIOS 6.30.01.15 with directory bios_6_30_01_15. Typically, these
patches only include critical bug fixes.
Please note that
version numbers and compatibility keys are NOT the same. For an
explanation of compatibility keys, please refer to the 'Upgrade and
Compatibility Information' section.