[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avr-gcc-list] Patching EEPROM image for production
From: |
dimax un |
Subject: |
[avr-gcc-list] Patching EEPROM image for production |
Date: |
Thu, 5 Oct 2006 12:26:04 +0200 |
Hi Folks,
I'm trying to find clean solution for the following system problem.
I have configuration structure in EEPROM:
struct VPD_t
{
char sn[10];
char id[20];
}VPD EEPMEM;
While linking I generate EEPROM image in lets say VPD.eep file.
For production purposes I need to burn every product with different sn
and id. So I have to patch VPD.eep all the time.
I'm trying to make a script that has VPD.eep sn and id on it's input
and generates VPS_sn.eep with patched sn and id on it's output.
What would you suggest me to do?
So far I'm thinking about something like that.
1. On linking stage I want to get EEPROM layout file VPD.map File
should contain information like
VPD.sn ADDRESS=0x20 SIZE=0x0A
VPD.id ADDRESS=0x2A SIZE=0x14
So far the only option to get ADDRESS and SIZE information I found was
to run [avr-]gdb and use commands like print &VPD.sn or print
sizeof(VPD.sn)
2. I will write the script to load VPD.eep and VPD.map and based on
information in map file generate VPD_sn.eep
Do you see any nicer solution?
- [avr-gcc-list] Patching EEPROM image for production,
dimax un <=