Thanks Bob.
Yes, I do use quite a bit of printf() functions for the LCD display.  I
definitely know thats eating up lots
of space!

Thanks again.
Dan



> You will find that a lot of the space you are using now is
> for the floating
> point library. That will not grow much as you add more code.
>
> Try this:
>
> Create a small program that uses all the floating point operations and
> functions that your program will. You will be surprised how
> big it will be
> when compiled and linked.
>
> If you really have 50% of the code done and are using 44% of
> the ROM space
> you are probably going to be just fine.
>
> Bob Ammerman
> RAm Systems
>
> ps: another HUGE gobbler of memory are the  ...printf()
> family of functions.
> If you can eliminate all references to them you will be much happier.
>
> ----- Original Message -----
> From: "Mccauley, Daniel H" <daniel.h.mccauley@LMCO.COM>
> To: <PICLIST@MITVMA.MIT.EDU>
> Sent: Tuesday, June 03, 2003 8:17 AM
> Subject: [PIC]: Tips to reduce Program Size using CCS C
>
>
> > I'm currently working on a large program using a PIC16C66x
> processor (8k)
> > using CCS C.  However, I'm already at 44% ROM space used
> and only about
> > half-way
> > through the program, so I am a little concerned about
> program space.  I
> > think the killers are the floating point numbers I'm using.
> >
> > Anyways, are there anything else I can do to help conserve
> program space.
> > Does using the #SEPARATE directive for functions help
> reduce space (at the
> > cost of speed)?
> >
> > Any help appreciated.
> >
> > Thanks
> >
> > Dan
> >
> > --
> > http://www.piclist.com hint: The PICList is archived three different
> > ways.  See http://www.piclist.com/#archives for details.
> >
>
> --
> http://www.piclist.com hint: The PICList is archived three different
> ways.  See http://www.piclist.com/#archives for details.
>

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body