Forums

help need urgent DSP/BIOS TMS320F2811

Started by mrbhalerao1 April 15, 2008
in project used TMS320F2811,
i want to transfer nonBIOS.cmd to BIOScfg.cmd in exiting application.
but when i do this it shows following error.

nonBIOS.cmd file:

-l bioscfg.cmd
memory:
{
page 0:
FLASHJ: 0x3d8000 2000 
}
but when allocate this on BIOScfg.cmd through graphical interface(after
removing in nonBIOS.cmd),it show folling error
>> FLASHJ and FLASHJ on page0 overlap
i checked .map nonBIOS.cmd & BIOScfg.cmd properly,but i didnot find any overlapping. can any body tell me what is problem? either i m doing wrong procedure or it is really problem of BIOScmd i want to completly remove this nonBIOS.cmd .if any body knows,please help because project is not yet being proceed. thanks shailesh
On Apr 15, 10:39&#2013266080;am, "mrbhalerao1" <des...@amtechelectronics.com>
wrote:
> in project used TMS320F2811, > i want to transfer nonBIOS.cmd to BIOScfg.cmd in exiting application. > but when i do this it shows following error. > > nonBIOS.cmd file: > > -l bioscfg.cmd > memory: > { > page 0: > FLASHJ: 0x3d8000 2000} > > but when allocate this on BIOScfg.cmd through graphical interface(after > removing in nonBIOS.cmd),it show folling error > > >> FLASHJ and FLASHJ on page0 overlap > > i checked .map nonBIOS.cmd & BIOScfg.cmd properly,but i didnot find any > overlapping. > can any body tell me what is problem? > either i m doing wrong procedure or it is really problem of BIOScmd > i want to completly remove this nonBIOS.cmd .if any body knows,please help > because project is not yet being proceed. > > thanks > > shailesh
Your post isn't really clear. The .CMD file are the linker definition files that determine what portions of your code will go where. Based on your comment about the BIOScmd file and nonBIOScmd file, I think you are experimenting with the projects. Instead of mucking with the .cmd files individually, try opening a different project, one that either uses or does not use the BIOS. The .CMD files necessary for that project will be loaded automatically. You can also spend time reading the compiler and assembler manuals, which BOTH have information on the linker definitions. It takes a while to understand, but it is really the only way to do anything with these files.