Hi Carl-Daniel,
I've attached the logfile output as requested.
The SRCMOS .EXE utility that comes on the BIOS update image saves 256 bytes of
data. The older versions has 128 bytes of data and the remainder was all 00x.
The last version has data within the last 128 bytes and that makes all the
difference.
Whether the utility only processed the first 128 bytes initially and was
corrected to save/restore the extra 128 bytes I don't know but it certainly
does the trick now.
It is a DOS based utility and I've been able to configure a FreeDOS image under
GRUB so that it will boot it once to set the BIOS settings I need and then boot
back to the Linux OS.
Getting the settings out was a bit of a chore as I had to hex dump them to the
screen so I could take a picture (and then type them in) as the image can't be
updated and has no access to any other devices. Running the utility from a USB
device is no help either as the moment I disable USB in the BIOS I can't access
the utility to write the settings to a file.
Best Regards,
Mark Rowlinson, Principal Engineer, Unix Support
MISGB Implementation Distributed
Fujitsu
Heather Court, 6 Maidstone Road, Footscray, Sidcup, Kent DA14 5HH
Tel: +44 (0) 843 354 2262
Mob: +44 (0) 7867 829249
E-mail: [email protected]<mailto:[email protected]>
Web: http://uk.fujitsu.com<http://uk.fujitsu.com/>
Upcoming Annual Leave : None planned.
[cid:[email protected]]<http://www.youtube.com/user/fujitsuUK>
[cid:[email protected]] <http://www.facebook.com/fujitsuuk>
[cid:[email protected]] <http://twitter.com/#!/fujitsu_uk>
[cid:[email protected]]
<http://www.linkedin.com/company/fujitsu-uk-and-ireland>
[cid:[email protected]] <http://blog.uk.fujitsu.com/>
[cid:[email protected]]
<https://plus.google.com/103287532874520008913/>
Fujitsu is proud to partner with Action for
Children<http://www.actionforchildren.org.uk/>
I-CIO<http://www.i-cio.com/>: Global Intelligence for the CIO. Fujitsu's online
resource for ICT leaders
Reshaping ICT, Reshaping Business in partnership with
FT.com<http://reshaping-ict.ft.com/>
P Please consider the environment - do you really need to print this email?
From: Carl-Daniel Hailfinger [mailto:[email protected]]
Sent: 29 October 2015 00:37
To: Rowlinson Mark <[email protected]>; [email protected]
Subject: Re: [flashrom] Flash chip/chipset not found
Hi Mark,
would it be possible for you to generate a log file using the additional
parameter --output logfile.txt when doing a read of the flash chip, then send
that log file to us?
That would help us to finally merge support for the VT8251 chipset in your
point-of-sale IBM/Toshiba AnyPlace Kiosk Model 48xx series. We have a strict
rule that flashrom must be 100% reliable and thus we keep log files for any
newly supported/tested chipset around for reference. Your log file would be
used as reference for VT8251.
That said, it would be very interesting to know where the settings are actually
stored. Have you looked into the top 128 bytes of NVRAM? Maybe there is another
flash chip? Is there any way to trace what the save/restore tool does (i.e.
does it run on Linux)?
Regards,
Carl-Daniel
On 28.10.2015 23:25, Rowlinson Mark wrote:
> Hi Carl-Daniel,
>
> That change does allow the chipset to be recognised and it will write out the
> ROM. It seems to be the BIOS code only (no settings) as it doesn't change if
> I change any settings within the BIOS.
>
> I've been directed to a save/restore utility that comes on the BIOS update
> image and it seems the last version actually accesses the data I'm interested
> in so I'm investigating this route at the moment.
>
> Best Regards,
> Mark Rowlinson
>
> -----Original Message-----
> From: Carl-Daniel Hailfinger
> [mailto:[email protected]]
> Sent: 24 October 2015 09:22
> To: Rowlinson Mark
> <[email protected]<mailto:[email protected]>>;
> [email protected]<mailto:[email protected]>
> Subject: Re: [flashrom] Flash chip/chipset not found
>
> Hi Mark,
>
> this is a VIA VT8251 PCI to ISA Bridge you're using.
>
> I think Stefan Tauner (in CC) already was discussing something similar here:
> http://www.flashrom.org/pipermail/flashrom/2012-July/009552.html
> That email even has a patch attached.
>
>
> On 22.10.2015 22:24, Rowlinson Mark wrote:
>> Thanks for the swift response, I have attached output from the command
>> requested.
>>
>> The device in question is an IBM (now Toshiba) AnyPlace Kiosk Model
>> 4838-310. The models we have are a mixture of 4838-310 and 4838-330 and
>> support documentation refers to them as 4838-3xx.
> Heh, would be fun to add this to our tests.
>
> Regards,
> Carl-Daniel
>
Unless otherwise stated, this email has been sent from Fujitsu Services
Limited, from Fujitsu (FTS) Limited, or from Fujitsu Telecommunications Europe
Limited, together "Fujitsu".
This email is only for the use of its intended recipient. Its contents are
subject to a duty of confidence and may be privileged. Fujitsu does not
guarantee that this email has not been intercepted and amended or that it is
virus-free.
Fujitsu Services Limited, registered in England No 96056, registered office 22
Baker Street, London W1U 3BW.
Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22
Baker Street, London W1U 3BW.
PFU Imaging Solutions Europe Limited, registered in England No 1578652,
registered office Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE.
Fujitsu Telecommunications Europe Limited, registered in England No 2548187,
registered office Solihull Parkway, Birmingham Business Park, Birmingham, B37
7YU.
flashrom v0.9.8-r1888 on Linux 2.6.32-573.el6.i686 (i686)
flashrom was built with libpci 3.1.10, GCC 4.4.7 20120313 (Red Hat 4.4.7-16),
little endian
Command line (6 args): ./flashrom --programmer internal -r
/var/tmp/flashrom.read --output /var/tmp/logfile.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 660M loops per
second, 10 myus = 18 us, 100 myus = 101 us, 1000 myus = 1000 us, 10000 myus =
9993 us, 4 myus = 5 us, OK.
Initializing internal programmer
No coreboot table found.
Using Internal DMI decoder.
DMI string chassis-type: "Desktop"
DMI string system-manufacturer: "IBM CORPORATION"
DMI string system-product-name: "483831E"
DMI string system-version: "483831E"
DMI string baseboard-manufacturer: "IBM CORPORATION"
DMI string baseboard-product-name: "CN896-8251"
DMI string baseboard-version: "1.0"
Found chipset "VIA VT8251" with PCI ID 1106:3287.
This chipset is marked as untested. If you are using an up-to-date version
of flashrom *and* were (not) able to successfully update your firmware with it,
then please email a report to [email protected] including a verbose (-V)
log.
Thank you!
Enabling flash write... OK.
The following protocols are supported: Non-SPI.
Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0x49, id2 0x4d, id1
is normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0x49, id2 0x4d,
id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0x49, id2 0x4d,
id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0x49, id2 0x4d,
id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49(H)F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49F080, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49F080T, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH00B4, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT49LH004, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for ESMT F49B002UA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Eon EN29LV040(A), 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff
Probing for Eon EN29GL064(A)B, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Eon EN29GL064(A)T, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Eon EN29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Eon EN29GL128, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Fujitsu MBM29F400BC, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Fujitsu MBM29F400TC, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Fujitsu MBM29LV160BE, 2048 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Fujitsu MBM29LV160TE, 2048 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for ISSI IS29GL064B, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for ISSI IS29GL064T, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for ISSI IS29GL064H/L, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for ISSI IS29GL128H/L, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Macronix MX29F022(N)B, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Macronix MX29F022(N)T, 256 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX29GL320EB, 4096 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29GL320ET, 4096 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29GL320EH/L, 4096 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29GL640EB, 8192 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29GL640ET, 8192 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29GL640EH/L, 8192 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29GL128F, 16384 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xbf, id2
0x5b
Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information,
using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information,
using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0xb3, id2 0x33, id1
is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0x49, id2
0x4d, id1 is normal flash content, id2 is normal flash content
Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing
information, using default 10mS/40uS. probe_jedec_common: id1 0xbf, id2 0x5b
Found SST flash chip "SST49LF080A" (1024 kB, LPC) mapped at physical address
0xfff00000.
Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F400BB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29F400BT, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0xb3, id2 0x33, id1 is
normal flash content, id2 is normal flash content
Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity
violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for ST M50LPW080, 1024 kB: probe_82802ab: id1 0x49, id2 0x4d, id1 is
normal flash content, id2 is normal flash content
Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common:
id1 0xbf, id2 0x5b
Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1
parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old
Winbond W29* probe method disabled because the probing sequence puts the AMIC
A49LF040A in a funky state. Use 'flashrom -c
W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip.
Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB:
probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xbf,
id2 0x5b
Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W29GL032CB, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Winbond W29GL032CT, 4096 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Winbond W29GL032CH/L, 4096 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Winbond W29GL064CB, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Winbond W29GL064CT, 8192 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Winbond W29GL064CH/L, 8192 kB: probe_jedec_29gl: man_id 0xff,
dev_id 0xffffff, man_id parity violation, man_id seems to be normal flash
content, dev_id seems to be normal flash content
Probing for Winbond W29GL128C, 16384 kB: probe_jedec_29gl: man_id 0xff, dev_id
0xffffff, man_id parity violation, man_id seems to be normal flash content,
dev_id seems to be normal flash content
Probing for Winbond W39F010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39L010, 128 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39L020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xbf, id2 0x5b
Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1
0xbf, id2 0x5b
Found SST flash chip "SST49LF080A" (1024 kB, LPC).
Reading flash... done.
Restoring PCI config space for 00:11:0 reg 0x40
Restoring PCI config space for 00:11:0 reg 0x41
_______________________________________________
flashrom mailing list
[email protected]
http://www.flashrom.org/mailman/listinfo/flashrom
