View Single Post
  #7   Spotlight this post!  
Unread 21-01-2006, 22:54
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
Re: .hex file too large for 2004 controller?

Bharat, Steve, Mark,

Thanks all for your responses to my question. It turns out that when I added our autonomous mode code to Kevin's default camera code I overlaid the 2006 InterruptHandlerLow () function with last year's version. This apparently caused the processor fault. One of our students found this.

Mark, One of these days I'd like to dig into the details of data space usage a bit more - I have a lot to learn in that area. I notice that most of our variables are loaded in lower memory while some "system" variables seem to be loaded in high memory. The map shows a gap between the end of our variables and the start of the system variables - I assume that this is available data memory.

Steve, We may end up using the streamlined verison of the code for our production build. At this point we are using the full version to get a handle on camera setup parameters. With the default settings from Kevin's code we are able to track the standard target at about 30 feet although we need to be about 10 feet away to acquire it. (camera lens screwed out about 3/4 of way) More testing / setup is obviously needed...

Best Regards, Al