How to connect BIOS to TMS320C6722?

Hi Alexander,

Which version of BIOS are you using?

I'm not sure I understand what your problem is.  Can you please provide some further insight?

Are you trying to connect your TMS320C6722 to CCS so that you can load an application onto it and debug it?

Or, are you only asking how to run a BIOS application on your TMS320C6722 hardware?

Alexandr Perepechay said:

The documentation says that I must install 'bios.GBL.LINKWITHROM = 1' in the configuration file prog.tcf. But CCS5.1 creating such a file does not give me the opportunity to make such setup in it.

You can open your application's *.tcf file in a text editor and then past the code 'bios.GBL.LINKWITHROM = 1' into the file.  Then, save the changes and rebuild your application and the change should take effect.

Steve

Thank you Steven.

Steven Connell said:

Which version of BIOS are you using?

At first I tried to connect BIOS from extern library having placed in the configuration file prog.cfg  of commands

var Defaults = xdc.useModule('xdc.runtime.Defaults');
var Diags = xdc.useModule('xdc.runtime.Diags');
var Error = xdc.useModule('xdc.runtime.Error');
var Log = xdc.useModule('xdc.runtime.Log');
var LoggerBuf = xdc.useModule('xdc.runtime.LoggerBuf');
var Main = xdc.useModule('xdc.runtime.Main');
var Memory = xdc.useModule('xdc.runtime.Memory')
var SysMin = xdc.useModule('xdc.runtime.SysMin');
var System = xdc.useModule('xdc.runtime.System');
var Text = xdc.useModule('xdc.runtime.Text');

var BIOS = xdc.useModule('ti.sysbios.BIOS');
var Clock = xdc.useModule('ti.sysbios.knl.Clock');
var Swi = xdc.useModule('ti.sysbios.knl.Swi');
var Task = xdc.useModule('ti.sysbios.knl.Task');
var Semaphore = xdc.useModule('ti.sysbios.knl.Semaphore');
var Hwi = xdc.useModule('ti.sysbios.hal.Hwi');

I yet not very well understand everything.  But I think that in case of this CCS connects one of BIOS 

libraries which are delivered together with CCS.

As a part of a packet of CCS5.1 two libraries BIOS are delivered:

bios_6_32_05_54 and bios_5_41_11_38

I am not confident in what of them is connected. But in case of BIOS connection attempt I received 

from CCS5.1 the message that the ti.targets. C67P platform isn't supported. And I decided that if 

TMS320C6722 has the built-in ROM-BIOS, then external BIOS can't be connected to it. 

Therefore I started to try to connect built-in ROM-BIOS.

Thus I faced with need to insert into the prog.tcf file the directive specified by me earlier 

--- 'bios.GBL.LINKWITHROM = 1'

You gave to me a valuable advice to make it in the text editor. Remarkably! I couldn't guess. 

Now I will try! Thanks

And generally, me the question interests: whether BIOS is engaged in loading and dynamic 

control of program flows?

My program codes will be stored on external FLASH via EMIF and can be more than processor RAM .

 Therefore loading, dynamic loading and control of program flows is necessary to me.

Steven Connell said:
Are you trying to connect your TMS320C6722 to CCS 
so that you can load an application onto it and debug it?

At present I train with a CCS simulator and with own starter-kit which has no external FLASH 

via XDC560 

Thank You. 

Alexander.

Oops!

Attempt to insert the directive about which I spoke in the .tcf file by means of the text editor leads to an error ((((

Alexander

Thank You, Steve.

It all are really very new for me.))  But I have no choice)

I found the document called by you and I study it.

Оne more question.

Whether has DSP/BIOS function of the secondary bootloader in itself or I in any

case should write myself the secondary bootloader ?

Besides. My program in external FLASH can have bigger volume, than the RAM, 

and dynamic control of program flows is necessary.

Whether DSP/BIOS will prosecute all these subjects?

Thank You. Excuse for importunity

Alexander

Alexander,

I'm not too familiar with putting DSP/BIOS into ROM, but I found this document that may be of help to you:

http://www.ti.com/lit/an/spra999a/spra999a.pdf

Steve

Thank You, Steve!

It's very interesting document for me.

I have not found it earlier.

Alexander

Trying work with CCSv5(Evaluation Lic) and TMS320C6722 I faced a problem of constructing of the secondary bootloader.
First I got acquainted (how do I have advised) with the document SPRAA69D–September 2009 (Using the TMS320C672x Bootloader).
This document advises to build the secondary bootloader by means of modules from library sprs203.zip
(the modules TISecondaryBoot.h, TISecondaryBoot.c) and via configuration files, built by means of PERL-utility genBootCnfg and genAis.
I was able to build configuration files by means of genBootCnfg and genAis.
But I can not compile my project with modules TISecondaryBoot.h and TISecondaryBoot.c.
Under direct inclusion these modules in my project CCSv5 makes TISecondaryBoot.obj
but final file xxx.out does not form and there is the error-message.
And when I turn in my project the module TISecondaryBoot.obj (excluding from it TISecondaryBoot.h And TISecondaryBoot.c)
linker does not see announced in TISecondaryBoot.c segments .Tibootstrap and .TIBoot.
Maybe it's because these segments are not called by my Main Project Modules and
there is a setting in CCS - "Eliminate sections not needed in the executable".
But if I remove this setting the compiler generates an error and does not build my project correctly.
What should I do?
OK.
Then I learned another document SPRA999A1 − May 2006 "Creating a Second-Level Bootloader for FLASH
Bootloading on TMS320C6000 Platform With Code Composer Studio"
This document offers a very different approach to the construction of the secondary bootloader.
But as an example, there is processor DSK6713.
And I do not know whether this is a method to my CPU 6722.
In addition. The document mentions the use of tools Flash.exe or Flashburn that
generate .hex file for the firmware in Flash.
But in my CCSv5.2(Evaluation Lic) no such tools. And I have been unable to download them.
Even for the money.
What should I do?
Thank's. Alexander

Alexandr,

It appears that this thread has now wandered into more generic C6722 territory.  My suggestion is that, to get a faster resolution, you label this thread as Answered and post a new one in the C67x Single Core DSP Forum (http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115.aspx).

Dave