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.

Compiler/TMS320C5504: Legacy Project Does Not Function With Newer Compiler

Part Number: TMS320C5504
Other Parts Discussed in Thread: OMAP5912

Tool/software: TI C/C++ Compiler

The project generates a binary that is placed into the DSP on an OMAP5912. This project was previously built on Code Composer v3.3 and I am attempting to update the project to be built on a more modern version. The project builds with only a handful of warnings, but the binary does not function. I have tried finding a download for the previous version of the tools, but they are obsolete. The release notes for even 4.0.0 are removed, so I cannot find documentation for the changes.

Are there any resources or perhaps a download for the older tool that I can be directed to?

Previous C55x tools were version 3.3.2, the newer tools are version 4.4.1.

  • Jake Thiem said:
    Previous C55x tools were version 3.3.2

    Unfortunately, those tools are not available for public download.

    Due in part to working from home, my usual access to older compilers is not available.  It will take me some time to work through that.  Please be patient.

    Thanks and regards,

    -George

  • The older compiler was supplied through other channels.  -George

  • Hi George,

    Thanks for the tools. How do we install the tools from a local source in code composer?

    If I add a local repository in the install dialog and point it to the directory where the tools are installed it doesn't see them.

    Can you provide instructions?

    Thanks

  • Please see the article Compiler Installation and Selection.

    Thanks and regards,

    -George

  • George,

    Thanks for that, I now have code composer recognizing the 3.3.2 compiler version. I also have it selected in the project properties.

    I've imported the project using the "Import Legacy CCSv3.3 Projects..." wizard. When I build I get the following error:

    "Product XDAIS v1.0.0 is not currently installed and no compatible version is available. Please install this product or a compatible version."

    XDAIS doesn't appear in a search for software within Code Composer's software installation tool. I found the following page http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/index.html but it doesn't contain version 1.0.0. 

    Is this something we need to obtain from you directly too?

  • I have notified the TI-RTOS experts about this thread.

    Thanks and regards,

    -George

  • Ryan,

    I doubt it is really looking fro version 1.0.0. What version was used in the older setup? What version of DSP/BIOS are you using in the older setup?

    Todd

  • Hi Todd,

    Here are the old version details.

  • Hi Ryan,

    I think the XDAIS 6.24.01.06 release should work for you. What version of XDCtools do you have?

    Todd

  • Hi Todd,

    I appear to be getting somewhere, the project is mostly building now but complains at the end:

    'hex55' is not recognized as an internal or external command,
    operable program or batch file.

    I now have the following setup with regard to XDAIS

    To answer your question, there are a few versions of XDCTools installed:

    I'm still not getting the a00 output file, I'm guessing the hex55 step is what generates this?

  • hex55 seems to be included as one of the standard c55x codegen utility tools:

    Directory of tools\compiler\c5500_4.4.1\bin

    09/30/2019 06:20 PM <DIR> .
    09/30/2019 06:20 PM <DIR> ..
    01/23/2014 06:11 PM 654,336 abs55.exe
    01/23/2014 06:11 PM 2,008,064 acp55.exe
    01/23/2014 06:11 PM 600,576 ar55.exe
    01/23/2014 06:11 PM 1,924,096 asm55.exe
    01/23/2014 06:11 PM 2,011,648 asm55p.exe
    01/23/2014 06:12 PM 106,496 bti5500.dll
    01/23/2014 06:11 PM 2,777,088 cg55.exe
    01/23/2014 06:11 PM 2,681,856 cg55p.exe
    01/23/2014 06:11 PM 209,408 ci55.exe
    01/23/2014 06:11 PM 1,088,000 cl55.exe
    01/23/2014 06:11 PM 73,728 clist55.exe
    01/23/2014 06:11 PM 88,576 dem55.exe
    01/23/2014 06:11 PM 882,176 dis55.exe
    01/23/2014 06:11 PM 649,728 embed55.exe
    01/23/2014 06:11 PM 871,424 hex55.exe
    01/23/2014 06:11 PM 762,880 ilk55.exe
    01/23/2014 06:11 PM 732,672 libinfo55.exe
    01/23/2014 06:11 PM 1,897,472 lnk55.exe
    01/23/2014 06:11 PM 1,153,536 masm55.exe
    01/23/2014 06:11 PM 93,184 mk55.exe
    01/23/2014 06:11 PM 672,256 nm55.exe
    01/23/2014 06:11 PM 872,960 ofd55.exe
    01/23/2014 06:11 PM 2,445,824 opt55.exe
    01/23/2014 06:11 PM 651,264 strip55.exe
    01/23/2014 06:11 PM 660,480 xref55.exe
    25 File(s) 26,569,728 bytes

    Is hex55.exe missing from your C55 codegen tools bin directory?

  • Hi Alan,

    I'm not using 4.4.1 but instead 3.3.2. It does appear to be present on the file system. 

    Is there another place, other than what is pictured below, I need to configure code composer to look specifically for hex55?

  • Does the "C5500 Hex Utility" sub-panel under 'Build' allow you to input the path to the utilities?

  • Alan,

    Yes it does allow it, however it doesn't appear to have any effect on the outcome. Initially is was disabled and I had to check the box to enable it.

    After checking the box to enable it appeared like so:

    I then manually entered the path:

    I tried it both with and without the .exe extension. Still get the same message during the build output stating hex55 cannot be found in all cases.

  • You may need quotation marks around the path to hex55.exe to deal with the embedded spaces.

    Have you tried unchecking the "Enable C5500 Hex Utility" option?

    I think the hex file is only necessary when you want the ARM processor to load the DSP image.

    Until you're ready for that step, I think you can simply load the .out file into the DSP using the CCS debugger.

  • Alan,

    I tried adding the double quotes but that also didn't make a difference.

    Yes the initial build after the import of the v3.3 project had the "Enable C5500 Hex Utility" option unchecked. This is when I first noticed the hex55 error.

    Loading the DSP from the ARM is precisely what our product does and what we are trying to accomplish.

    The end goal here is to generate the .a00 file from a modern machine/OS so we no longer have to keep an old XP machine around.

    I'm using Windows 10 to start with so I can use the "Import Legacy CCSv3.3 Projects" tool to convert it to a CCS/eclipse project. Once I get that environment to produce a working .a00 file I intend to move it to Debian 10.

    Historically we have used the XDS510 emulator which I understand no longer functions with the latest versions of CCS. This is another reason why we need the .a00 file.

  • Have you tried creating and initializing the original "CG_TOOL_HEX" Windows environment variable?

    Coercing CCS into finding tools isn't my expertise so I'm simply guessing at this point.

    Alan

  • Alan,

    So in CCS v3.3, in the build options for the projects there is a section called "Final build steps". The project has a "Build Command" defined:

    hex55 -a -romwidth 32 %{Proj_dir}\Debug\dsp_mai.out

    It appears the import of the legacy project generates a batch file that contains this command. This is where my error is coming from.

    Here is the line in the batch file:
    echo hex55 -a -romwidth 32 %PROJECT_ROOT%\Debug\dsp_mai.out >> temp_postBuildStep_Debug.bat

    If I change it to:
    echo "C:/Program Files (x86)/Texas Instruments/C5500 Code Generation Tools 3.3.2/bin/hex55" -a -romwidth 32 %PROJECT_ROOT%/../Debug/dsp_mai.out >> temp_postBuildStep_Debug.bat

    then I get a .a00 file.

    What is the proper way to make CCS do this?

  • Ryan,

    There are a couple of ways of invoking the hex55 utility in CCS. 

    1) Under Project Properties->Build->Steps tab, add the hex55 command to the Post-build steps box. In this case the C5500 Hex Utility sub-panel under Build does not need to be enabled. The command as entered in the Post-build step will run after the main project build step.

    OR

    2) Enable the C5500 Hex Utility sub-panel under Build. Then add the necessary options (-a and -romwidth) using the GUI. In this case, make sure that there is no command in the Post-build Steps box.

    Let us know if this helps. If the error persists, please save the complete build log to a text file and attach it here.