Searching \ for '[PIC] : CCS compiler - Optimizing code in main() f' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: ': CCS compiler - Optimizing code in main() f'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] : CCS compiler - Optimizing code in main() f'
2001\01\19@035619 by etorius Johan * Spoornet

flavicon
face
When I compile my program it says 94 % used. I ad on line of code an it is
out of ROM space or segment to large. I suspect the segment contains the
main() function is to large. How do I get some code move out of this segment
?

Cheers

Johan Pretorius
(083) 6506752 (Cell)
(011) 7732423 (Phone)
(011) 7732184 (Fax)

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


2001\01\19@095059 by Mike Mansheim

flavicon
face
>When I compile my program it says 94 % used. I ad on line of code an it is
>out of ROM space or segment to large. I suspect the segment contains the
>main() function is to large. How do I get some code move out of this
>segment?

The #separate directive forces a function to be separate when the compiler
might want to make it inline.
Look in the back of your CCS manual in the "Common Questions and Answers"
section for their answer to the question "Why do I get an OUT OF ROM error
when there seems to be ROM left?" for a discussion of your exact situation.
Also from the CCS manual, be aware of this note when using the #separate
directive:  "The compiler will make all procedures marked SEPARATE
separate,
as requested even if there is not enough stack space to execute"

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.


More... (looser matching)
- Last day of these posts
- In 2001 , 2002 only
- Today
- New search...