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.

Failed installation of BIOS components of CCS 5.4

Other Parts Discussed in Thread: SYSBIOS, CONTROLSUITE, TMS320F28335

I was able to install CCS 5 yesterday and realized that I require the BIOS components today (F2_BIOScfg.cmd is not being generated) and tried to add them but the install fails.  attached is the install log folder that was requested in the Invalid Install window.  Any help would be appreciated.

60556FE5-C1A1-4061-8DF8-FFB8393BAE2D.zip
  • Hi Dayton,

    This is failing because another system process is blocking access to files being installed. The usual culprit is anti-virus software, like TrendMicro, but anything that scans new files being placed on the system could also do it.  Do you have any desktop search software running perhaps? Which antivirus software are you using? I'm wondering if disabling it from the UI doesn't disable its realtime file protection aspects.

    FYI, the symptom I'm looking at is the "CreateFile() error 32 when trying set file time" message at the bottom of the log file

    Once we've figured out what the reason for the failure is, we can try and restart your Bios update.

    Danish

  • Hi Dayton,

    could you please confirm a couple things

    - how did you try to add bios support?  Normally if you already have ccs you can add it stand alone

    - did you try multiple times to install over an exisiting installation?  Your logs show 3 ccs installs of the same version and this might indicate the installer could get confused and enter "rerun" mode which is not good

    Best Regards,
    Lisa

  • Hi Danish,

    I had some issues installing CCS5.4 that were resolved when I disabled the shields running in webroot SecureAnywhere (our anti-virus SW).  When I disabled the shields, I was able to successfully install CCS5.4.  Now that I am adding  the BIOS feature it is not working, even when I have the shields disabled...  Is there something else that I need to disable to complete this install?

    Is there a download that I can get to install offline that would bypass this feature of anti-virus sw?

  • I tried installing CCS 2x and failed before I had anti-virus shields disabled then the installation was successful.  The only place I have seen the BIOS installation feature was during the original install so I tried running this again and pointed to the current installation of CCS.  The first attempt failed as anti-virus was running (I assume).  I had the shields disabled and tried again but got the same result.

  • Hi Dayton,

    you can download bios from these pages

    http://processors.wiki.ti.com/index.php/Category:SYSBIOS

    You will likely still need it to be brought into ccs but it cetainly worth trying to add bios support by this method.  Note I would install to c:/ti

    Please keep us informed.

    Best Regards,
    Lisa

  • I downloaded and installed bios_setupwin32_6_35_01_29.exe  (SYS/BIOS 6.x).  I still get the same error when I try to build. 

    gmake[1]: *** No rule to make target `U:/MPD/Projects/SYS/03_M1020/02_SMC_LAT_TEST/F2_BIOScfg.cmd', needed by `U:/MPD/Projects/SYS/03_M1020/02_SMC_LAT_TEST/firmware_project/../02_SMC_Dev/F2.out'.
    gmake[1]: Target `main-build' not remade because of errors.
    gmake: *** [all] Error 2

    When I used CCS 3.x  this F2_BIOScfg.cmd was autogenerated.  If I try to include this file in the new project it throws a lot of errors that leave me clueless so I don't think this was the right approach.  What do I need to do to autogenerate this file or get past this error?  FYI, I am building for a F28335PGFA processor and have a XDS510 USB emulator.

  • Hi Dayton,

    could you please try a built in example?  There were many changes to bios since that very old ccs version and I would like to verify whether this is a migration item or an actual bios problem.

    Best Regards,

    LIsa

  • I downloaded the controlSUITE yesterday but am not sure what device I should be looking at for examples for my processor.  could you direct me to where I can find examples relevant to my processor?

    I randomly grabbed Delfino C2834x CPU Timer and built it and it creates an output file.

  • Hi Dayton,

    the new project wizard has build in bios examples.

    Are you able to build and run one of those without issue?

    See the screen capture ... I could not expand it far enough but you could for example try the hello example under generic examples.

    Best Regards,
    Lisa

  • for device TMS320F28335 I selected SYS/BIOS->SYS/BIOS->28x examples->Swi Example

    This built and generated a *.out file.

  • Hi Dayton,

    so I suspect the problem is more the migration from the old version.

    How did you do the migration?  Have you looked at the same bios wiki I sent for migration instructions?

    Best Regards,
    Lisa

  • I must have missed your post regarding the bios wiki and migration instructions.  Did you send a link?  I don't see it in the this thread. 

    I migrated the project by going to Project->Import Legacy 3.3 Project

  • Hi Dayton,

    I have sent it again here.  With bios projects you both need to import and to migrate your project (as appropriate) to the new bios version.

    http://processors.wiki.ti.com/index.php/Category:SYSBIOS

    Best Regards,
    Lisa

  • Oh I thought that was just a download link...  I see instructions for migrating ccs 4 projects but don't see any references to CCS 2 or CCS 3 projects (yes we are still using CCS 2 as well)

  • Hi Dayton,

    I'm trying to follow this thread so bear with me here... are you trying to migrate some old CCSv3 project using BIOS5 to CCSv5 and BIOS6? A migration from BIOS 5 -> 6 is not trivial. Note that CCSv5 also supports BIOS 5 (though you need 5.4 to get kernal visibility).

    ki

  • My primary focus is fixing a problem that keeps surfacing where when I define an extra variable the system never enters main ().  This behavior is rather inconsistent.  Sometimes it looks like there is not enough memory, but then I define an array of u16's with a thousand elements and it makes it into main ().  Sometimes the exact same build that didn't work one night works the next morning.  I have probably wasted more than a months worth of time trying to resolve issues like this in the past and figured it was worth trying the latest tools to see if that remedy the situation.

    That said, I'm trying to move one of our projects (CCSv3 and ??BIOS) over to CCS5.  Ideally I would like to move away from using a BIOS all together, but I don't think we have the time to make that change atm.

  • Well, it is good that you wish to update the tools. However I recommend sticking to BIOS 5 (assuming you are using BIOS 5 in CCSv3) instead of trying to play with BIOS 6. CCSv5 comes with BIOS 5.4. It is a minor version number difference than the one that comes with CCSv3.3 but the impact should be minimal. You should be able to import your CCSv3 project and tell it to use BIOS 5.

  • How do I tell it to use BIOS5?  Do I need to install DSP/BIOS 5.x?  I am downloading 5.4.00.07 windows installer now...what do I do after installing?

  • The CCSv5 installer comes bundled with both BIOS 5 and 6. But if you did a custom install and did not enable the option to install BIOS, it would not be available. You can re-run the CCSv5 installer and install BIOS 5 or you can get the standalone version, install it and then point CCS to it via Windows -> Preferences -> Code Composer Studio -> RTSC

  • I have installed BIOS 5.42.0.07 and have done the CCS->Windows->Preferences->CCS->RTC and checked 5.4.0.07.  When I try to rebuild, I get the same error. 

    gmake[1]: *** No rule to make target `U:/MPD/Projects/SYS/03_M1020/02_SMC_LAT_TEST/F2_BIOScfg.cmd', needed by `U:/MPD/Projects/SYS/03_M1020/02_SMC_LAT_TEST/firmware_project/../02_SMC_Dev/F2.out'.
    gmake[1]: Target `main-build' not remade because of errors.
    gmake: *** [all] Error 2

    How do I migrate the bios from 3.3 to CCS 5? 

  • Dayton Simmons said:
    I have installed BIOS 5.42.0.07 and have done the CCS->Windows->Preferences->CCS->RTC and checked 5.4.0.07.

    You pointed CCS to the location of your BIOS 5 install. But did you actually change your project properties so that it is a BIOS 5 project?

    Dayton Simmons said:
    How do I migrate the bios from 3.3 to CCS 5? 

    BIOS is somewhat independent of CCS version. I say "somewhat" because CCSv5 does recommend you using at least BIOS version 5.40. For example, it is possible to use CCSv3.3 with the same DSP/BIOS version that comes with CCSv5. In any case both CCSv3 and CCSv5 comes with BIOS 5.x. (5.2 or 5.3 with CCSv3 and 5.4 with CCSv5). So there really isn't much migration needed that you need to do yourself (CCSv5 handles it under the hood). Now that you have BIOS 5.42 installed, reimport your old 3.3 project and during the import process, make sure you choose BIOS 5.42 to use.

    ki

  • So I imported the same project again, but it gave the same result.  I then right clicked on my project->Properties->Build->TConf->General Options and changed the configuration import path from the bios in CCS3.3 to C:\ti\bios_5_42_01_09 and then the project was able to build and an output file generated.

    For some reason, there are 40 warnings when it builds.  the 1st is because we moved the entry-point as we have a boot loader at the default starting location.  I don't know what the other 39 warnings are

    #10062-D build attribute vendor section TI missing in "C:\ti...": compatibility cannot be determined

    http://processors.wiki.ti.com/index.php/C28x_Compiler_Error_and_Warning_Messages#Warning:_build_attribute_vendor_section_TI_missing_in_.22.3Clibrary_or_object.3E_:_compatibility_cannot_be_determined

    indicates that this is the result of porting a library from an older tool set and that it can be suppressed with the linker option --diag_suppress=16002.  Will test soon, but it looks like all is good.

    Thanks for all the help in guiding me to this point.

  • Dayton Simmons said:
    indicates that this is the result of porting a library from an older tool set and that it can be suppressed with the linker option --diag_suppress=16002.  Will test soon, but it looks like all is good.

    You can also choose to simply use the same CGT version from CCSv3 with your CCSv5 install. But that is up to you if you don't mind the warnings.