Re: [flashrom] Read the content of AT49F002(N)T on Syntax SV266A

[Paul Menzel]

[ Please CC me, as I am not subscribed. ]
[ This thread was started on the coreboot list [1]. ]

[1] http://www.coreboot.org/pipermail/coreboot/2009-March/045774.html

Am Sonntag, den 22.03.2009, 19:43 +0100 schrieb Paul Menzel:
> Am Montag, den 23.03.2009, 02:29 +0800 schrieb FENG Yu Ning:
> > 2009/3/23 Paul Menzel :
>
> […]
> > > I tried flashrom with the different delays (10, 100, 1000, 10000, 40000
> > > all in us) afterwards, but the image did not differ.
> >
> > How about probing? does auto-detect work now?
>
> I am afraid it does not.
>
> $ cat /proc/mtrr
> reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
> reg01: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1
> reg02: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1
> reg03: base=0xd8000000 (3456MB), size=  64MB: write-combining, count=1
> reg04: base=0xfffc0000 (4095MB), size= 256KB: uncachable, count=1
> $ $ sudo ./flashrom -V
> Calibrating delay loop... 490M loops per second, 100 myus = 141 us. OK.

[…]

Currently I am having access to this machine again, so I tried with
v0.9.2-r1033. Unfortunately I still cannot report success on
auto-detection.

Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec_common: id1 0x25, id2 0xe4, id1 is normal flash content, id2 is normal flash content
    […]
    No EEPROM/flash device found.
    Note: flashrom can never write if the flash chip isn't found automatically.

Did something change in the flashrom infrastructure/source, that makes
adding support for this board easier than over a year ago?

I checked different probe timings (10, 100, 1000, 10000, 40000; all in
us) modifying `flashchips.c` and with and without modifying the MTRR
settings.

$ cat /proc/mtrr
        reg00: base=0x000000000 (    0MB), size=  512MB, count=1: write-back
        reg01: base=0x0d0000000 ( 3328MB), size=  128MB, count=1: write-combining
        reg02: base=0x0d0000000 ( 3328MB), size=  128MB, count=1: write-combining
        reg03: base=0x0d8000000 ( 3456MB), size=  128MB, count=1: write-combining
        $ sudo sh -c 'echo "base=0xfffc0000 size=0x40000 type=uncachable" >| /proc/mtrr'
        $ more /proc/mtrr
        reg00: base=0x000000000 (    0MB), size=  512MB, count=1: write-back
        reg01: base=0x0d0000000 ( 3328MB), size=  128MB, count=1: write-combining
        reg02: base=0x0d0000000 ( 3328MB), size=  128MB, count=1: write-combining
        reg03: base=0x0d8000000 ( 3456MB), size=  128MB, count=1: write-combining
        reg04: base=0x0fffc0000 ( 4095MB), size=  256KB, count=1: uncachable

Probably unrelated but back then the output for `reg03` was different.

reg03: base=0xd8000000 (3456MB), size=  64MB: write-combining, count=1

I am probably forced to do a BIOS upgrade on this board. Is there a
chance I will be able to do this using flashrom?

Thanks,

Paul

Read the content of AT49F002(N)T on Syntax SV266A

[Carl-Daniel Hailfinger]

On 06.06.2010 15:40, Paul Menzel wrote:
> [ Please CC me, as I am not subscribed. ]
> [ This thread was started on the coreboot list [1]. ]
>
> [1] http://www.coreboot.org/pipermail/coreboot/2009-March/045774.html
>
> Am Sonntag, den 22.03.2009, 19:43 +0100 schrieb Paul Menzel:
> > Am Montag, den 23.03.2009, 02:29 +0800 schrieb FENG Yu Ning:
> > > 2009/3/23 Paul Menzel :
> >
> > […]
> > > > I tried flashrom with the different delays (10, 100, 1000, 10000, 40000
> > > > all in us) afterwards, but the image did not differ.
> > >
> > > How about probing? does auto-detect work now?
> >
> > I am afraid it does not.
>
> […]
>
> Currently I am having access to this machine again, so I tried with
> v0.9.2-r1033. Unfortunately I still cannot report success on
> auto-detection.
>
> flashrom v0.9.2-r1033 on Linux 2.6.32-5-686 (i686), built with libpci 3.1.7, GCC 4.4.4, little endian
> Initializing internal programmer
> No coreboot table found.
> DMI string system-manufacturer: "VIA Technologies, Inc."
> DMI string system-product-name: "VT8367-8235"
> DMI string system-version: " "
> DMI string baseboard-manufacturer: " "
> DMI string baseboard-product-name: "VT8367-8235"
> DMI string baseboard-version: " "
> DMI string chassis-type: "Desktop"

