View Single Post
  #3   Spotlight this post!  
Unread 17-02-2008, 23:47
gnormhurst's Avatar
gnormhurst gnormhurst is offline
Norm Hurst
AKA: gnorm
#0381 (The Tornadoes)
Team Role: Programmer
 
Join Date: Jan 2004
Location: Trenton, NJ
Posts: 138
gnormhurst will become famous soon enoughgnormhurst will become famous soon enough
Re: what is the eeprom write bandwidth?

Quote:
Originally Posted by Kevin Watson View Post
If you're referring to my code, you can also call EEPROM_Write_Handler() multiple times per 26ms loop. Just be aware that
EEPROM_Write_Handler() takes about two milliseconds to execute.

-Kevin
I am using your code (thanks!). And if had taken a moment to look at the write handler I would have seen that the queue size is decremented every call. (I had imagined that the eeprom write operation was asynchronous, and the write handler was just periodically checking to see if the current byte was done.)

I think that means that I can add a second call to the write handler and get a write bandwidth of 38 * 2 = 76 bytes per second, which is (on average) fast enough to fill the eeprom during autonomous (15 * 76 = 1140 > 1024). The only question that remains is whether I will overrun the queue buffer with a burst. I guess I'll just have to try it.
__________________
Trenton Tornadoes 381
2004 Philadelphia Regional Winners
2006 Xerox Creativity Award
---
My corner of the USPTO.
My favorite error message from gcc: main is usually a function
My favorite error message from Windows: There is not enough disk space available to delete this file.