Reply by Derk van de Velde December 1, 20012001-12-01
hi,

if it doesn't matter where the code comes, you can use the virtual linker.
the .cmd file option is better to place exact.
you can also use #pragma codesection, to place at routine basis. about ovly:
i work much with far code and always use ovly=1

some things:
1. keep isr's in the overlaypage.
2. keep vectrotable in the overlay page.

it is sometimes some work to get it running, but nice to do.
derk
-----Original Message-----
From: [mailto:]
Sent: vrijdag 30 november 2001 20:48
To:
Subject: RE: [c54x] Problem with CCS 2.0, DSP/BIOS and extended program
memory on C54 02 Or use the visual linker to do it for you.

Carl Chipman
Nomadics, Inc.

http://www.nomadics.com > -----Original Message-----
> From: KRUCHIO Gabor [mailto:]
> Sent: Friday, November 30, 2001 9:46 AM
> To: '
> Subject: RE: [c54x] Problem with CCS 2.0, DSP/BIOS and extended
program
> memory on C54 02
>
> > 2. SInce my program space is no longer contiguous, I have
> > defined multiple
> > code
> > memory segments eg
> > name start length
> > EPROG 00014000 0000c000
> > EPROG2 00024000 0000c000
> > EPROG3 00034000 0000c000
> > The problem is that the code all goes into the .text segment
> > which attempts
> > to put it all in the EPROG section. Is there any way to tell
> > the linker
> > that the .text segment can be allocated into mutiple segments?
>
> Use something like the following in your .cmd file (e.g. build.cmd): > -lclabcfg.cmd
>
> SECTIONS
> {
> .text_for_eprog
> {
> file11.obj (.text)
> file12.obj (.text)
> file13.obj (.text)
> } > EPROG PAGE 0
>
> .text_for_eprog2
> {
> file21.obj (.text)
> file22.obj (.text)
> file23.obj (.text)
> } > EPROG2 PAGE 0
>
> .text_for_eprog3
> {
> file31.obj (.text)
> file32.obj (.text)
> file33.obj (.text)
> } > EPROG3 PAGE 0
> } > _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author
> of this message will receive your answer. You need to do a "reply
all" if
> you want your answer to be distributed to the entire group.
>
> _____________________________________
> About this discussion group:
>
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to
>
> Archives: http://www.yahoogroups.com/group/c54x
>
> Other Groups: http://www.dsprelated.com > ">http://docs.yahoo.com/info/terms/
>

_____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join: Send an email to

To Post: Send an email to

To Leave: Send an email to

Archives: http://www.yahoogroups.com/group/c54x

Other Groups: http://www.dsprelated.com ">http://docs.yahoo.com/info/terms/



Reply by November 30, 20012001-11-30
Or use the visual linker to do it for you.

Carl Chipman
Nomadics, Inc.

http://www.nomadics.com > -----Original Message-----
> From: KRUCHIO Gabor [mailto:]
> Sent: Friday, November 30, 2001 9:46 AM
> To: '
> Subject: RE: [c54x] Problem with CCS 2.0, DSP/BIOS and extended
program
> memory on C54 02
>
> > 2. SInce my program space is no longer contiguous, I have
> > defined multiple
> > code
> > memory segments eg
> > name start length
> > EPROG 00014000 0000c000
> > EPROG2 00024000 0000c000
> > EPROG3 00034000 0000c000
> > The problem is that the code all goes into the .text segment
> > which attempts
> > to put it all in the EPROG section. Is there any way to tell
> > the linker
> > that the .text segment can be allocated into mutiple segments?
>
> Use something like the following in your .cmd file (e.g. build.cmd): > -lclabcfg.cmd
>
> SECTIONS
> {
> .text_for_eprog
> {
> file11.obj (.text)
> file12.obj (.text)
> file13.obj (.text)
> } > EPROG PAGE 0
>
> .text_for_eprog2
> {
> file21.obj (.text)
> file22.obj (.text)
> file23.obj (.text)
> } > EPROG2 PAGE 0
>
> .text_for_eprog3
> {
> file31.obj (.text)
> file32.obj (.text)
> file33.obj (.text)
> } > EPROG3 PAGE 0
> } > _____________________________________
> Note: If you do a simple "reply" with your email client, only the
author
> of this message will receive your answer. You need to do a "reply
all" if
> you want your answer to be distributed to the entire group.
>
> _____________________________________
> About this discussion group:
>
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to
>
> Archives: http://www.yahoogroups.com/group/c54x
>
> Other Groups: http://www.dsprelated.com > ">http://docs.yahoo.com/info/terms/
>




Reply by KRUCHIO Gabor November 30, 20012001-11-30
> 2. SInce my program space is no longer contiguous, I have
> defined multiple
> code
> memory segments eg
> name start length
> EPROG 00014000 0000c000
> EPROG2 00024000 0000c000
> EPROG3 00034000 0000c000
> The problem is that the code all goes into the .text segment
> which attempts
> to put it all in the EPROG section. Is there any way to tell
> the linker
> that the .text segment can be allocated into mutiple segments?

Use something like the following in your .cmd file (e.g. build.cmd): -lclabcfg.cmd

SECTIONS
{
.text_for_eprog
{
file11.obj (.text)
file12.obj (.text)
file13.obj (.text)
} > EPROG PAGE 0

.text_for_eprog2
{
file21.obj (.text)
file22.obj (.text)
file23.obj (.text)
} > EPROG2 PAGE 0

.text_for_eprog3
{
file31.obj (.text)
file32.obj (.text)
file33.obj (.text)
} > EPROG3 PAGE 0
}