On Sun, 26 Feb 2006 16:55:54 +0100 Peter Stuge stuge-linuxbios@cdy.org wrote:
On Sun, Feb 26, 2006 at 06:00:07PM +0300, Anton Borisov wrote:
Hello. There is a tricky case - I can't see which exactly flash chip installed in system. flashrom from v2161 was unable to identify it too. I found an interesting site - http://ctflasher.sourceforge.net
- however this tool doesn't have bios-flasher yet.
If the requirement is to use software only then perhaps you can make flashrom print vendor ID and product ID - and use that as reference?
Alas, nothing informative.
Calibrating timer since microsleep sucks ... takes a second Setting up microsecond timing loop 788M loops per second OK, calibrated, now do the deed Trying Am29F040B, 512 KB probe_29f040b: id1 0xff, id2 0xff Trying At29C040A, 512 KB probe_jedec: id1 0xff, id2 0xff Trying Mx29f002, 256 KB probe_29f002: id1 0xdf, id2 0x24 Trying SST29EE020A, 256 KB probe_jedec: id1 0xdf, id2 0x24 Trying SST28SF040A, 512 KB probe_28sf040: id1 0xff, id2 0xff Trying SST39SF020A, 256 KB probe_jedec: id1 0xdf, id2 0x24 Trying SST39VF020, 256 KB probe_jedec: id1 0xdf, id2 0x24 Trying SST49LF040, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF002A/B, 256 KB probe_jedec: id1 0xdf, id2 0x24 Trying SST49LF003A/B, 384 KB probe_jedec: id1 0x47, id2 0x97 Trying SST49LF004A/B, 512 KB probe_jedec: id1 0xff, id2 0xff Trying SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Trying Pm49FL004, 512 KB probe_jedec: id1 0xff, id2 0xff Trying W29C011, 128 KB probe_jedec: id1 0xff, id2 0xff Trying W29C020C, 256 KB probe_jedec: id1 0xdf, id2 0x24 Trying W49F002U, 256 KB probe_jedec: id1 0xdf, id2 0x24 Trying M29F400BT, 512 KB probe_m29f400bt: id1 0xff, id2 0xff Trying 82802ab, 512 KB probe_82802ab: id1 0xff, id2 0xff Trying 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Trying MD-2802 (M-Systems DiskOnChip Millennium Module), 8 KB probe_md2802: probe_md2802: ******************************* probe_md2802: * THIS IS A PRE ALPHA VERSION * probe_md2802: * IN THE DEVELOPEMENT ********* probe_md2802: * PROCESS RIGHT NOW. ********** probe_md2802: ******************************* probe_md2802: * IF YOU ARE NOT A DEVELOPER ** probe_md2802: * THEN DO NOT TRY TO READ OR ** probe_md2802: * WRITE TO THIS DEVICE ******** probe_md2802: ******************************* probe_md2802: probe_md2802: switching off reset mode ... probe_md2802: switching off reset mode ... done probe_md2802: probe_md2802: switching off write protection ... probe_md2802: switching off write protection ... done probe_md2802: probe_md2802: IPL_0x0000: 0x00 probe_md2802: IPL_0x0001: 0x00 probe_md2802: IPL_0x0002: 0x00 probe_md2802: IPL_0x0003: 0x00 probe_md2802: probe_md2802: ChipID: 0x8c probe_md2802: DOCStatus: 0xc8 probe_md2802: FloorSelect: 0x00 probe_md2802: CDSNControl: 0xf0 probe_md2802: CDSNDeviceSelect: 0x3d probe_md2802: ECCConfiguration: 0x00 probe_md2802: CDSNSlowIO: 0x00 probe_md2802: ECCSyndrome0: 0xe3 probe_md2802: ECCSyndrome1: 0x8e probe_md2802: ECCSyndrome2: 0x00 probe_md2802: ECCSyndrome3: 0xf0 probe_md2802: ECCSyndrome4: 0x00 probe_md2802: ECCSyndrome5: 0x00 probe_md2802: AliasResolution: 0x00 probe_md2802: ConfigurationInput: 0x00 probe_md2802: ReadPipelineInitialization: 0x00 probe_md2802: LastDataRead: 0x00 probe_md2802: probe_md2802: checking ECCConfiguration toggle bit probe_md2802: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 probe_md2802: toggle result: 0/0 EEPROM not found
If you do have access to the hardware I suggest identifying the flash chip visually.
Unfortunately, I don't have it.