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.

SPRA999A - applyTableBinitCmdFile -- will it run on CCS 5?

All: Post     

In

http://e2e.ti.com/support/embedded/bios/f/355/t/303442.aspx

I reference a JavaScript file that can be used to add BINIT information to flash info being copied into RAM.

This runs on CCS 3.3 - will it also run on CCS 5.5?

  If so, are there environment setup conditions required to make it work?

 

  • Hi Todd,

    That is a BIOS5 Tconf include file (*.tci). The dependency is BIOS, not CCS. CCSv5 officially supports BIOS 5.4 but you can use older BIOS 5 versions (but you just lose some debug support).

    Thanks

    ki

  • Ki It looks like it has to be run under DSS? Is there a document or procedure that updates the appendix in SPRA999 to allow the .tci file to be run as a user - included file as stated in the SPRA999 appendix? BTW, we are running this under the latest DSP/BIOS, on both CCS3.3 and on CCS5.5
  • All:

    On CCS3.3, what is the mechanism used for ti_tcapps_utils? and utils.importFile? (mentioned in SPRA999 appendix A)

    I could not find either of them in the CCS3.3 install directory, but on CCS3.3, it does appear to work. I was hoping to at least set the environment so that when it is tried to be invoked in CCS5.5, I would be able to process the command file to get a BINIT added to the Bios-generated linker command file.

  • Todd - I'm not very familiar with that document and have just basic knowledge of tcf files. I will move your post to the TI-RTOS forum where there is much more expertise with DSP/BIOS there.

    ki

  • I was able to get the "applyTableBinitCmdFile.tci" to work in CCS 5.5 -

    1. In my project, I opened up a scripting console environment by View--> Scripting Console

    2. At the js: > I typed " load ("c:/  PROJECTPATH /applyTableBinitCmdFile.tci")

         a. Specifically spelled out the path to the .tci file (I will try associating with project parameters later.)

         b. Forward slashes were important - backward slashes did not work.

    3. I did need to go into  applyTableBinitCmdFile.tci and change a few lines:

         a. I changed "ti_tcapps_utils.applyTableBinitCmdFile" to "applyTableBinitCmdFile."

         b. Style - moved "{" to new line so that I could more easily see the "{" to"}".

    4. Inside of the BIOS .tcf file, I did a similar

         load ("xxxxxx/applyTableBinitCmdFile.tci") where xxxxxx is the full path to the .tci file

        instead of the utils.importFile(  ).

    5. I removed the "ti_tcapps_utils" from the "ti_tcapps_utils.applyTableBinitCmdFile"

    And it worked - specifically generating .trcdata and .hwi_vecs binit information.