• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 507 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.

Command Line Setup for DSP->SYS BIOS Conversion

Tim Klein
Intellectual 580 points


I have two (2) questions concerning the command line setup for converting a .tcf to a .cfg.  Here is what I presently am working with:

C:/ti/xdctools_3_24_05_48/xs.exe --xp "C:/ti/bios_6_34_02_18/packages" ti.bios.conversion -c Semikron_DCDC_v05.cfg --pr "C:/ti/xdctools_3_24_05_48/packages" --pn ti.platforms.tms320x28 C:/Users/monreaji/Documents/Semikron_DCDC_v05/Semikron_DCDC_v05.tcf -i SWI_ISR.c -i HWI_ISR.c -i Tasks.c

And this is what the program "spits" out (no errors, but I have issues with it - see below):

Platform: ti.platforms.ezdsp28335
        params.clockRate:150
        params.catalogName:ti.catalog.c2800
        params.deviceName:28335
Target: ti.targets.C28_large
Clock Rate: 300

1. How do I make the Target become "ti.targets.C28_float"?  That is what we have been compiling with using DSP/BIOS and would like to contiue to use with SYS/BIOS.

2. Have I appended the command line text with "-i SWI_ISR.c -i HWI_ISR.c -i Tasks.c" correctly?  These are files that reside in the root project folder (C:/Users/monreaji/Documents/Semikron_DCDC_v05/) with the .tcf file.  These files have the c-code functions that are referenced in the .tcf as instance("x").fxn=prog.extern("y") with "x" and "y" being the function name in the .tcf and the c-code function callout, respectively.  If I leave off all the -i portions, the same message spits out of the job, which makes me wonder if I have it correct, in the right spot, or generally doing something wrong.  If I move things around and put full paths in as below, running from c:\ at the cmd promp, I get ALL sorts of errors until the program dies from an overload of them...

C:/ti/xdctools_3_24_05_48/xs.exe --xp "C:/ti/bios_6_34_02_18/packages" ti.bios.conversion -c Semikron_DCDC_v05.cfg --pr "C:/ti/xdctools_3_24_05_48/packages" --pn ti.platforms.tms320x28  -i C:/Users/monreaji/Documents/Semikron_DCDC_v05/SWI_ISR.c -i C:/Users/monreaji/Documents/Semikron_DCDC_v05/HWI_ISR.c -i C:/Users/monreaji/Documents/Semikron_DCDC_v05/Tasks.c C:/Users/monreaji/Documents/Semikron_DCDC_v05/Semikron_DCDC_v05.tcf

The point to all of this is, hopefully, if I follow all the steps to a "T", then this program will compile without incident under SYS/BIOS.  Which is not happening for a coworker of mine.

  • 0
    TI__Mastermind 37985 points

    Tim,
    I want to mention first that in your SYS/BIOS installation, there is a directory 'docs' and in it you can find a file Bios_Legacy_App_Note.pdf. Chapter 2 covers the configuration conversion, and you may want to take a look to get a better idea how the conversion process works.

    The target property that the conversion tool displays is just a guess which target will certainly work with the platform being generated. Don't worry about it, you'll have a chance to select the right target once you start using your converted CFG script.

    You can find more details about the option '-i' in the document I mentioned above. Unless your TCF script includes function calls to utils.importFile(), you don't need to use -i. As for C files you are supplying, they are not relevant at that point. The conversion tool does not need to see these C files. It just reads your TCF script and creates a new CFG script. Only when you actually run that CFG script in CCS or using configuro, these C files will be needed.
    Try conversion without -i options, and if it doesn't report any errors, try using the new CFG script in a project.