Re: [flashrom] support for delta mp2-bx-x motherboard (tested)

On Thu, May 29, 2008 at 11:58:10AM +0300, Andriy Gapon wrote:

> This board can not be uniquely identified by PCI devices, all of them
> are part of 440BX/PIIX4E chipset.

>  	 "artecgroup", "dbe62", "Artec Group DBE62", board_artecgroup_dbe6x},
>   	{0x8086, 0x27b8, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000,
>   	 "kontron", "986lcd-m", "Kontron 986LCD-M", board_kontron_986lcd_m},
> +	{0x8086, 0x7113, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000, 0x0000,
> +	 "delta", "mp2-bx-x", "Delta MP2-BX-X", board_mp2_bx_x},
>  	{0, 0, 0, 0, 0, 0, 0, 0, NULL, NULL}	/* Keep this */
>  };
>  

I see a lot of 0's in the pci-id list, same for the kontron board.

Surely at least one other set of main device ids can be put in there. 
Due to the lack of subsystem ids this will not give you unique 
identification, but this will provide an additional safeguard.

For the recent kontron board, though, nothing less than a full set seems 
acceptable. Unless kontron, as an embedded vendor, couldn't be bothered 
with card ids as usual.

Luc Verhaegen.
SUSE/Novell X Driver Developer.

--

-- 
coreboot mailing list
coreboot <at> coreboot.org

Subject: Re: [flashrom] flashrom problem: will not flash on compaq/deskpro Deskpro EN SFF P600. "ERASE FAILED @237568, val 60!" My box is doomed to be bricked

Hi all,

[Ludwig: can you please subscribe to the coreboot list? We can continue
working on your problem there.]

IIRC Uwe has been working with the mainboard mentioned below. Could you
please take a look?

Regards,
Carl-Daniel

