The above video goes away if you are a member and logged in, so log in now!
Replacing EEPROM on CC1.1
Replacing EEPROM on CC1.1 –
Since I have the feeling that the EEPROM on my CC1.1 might be bad and I might have to replace it, here are some questions.
But first, why do I think it's bad?
The upgrade CD boots fine (Photo1: BM2.10, main menu).
Trying to to flash either fw30 or fw31 fails with "Failed programming firmware file!": (Photo2: Programming...)(Photo3: Failed).
After the 'failed programming' I have to reprogramm the firmware from an
old upgrade disk, so it definitely does _something_ to the eeprom.
Interesting: Programming with the old fwares takes much longer than with fw30 or fw31.
Also, fw30 and fw31 are quite a bit different from fw24/fw29:
-rw-r--r-- 1 ranma users 4100 2007-01-13 13:06 fware11-v24.cci
-rw-r--r-- 1 ranma users 4100 2007-01-13 13:05 fware11-v29.cci
-rw-r--r-- 1 ranma users 2355 2007-01-14 14:35 fware11-v31.cci
(v24 and v29 are zero-padded, actual sizes are 2206 and 2212 byte respectively, excluding the 32bit checksum)
So, the new firmware is 323 bytes larger than the old one and might be hitting bad cells in the EEPROM.
Now, on to the questions:
Can I hook up a Dataflash instead of the EEPROM to the CC11?
What about a bigger EEPROM, as long as its pin and interface are compatible, it should work, right (might be a bit difficult to get the exact same EEPROM)?
Incidentally, it seems a 16Mbit Dataflash costs only 3.5 EUR...
Originally Posted by ranmachan
The pins around the EEPROM are hooked up like this:
The top and bottom row are where the EEPROM (atmel 25320) is soldered onto.
GND /WP SO /CS
SI SCK /HOLD VCC
/HOLD and /WP are connected to VCC.
/RESET on the right row does not correspond to one of the top/bottom row pins, but is connected to the ASIC.
The left/right rows correspond to the dataflash pinout (e.g. atmel 45db011 as in the CC1.2 or the 45db161 I could get for 3.5 EUR).