Mh. So the DMI strings are completely useless.
> Found ITE Super I/O, id 8705

That's good. Really good.

I just sent a patch titled "Add IT8705 autodetection" to the flashrom
list (you're in CC). Could you apply that patch against latest flashrom
from svn and test probing again? Write might still fail (in fact, that's
pretty likely), but if detection works, this is a big step forward.
> Found chipset "VIA VT8235", enabling flash write... chipset PCI ID is 1106:3177, OK.
> This chipset supports the following protocols: Non-SPI.
> SuperI/O ID 8705 is not on the controller list.
> [...]
> No EEPROM/flash device found.

Should be fixed with my patch.
> Did something change in the flashrom infrastructure/source, that makes
> adding support for this board easier than over a year ago?

Yes, indeed.
> I am probably forced to do a BIOS upgrade on this board. Is there a
> chance I will be able to do this using flashrom?

Yes, of course.

Regards,
Carl-Daniel

Read the content of AT49F002(N)T on Syntax SV266A

[Paul Menzel]

Am Montag, den 07.06.2010, 03:22 +0200 schrieb Carl-Daniel Hailfinger:
> On 06.06.2010 15:40, Paul Menzel wrote:
> > [ Please CC me, as I am not subscribed. ]

[ I am subscribed to [e-mail] now. ]
> > Am Sonntag, den 22.03.2009, 19:43 +0100 schrieb Paul Menzel:
> > > Am Montag, den 23.03.2009, 02:29 +0800 schrieb FENG Yu Ning:
> > > > 2009/3/23 Paul Menzel :
> > >
> > > […]
> > > > > I tried flashrom with the different delays (10, 100, 1000, 10000, 40000
> > > > > all in us) afterwards, but the image did not differ.
> > > >
> > > > How about probing? does auto-detect work now?
> > >
> > > I am afraid it does not.
> >
> > […]
> >
> > Currently I am having access to this machine again, so I tried with
> > v0.9.2-r1033. Unfortunately I still cannot report success on
> > auto-detection.
> >
> > flashrom v0.9.2-r1033 on Linux 2.6.32-5-686 (i686), built with libpci 3.1.7, GCC 4.4.4, little endian
> > Initializing internal programmer
> > No coreboot table found.
> > DMI string system-manufacturer: "VIA Technologies, Inc."
> > DMI string system-product-name: "VT8367-8235"
> > DMI string system-version: " "
> > DMI string baseboard-manufacturer: " "
> > DMI string baseboard-product-name: "VT8367-8235"
> > DMI string baseboard-version: " "
> > DMI string chassis-type: "Desktop"
>
> Mh. So the DMI strings are completely useless.
> > Found ITE Super I/O, id 8705
>
> That's good. Really good.
>
> I just sent a patch titled "Add IT8705 autodetection" to the flashrom
> list (you're in CC). Could you apply that patch against latest flashrom
> from svn and test probing again?

Yes it worked! I responded to your patch. Thanks!
> Write might still fail (in fact, that's
> pretty likely), but if detection works, this is a big step forward.
> > Found chipset "VIA VT8235", enabling flash write... chipset PCI ID is 1106:3177, OK.
> > This chipset supports the following protocols: Non-SPI.
> > SuperI/O ID 8705 is not on the controller list.
> > [...]
> > No EEPROM/flash device found.
>
> Should be fixed with my patch.

Yes it is. See above.

[…]
> > I am probably forced to do a BIOS upgrade on this board. Is there a
> > chance I will be able to do this using flashrom?
>
> Yes, of course.

I know, it was a stupid question. ;-)

I also tried `-Vr` and the first line of the read image did not change
though. But was expected, I guess.

0000000: 25e4 2d6c 6835 2d6f 2901 0000 0002 0000
        %.-lh5-o).......

Thanks,

Paul