chip "PMC Pm29F002T" test results

[Tadas S]

Hello,
Chip "PMC Pm29F002T" is working right with flashrom as I can see.
Verbose logs attached. Is that information enough?

Regards,
Tadas

[Uwe Hermann]

On Fri, Sep 03, 2010 at 12:11:56AM +0300, Tadas S wrote:
> Hello,
> Chip "PMC Pm29F002T" is working right with flashrom as I can see.
> Verbose logs attached. Is that information enough?

Yep, thanks, we marked the chip as tested now. Please also let us know
which mainboard this is so we can also mark it as tested.

Also, please install "dmidecode" if possible (gives us more info in the
flashrom logs) and repost the following logs for completeness:

- flashrom -V -w foo.bin

- lspci -nnvvvxxx

- superiotool -deV

Thanks, Uwe.

[Tadas S]

Mainboard is MSI MS-6119. I used dmidecode 2.10. "foo.bin" replaced with
working image filename.
Superiotool from coreboot isn't working right, it started the login console
somehow, so the log isn't complete. Any suggestions? :)

2010/9/5 Uwe Hermann
> On Fri, Sep 03, 2010 at 12:11:56AM +0300, Tadas S wrote:
> > Hello,
> > Chip "PMC Pm29F002T" is working right with flashrom as I can see.
> > Verbose logs attached. Is that information enough?
>
> Yep, thanks, we marked the chip as tested now. Please also let us know
> which mainboard this is so we can also mark it as tested.
>
> Also, please install "dmidecode" if possible (gives us more info in the
> flashrom logs) and repost the following logs for completeness:
>
> flashrom -V -w foo.bin
>
> lspci -nnvvvxxx
>
> superiotool -deV
> Thanks, Uwe.
>
> http://hermann-uwe.de     | http://sigrok.org
> http://randomprojects.org | http://unmaintained-free-software.org

[Uwe Hermann]

On Sun, Sep 05, 2010 at 06:22:42PM +0300, Tadas S wrote:
> Mainboard is MSI MS-6119. I used dmidecode 2.10. "foo.bin" replaced with
> working image filename.

Thanks.
> Superiotool from coreboot isn't working right, it started the login console
> somehow, so the log isn't complete. Any suggestions? :)

I don't understand the question. The superiotool output you attached
looks OK.
> flashrom v0.9.2-r1146 on Linux 2.6.34-ARCH (i686), built with libpci 3.1.7, GCC 4.5.0 20100610 (prerelease), little endian
> flashrom is free software, get the source code at http://www.flashrom.org
>
> Calibrating delay loop... OS timer resolution is 5 usecs, 199M loops per second, 10 myus = 13 us, 100 myus = 102 us, 1000 myus = 997 us, 10000 myus = 10047 us, 20 myus = 23 us, OK.
> Initializing internal programmer
> No coreboot table found.
> DMI string system-manufacturer: ""
> DMI string system-product-name: ""
> DMI string system-version: ""
> DMI string baseboard-manufacturer: ""
> DMI string baseboard-product-name: ""
> DMI string baseboard-version: ""
> DMI string chassis-type: ""

The empty DMI strings are due to you running on coreboot (which doesn't
provide DMI tables usually). Could you retry the write operation using
the vendor BIOS and post that output? Thanks!
> This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
> The test status of this chip may have been updated in the latest development
> version of flashrom. If you are running the latest development version,
> please email a report to [e-mail] if any of the above operations
> work correctly for you with this flash part. Please include the flashrom
> output with the additional -V option for all operations you tested (-V, -Vr,
> -Vw, -VE), and mention which mainboard or programmer you tested.
> Thanks for your help!
> ===
> coreboot last image size (not ROM size) is 262144 bytes.

