Thread: Mplink error
View Single Post
  #3   Spotlight this post!  
Unread 14-11-2007, 15:50
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,801
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Mplink error

rom won't help this, the controller doesn't have enough program memory to hold all the code you're trying to shove into it.
The code needs to be trimmed down or you need a processor with more memory.

You can get a very rough idea of how much more didn't get into the space allotted by looking at the Linker command and seeing where printf.o probably fell and what is listed after it.
You could also, as you seem to suggest, select a target PIC that has a lot of memory, then take a look at the MPLAB memory gauge to see how much space it all takes up.

Are you compiling with a particular PIC in mind or don't you care which one is the target?
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 14-11-2007 at 16:12.