• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 38 subscribers
  • Views 351 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 -- TConf Error

Justin Hadella
Prodigy 50 points

I am trying to get an old project working again using modern tools. The old project uses DSP/BIOS 5.41 and I am attempting to use CCS version 12. I've been through a number of steps so far. 

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1255050/adding-dsp-bios-5-support-in-code-composer-studio-12

The issue I am currently seeing may be related to something with tconf?

From other archived projects, I see that the tcf file generates some project cdf header and c file. For example, my blinky.tcf would produce a blinkycfg.h and .c file. This is not happening so far.

  • 0
    TI__Guru**** 191886 points

    Hi,

      Can you please clarify which TI part number this is? 

  • 0 in reply to Charles Tsai
    Prodigy 50 points

    In terms of CCS its version 12.4. I was attempting to use DSP/BIOS 5.41.10.36. I think the XDC tools was 3.22.01.21. One thing that I'm not sure on is that there are a variety of xdctools and jre all over.

    The last time I worked on this project was years ago using CCS v4.2 with the same other tools mentioned. On windows 10, I can't seem to get anything to work in CCS v4 anymore. It's not recognizing anything in the ti folder.

    I attempted to use CCS v12 since it's current. Not sure how well these old libraries are supported. I've been able to get some simple projects working as long as they don't use DSP/BIOS. None of my DSP/BIOS projects will compile due to this TCF not generating the necessary code.

    I did install CCS v5 and that tool worked for the DSP/BIOS projects just fine. If there isn't a convincing argument to use CCS v12 I just may keep on with the v5 since I can get things done.

  • +1 in reply to Justin Hadella
    TI__Guru**** 191886 points
    Justin Hadella said:
    If there isn't a convincing argument to use CCS v12 I just may keep on with the v5 since I can get things done.

    Hi Justin,

      I will suggest you stay with CCS v5. In addition, I also suggest you stay with the same DSP/BIOS and XDC version that were originally installed. You have a legacy device that we can longer support on e2e. It will be best to use the original versions that was proven to work.