Hm, I guess this string could use some clarification/rewording, it
probably just confuses most users (including myself).
> Manufacturer: MSI
> Mainboard ID: MS-6119
> Note: If the following flash access fails, try -m <vendor>:<mainboard>.
> Writing flash chip... Erasing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x01ffff, 0x020000-0x037fff, 0x038000-0x039fff, 0x03a000-0x03bfff, 0x03c000-0x03ffff, 
> SUCCESS.
> Programming page: address: 0x00000000 [...] DONE
> COMPLETE.
> Verifying flash... VERIFIED.

Looks good.

We'll mark your board as supported soon.

Uwe.

[Tadas S]

> > coreboot last image size (not ROM size) is 262144 bytes.
>
> Hm, I guess this string could use some clarification/rewording, it
> probably just confuses most users (including myself).

I don't understand, was this quote in my message?

2010/9/7, Uwe Hermann :
> On Sun, Sep 05, 2010 at 06:22:42PM +0300, Tadas S wrote:
> > Mainboard is MSI MS-6119. I used dmidecode 2.10. "foo.bin" replaced with
> > working image filename.
>
> Thanks.
> > Superiotool from coreboot isn't working right, it started the login
> > console
> > somehow, so the log isn't complete. Any suggestions? :)
>
> I don't understand the question. The superiotool output you attached
> looks OK.
> > flashrom v0.9.2-r1146 on Linux 2.6.34-ARCH (i686), built with libpci
> > 3.1.7, GCC 4.5.0 20100610 (prerelease), little endian
> > flashrom is free software, get the source code at http://www.flashrom.org
> >
> > Calibrating delay loop... OS timer resolution is 5 usecs, 199M loops per
> > second, 10 myus = 13 us, 100 myus = 102 us, 1000 myus = 997 us, 10000 myus
> > = 10047 us, 20 myus = 23 us, OK.
> > Initializing internal programmer
> > No coreboot table found.
> > DMI string system-manufacturer: ""
> > DMI string system-product-name: ""
> > DMI string system-version: ""
> > DMI string baseboard-manufacturer: ""
> > DMI string baseboard-product-name: ""
> > DMI string baseboard-version: ""
> > DMI string chassis-type: ""
>
> The empty DMI strings are due to you running on coreboot (which doesn't
> provide DMI tables usually). Could you retry the write operation using
> the vendor BIOS and post that output? Thanks!
> > This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
> > The test status of this chip may have been updated in the latest
> > development
> > version of flashrom. If you are running the latest development version,
> > please email a report to [e-mail] if any of the above
> > operations
> > work correctly for you with this flash part. Please include the flashrom
> > output with the additional -V option for all operations you tested (-V,
> > -Vr,
> > -Vw, -VE), and mention which mainboard or programmer you tested.
> > Thanks for your help!
> > ===
> > coreboot last image size (not ROM size) is 262144 bytes.
>
> Hm, I guess this string could use some clarification/rewording, it
> probably just confuses most users (including myself).
> > Manufacturer: MSI
> > Mainboard ID: MS-6119
> > Note: If the following flash access fails, try -m <vendor>:<mainboard>.
> > Writing flash chip... Erasing flash chip... Looking at blockwise erase
> > function 0... trying... 0x000000-0x01ffff, 0x020000-0x037fff,
> > 0x038000-0x039fff, 0x03a000-0x03bfff, 0x03c000-0x03ffff,
> > SUCCESS.
> > Programming page: address: 0x00000000 [...] DONE
> > COMPLETE.
> > Verifying flash... VERIFIED.
>
> Looks good.
>
> We'll mark your board as supported soon.
> Uwe.
>
> http://hermann-uwe.de     | http://sigrok.org
> http://randomprojects.org | http://unmaintained-free-software.org

[Uwe Hermann]

On Tue, Sep 07, 2010 at 10:17:26PM +0300, Tadas S wrote:
> > > coreboot last image size (not ROM size) is 262144 bytes.
> >
> > Hm, I guess this string could use some clarification/rewording, it
> > probably just confuses most users (including myself).
>
> I don't understand, was this quote in my message?

It was some output of flashrom itself which we should probably
improve. Don't worry about it.

Uwe.