flashrom verify fails, CK804, MCP55

[Tiago Marques]

On two boards, one MCP55 based and another CK804, if I flash the
proprietary BIOS with: flasrom -wv bios.bin
Verification fails and if I try to boot, it doesn't. Have to flash the
BIOS in another board based on K8T890 that I have. In that one all
works fine, with both BIOS chips I have - one winbond and a PMC.
Haven't tried flashing coreboot due to lack of support.
Since the chipsets are support, this isn't supposed to happen, right?
Best regards,
                             Tiago Marques


On 1/27/08, Stefan Reinauer <stepan(a)coresystems.de&gt; wrote:
 * Tiago Marques <tiagomnm(a)gmail.com&gt; [080127 16:21]:
 > Hi.
 > Both failed, tried with two different BIOS chips.
 > Flashing with AWDFlash works fine though.
 > Had to flash it again in a VIA K8T890 board, which works flawlessly.
 > Any ideas, fix?

 What's the problem?

 --
 coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
       Tel.: [phone] • Fax: [phone]
 Email: info(a)coresystems.de  • http://www.coresystems.de/
 Registergericht: Amtsgericht Freiburg • HRB 7656
 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

[Ward Vandewege]

On Sun, Jan 27, 2008 at 06:06:45PM +0000, Tiago Marques wrote:
 On two boards, one MCP55 based and another CK804, if I flash the
 proprietary BIOS with: flasrom -wv bios.bin
 Verification fails and if I try to boot, it doesn't. Have to flash the
 BIOS in another board based on K8T890 that I have. In that one all
 works fine, with both BIOS chips I have - one winbond and a PMC.
 Haven't tried flashing coreboot due to lack of support.
 Since the chipsets are support, this isn't supposed to happen, right?
Which board(s)? Which superio? I'm assuming your bios is a plcc chip, not an
spi chip?

Thanks,
Ward.

-- 
Ward Vandewege <ward(a)fsf.org&gt;
Free Software Foundation - Senior System Administrator

[Tiago Marques]

Yes, PLCC.
SuperIO?
The chips are a w39v040B and a Pm49FL004.

                    Tiago Marques


On 1/27/08, Ward Vandewege <ward(a)gnu.org&gt; wrote:
 On Sun, Jan 27, 2008 at 06:06:45PM +0000, Tiago Marques wrote:
 > On two boards, one MCP55 based and another CK804, if I flash the
 > proprietary BIOS with: flasrom -wv bios.bin
 > Verification fails and if I try to boot, it doesn't. Have to flash the
 > BIOS in another board based on K8T890 that I have. In that one all
 > works fine, with both BIOS chips I have - one winbond and a PMC.
 > Haven't tried flashing coreboot due to lack of support.
 > Since the chipsets are support, this isn't supposed to happen, right?

 Which board(s)? Which superio? I'm assuming your bios is a plcc chip, not an
 spi chip?

 Thanks,
 Ward.

 --
 Ward Vandewege <ward(a)fsf.org&gt;
 Free Software Foundation - Senior System Administrator

[Carl-Daniel Hailfinger]

On 27.01.2008 20:19, Tiago Marques wrote:
 Yes, PLCC.
 SuperIO?
See http://www.coreboot.org/Superiotool for details.

 The chips are a w39v040B and a Pm49FL004.
Which boards? We need exact vendor name, board name and revision.

Regards,
Carl-Daniel

[Ward Vandewege]

On Sun, Jan 27, 2008 at 07:19:55PM +0000, Tiago Marques wrote:
 Yes, PLCC.
 SuperIO?
 The chips are a w39v040B and a Pm49FL004.
What *motherboards*? That will tell us which superio is on the board.

Thanks,
Ward.

-- 
Ward Vandewege <ward(a)fsf.org&gt;
Free Software Foundation - Senior System Administrator

[Tiago Marques]

I know that has the hardware monitoring chip.
The MCP55 motherboard is a jetway M25GT6 which has the Fintek F71882FG.
The CK804 is a Biostar NF4ST-A9 which has the ITE IT8712F-A.

Tiago Marques

On 1/27/08, Ward Vandewege <ward(a)gnu.org&gt; wrote:
 On Sun, Jan 27, 2008 at 07:19:55PM +0000, Tiago Marques wrote:
 > Yes, PLCC.
 > SuperIO?
 > The chips are a w39v040B and a Pm49FL004.

 What *motherboards*? That will tell us which superio is on the board.

 Thanks,
 Ward.

 --
 Ward Vandewege <ward(a)fsf.org&gt;
 Free Software Foundation - Senior System Administrator

[Tiago Marques]

Any ideas? From where should I start?

Tiago Marques


On 1/27/08, Tiago Marques <tiagomnm(a)gmail.com&gt; wrote:
 I know that has the hardware monitoring chip.
 The MCP55 motherboard is a jetway M25GT6 which has the Fintek F71882FG.
 The CK804 is a Biostar NF4ST-A9 which has the ITE IT8712F-A.

 Tiago Marques

 On 1/27/08, Ward Vandewege <ward(a)gnu.org&gt; wrote:
 > On Sun, Jan 27, 2008 at 07:19:55PM +0000, Tiago Marques wrote:
 > > Yes, PLCC.
 > > SuperIO?
 > > The chips are a w39v040B and a Pm49FL004.
 >
 > What *motherboards*? That will tell us which superio is on the board.
 >
 > Thanks,
 > Ward.
 >
 > --
 > Ward Vandewege <ward(a)fsf.org&gt;
 > Free Software Foundation - Senior System Administrator
 >

