• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 859 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.

dspbios.cdb to dspbios.tcf conversion

JW Hellenthal
Prodigy 40 points
Other Parts Discussed in Thread: TMS320F2812

Dear community members,

Please can anyone tell me what the next error means (see attachment) trying to open the .tcf within the CCS3.3 IDE? The tcf file was generated after converting  a CCS2.2 cdb file to a CCS3.3 tcf file. No warnings or errors were issued by the conversion tool itself. 

The TSK::<name>.iSTKSEG.MemberTest failed does not give much clues were to look. 

Regards,

Wim

  • 0
    TI__Mastermind 37985 points
    Wim,
    which device and platform are you using? Can you post the content of line 451, or even the whole script?
  • 0 in reply to Sasha Slijepcevic
    Prodigy 40 points

    Hi Sasha,

    I'm working on a Windows XP machine Service Pack 3

    The original CCS version is 2.20 with a DSPBiosBuilder.

    Converting to CCS version 3.3 BIOS 5.33.05

    The processor is located on a custom board and is the TMS320F2812

    We are using the SpectrumDigital JTAG Emulator XDS510LC

    Attached are both the .cdb file and the .tcf

    Regards,

    Wim4186.scripts.zip

  • 0 in reply to JW Hellenthal
    TI__Mastermind 37985 points

    Wim,
    the source of the problem is the line
    bios.TSK.OBJMEMSEG = prog.get("EXT_RAM_DATA");
    It seems that the assignment is failing because EXT_RAM_DATA begins at 0x10000, while the code that verifies the assignment requires the address to be below 0xffff because OBJMEMSEG is then used as a default for STACKSEG, which can't be above 0xffff. I know that the error message is cryptic, but DSP/BIOS is not really in a development mode for some time now, so chances are that the error message for that problem will not get any better.

    Your workaround is to change the line to
    bios.TSK.OBJMEMSEG = prog.get("L0SARAM");
    and then when you open the configuration in Gconf, you can set that parameter to whatever you want it to be, even back to EXT_RAM_DATA because at the end of the script, STACKSEG is not automatically equated to OBJMEMSEG.

  • 0 in reply to Sasha Slijepcevic
    Prodigy 40 points

    Sasha,

    The suggestion solved the problem opening the configuration. Thank you so much!

    regards,

    Wim