Thread: .hex file too large for 2004 controller?
View Single Post
  #1   Spotlight this post!  
Unread 19-01-2006, 00:56
AL_E AL_E is offline
Registered User
AKA: Al Evangelista
None #0703 (Phoenix)
Team Role: Coach
  
Join Date: Jan 2005
Rookie Year: 2004
Location: Saginaw, MI
Posts: 5
AL_E is an unknown quantity at this point
.hex file too large for 2004 controller?
Gang,

While attempting to test a program based on Kevin's "bells and whistles" camera code (with the addition of our own autonomous and RC mode drive code) we ran into a problem when loading the .hex file into the 2004 controller.

The download appears to complete correctly however the program state LED goes to red and the controller does not operate. We double checked the compile options (Device = PIC18F8520) and confirmed that the correct linker script and library have been selected for the 8520.

The .map file reports "30471 out of 33816 program addresses used, program memory utilization is 90%" I do not see a corresponding space usage summary report for the data area (RAM).

My question is this: Does the memory utilization figure reported in the .map file tell the whole story or are there other considerations (RAM usage or other factors) which would contribute to this problem. In short, is there a way to determine from the .map file whether or not the .hex file is too large for the 2004 controller?

Thanks in advance for the assistance

-Al