cwilson 
Hi everyone,
I'm looking to be able to program the eeprom with some parameters for different modes of operation for the AVR micro.
I have tried goggling a number of topics without luck.
What I was looking to do is have the micro on start up read the eeprom for a parameter so it knows what part of the program to run. The issue is I need it to be able to be updated in the field by some sort of programming without changing the main code it self.
Any help would be greatly appreciated.
Craig
You have a number of choices for altering eeprom values -it depends on your imagination. It could be something as simple as a pushbutton to something more involved like bluetooth.
cwilson I was thinking something along the lines of serial communication but was trying to limit it so there was no need for additional hardware needed in the field to program it.
Would the USB versions of the AVR be an option?
Running usb does impose a real time overhead on your code when usb is plugged in. This may or may not be an issue.
clawson 
You are lacking a lot of detail - language? if C, which one? etc
But surely you just create a .eep with your EEPROM defaults and ISP it into the unit?
Are you talking about later update of the EEPROM "in the field" using a package of values sent to the device? To do that you need some kind of comms/programming built into the application.
Too little detail to provide a specific answer to your question. Perhaps the standalone programmer offered by a member in the marketplace forum would help.
Jim
theusch 
using a package of values sent to the device? To do that you need some kind of comms/programming built into the application.
I found it ironic that OP didn't want "serial" communications but then mentioned USB -- Universal >>Serial<< Bus.
In my "full" AVR8 industrial/commercial controller apps, I have up to a four-pronged approach:
-- .EEP with the default values, loaded during ISP
-- [sometimes] A shadow set of defaults in EEPROM or flash, for "Restore Factory Defaults"
-- A menu system to adjust some/many/most/all parameter values on the unit itself
-- A PC program "configuration editor", with the resulting "image" transferred to the device (one delivery mechanism is a .CFG file transferred to the SD card)
