This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ROM contents of C6727



Hi, I am trying to use the ROM version of DSPBIOS on the C6727.  I thought that version 5.41.0x was backward compatible with 5.20.0x, however I cannot configure this DSPBIOS to link with the ROM.  Is v5.20.0x my only option?

"C:/Program Files/Texas Instruments/xdctools_3_16_02_32/tconf" -b -Dconfig.importPath="C:/Program Files/Texas Instruments/bios_5_41_02_14/packages;" "../UhpiTest.tcf" ("Error: ", self.name, $1) ==> "This BIOS version does not support linking with ROM." js: "C:/Plt/BroadReach/SbSat/Software/Dsp/CcsWorkspace/UhpiTest/UhpiTest.tcf", line 8: This BIOS version does not support linking with ROM. C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [UhpiTestcfg.cmd] Error 1

  • Yes.   5.20.0x is your only option.

    5.41 is not compatible with the 6727 ROM.

    Regards,
    -Karl-

  • On the DSPBIOS download page for 5.x versions there is a warning beside all releases after 5.2x indicate that it is not compatible with C6727 ROM.  However, this warning is not displayed beside 5.4x.  Should there be a similar warning in the description for this release?

    http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/bios/index.html

  • Also, I am having trouble working with DSPBIOS 5.2x in CCS4.  I gather from reading some other posts that others have had issues as well.  If I must use 5.2x does this also mean I have to use CCS3.3? (I really hope not).  Here is the first compile problem I encounter with BIOS 5.2x in CCS4.

    "TestBios542cfg.h62", WARNING! at line 120: [E0300] Cannot define an absolute
                                                        symbol with a
                                                        floating-point value;
                                                        symbol's value will be
                                                        encoded in floating-point
                                                        format

  • Unfortunately, CCSv4 requires BIOS 5.41or later.  Changes to tools and such were needed to integrate into CCSv4.

    You might be able to build your code outside CCSv4 (via command line, CCSv3 or via 'timake' utility which builds CCSv3 .pjt files) and debug the .out file with CCSv4.

    The error you get above looks like an assembler error.  CCSv4 has much newer codegen (6.1.x).   We made updates along the way since 5.2x for new codegen.  You might be able to copy the codegen from CCSv3 into your CCSv4 environ to get this to work, but this is all getting a bit dicey.  You'll probably bump up against another issue and this hasn't been tested or supported from our side.

    Regards,
    -Karl-

  • I am having exactly the same problem using CCS3.3.82.13, CGT6.1.18, and DSPBIOS 5.20.05.34

    This warning started after upgrading the CGT to 6.1.18 from 6.0.8.

    At:  http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/bios/bios_5_20/index.html

    The overview for 5.20 states:

    "... Going forward, it is intended that customers should typically not be required to upgrade DSP/BIOS when they upgrade CCS."

    According to the release documentation this is the only version compatible with ROM.

    All other versions state "Not compatible with C672x ROM image."

    Is this a warning I have to live with?  Are there other issues I'm not aware of?

  • Paul --

    Do you have strong reason to move to 6.1.18 codegen?   If not, I would recommend using 6.0.x.   The compiler team continues to make maintenance releases of 6.0.x.

    https://www-a.ti.com/downloads/sds_support/CodeGenerationTools.htm

    Regards,
    -Karl-

  • No strong reason, I assumed it contained better optimizations.

    Will try the latest 6.0.x

    Thanks,

    paul

  • Karl,

    At the link you gave there is no indication that BIOS 5.20 is NOT compatible with all versions of the CGT (6.0.x, 6.1.x, or 7.0.x) for C6000.

    Are there undocumented dependencies that exist for the C6000 family?

    Thanks,

    Paul