[Carl-Daniel Hailfinger]

On 29.01.2008 18:59, Tiago Marques wrote:
 Any ideas? From where should I start?
Try to erase a chip with "flashrom -E" (just erase, no write, no verify)
and then read back the contents with "flashrom -r". Look at the
resulting file with xxd or hexdump and check if it is all 0xff.
I suspect that it will not be all 0xff when erased in the problematic
boards, but it will be all 0xff when erased in the K8T890 board.

Regards,
Carl-Daniel

-- 
http://www.hailfinger.org/

[Tiago Marques]

Finally had some time to test this.
The erase command does nothing, I was still able to download the full
BIOS and boot the machine. This using the latest flashrom revision.
First step is to make it erase? Where should I start?

Best regards


On 2/8/08, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net&gt; wrote:
 On 29.01.2008 18:59, Tiago Marques wrote:
  > Any ideas? From where should I start?
  >


 Try to erase a chip with "flashrom -E" (just erase, no write, no verify)
  and then read back the contents with "flashrom -r". Look at the
  resulting file with xxd or hexdump and check if it is all 0xff.
  I suspect that it will not be all 0xff when erased in the problematic
  boards, but it will be all 0xff when erased in the K8T890 board.

  Regards,
  Carl-Daniel


  --
  http://www.hailfinger.org/

[Tiago Marques]

help?


On 6/1/08, Tiago Marques <tiagomnm(a)gmail.com&gt; wrote:
 Finally had some time to test this.
  The erase command does nothing, I was still able to download the full
  BIOS and boot the machine. This using the latest flashrom revision.
  First step is to make it erase? Where should I start?

  Best regards



  On 2/8/08, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net&gt; wrote:
  > On 29.01.2008 18:59, Tiago Marques wrote:
  >  > Any ideas? From where should I start?
  >  >
  >
  >
  > Try to erase a chip with "flashrom -E" (just erase, no write, no verify)
  >  and then read back the contents with "flashrom -r". Look at the
  >  resulting file with xxd or hexdump and check if it is all 0xff.
  >  I suspect that it will not be all 0xff when erased in the problematic
  >  boards, but it will be all 0xff when erased in the K8T890 board.
  >
  >  Regards,
  >  Carl-Daniel
  >
  >
  >  --
  >  http://www.hailfinger.org/
  >
  >

[Carl-Daniel Hailfinger]

On 05.06.2008 21:59, Tiago Marques wrote:
 help?


 On 6/1/08, Tiago Marques <tiagomnm(a)gmail.com&gt; wrote:
   
> Finally had some time to test this.
>  The erase command does nothing, I was still able to download the full
>  BIOS and boot the machine. This using the latest flashrom revision.
>  First step is to make it erase? Where should I start?
>
Sorry, I will be unavailable for the rest of the month due to diploma
thesis work. I hope you can find somebody else on this list to help you.


Regards,
Carl-Daniel

[Tiago Marques]

Help!
Can't someone give me some pointers?
Tks,
            Tiago Marques



On 6/5/08, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net&gt; wrote:
 On 05.06.2008 21:59, Tiago Marques wrote:
  > help?
  >
  >
  > On 6/1/08, Tiago Marques <tiagomnm(a)gmail.com&gt; wrote:
  >
  >> Finally had some time to test this.
  >>  The erase command does nothing, I was still able to download the full
  >>  BIOS and boot the machine. This using the latest flashrom revision.
  >>  First step is to make it erase? Where should I start?
  >>


 Sorry, I will be unavailable for the rest of the month due to diploma
  thesis work. I hope you can find somebody else on this list to help you.


  Regards,

 Carl-Daniel

[Peter Stuge]

Dear Tiago,

On Sun, Jun 01, 2008 at 04:09:07PM +0100, Tiago Marques wrote:
 Finally had some time to test this.
 The erase command does nothing, I was still able to download the
 full BIOS and boot the machine. This using the latest flashrom
 revision. First step is to make it erase? Where should I start?
If this is the case with both Winbond and PMC flash chips it seems
like the write disable signals to the chip were set, but in that
case it would not have been possible for flashrom to PROBE
successfully. Hm.

I am interested in debugging this. Would it be possible for you to
join our IRC channel sometime for a more effective session?

irc.freenode.net #coreboot

If not, we can do email too. :)


//Peter

[Tiago Marques]

I would rather do it by e-mail, for now.
What information would you need?
Best regards


On 6/21/08, Peter Stuge <peter(a)stuge.se&gt; wrote:
 Dear Tiago,


  On Sun, Jun 01, 2008 at 04:09:07PM +0100, Tiago Marques wrote:
  > Finally had some time to test this.
  > The erase command does nothing, I was still able to download the
  > full BIOS and boot the machine. This using the latest flashrom
  > revision. First step is to make it erase? Where should I start?


 If this is the case with both Winbond and PMC flash chips it seems
  like the write disable signals to the chip were set, but in that
  case it would not have been possible for flashrom to PROBE
  successfully. Hm.

  I am interested in debugging this. Would it be possible for you to
  join our IRC channel sometime for a more effective session?

  irc.freenode.net #coreboot

  If not, we can do email too. :)


  //Peter


  --
  coreboot mailing list
  coreboot(a)coreboot.org
  http://www.coreboot.org/mailman/listinfo/coreboot