SYS/BIOS 6.41.00.26 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.41.00.26.
Added Seconds module (Seconds_get/set()) and integration with standard C runtime’s time.h APIs
Added SMP support for dual-core Cortex-A15 devices
Fixed warnings for the bios.mak rebuild
Updated the SYS/BIOS User’s Guide including new section for the Support modules
Miscellaneous bug fixes (including 2 critical bug fixes for GateMutexPri)
Defects Fixed in
SYS/BIOS
6.41.00.26 GA (Fixes since SYS/BIOS 6.40.03):
ID
Headline
SDOCM00113731 Hwi_switchAndRun() internal
assembly function should use XAR5 instead of XAR3 to follow compiler
conventions SDOCM00113659 Tasks failing to acquire a GateMutexPri gate are not queued in task priority order. SDOCM00113586
GateMutexPri_enter() is not thread safe, allowing mutliple threads to
enter the gate simultaneously. SDOCM00113565 Add SMP support for Cortex-A15 (on OMAP5, DRA7XX, Keystone2 devices) SDOCM00113464 iar.tools.configuro getCompileOpts() fails to get the correct -I and -D SDOCM00113403 BIOS custom build output are not cleaned in IAR Embedded Workbench SDOCM00113388 Add documentation to BIOS User's Guide for Seconds module SDOCM00113312
rebuild bios.mak path for GCC in BIOS user guide should only be the
path to the directory, not the executable SDOCM00113310 SMP version of Task_yield() and Task_setAffinity() has a bug SDOCM00113081 Incorrect reference to ti.sysbios.misc package in User Guide SDOCM00113079 Event documentation incorrect reference to Mailbox_Params.notEmptyEvent SDOCM00113017 c66 Cache_getSize() needs to be fixed to return values greater than 256KB SDOCM00112736 modify Cortex-A15 Cache module to setup/initialize cache as early as possible during boot time SDOCM00112735 C66 Cache module to setup/initialize cache as early as possible during boot time SDOCM00112647 Add XDC runtime modules to BIOS User’s Guide SDOCM00112618 Stop shipping prebuilt Instrumented and nonInstrumented libs SDOCM00112239 update IAR targets to give warning if "Program.stack" has been $iswritten SDOCM00112160 CpInt's ROV is always showing CIC0 SDOCM00112060
C66 CpIntc_dispatch() signature should match hwiFxn function signature
and the cdoc should include a cfg script example SDOCM00108194 doc typo: Timer_ANY should be Timer.ANY in the example on p 162 of BIOS UG (SPRUEX3N) SDOCM00108116 SYS/BIOS source code rebuild has remarks for C6x devices SDOCM00108095 The time() function (generated by Seconds module) does not work for IAR/MSP430 SDOCM00107245 Errors during the clean when rebuilding SYS/BIOS SDOCM00106500 Undocumented parameter in EventCombiner_dispatchPlug SDOCM00106164 add support for 2807x devices
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.