• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 54 subscribers
  • Views 921 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.

CCS/TMDSDSK6713: Problems with pop ups when creating a new project with DSP/BIOS in CCS

Daniel Harvey
Intellectual 310 points
Part Number: TMDSDSK6713

Tool/software: Code Composer Studio

Hi

I am preparing some course work booklets for  DSP course for students here at Imperial College - they have to create a project with DSP BIOS in CCS for a DSK6713. When doing this a number of pop ups appear with errors (although the project works!!) and I would like to resolve this so the students don't have to deal with the buggy pop ups

After creating a new DSP BIOS connection the following windows appear,

first this one:

then I enter the XDC tool directory

hit ok

hit yes

IS there any way of sorting this out so the messages don't appear?

I am using:

Compiler 7.4.23 (the latest doesn't work) and DSP BIOS 5.42.2.10

thanks

Danny Harvey

  • 0
    TI__Guru* 96960 points
    Hi Danny,

    Try using the XDCtools that is included in DSP/BIOS (e.g. C:\ti\bios_5_42_02_10\xdctools) instead of 3_50_07_20.

    Todd
  • 0 in reply to ToddMullanix
    Intellectual 310 points
    Hi Todd

    Yes that's improved things - It no longer reports "Unable to create Bios Config server".

    The problem is the other pop ups still appear when I create a new project and add dsp/bios config - is there any way of setting the environment so that it doesn't ask for the folder of the XDC tools every time?

    thanks
    Dan
  • 0 in reply to Daniel Harvey
    TI__Mastermind 32475 points

    Dan,

    I'm not seeing what you see.  What version of CCS are you using?  And how are you creating the project?
    When I create via this menu, I don't see what you are saying:

  • 0 in reply to judahvang
    Intellectual 310 points

    Hi

    thanks for response. The version  is

    Code Composer Studio
    Version: 8.1.0.00011

    We first create a CCS project - but do not click on the DSP/BIOS examples but rather select a empty project. This part is actually ok. It is when we add the DSP/BIOS config file later (menu file/new/dsp bios V5.x configuration file) where the problems start (see second pic) specifically when I hit finish to save the file.

  • 0 in reply to Daniel Harvey
    TI__Guru* 96960 points
    Hi Daniel,

    I would not start with an empty project. I would start with one of the DSP/BIOS examples.

    Todd
  • 0 in reply to ToddMullanix
    Intellectual 310 points
    Hi

    That's a little counter intuitive to the way the students are asked to work in the lab assignment as they are asked to add a C file template into the project folder later. I'm assuming that creating a DSP/BIOS example project, creates a C file, yes? They will have to delete this and replace it with one of our templates.

    R.
    Dan
  • 0 in reply to Daniel Harvey
    TI__Mastermind 32475 points
    Dan,

    Ok, I was able to reproduce what you saw...but here's an other idea. Is it possible to pre-create the .tcf file? So instead of creating a new one...copy an existing one into the project? When I do this, it does not prompt me to specify the xdctools path but it does prompt me if I want to convert this to a rtsc project.

    As far as I know...there isn't a way to shutdown that dialog box when creating a new tcf file.

    Judah
  • 0 in reply to judahvang
    Intellectual 310 points

    Ok - I will try this and think about using it possibly. We would then have to include it in the zip file for the students. The good thing about them explicitly creating the file is that we explain that the tool is a graphical tool for setting memory and other hardware and it ensures that only the required modules are linked into the code and so on... and it flows nicely on from the first lab that uses only  a .cmd file for some settings.