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.

TMS320F2812: Migrating a CCS 3.3 project into 12

Part Number: TMS320F2812

I am migrating a CCS 3.3 project that needs work done into CCS 12 and am running into an issue with the DSP/Bios package. The project used version 5.33.04 and I replaced the internal files of the newer built in version of DSP/Bios and it seemed to get rid of package errors. Now I am getting errors from the generated .cmd files which seems to be created from a .tcf file. The errors I am getting are all like this:

"./axecfg.cmd", line 188: error #10104: undefined symbol "PIE_INT9_3" used in expression

I think this is caused by some kind of change between the change from DSP/Bios versions and how CCS 12 handles the older DSP/Bios version as the project works in CCS 3.3 as is.

  • What version of the C2000 compiler are you using? What is the newer version of DSP/BIOS that you're using? Can you show me a few of the lines in axecfg.cmd that are causing errors?

    Looking at the 5.42.02.10 release notes (the most recent DSP/BIOS release from 2016), it appears to have been tested with CCS v5.1 and C28x codegen tools 5.2.1. Since we haven't been doing regular maintenance releases of it, it's quite possible it's just not compatible with CCS v12.

    Whitney

  • The compiler is TI v22.6.0.LTS and the DSP/BIOS was modified by removing the internal files and replacing it with what was used for the original build of the project which is 5.33.04. The project would not attempt to build without using the original DSP/BIOS version.

    The lines that are creating the errors are:

    _HWI_USER9 = HWI_USER9;
    _HWI_USER10 = HWI_USER10;
    _HWI_USER11 = HWI_USER11;
    _HWI_USER12 = HWI_USER12;
    _PIE_INT1_1 = PIE_INT1_1;
    _PIE_INT1_2 = PIE_INT1_2;

    These seem to be generated by a config file for the DSP/BIOS for hardware interrupts.

  • I'm not sure what you mean by "replacing internal files"--can you explain?

    DSP/BIOS is old enough that we aren't able to provide much support for it. At this point, we're not even recommending the newer SYS/BIOS for new projects and instead recommend folks use FreeRTOS. I'll try to help provide some ideas, but I'm not sure how much help I can be.

    Whitney

  • I could not get CCS 12 to recognize the older version of the DSP/BIOS (5.33.04) but it could detect the folder for version 5.42.02. So I deleted the files in version 5.42.02 and replaced it with what was in 5.33.04 and that modification allowed it to start building until it hit the errors I mentioned in the original post.

    The project is already built with DSP/BIOS with everything set up. We need to support the product for several more years so I would like to have it in a working state. Is there any resources for changing the DSP/BIOS such as modifying the configurations files and such for upgrading to something newer?

    Thank you,

    Steven

  • I could not get CCS 12 to recognize the older version of the DSP/BIOS (5.33.04) but it could detect the folder for version 5.42.02. So I deleted the files in version 5.42.02 and replaced it with what was in 5.33.04 and that modification allowed it to start building until it hit the errors I mentioned in the original post.

    DSP/BIOS 5.3x was simply never officially supported by any instance of CCS Eclipse. DSP/BIOS 5.4x was created for integration with CCS Eclipse. DSP/BIOS 5.4x is supposed to be binary compatible with DSP/BIOS 5.3x and there should not be much different between the two versions as far as I know.

    Please note that DSP/BIOS 5.x is not supported any more. The team that had developed it is no longer. Expertise outside of that team is limited. If you have a working environment with CCS 3.3 and DSP/BIOS 5.3x, you may want to stick with that setup. CCS 3.3 is the last version of CCS to support DSP/BIOS 5.3x