On 01.06.2008 00:24, Ludwig Jaffe wrote:
> Hi Having the Deskpro EN SFF P600. abused as poor mans webservers,
> I was anoyed by the compaq-bios requiring a kbd to boot. even in
> "server-mode"
> Now having build a rom, I am little bit frustrated on programming the
> flash.
> Because if one has a programmer one has to de-solder the flash,
> because there is *no*
> socket. If one desolders one can also use a bigger flash, not having
> to fiddle around with filo-features
> just to get it fit (usb has to stay out)
>
> Now my machine is doomed to be bricked as soon as power fails ((
> Would be nice if you can resolve the problem.
>
> Here is the program output:
>
>
> ./flashrom  -w coreboot.rom

Subject: [Fwd: Re: [flashrom] flashrom problem: will not flash on compaq/deskpro Deskpro EN SFF P600. "ERASE FAILED @237568, val 60!" My box is doomed to be bricked ]

]

From: Ludwig Jaffe <luja <at> openhardware.de>
Subject: Re: [flashrom] flashrom problem: will not flash on compaq/deskpro Deskpro EN SFF P600. "ERASE FAILED @237568, val 60!" My box is doomed to be bricked png">]
Date: 2008-06-01 14:59:56 GMT

Hi all,

i fiddled around with the flashrom util, and I managed to rewrite the 
original compaq-bios, which I saved before.
I modified the flashrom-utily to enable writing the flashrom. The 
29F002BT works with 29f002-funktions and *not* with jedec....
The only problem that remains, is that it is not possible to unprotect 
the 20f002bt (ST). with the flashrom utily. So I can not upgrade the flash!
I will go and code some improvement to that.

A suggestion regarding architecture:

struct flashchip flashchips[] = {

/**********************************************************************************************************************************************************************************************************************/
        /* Vendor       Chip                    Vendor ID       Chip 
ID                 TODO    TODO            Test status     Probe 
function          Erase function                  Write 
function          Read function */

Re: flashrom verify fails, CK804, MCP55

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 <at> gmx.net> 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/
>
>

--

-- 
coreboot mailing list

flashrom patch for little improvement with st 29F002BT

Hello,
while fixing the dangerous situation for my boxes I made little 
improvements to
flashrom.
It is still impossible to flash ST 29F002BT because unprotecting does 
not work for now.
But read/write/probe does.

Greetings

LuJa

diff -Nur flashrom_orig/Doxyfile flashrom/Doxyfile
--- flashrom_orig/Doxyfile	2008-06-01 10:57:45.000000000 +0200
+++ flashrom/Doxyfile	1970-01-01 01:00:00.000000000 +0100
@@ -1,281 +0,0 @@
-# Doxyfile 1.5.3
-
-#---------------------------------------------------------------------------
-# Project related configuration options
-#---------------------------------------------------------------------------
-DOXYFILE_ENCODING      = UTF-8
-PROJECT_NAME           = flashrom
-PROJECT_NUMBER         = v2-3359
-OUTPUT_DIRECTORY       = /exports/3/laj/ingbuero/edv/webserver/hw/compaq-dpens-p600/bios/coreboot/coreboot-v2-3359/util/flashrom/doc/
-CREATE_SUBDIRS         = NO
-OUTPUT_LANGUAGE        = English
-BRIEF_MEMBER_DESC      = YES

Re: LinuxTag 2008 Status

Hi all,

On 29.05.2008 22:02, Paul Menzel wrote:
> Am Donnerstag, den 29.05.2008, 13:39 -0400 schrieb Joseph Smith:
>   
>> How is LinuxTag 2008 going Peter, Paul, and Carl-Daniel?
>>     
>
> Pierre, who offered his help with the booth and is considered a spammer
> by trac, is also presenting coreboot.
>   

We were a team of four for most of the time. Thanks again to Paul and
Pierre for helping us out, they were a pleasure to work with! There was
some sort of "collateral damage", though: I believe Paul and Pierre now
know a lot more about coreboot. 

>> Are you getting alot of people excited about coreboot?
>>     
>
> So I will try to give a quick summary of the first two days. I was there
> about 70 % of it.
>
> - Peter is talking a lot to people. As evidence he is gravelly.
> Especially after the workshop/talk he gave today.
>   

His voice recovered. Sort of.

> I would guess that we talk to about 4–6 people in an hour. But since we

Re: LinuxTag 2008 Status

On 30.05.2008 22:44, Jordan Crouse wrote:
> On 29/05/08 14:58 -0700, ron minnich wrote:
>   
>> Wow, wonderful job to all at LInuxTag! Thanks to you all!
>>
>> I just ran the bayou demo and it is really impressive. I wonder if
>> there is anything else like it? It's really neat.
>>     
>
> Thanks.  There is still much to be done, but I think this is a pretty
> good start.. :) To that end, let me solicit the help of the community to
> think about the next step. 
>
> As a group we have identified two main behaviors for the chooser:
>
>  * An interactive menu
>  * Chaining (running one payload after another in the fashion of a 
>  traditional BIOS)
>   

Absolutely.

> But when you look closer, the number of possible modes explodes.  As an
> example:
>
>  - You may want to add a timeout to the menu, so that if somebody doesn't
>  press the hotkey, a default payload is chosen.
>   

Reasonable.

Unprotecting 29F002BT

Hi,

looking for the unprotect-algorithm I found the AN1122 from ST.
The figure 4 shows a way to do this, but, how do we put VID=12V to Pin#1?
Does anybody know how this is done or if we should use the 
programmer-mode/way instaed of insystem/mode/way?

Thanks for your comments.

Attached the application-note, and the datasheet of st29F002B series.

Greetings

LuJa

--

-- 
coreboot mailing list
coreboot <at> coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot

buildrom

I build a rom for ADM DB800. One error appear as following:

[root <at> localhost buildrom-devel]# make
Unpacking mkelfimage...
Patching mkelfimage...
Applying patch mkelfImage-2.7-x86_64.patch
Applying patch mkelfimage-autoconf.patch
Now at patch mkelfimage-autoconf.patch
Building mkelfImage...
Building unifdef (host)...
Building lzma...
Unpacking kernel (2.6.20.2)...
Patching kernel...
Building kernel...
Installing kernel headers...
Building the ELF payload...
Compressing the ELF payload with lzma...
******************
Payload takes 1508825 Bytes (1473 KBytes) in ROM:
******************
Unpacking coreboot (coreboot-svn-3335.tar.gz)...
Patching coreboot...
Building target...
/bin/sh: line 0: cd: /bios/buildrom/buildrom-devel/work/coreboot/svn/targets/: 没有那个文件或目录
make: *** [/bios/buildrom/buildrom-devel/work/coreboot/stamps/.configured-db800] 错误 127
[root <at> localhost buildrom-devel]# 

How can i clear this error?

My gcc'version is 4.2.2.

Subject: Re: [flashrom] flashrom problem: will not flash on compaq/deskpro Deskpro EN SFF P600. "ERASE FAILED @237568, val 60!" My box is doomed to be bricked

Hi all,

i fiddled around with the flashrom util, and I managed to rewrite the 
original compaq-bios, which I saved before.
I modified the flashrom-utily to enable writing the flashrom. The 
29F002BT works with 29f002-funktions and *not* with jedec....
The only problem that remains, is that it is not possible to unprotect 
the 20f002bt (ST). with the flashrom utily. So I can not upgrade the flash!
I will go and code some improvement to that.

A suggestion regarding architecture:

struct flashchip flashchips[] = {

/**********************************************************************************************************************************************************************************************************************/
        /* Vendor       Chip                    Vendor ID       Chip 
ID                 TODO    TODO            Test status     Probe 
function          Erase function                  Write 
function          Read function */

/**********************************************************************************************************************************************************************************************************************/
        {"AMD",         "Am29F016D",            AMD_ID,         
AM_29F016D,             2048,   64 * 1024,      TEST_UNTESTED,  
probe_29f040b,          erase_29f040b,                  write_29f040b},
        {"AMD",         "Am29F040B",            AMD_ID,         
AM_29F040B,             512,    64 * 1024,      TEST_OK_PREW,   
probe_29f040b,          erase_29f040b,                  write_29f040b},
        {"AMD",         "Am29LV040B",           AMD_ID,         
AM_29LV040B,            512,    64 * 1024,      TEST_UNTESTED,  
probe_29f040b,          erase_29f040b,                  write_29f040b},