[coreboot] flashrom not working - asus p5q (ICH10R)
dev at duffd.net
Mon Dec 22 02:32:52 CET 2008
Peter Stuge wrote:
> Hi Thomas!
> Thomas Prochaska wrote:
>> today i tried the flashrom utility from coreboot-v2 svn trunk.
>> this is the output:
>> fin at xiix:~$ sudo flashrom
>> Calibrating delay loop... OK.
>> Can't mmap memory using /dev/mem: Invalid argument
>> therefore i want to ask you if my chipset is unsupported.
>> maybe you can shed some light on this.
>> my system:
>> asus p5q
>> debian/gnu linux (sid) (debian standard kernel 188.8.131.52, customized
>> vanilla 2.6.28-rc8)
>> i tested it with both kernels and got same results.
> Please check that CONFIG_STRICT_DEVMEM is not set in your kernel
> configuration. If it is set (I believe at least debian has it set)
> flashrom can not work properly.
>> also i wanted to ask if it's possible to support this motherboard
>> if i help you and test stuff and so on.
> Yes, it should be possible to support your board. ASUS has had tricky
> board enables in the past, but hopefully yours isn't one of them.
ok, i found the problem. i hadn't set CONFIG_STRICT_DEVMEM but i had
x86-pat enabled. this was the problem. with the nopat kernel boot option
it produces this output:
xiix:~# flashrom -V
Calibrating delay loop... 855M loops per second, 100 myus = 200 us. OK.
No coreboot table found.
Found chipset "Intel ICH10R", enabling flash write...
BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000
GCS = 0x1464: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1
Top Swap : not enabled
SPIBAR = 0xfed1c000 + 0x3800
0x00: 0x1fff (HSFS)
FLOCKDN 1, FDV 1, FDOPSS 0, SCIP 0, BERASE 0, AEL 0, FCERR 0, FDONE 0
0x50: 0x00000202 (FRAP)
BMWAG 0, BMRAG 0, BRWA 2, BRRA 2
0x54: 0x00001fff (FREG0)
0x58: 0x00001fff (FREG1)
0x5C: 0x00001fff (FREG2)
0x60: 0x00001fff (FREG3)
0x64: 0x00001fff (FREG4)
0x74: 0x00000000 (PR0)
0x78: 0x00000000 (PR1)
0x7C: 0x00000000 (PR2)
0x80: 0x00000000 (PR3)
0x84: 0x00000000 (PR4)
0xB0: 0x00000000 (FDOC)
SPI Read Configuration: prefetching disabled, caching enabled, OK.
Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0x4d, id2 0x5a,
id1 parity violation
Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0x4d, id2 0x5a,
id1 parity violation
Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xa3, id2 0x51
Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xa3, id2 0x51
Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x4d, id2 0x5a, id1
Probing for Atmel AT25DF021, 256 KB: Segmentation fault
is that a problem or just because i haven't provided an image to write.
More information about the coreboot