[flashrom] Dell Vostro V13 Laptop flashrom found something

[Michael Karcher]

Am Montag, den 02.08.2010, 12:11 +0000 schrieb XVilka Haos of System:
> Flashrom found something when tried to check flash chip id1=4e id2=44
That doesn't mean anything. The lines where something was "found" are,
sorted by size:

| Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
| Probing for Winbond W39V080FA (dual mode), 512 KB: probe_jedec_common: id1 0x4e, id2 0x41, id1 parity violation, id1 is normal flash content, id2 is normal flash content
"Probing" on FWH/Parallel/LPC chips (having a memory-mapped interface)
works by writing magic bytes to magic addresses, and magically reading
ID bytes from the flash chip instead of standard flash data. If the chip
can not be probed the way flashrom is trying, it still returns the same
old flash memory contents as it always does. The probes I quoted also
detect the condition "... is normal flash content". What I can tell you
is that at offset 0x180000 of your 2MB flash chip the first two bytes
are 4e and 41.

| Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
| Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
| Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
| Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
| Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
| Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
| Probing for Winbond W39V080FA, 1024 KB: probe_jedec_common: id1 0xdf, id2 0x28, id1 is normal flash content, id2 is normal flash content
This tells you that at offset 0x100000 the two flash data bytes are df and 28

| Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0x02, id2 0x00, id1 is normal flash content, id2 is normal flash content
| Probing for SST SST49LF016C, 2048 KB: probe_82802ab: id1 0x02, id2 0x00, id1 is normal flash content, id2 is normal flash content
And your flash chip starts with 02 00.

Regards,
  Michael Karcher