Dell Vostro V13 Laptop flashrom found something

List overview All Threads
Download

newer

older

Results Asus Rampage II Extreme...

[commit] r1130 - trunk

XVilka Haos of System

2 Aug 2010 2 Aug '10

2:11 p.m.

Hi! I'm tried newest flashrom on newest kernel from git

Caption: Dell Vostro V13 Product Link: http://www.dell.com/us/en/business/notebooks/vostro-v13/pd.aspx?refid=vostro... Board Vendor: Dell Inc. Board name: 0R45H1 CPU: Intel® Celeron 743 (1.2GHz, 1MB L2 cache) (Ultra Low Voltage) Chipset: Mobile Intel® GS45 Express Chipset ICH9M-Enhanced Graphics: Intel Graphics Media Accelerator (GMA) 4500MHD Northbridge: GS45-GMHC Southbridge: ICH9M-E Motion Sensor: STM DE351DL

DRAM bus width: 64-bit buses Processor address bus width: 36 bits Flash EPROM: SPI 16 Mbits PCI bus: 32 bits, 33 MHz

Dissassebmle: http://blog.screenaid.com/2010/02/03/dell-vostro-v13-disassembly/

Service manual: http://support.dell.com/support/edocs/systems/vosV13/en/sm/specs.htm Super I/O chip: ITE IT8502E Embedded controller chip: ITE IT8502E Flash chip: Winbond 25Q16BVSIG

Flashrom found something when tried to check flash chip id1=4e id2=44

-- Best regards, XVilka.

Attachments:

acpitool.log.gz (application/x-gzip — 666 bytes)
flashrom.log (application/octet-stream — 26.5 KB)
superiotool.log (application/octet-stream — 5.4 KB)
inteltool.log (application/octet-stream — 177.2 KB)
dmesg.log (application/octet-stream — 75.5 KB)
lspci.log (application/octet-stream — 162.9 KB)
lsusb.log (application/octet-stream — 1.4 KB)
dmidecode.log.gz (application/x-gzip — 4.0 KB)
biosdecode.log.gz (application/x-gzip — 361 bytes)

Show replies by date

Michael Karcher

2 Aug 2 Aug

3:30 p.m.

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

5226

days inactive

5226

days old

flashrom@flashrom.org

1 comments

2 participants

tags (0)

participants (2)

Michael Karcher
XVilka Haos of System