• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 711 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.

Enabling 'Generate Reset Vector' in TCF results in generate failure.

Timothy Freeburn
Prodigy 20 points
Other Parts Discussed in Thread: CCSTUDIO, TMS320C6713B

Greetings,

I have a project which I have recently migrated from CCS3.1 to CCS3.3. The automatic textual config conversion tool failed and so I had generated a new config, which has a very similar configuration to the previous .cdb file.

When I try to set the 'Generate Reset Vector' in HWI to 'True' and then try to save the config file, I get the following;

 
js: "./Servo.TCF", line 121: Failed to generate config files.
    "./<stdin>", line 3
Correct any script errors in C:/Trunk/Source/DSP3.3/Servo.tcf
using the Configuration Tool or a text editor, if necessary.
TConf initialization arguments:
-e environment['config.importPath']='C:/CCStudio_v3.3/bios_5_31_02/packages' -e environment['config.scriptName']='Servo.tcf'
 
However if the 'Generate Reset Vector' is set to 'False', the file saves and compiles normally.

Any help greatly appreciated.


Thanks,
Timothy Freeburn.


TMS320C6713B / CCS Platinum v3.3

 

  • 0
    TI__Mastermind 18130 points

    I think I have found the problem here, but I am not sure exactly what causes the failure. It appears that there was a bug with 5.31.02 that caused a script failure when 'bios.HWI.RESETVECTOR = 1;'. I created a simple little C67xx project and created a new TCF file. I found that I received the same error as you when trying to save the TCF file; however, after swapping to a newer version of BIOS (in my case 5.33.03) the problem went away.

    I looked around for any bugs filed relating to this problem but I cannot find any. My only suggestion at the moment is to upgrade to a newer version of BIOS as this feature does not appear to work properly with BIOS v5.31.02.

  • 0 in reply to TimHarron
    Prodigy 20 points

    Hi Tim,

    Yes you are correct with the bios.HWI.RESETVECTOR = 1; causing the problem.

    I will update the BIOS to 5.33.03 and try again.

    Thanks for your help,

    Timothy Freeburn.