• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 1154 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.

CCS 3.3 with DSK 5510

Alex Laird
Intellectual 320 points

I have been using CCS 3.1, and I just upgrade to 3.3.  When I imported my project, it said it updated successfully, and I can view all my source files.  However, first went to view the DSP/BIOS .tcf file, I got several script errors.  After editing the file in UltraEdit, I fixed the scripting errors, but I'm not getting linking errors on compile (which is understandable considering I hand-edited the .tcf file).

I thought it might be easier to just recreate my DSP/BIOS configuration file, so I created a new file in CCS 3.3.  Before changing anything in it, I saved the file and still received an error saying:

js: "./MyFile.tcf", line 11: Heaps are enabled, but the segment for DSP/BIOS objects (MEM.BIOSOBJSEG) is not set correctly.  Please create a heap in one of your deata segments and set MEM.BIOSOBJSEG to it.
"./<stdin>", line 3

If I disable the heaps, this error goes away, but the fact is I need the heaps for the application I'm doing.  Suggestions?

  • 0
    Intellectual 320 points

    It's worth noting I think that, if I do disable heaps so this will compile, I'm still left with seven linking errors on the auto-generated .cmd file.  Is it normal to receive errors on auto-generated files that were just created and have essentially nothing in them?

  • 0 in reply to Alex Laird
    TI__Mastermind 18130 points

    Does your Memory Manager look like mine in the attached photo? If you enable heaps you must specify the default heap for each of the two drop-downs or you will receive build errors. If you have not created any heaps in a memory segment marked as 'data' or 'code/data' then your drop-downs will not contain any heaps as mine show.

    If this is the case right click on a memory segment, select Properties, check the heap button and make certain that segment is listed as data or code/data.

  • 0 in reply to Alex Laird
    TI__Mastermind 18130 points

    Alex Laird said:
    It's worth noting I think that, if I do disable heaps so this will compile, I'm still left with seven linking errors on the auto-generated .cmd file.  Is it normal to receive errors on auto-generated files that were just created and have essentially nothing in them?

    These BIOS-generated files are pretty complex, so depending on the errors there may or may not be a simple explanation.

  • 0 in reply to TimHarron
    Intellectual 320 points

    Thanks, selecting DARAM from those drop-downs solved that problem--however, after compile, I'm still getting the seven linking errors.  For the sake of control, I am doing this on a brand new project, so it's baffling me how these files wouldn't be automatically created correctly.  The linking errors are suggesting the following:

    The input files lnkrtdx.a55, drivers.a55, siobotha55, bios5510.a55, bios.a55, and rtdx.lib are missing.

    I have included the rts55.lib file that is provided in C5500/cgtools/lib, which was all that CCS 3.1 required.  Are there additional includes I'm missing now that I've upgraded to 3.3?

  • 0 in reply to Alex Laird
    TI__Mastermind 18130 points

    It sounds like the linker cannot find any of these libraries, but these should be added automatically as part of the BIOS kernel. I do not know where these physically sit on the file system or I would suggest pointing the linker to that directory.

    I wish I could help with this second question, but I am going to have to pass the torch off to someone else more knowledgeable with the behind-the-scenes.

  • 0 in reply to TimHarron
    Intellectual 320 points

    Thanks for your help.  After an uneventful morning of searching, I finally Googled the right phrase this afternoon and found this very helpful Wiki:

    http://processors.wiki.ti.com/index.php/55x_FAQ#Why_am_I_getting_a_bunch_of_linker_errors_such_as.2C_.22can.27t_find_input_file_.27bios5510.a55.27.22_when_I_build_my_BIOS_project.3F

    Seeing as how these are the default settings that don't work, I feel like TI should make it significantly more clear in CCS why this doesn't work on the fly--at least put it in the tutorials.  Thanks for your help on the first question though.

  • 0 in reply to Alex Laird
    TI__Guru*** 125430 points

    Alex Laird said:
    Seeing as how these are the default settings that don't work, I feel like TI should make it significantly more clear in CCS why this doesn't work on the fly--at least put it in the tutorials.  Thanks for your help on the first question though.

    Alex, FYI this issue was fixed over a year ago, i.e. you wouldn't have run into it on newer tools.  Here's a quote from the last sentence of the wiki page you referenced:

    "As of BIOS 5.33.05 the new default for 55x configuration files is the large memory model. As of CCS 4.0 the new project default for 55x is also large memory model."

    In other words, the 2 settings the wiki article had you change are now the defaults.  Sorry for the trouble, but I'm glad Google was able to help you find the answer! :)

    Best regards,
    Brad