.
Robin2:
Just a moment now ... This is a whole lot of new information that was not part of your Original Post. You can't expect us to be able to give useful advice based on partial information. I have been assuming you were using an Uno or nano with an onboard USB connection.
Take a few moments to describe the whole project, what it does, what the EEPROM data is for, why it might need to be updated, and the exact hardware that your user will have.
Ah well, this is always the difficulty. Give too much information, and posters can get sidetracked by irrelevant information and try to reinvent your whole project. Give too little and it risks the wrath of such as yourself
I'm not sure anything in my original post justified the belief I was using a nano or Uno ...
But here goes: the system consists of a ardunio pro/NRF24l01 connected to an RFID reader (I'm sure you don't want to know about that) which reads tags and transmits the bytes to a similar set up which decodes them, compares them against values stored in the EEPROM and displays text on a small OLED screen. Space is at a premium on the receiver, and so is the need to minimise current because it will be running from a small LIPO battery. I envisage that the EEPROM on the receiver end will be coded for the tags, and there will be no need for an SD card to be inserted unless a new set of RFID tags is used, which will need a new dataset. (I don't want to have the current consumption overload associated with the SD setup in normal use).
It is my understanding that the OP is looking for a system that could be used reliably by a customer who knows nothing about Arduinos and very little about computers - great aunt Matilda, perhaps. To my mind this needs an interface in which the user plugs in the Arduino board and double-clicks a program icon and does not have to do anything else
exactly.
Thinking more about the problem, maybe the best solution is to use an SD Card rather than EEPROM memory and then the user can just replace the SD Card - no need for any program interaction. And it has the advantage that if the new SD Card does not work the user can resume using the previous one. (It really pisses me off that so many PC software upgrades are not instantly undoable)
...R
Yes - that is more or less where I was starting, except that the receiver end would come with the original data on the internal EEPROM, but with a SD card in case the EEPROM got corrupted, or if an upgrade was needed. In case of the upgrade, the SD reader would rewrite the EEPROM and then the card could be taken out and stored. I haven't looked into this but I assume there will be current-consumption advantages in using the EEPROM rather than the card reader most of the time.
I think this is going to be OK, but I was really trying to think of ways to make it even easier.