• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 915 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Adding DSP/BIOS 5 support in Code Composer Studio 12

Justin Hadella
Prodigy 50 points

Hello,

I am trying to update some legacy projects which were build using DSP/BIOS 5 with CCSv4. I have several projects already working which *dont* use DSP/BIOS 5 working already. I was reading through https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_faqs.html which indicates DSP/BIOS 5 is supported in CCS 12.

When I right-click a project and select properties, under the "Resource->Linked Resources" option, I see an blank entry for BIOS_CG_ROOT. I does not allow me to edit or remove this entry. I've installed the specific version of DSP/BIOS 5 the project used and a newer version as well. How do I let CCS know about them?

In the General project properties, I see an entry at the bottom which shows DSP/BIOS 5.41.10.36 in a drop-down, but it doesn't let me choose any thing else. I have that version and also 5.42.02.10 installed.

My target processor is a C6747.

Regards,

Justin Hadella

  • 0
    Guru 13202 points

    Hello!

    It's been a while since I played with these combinations. Looking into my setup I see 5.42.02.10, but no one earlier. I used this one to work with C641x and newer CCS.I am under impression that earlier minor versions did not work for my setup, but would not rely on my memory though.

    As to blank entry for BIOS_CG_ROOT it helps to click Install button and point to bios install directory.

  • 0
    TI__Guru**** 451311 points
    Justin Hadella said:
    DSP/BIOS 5 is supported in CCS 12.

    "Support" is quite minimal. As mentioned in the FAQ, DSP/BIOS support has been greatly deprecated. It is possible to get things to work though it is not an officially tested environment any more.  

    Justin Hadella said:
    How do I let CCS know about them?

    Check the discovered products list to see if your desired DSP/BIOS version appears:

    If it is not there, try pressing the Refresh button. Note that you may also need to add the path to it in the "Product discovery path" if you installed in some custom location.

    Also note that there is a known issue when trying to have multiple DSP/BIOS version discovered ("conflicting dependency" issue). I believe this happens if you try to discover an older version of DSP/BIOS than what is already discovered. 

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    Through the Window->Preferences option, I was able to get CCS to finally discover the installed products. I had installed them separately but when CCS launched, it hadn't indicated it found them. When I show the same pic, I see this:

    To eliminate any issues my my code, I created a blank DSP/BIOS project based on the TSK template. When I attempt to build it I see the error:

    **** Build of configuration Debug for project EraseMePlease ****

    "C:\\ti\\ccs1240\\ccs\\utils\\bin\\gmake" -k -j 12 all -O

    Building file: "../tsk.tcf"
    Invoking: TConf
    "C:/ti/bios_5_42_02_10/xdctools/tconf" -b -Dconfig.importPath="C:/ti/bios_5_42_02_10/packages;" "../tsk.tcf"
    subdir_rules.mk:19: recipe for target 'build-1678155679-inproc' failed
    C:\ti\bios_5_42_02_10\xdctools\C:/ti/bios_5_42_02_10/xdctools/tconf: can't create session manager: create of JVM failed
    gmake[1]: *** [build-1678155679-inproc] Error 1
    subdir_rules.mk:16: recipe for target 'build-1678155679' failed
    gmake: *** [build-1678155679] Error 2
    gmake: Target 'all' not remade because of errors.

    **** Build Finished ****

    If I right-click the TCF file and select "Open With->DSP/BIOS Configuration Tool" I get a popup error.

    Configuration Tool: (popup)

    CoCreateInstanceFailed: hiervw.dll

    Then after some time, I see another popup which says:

    ScriptPane (popup)

    Unable to Create BIOS Config Server.

    When I build one of my old projects, I get the same issue. When I searched for the error, it came up with something related to the Java JRE. It seems like there are several of them in my TI folder. This is what the example DSP/BIOS TSK project shows for its environment variables.

    I've been stuck at this point now for a while. It would be great if there were something simple in the setup I am missing. I was attempting to update to the latest tools here at least in terms of CCS instead of using the old v4 version which was old when I first worked on the project.

  • 0 in reply to Justin Hadella
    Prodigy 50 points

    Using the advice in this link:

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/422003/c5x-dspbios-tconf-can-t-create-session-manager-create-of-jvm-failed

    This gets me further along. It now appears to compile more files and takes a while which is a good sign. However, I now get a new error which says it can't find a header file -- one that should be autogenerated from the TCF file. I can see in an old archived project there should be some header made. So for example, my test project has a file, blinky.tcf, then it's complaining there is no blinkycfg.h.

  • 0 in reply to Justin Hadella
    TI__Guru**** 451311 points
    Justin Hadella said:
    This gets me further along. It now appears to compile more files and takes a while which is a good sign. However, I now get a new error which says it can't find a header file -- one that should be autogenerated from the TCF file. I can see in an old archived project there should be some header made. So for example, my test project has a file, blinky.tcf, then it's complaining there is no blinkycfg.h.

    Looks like you are getting TCONF build errors. DSP/BIOS is supported by the device teams. I suggest starting a new forum thread for this issue for the device experts.