DSP/BIOS v5.31.08 Release Notes

Last updated:  10 Jul 2007

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.08 is an all ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_08.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.08

• All ISA release which includes all changes in BIOS 5.31.07.

• Maintenance release with defect fixes.

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

   OMAP2430/3430 HWI/WUGEN API Documentation -- The new HWI/WUGEN APIs are not documented in the BIOS API Guide.  This is tracked by SDSCM00016107 which contains documentation for each API.

    PWRM/3430 Documentation Update  --  SDSCM00014096: When the IVA MMU is enabled and PWRM is enabled, the base addresses of the support modules must be mapped into the IVA MMU and BIOS must be configured with the respective virtual addresses using the following PWRM configuration properties:

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

    DSP/BIOS RTA Control Panel does not update values correctly when using comma decimal separator in Windows -- The RTA Control Panel does not work as expected when using Windows Regional Settings where ',' is used instead of '.' for the decimal separator.  Only workaround is to use Regional Settings where '.' is the decimal separator, or use default 1 second update rate.  This is tracked by SDSCM00017755.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.05 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.08 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.03 with directory bios_5_31_03.  

Point releases where new features such as additional device support are added, increment the minor digits and reset the patch counter (i.e., the patch counter is set to zero and removed from the directory qualifier).  For example, if the current BIOS version is 5.31.03, a subsequent point release would be 5.32. 

DSP/BIOS v5.31.07 Release Notes

Last updated:  29 May 2007

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.07 is an all ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_07.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.07

• All ISA release which includes all changes in BIOS 5.31.06.

• Maintenance release with defect fixes.

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

   OMAP2430/3430 HWI/WUGEN API Documentation -- The new HWI/WUGEN APIs are not documented in the BIOS API Guide.  This is tracked by SDSCM00016107 which contains documentation for each API.

    PWRM/3430 Documentation Update -- When the IVA MMU is enabled and PWRM is enabled, the base addresses of the support modules must be mapped into the IVA MMU and BIOS must be configured with the respective virtual addresses using the following PWRM configuration properties:

CM_BASEADDR
IVAMMU_BASEADDR
PRM_BASEADDR
SCM_BASEADDR

