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.

Flashing .ROM file wipes out bootloader after conversion to CCS5

Other Parts Discussed in Thread: TMS320F2812

I converted a project from CCS3.1 to CCS5. The new CCS5 version of the project will build successfully and create an .out file which is then converted to a .rom. When I flash the .rom using our flash utility it wipes out the bootloader on the TMS320F2812. (Flashing the .rom generated via CCS3.1 works fine). Is there something I might have missed in the conversion from CCS 3.1 to 5?

  • I would start by comparing the link .map files generated by the CCS 3.1 build and CCSv5 build to ensure that code and data sections are being allocated in a similar fashion in both versions.
  • Thanks.
    codestart has an origin of 003d8004 with length 2 in both files.
    .data has an origin of 003d8006 with length 0 in both files.

    The ccs 5 map has a .vers w/ origin 00000000 (in section allocation map) that the ccs3.1 map does not have. Could this cause the issue? Why would it be in one version and not the other?
  • Robert Quinn said:
    The ccs 5 map has a .vers w/ origin 00000000 (in section allocation map) that the ccs3.1 map does not have. Could this cause the issue? Why would it be in one version and not the other?

    The .vers section is created by BIOS but it is marked as a COPY section, so does not need to get loaded to the target. This section is only used to gather version information from the COFF file. 

    Is it possible that your flash loader may not be handling the COPY sections correctly? More info on COPY section is in this page:
    http://processors.wiki.ti.com/index.php/Linker_Special_Section_Types