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.

Errors compiling when using BIOS 5.20.05 but not 5.41.13.42

I am porting a project from Code Composer 3.3 to 5.1.  I have the project successfully building with BIOS 5.41, but I would like to use BIOS 5.20 since that is what I was using before.  When I compile I get the following errors:

#10010 errors encountered during linking; "C:/NG EM Controller Firmware 5900 EM main    C/C++ Problem
<a href="file:/C:/ti/ccsv5/tools/compiler/dmed/HTML/10234.html">#10234-D</a>  unresolved symbols remain 5900 EM main    C/C++ Problem
unresolved symbol _HWI_D_inhwi, first referenced in C:\NG 5900 EM main    C/C++ Problem
unresolved symbol _SWI_D_inswi, first referenced in C:\NG 5900 EM main    C/C++ Problem

 

Any idea what I can change to get it to work with the older BIOS version?

 

Thanks

  • Hi David,

    A couple initial things to check here.

    Does CCS recognize both of the BIOS versions?  Ie are both selectable when working with projects?  Do you see both versions if you go to Window->Preferences->Code COmposer Studio->RTSC->PRoducts?

    This error can be caused by a problem with the include paths and variables.  Have a look at this wiki.

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Please keep us informed.

    Best Regards,
    Lisa

  • Yes, both versions are recognized.  I will look through the wiki and see if it helps.


    Thanks

  • Hi David,

    just thought I would check for updates to your enquiry.   Was the wiki useful for you.

    Best Regards,
    Lisa

  • No.  I have been unable to get BIOS 5.20 to build successfully. I can build fine with BIOS 5.41, but I really need to use BIOS 5.20.  I read that BIOS 5.20 is not supported in CCS5, which I don't understand why, so I am not sure I will be able to get it to work.

  • Hi David,

    it seems perhaps there is an incompatibility there.  I am moving this to the BIOS forum for you as they may be able to confirm better/have more experience.

    Best Regards,
    Lisa

  • Hi David,

    I'm wondering if you might be running into a compiler compatibility issue.

    David Sabol said:
    but I would like to use BIOS 5.20 since that is what I was using before

    I'm assuming that your app build successfully in CCS3 in this case.  Can you check the versions of Code Gen tools used to build with BIOS 5.20?  Also, the version of XDC tools?

    Once you have that information, let's compare it against the versions you are building against now, in CCSv5.

    If they are different, can you try pointing your CCSv5 project (that's building for BIOS 5.20) to the same version of Code Gen tools that worked for you in CCSv3?

    Steve

  • Hi Steve,

    Yes, I can build successfully with BIOS 5.20 on CCS 3.

    I was able to get some of the information, but could not find all of the pieces.  If you can point me in their direction that would be great.

    Code Gen:

    CCS 5 - 7.3.9

    CCS 3 - 6.1.12         

    XDC Tools:  

    CCS 5 - I have v3.22.4.46 and 3.23.3.53 installed, but neither is selected under preferences->RTSC

    CCS 3 - Cannot find

     

    I have changed to use CGT 6.1.12.  After it updated, I get many errors when I build.  I am working through them now, however I am not having much success.

    Thanks for your help,

    David

  • David,

    David Sabol said:
    CCS 5 - I have v3.22.4.46 and 3.23.3.53 installed, but neither is selected under preferences->RTSC

    You will need to select an XDC version.  Just to be sure, you should do this in your project's build settings (right click on project, select show build settings)

    David Sabol said:
    I have changed to use CGT 6.1.12.  After it updated, I get many errors when I build.  I am working through them now, however I am not having much success.

    These look like path related errors in the project settings of your current project.  Can you check those dependent project paths?  If the paths are using some sort of variable then that variable may not be defined for whatever reason.  A quick way to check is to replace the variable or relative path that's being used to be the full path to the dependent project.

    Steve