Base address of Clock Manager (CM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Clock Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: CM_BASEADDR
Type: Address
Example: bios.PWRM.CM_BASEADDR = 0x12004000

Base address of IVA MMU. When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the IVA MMU. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: IVAMMU_BASEADDR
Type: Address
Example: bios.PWRM.IVAMMU_BASEADDR = 0x12005000

Base address of Power & Reset Manager (PRM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Power & Reset Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: PRM_BASEADDR
Type: Address
Example: bios.PWRM.PRM_BASEADDR = 0x12006000

Base address of System Control Module (SCM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the System Control Module. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: SCM_BASEADDR
Type: Address
Example: bios.PWRM.SCM_BASEADDR = 0x12007000

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.05 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.07 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.03 with directory bios_5_31_03.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.03) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31.06 Release Notes

Last updated:  11 April 2007

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.06 is an all ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_06.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.06

• All ISA release which includes all changes in BIOS 5.31.05.

• Maintenance release with defect fixes.

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

   OMAP2430/3430 HWI/WUGEN API Documentation -- The new HWI/WUGEN APIs are not documented in the BIOS API Guide.  This is tracked by SDSCM00016107 which contains documentation for each API.

    PWRM/3430 Documentation Update -- When the IVA MMU is enabled and PWRM is enabled, the base addresses of the support modules must be mapped into the IVA MMU and BIOS must be configured with the respective virtual addresses using the following PWRM configuration properties:

CM_BASEADDR
IVAMMU_BASEADDR
PRM_BASEADDR
SCM_BASEADDR

Base address of Clock Manager (CM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Clock Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: CM_BASEADDR
Type: Address
Example: bios.PWRM.CM_BASEADDR = 0x12004000

Base address of IVA MMU. When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the IVA MMU. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: IVAMMU_BASEADDR
Type: Address
Example: bios.PWRM.IVAMMU_BASEADDR = 0x12005000

Base address of Power & Reset Manager (PRM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Power & Reset Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: PRM_BASEADDR
Type: Address
Example: bios.PWRM.PRM_BASEADDR = 0x12006000

Base address of System Control Module (SCM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the System Control Module. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: SCM_BASEADDR
Type: Address
Example: bios.PWRM.SCM_BASEADDR = 0x12007000

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

    Stairstep project file missing source file entries for evm6424 in stairstep.pjt -- This is tracked by SDSSCM00016558.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.05 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.06 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.03 with directory bios_5_31_03.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.03) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31.05 Release Notes

Last updated:  28 Mar 2007

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.05 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_05.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.05

• All ISA release which includes all changes in BIOS 5.31.04.

• Maintenance release with defect fixes.

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

   OMAP2430/3430 HWI/WUGEN API Documentation -- The new HWI/WUGEN APIs are not documented in the BIOS API Guide.  This is tracked by SDSCM00016107 which contains documentation for each API.

    PWRM/3430 Documentation Update -- When the IVA MMU is enabled and PWRM is enabled, the base addresses of the support modules must be mapped into the IVA MMU and BIOS must be configured with the respective virtual addresses using the following PWRM configuration properties:

CM_BASEADDR
IVAMMU_BASEADDR
PRM_BASEADDR
SCM_BASEADDR

Base address of Clock Manager (CM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Clock Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: CM_BASEADDR
Type: Address
Example: bios.PWRM.CM_BASEADDR = 0x12004000

Base address of IVA MMU. When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the IVA MMU. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: IVAMMU_BASEADDR
Type: Address
Example: bios.PWRM.IVAMMU_BASEADDR = 0x12005000

Base address of Power & Reset Manager (PRM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Power & Reset Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: PRM_BASEADDR
Type: Address
Example: bios.PWRM.PRM_BASEADDR = 0x12006000

Base address of System Control Module (SCM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the System Control Module. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: SCM_BASEADDR
Type: Address
Example: bios.PWRM.SCM_BASEADDR = 0x12007000

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.05 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.03 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.03 with directory bios_5_31_03.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.03) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31.04 Release Notes

Last updated:  08 Feb 2007

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.04 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_04.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.04

• All ISA release which includes all changes in BIOS 5.31.03

• Maintenance release with defect fixes.

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

   PWRM/3430 Documentation Error --There is a typo in the DSP/BIOS Power Management AppNote document (SPRAA98). Its in a code example on how to set the wakeup event. The index values for sleepArgs should start at 0, not at 1. This is tracked by SDSCM00014100.

Incorrect version (page 28):

sleepArgs[1] = 0xFFFFFFBF; /* enable GP timer 5 as wakeup */
sleepArgs[2] = 0x0000FFFF; /* no wakeups via WUGEN_MEVT1 */
sleepArgs[3] = 0x000FFFFF; /* no wakeups via WUGEN_MEVT2 */
sleepArgs[4] = 0x00000001; /* no wakeups via WUGEN_MEVT3 */

Correct version:

sleepArgs[0] = 0xFFFFFFBF; /* enable GP timer 5 as wakeup */
sleepArgs[1] = 0x0000FFFF; /* no wakeups via WUGEN_MEVT1 */
sleepArgs[2] = 0x000FFFFF; /* no wakeups via WUGEN_MEVT2 */
sleepArgs[3] = 0x00000001; /* no wakeups via WUGEN_MEVT3 */

    PWRM/3430 Documentation Update -- When the IVA MMU is enabled and PWRM is enabled, the base addresses of the support modules must be mapped into the IVA MMU and BIOS must be configured with the respective virtual addresses using the following PWRM configuration properties:

CM_BASEADDR
IVAMMU_BASEADDR
PRM_BASEADDR
SCM_BASEADDR

Base address of Clock Manager (CM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Clock Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: CM_BASEADDR
Type: Address
Example: bios.PWRM.CM_BASEADDR = 0x12004000

Base address of IVA MMU. When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the IVA MMU. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: IVAMMU_BASEADDR
Type: Address
Example: bios.PWRM.IVAMMU_BASEADDR = 0x12005000

Base address of Power & Reset Manager (PRM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Power & Reset Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: PRM_BASEADDR
Type: Address
Example: bios.PWRM.PRM_BASEADDR = 0x12006000

Base address of System Control Module (SCM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the System Control Module. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: SCM_BASEADDR
Type: Address
Example: bios.PWRM.SCM_BASEADDR = 0x12007000

    Examples "makefile,64P" issue -- The provided makefile,64P in the examples directory for building all 64P devices has an error in it. There is a ")" where there should be a "\". This can be corrected or the user can build the individual examples using the provided makefiles for each. This is tracked by SDSCM00014184.

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.03 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.03 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.03 with directory bios_5_31_03.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.03) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31.03 Release Notes

Last updated:  21 Dec 2006

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.03 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_03.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.03

• All ISA release which includes all changes in BIOS 5.31.02

• Maintenance release with defect fixes and minor enhancements.

• Minor documentation updates.

• New chip support

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

   PWRM/3430 Documentation Error --There is a typo in the DSP/BIOS Power Management AppNote document (SPRAA98). Its in a code example on how to set the wakeup event. The index values for sleepArgs should start at 0, not at 1. This is tracked by SDSCM00014100.

Incorrect version (page 28):

sleepArgs[1] = 0xFFFFFFBF; /* enable GP timer 5 as wakeup */
sleepArgs[2] = 0x0000FFFF; /* no wakeups via WUGEN_MEVT1 */
sleepArgs[3] = 0x000FFFFF; /* no wakeups via WUGEN_MEVT2 */
sleepArgs[4] = 0x00000001; /* no wakeups via WUGEN_MEVT3 */

Correct version:

sleepArgs[0] = 0xFFFFFFBF; /* enable GP timer 5 as wakeup */
sleepArgs[1] = 0x0000FFFF; /* no wakeups via WUGEN_MEVT1 */
sleepArgs[2] = 0x000FFFFF; /* no wakeups via WUGEN_MEVT2 */
sleepArgs[3] = 0x00000001; /* no wakeups via WUGEN_MEVT3 */

    PWRM/3430 Documentation Update -- When the IVA MMU is enabled and PWRM is enabled, the base addresses of the support modules must be mapped into the IVA MMU and BIOS must be configured with the respective virtual addresses using the following PWRM configuration properties:

CM_BASEADDR
IVAMMU_BASEADDR
PRM_BASEADDR
SCM_BASEADDR

Base address of Clock Manager (CM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Clock Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: CM_BASEADDR
Type: Address
Example: bios.PWRM.CM_BASEADDR = 0x12004000

Base address of IVA MMU. When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the IVA MMU. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: IVAMMU_BASEADDR
Type: Address
Example: bios.PWRM.IVAMMU_BASEADDR = 0x12005000

Base address of Power & Reset Manager (PRM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the Power & Reset Manager. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: PRM_BASEADDR
Type: Address
Example: bios.PWRM.PRM_BASEADDR = 0x12006000

Base address of System Control Module (SCM). When enabling the IVA MMU, use this configuration property to specify the virtual address mapped to the physical address of the System Control Module. The IVA MMU must map one page (4K bytes) of virtual memory starting at the given address.

Tconf Name: SCM_BASEADDR
Type: Address
Example: bios.PWRM.SCM_BASEADDR = 0x12007000

    Examples "makefile,64P" issue -- The provided makefile,64P in the examples directory for building all 64P devices has an error in it. There is a ")" where there should be a "\". This can be corrected or the user can build the individual examples using the provided makefiles for each. This is tracked by SDSCM00014184.

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.03 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.03 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.03 with directory bios_5_31_03.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.03) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31.02 Release Notes

Last updated:  14 Nov 2006

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.02 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_02.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.02

• All ISA release which includes all changes in BIOS 5.31

• Maintenance release with defect fixes and minor enhancements.

• Minor documentation updates.

• New chip support

Device Support

Known Issues

    Please check the following link for additional information when upgrading from 4.90 to 5.x -- Knowledge base with known 4.90 to 5.x upgrade issues

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

    RTA/RTDX problem when load/run different programs -- After running RTA successfully on a DaVinci program, if another program is then loaded without restarting CCS 3.2 then RTA may not work sometimes.  This problem is intermittent.  If displays do not update, the workaround is to restart CCS before loading a new program.  This is tracked by SDSCM00003318.

    DSP/BIOS RTA plugins update very slowly via RTDX on DaVinci -- (CCS 3.2 issue) When RTA plugins are opened after a program is loaded and started. To work around this problem, open the DSP/BIOS RTA plugins before starting the program. This is tracked by SDSCM00002472

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    DSP/BIOS does not create a reset vector at address 0x800000 for TCI6482 or dsk6455. This is tracked by SDSCM00010342.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX error comes up on Debug -> Run when executing examples on 5912 via XDS 510 -- This is tracked by SDSSCM00005600.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

    RTA (VBD) crash after lots of disconnects and connects -- This is tracked by SDSSCM00012471.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31.02 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.02 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.02 with directory bios_5_31_02.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.02) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31.01 Release Notes

Last updated:  06 Oct 2006

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31.01 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31_01.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31.01

• All ISA release which includes all changes in BIOS 5.31

• Maintenance release with defect fixes and minor enhancements.

• Minor documentation updates.

• New chip support

Device Support

Known Issues

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

    RTA/RTDX problem when load/run different programs -- After running RTA successfully on a DaVinci program, if another program is then loaded without restarting CCS 3.2 then RTA may not work sometimes.  This problem is intermittent.  If displays do not update, the workaround is to restart CCS before loading a new program.  This is tracked by SDSCM00003318.

    DSP/BIOS RTA plugins update very slowly via RTDX on DaVinci -- (CCS 3.2 issue) When RTA plugins are opened after a program is loaded and started. To work around this problem, open the DSP/BIOS RTA plugins before starting the program. This is tracked by SDSCM00002472

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    DSP/BIOS does not create a reset vector at address 0x800000 for TCI6482 or dsk6455. This is tracked by SDSCM00010342.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX error comes up on Debug -> Run when executing examples on 5912 via XDS 510 -- This is tracked by SDSSCM00005600.

    RTDX tutorial examples do not all execute as expected  when run on TCI6482 simulator little endian -- This is tracked by SDSSCM00010736.

    RTDX Hot-Connect does not work for C64P -- This is tracked by SDSSCM00011954.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31_01 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31.01 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.01 with directory bios_5_31_01.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.01) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.31 Release Notes

Last updated:  08 Aug 2006

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Check the following web site for updates: https://www-a.ti.com/downloads/sds_support/targetcontent/bios/index.html

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.31 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_31.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.31

• All ISA release which includes all changes in BIOS 5.30

• Maintenance release with defect fixes and minor enhancements.

• Minor documentation updates.

• New chip support

Device Support

Known Issues

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

    BCACHE_wb()/OMAP2430 Problem -- BCACHE_wb() and BCACHE_wbInv() implementation for the OMAP2430 does not contain extra logic to ensure that the data has reached the destination memory before the 'wait' returns.  The cache registers correctly indicate that the data has been written from the cache to memory, but there may be additional delay before the data reaches its final destination memory.  This may be a problem when this memory is accessed by another CPU or peripheral before the final write has completed.  The workaround is to do dummy read of the last word of the buffer passed to BCACHE_wb() since this read will not complete until the writeback has completed.  This is not a problem for Davinci, 6455 or TCI6482 implementation which contain extra logic to ensure that the 'wait' does not return until the destination memory has been completely updated.  This is tracked by SDSCM00003322.

    RTA/RTDX problem when load/run different programs -- After running RTA successfully on a DaVinci program, if another program is then loaded without restarting CCS 3.2 then RTA may not work sometimes.  This problem is intermittent.  If displays do not update, the workaround is to restart CCS before loading a new program.  This is tracked by SDSCM00003318.

    DSP/BIOS RTA plugins update very slowly via RTDX on DaVinci -- (CCS 3.2 issue) When RTA plugins are opened after a program is loaded and started. To work around this problem, open the DSP/BIOS RTA plugins before starting the program. This is tracked by SDSCM00002472

   Gconf uses wrong parameters when more than one pjt is opened and they share the same .tcf file -- When more than one CCS project (.pjt file) share the same .tcf file, and two or more of the projects are opened in CCS, opening a .tcf from one of the projects will launch GConf using the DspBiosBuilder builder parameters defined for the most recently opened project. This may result in incorrect base seed properties and import file paths in the .tcf file being edited. To workaround, do not share .tcf files between projects. This is tracked by SDSCM00003834

  BIOS RTA has problems reading data in stop mode for some 64x+ devices -- Currently, stop mode reads will only work for DaVinci. This is tracked by SDSCM00010400

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX error comes up on Debug -> Run when executing examples on 5912 via XDS 510 -- This is tracked by SDSSCM00005600.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

Validation Information

Codegen versions used in BIOS 5.31 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.31 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.31.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_31.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.31.00.01 with directory  bios_5_31_00_01) and the final release will be bios_5_31 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.31.01 with directory bios_5_31_01.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.31 with directory bios_5_31.  When referring to the release, the term bios "five dot thirty-one" generally refers to the baseline bios 5.31 and the patches (ex. 5.31.01) and point releases (ex. 5.32) that comprise the compatible group.

DSP/BIOS v5.30 Release Notes

Last updated: 14 Jun 2006

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.30 is an All ISA release and can be used with CCS 3.2, CCS 3.3 or later. This will be installed in <installdir>/bios_5_30.

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.30

• All ISA release which includes all changes in BIOS 5.30 and BIOS 5.20.05

• RTDX examples have been updated to support current platforms and moved to the BIOS directory structure. The RTDX and the examples are provided with the BIOS release package.

• Maintenance release with defect fixes and minor enhancements.

• Minor documentation updates.

• New Stairstep BIOS example added.

Known Issues

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

    RTA/RTDX problems on simulators -- Real time analysis (RTA) and RTDX are not reliable on the 64x+ simulators.  For some applications, a few LOG entries are not displayed and other applications have no LOG output at all.  This problem appears to be unique to the simulator since the same examples run fine on the sdp2430 or evm6446 boards.  These issues are tracked by SDSCM00003849, SDSCM00003850, SDSCM00003851 and SDSCM00006695.

    BCACHE_wb()/OMAP2430 Problem -- BCACHE_wb() and BCACHE_wbInv() implementation for the OMAP2430 does not contain extra logic to ensure that the data has reached the destination memory before the 'wait' returns.  The cache registers correctly indicate that the data has been written from the cache to memory, but there may be additional delay before the data reaches its final destination memory.  This may be a problem when this memory is accessed by another CPU or peripheral before the final write has completed.  The workaround is to do dummy read of the last word of the buffer passed to BCACHE_wb() since this read will not complete until the writeback has completed.  This is not a problem for Davinci, 6455 or TCI6482 implementation which contain extra logic to ensure that the 'wait' does not return until the destination memory has been completely updated.  This is tracked by SDSCM00003322.

    RTA/RTDX problem when load/run different programs -- After running RTA successfully on a DaVinci program, if another program is then loaded without restarting CCS 3.2 then RTA may not work sometimes.  This problem is intermittent.  If displays do not update, the workaround is to restart CCS before loading a new program.  This is tracked by SDSCM00003318.

    DSP/BIOS RTA plugins update very slowly via RTDX on DaVinci -- When RTA plugins are opened after a program is loaded and started. To work around this problem, open the DSP/BIOS RTA plugins before starting the program. This is tracked by SDSCM00002472

    DSP/BIOS examples that are using RTA halt when run every other time on DSK5510/DSK5509A via XDS560. This is tracked by SDSCM00005820.

    CCS window closes on refreshing KOV Window when it receives illegal values -- KOV will crash if Module Objects have illegal values. For e.g if a dynamic task has a bad name, KOV will try to print the illegal name and crash. This is tracked by SDSCM00006694.   

    KOV window shows wrong names for dynamic objects -- This is tracked by SDSCM00007151.

    KOV displays wrong names for memory sections -- This is tracked by SDSCM00004917.

    Incorrect platform name in Tconf User's Guide in "Create New Platform" section -- The spru0007h.pdf document contains the correct instructions for creating a new platform using the Tconf's User's Guide, the help files were not updated to reflect the same naming convention. This is tracked by SDSCM00003471.

    RTDX error comes up on Debug -> Run when executing examples on 5912 via XDS 510 -- This is tracked by SDSSCM00005600.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.

The following defects were fixed in 5.20.02 but were not mentioned in the release notes for that version.

Validation Information

Codegen versions used in BIOS 5.30 product validation. See kernel release notes for the compiler versions used to build the target content.

Deprecation Notice

Deprecated DSP/BIOS APIs: Some DSP/BIOS APIs are being deprecated and will no longer be supported in the next major release of DSP/BIOS.

These APIs are still supported in DSP/BIOS 5.30 and will be supported in any patch releases or minor enhancements to DSP/BIOS 5.30.

The deprecated APIs are:

All APIs associated with the DEV driver interface. Developers are recommended to use the IOM driver interface.

DEV_createDevice

DEV_deleteDevice

DEV_match

Dxx_close

Dxx_ctrl

Dxx_idle

Dxx_init

Dxx_issue

Dxx_open

Dxx_ready

Dxx_reclaim

DGN Driver

DGS Driver

DHL Driver

All APIs associated with the PIP module. Developers are recommended to use the SIO module.

PIP_alloc

PIP_free

PIP_get

PIP_getReaderAddr

PIP_getReaderNumFrames

PIP_getReaderSize

PIP_getWriterAddr

PIP_getWriterNumFrames

PIP_getWriterSize

PIP_peek

PIP_put                                                                                        

PIP_reset

PIP_setWriterSize

Note on BIOS versioning:    The BIOS product version follows a version format, M.mm.pp.b , where M is single digit Major version, mm is 2 digit minor version, pp is 2 digit patch, and b is an unrestricted set of digits used as incrementing build counter. 

To support multiple installations of different bios versions, the product version is encoded in the top level directory, ex. bios_5_30.   Interim deliveries of major baseline bios releases, such as a beta or early adopter (EA), will have a full qualified version (ex. 5.30.00.01 with directory  bios_5_30_00_01) and the final release will be bios_5_30 following the convention of stripping the patch and build counter for final release.  

Subsequent releases of patch upgrades will be identified by the patch number, ex. bios 5.30.01 with directory bios_5_30_01.  

Point releases where new features such as additional device support are released same as major baselines, i.e., with patch counter of zero and removed from directory qualifier, ex. 5.30 with directory bios_5_30.  When referring to the release, the term bios "five dot thirty" generally refers to the baseline bios 5.30 and the patches (ex. 5.30.01) and point releases (ex. 5.31) that comprise the compatible group.

DSP/BIOS v5.21 Release Notes

Last updated: 05 January 2006

The DSP/BIOS distribution is composed of sub-component packages each containing specific release notes.   This top level release note covers general product level issues related to installation and getting started and is divided into four sections, "General Info", "Known Issues", "Fixed In This Release", and "Validation Info".   

Release Notes for each separately versioned sub-component package:

Sub-components applicable to Windows installations used with Code Composer Studio:

General Information

DSP/BIOS 5.21 is a 6x-only release and can only be used with CCS 3.2 or later.   Documentation for other devices is provided with this release, but no software is provided to support anything but 6x devices.  This will be installed in <installdir>/bios_5_21_pp_b (pp_b are optional and used for patch and build counter).

It is strongly recommended to follow the instructions in the DSP/BIOS Setup Guide, also available from the documentation index for information on updating from previous BIOS releases and instructions on how to use the BIOS Selector in the Component Manager of Code Composer Studio.

What's New in BIOS 5.21

• Cache APIs (BCACHE) for 64x+ devices.  Documentation can be found here.

• Memory Protection APIs (MPC) and examples for 64x+ devices.  Documentation can be found here.

• Event Combiner APIs (ECM) for 64x+ devices.  Documentation can be found here.

• HWI_eventMap() API was added for 64x+ devices.  Documentation can be found here.

• Memory Protection Examples.  See ti/bios/examples/advanced/mpc_*.

• Examples for OMAP2430 SDP board (sdp2430).

• Examples for 6455 DSK board (dsk6455).

• Platform files for dsk6455, dskTCI6482, sdp2430, evmDM420 and evmDM6446.

Known Issues

   evmDavinci platform replaced by evmDM6446 and evmDM420 -- The evmDavinci platform support files and examples have been removed from this release.  This has been replaced by evmDM420 and evmDM6446 platform support.  Examples for the evmDM6446 board are provided with this release.  If you are using evmDavinci platform from 5.20, you can change your .tcf file(s) to use 'utils.loadPlatform("ti.platforms.evmDM6446")' or 'utils.loadPlatform("ti.platforms.evmDM420")'.   The following changes were also made to these platforms: (1) the 'DDR' memory segment from evmDavinci was renamed to 'DDR2', and (2) the params.clockRate was changed from 594 to 486 to match the default CPU rate for the EVM boards (set via Linux UBOOT and/or Arm .gel file).

    Memory heap issue when updating  existing configuration files -- Prior versions of the configuration tool allowed for an inconsistent memory heap configuration.   The tool allowed users to enable heaps when no heaps were actually configured and the default for bios.MEM.MALLOCSEG and bios.MEM.SEGZERO were still set to 'MEM_NULL'.  This was causing problems in applications since malloc() and MEM_alloc() were failing even when user thought they had configured BIOS for dynamic memory allocation.  The configuration tool is now checking to make sure that configurations that have heaps also have bios.MEM.MALLOCSEG and bios.MEM.SEGZERO set to a valid heap.  Update from existing projects might yield an error message.  The work around is to either remove the 'bios.enableMemoryHeaps(prog);' line from your configuration, or to add a heap and set bios.MEM.MALLOCSEG and bios.MEM.SEGZERO accordingly.  See the ti/bios/examples/common/evmDM6446_common.tci file (or others) for an example of how to do this.

    RTA/RTDX problems on simulators -- Real time analysis (RTA) and RTDX are not reliable on the 64x+ simulators.  For some applications, a few LOG entries are not displayed and other applications have no LOG output at all.  This problem appears to be unique to the simulator since the same examples run fine on the sdp2430 or evm6446 boards.  These issues are tracked by SDSsq44620, SDSsq44630 and SDSsq44631.

    BCACHE_wb()/OMAP2430 Problem -- BCACHE_wb() and BCACHE_wbInv() implementation for the OMAP2430 does not contain extra logic to ensure that the data has reached the destination memory before the 'wait' returns.  The cache registers correctly indicate that the data has been written from the cache to memory, but there may be additional delay before the data reaches its final destination memory.  This may be a problem when this memory is accessed by another CPU or peripheral before the final write has completed.  The workaround is to do dummy read of the last word of the buffer passed to BCACHE_wb() since this read will not complete until the writeback has completed.  This is not a problem for Davinci, 6455 or TCI6482 implementation which contain extra logic to ensure that the 'wait' does not return until the destination memory has been completely updated.  This is tracked by SDSCM00003322.

    CACHE initialization is too late if L1D is used for initialized data -- DSP/BIOS initializes the cache within BIOS_init() which is called after .cinit processing.  The .cinit processing occurs in the function _auto_init(), and the DSP/BIOS cache configuration happens after the processing of .cinit records.  Since some .cinit records initialize data that has possibly been placed in L1D RAM, if that RAM is still configured as cache, L1D cache activity related to L2 or external memory accesses can potentially step on the initialization into L1D.  This problem occurs since the device boots with L1D and L1P in '32K mode' (L2 is '0K' at reset).  To workaround this, either make sure you don't have any initialized data in L1D, or set L1PCFG and L1DCFG (0x01840020 and 0x01840040) to '0' in a custom boot.c file that you link with your application.  This disables the L1P and L1D caches during boot.  See the ti/bios/examples/advanced/mpc*/boot.c for an example of the workaround.  This is tracked by SDSCM00003329.

    PATH inconsistent with CCS 3.2 beta -- The CCS 3.2 beta2 installation sets the "PATH" environment variable to point to the 'bios_5_20_03' directory since CCS 3.2 beta 2 contains BIOS 5.20.03.  This can cause problems if you are doing Windows builds from the command line.  This will not be a problem if you are doing builds using CCS .pjt files.  Make sure that your PATH and BIOS_INSTALL_DIR variables are both pointing to bios_5_21 (or whatever DSP/BIOS release you want to work with).  This is tracked by SDSCM00003316.

    RTA/RTDX problem when load/run different programs -- After running RTA successfully on a DaVinci program, if another program is then loaded without restarting CCS 3.2 then RTA may not work sometimes.  This problem is intermittent.  If displays do not update, the workaround is to restart CCS before loading a new program.  This is tracked by SDSCM00003318.

    MPC examples don't work on sdp2430 board -- The MPC examples don't work correctly for the sdp2430 board.  This is tracked by SDSCM00003359.

Fixed In This Release

The following bugs and enhancements have been fixed in this release.  These are also listed in the sub-component release notes, but provided here for convenience.