coreboot November 2009

coreboot@coreboot.org

55 participants
232 discussions

#133: Create a typical failures FAQ
by coreboot 16 Jan '10

16 Jan '10

#133: Create a typical failures FAQ ---------------------------------------+------------------------------------ Reporter: stuge | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: flashrom | Version: Keywords: faq documentation debug | Dependencies: Patchstatus: there is no patch | ---------------------------------------+------------------------------------ Briefly describe what flashrom needs to do to successfully identify, read and write/erase the different type of chips to optimize the remote debugging process with new users. -- Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/133> coreboot <http://www.coreboot.org/>

1 2

#130: flashrom segfault (with backtrace)
by coreboot 16 Jan '10

16 Jan '10

#130: flashrom segfault (with backtrace) ---------------------------------+------------------------------------------ Reporter: fragabr@… | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: flashrom | Version: v2 Keywords: | Dependencies: Patchstatus: there is no patch | ---------------------------------+------------------------------------------ I want to test flashrom with a supported motherboard (Asus M2N-E with Linux 2.6.30-rc4) and it segfaults when I run it. I'm using the latest libpci (3.1.2): {{{ Calibrating delay loop... OK. No coreboot table found. Segmentation fault }}} Backtrace: {{{ #0 0x00007f1395141d49 in pci_fill_info_v31 () from /usr/local/lib/libpci.so.3 #1 0x00007f1395143c59 in pci_filter_match () from /usr/local/lib/libpci.so.3 #2 0x000000000040732f in ?? () #3 0x00000000004016f8 in ?? () #4 0x0000000000406d46 in ?? () #5 0x00007f1394df24f6 in __libc_start_main () from /lib64/libc.so.6 #6 0x0000000000401619 in ?? () #7 0x00007fff9d579e98 in ?? () #8 0x000000000000001c in ?? () #9 0x0000000000000001 in ?? () #10 0x00007fff9d57ab55 in ?? () #11 0x0000000000000000 in ?? () }}} -- Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/130> coreboot <http://www.coreboot.org/>

1 3

#140: flashrom: Consistently use stderr for error printing
by coreboot 16 Jan '10

16 Jan '10

#140: flashrom: Consistently use stderr for error printing ---------------------------------+------------------------------------------ Reporter: uwe | Owner: somebody Type: defect | Status: new Priority: minor | Milestone: flashrom v1.0 Component: flashrom | Version: Keywords: | Dependencies: Patchstatus: there is no patch | ---------------------------------+------------------------------------------ We're not very consistent with error printing in flashrom. Many errors go to stdout instead of stderr. We should fix that by using fprintf(stderr, "Foo") where needed. -- Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/140> coreboot <http://www.coreboot.org/>

1 2

#144: TYAN S7012 support
by coreboot 16 Jan '10

16 Jan '10

#144: TYAN S7012 support --------------------------------------------------------+------------------- Reporter: john@… | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: flashrom | Version: v2 Keywords: TYAN S7012 Intel ICH10R SST SST25VF032B | Dependencies: Patchstatus: there is no patch | --------------------------------------------------------+------------------- I'm unable to flash a system that runs on a TYAN S7012 motherboard. # flashrom -w bios.bin flashrom v0.9.0-r659 No coreboot table found. Found chipset "Intel ICH10R", enabling flash write... OK. This chipset supports the following protocols: LPC,FWH,SPI. Calibrating delay loop... OK. Found chip "SST SST25VF032B" (4096 KB, SPI) at physical address 0xffc00000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... COMPLETE. Verifying flash... VERIFY FAILED at 0x00002000! Expected=0x00, Read=0xff Running it with verbose the following error messages are printed out (repeating). Writing flash chip... Invalid OPCODE 0x06 due to SPI master limitation, ignoring and hoping it will be run as PREOP Transaction error! run OPCODE 0x02 failed spi_byte_program failed during command execution Invalid OPCODE 0x06 due to SPI master limitation, ignoring and hoping it will be run as PREOP Transaction error! run OPCODE 0x02 failed spi_byte_program failed during command execution Invalid OPCODE 0x06 CONFIG_STRICT_DEVMEM is not set in my kernel. Anything I should try out? -- Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/144> coreboot <http://www.coreboot.org/>

1 2

Coreboot Support for MSI KT4 Ultra (MS-6590)
by freeman2411 09 Dec '09

09 Dec '09

Hi Guys! Could you please help me with my MSI Mainboard. I would really like to get it running on this Mainboard. *1.)* MSI KT4 Ultra (MS-6590) AMD Athlon XP 2200+ *2.)* -[0000:00]-+-00.0 VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge [1106:3189] +-01.0-[0000:01]-- +-0a.0 Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] +-0c.0 C-Media Electronics Inc CM8738 [13f6:0111] +-10.0 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-10.1 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-10.2 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-10.3 VIA Technologies, Inc. USB 2.0 [1106:3104] +-11.0 VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177] \-11.1 VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] *3.)* superiotool r3695 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0x50fe, id=0x1660 Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0x6016, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8661f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8671f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x15c... Failed. Returned data: port=0xff, port+1=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Found Winbond W83697HF/F/HG (id=0x60, rev=0x16) at 0x2e Register dump: idx 20 21 22 23 24 25 26 28 29 2a val 60 16 ff fe 50 00 00 00 00 ff def 60 NA ff 00 00 00 00 00 00 MM LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f1 f2 f4 f5 val 01 03 f0 06 02 0e 00 ff 00 00 def 01 03 f0 06 02 0e 00 ff 00 00 LDN 0x01 (Parallel port) idx 30 60 61 70 74 f0 val 01 03 78 07 03 3a def 01 03 78 07 04 3f LDN 0x02 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 00 def 01 03 f8 04 00 LDN 0x03 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 00 40 def 01 02 f8 03 00 00 LDN 0x06 (Consumer IR) idx 30 60 61 70 val 00 00 00 00 def 00 00 00 00 LDN 0x07 (Game port, GPIO 1) idx 30 60 61 62 63 f0 f1 f2 val 00 00 00 00 00 ff ff ff def 00 02 01 00 00 ff 00 00 LDN 0x08 (MIDI port, GPIO 5) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 val 00 00 00 00 00 00 ff ff ff 00 00 00 def 00 03 30 00 00 09 ff 00 00 00 00 00 LDN 0x09 (GPIO 2, GPIO 3, GPIO 4) idx 30 60 61 f0 f1 f2 f3 f4 f5 f6 f7 f8 f5 val 00 00 00 ff ff ff ff ff ff ff ff ff ff def 00 00 00 ff 00 00 ff 00 00 ff 00 00 00 LDN 0x0a (ACPI) idx 30 70 e0 e1 e2 e5 e6 e7 f0 f1 f3 f4 f6 f7 f9 val 00 00 00 00 ff 00 00 00 00 8f 0f 00 00 00 00 def 00 00 00 00 NA 00 00 00 00 00 00 00 00 00 00 LDN 0x0b (Hardware monitor) idx 30 60 61 70 val 01 02 90 00 def 00 00 00 00 Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff *4.)* Calibrating delay loop... 620M loops per second, 100 myus = 200 us. OK. No coreboot table found. Found chipset "VIA VT8235", enabling flash write... OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT25DF021, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF041A, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF081, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF161, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF321A, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF641, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25F512B, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25FS010, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25FS040, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF041, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF081A, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF161, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF161A, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26F004, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT45CS1282, 16896 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB011D, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB021D, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB041D, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB081D, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB161D, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB321C, 4224 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB321D, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB642D, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMIC A25L40P, 512 KB: 4b ID not supported on this SPI controller Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L512, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L1005, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L2005, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L6405, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0xff, id2 0xff Probing for Numonyx M25PE10, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE40, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE16, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff Probing for Spansion S25FL016A, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF032B, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF080B, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xe8, id2 0x2f, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P40, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI chipset/strapping detected spi_command called, but no SPI chipset/strapping detected Probing for ST M25P80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P16, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P32, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P64, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P128, 16384 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M29F002B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W25x10, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x1b, id2 0xf0, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W29EE011, 128 KB: === Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. === Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for Atmel unknown Atmel SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected No EEPROM/flash device found. If you know which flash chip you have, and if this version of flashrom supports a similar flash chip, you can try to force read your chip. Run: flashrom -f -r -c similar_supported_flash_chip filename Note: flashrom can never write when the flash chip isn't found automatically. *5.)* http://www.msi-computer.de/index.php?func=proddesc&maincat_no=1&cat2_no=&ca… *6.)* Sorry I can't give more hints at this time. :-( Thank you for your help! Greetings Freeman

4 8

[PATCH]: Add superio sch4304 support.
by Bao, Zheng 01 Dec '09

01 Dec '09

Add support of superio sch4304. The Device id is 0x90. The number of X-BUS logical device is 11. I have not get the board to test it. I will have one. But I believe it is right, isn't it? Signed-off-by: Zheng Bao <zheng.bao(a)amd.com> Index: src/superio/smsc/smscsuperio/superio.c =================================================================== --- src/superio/smsc/smscsuperio/superio.c (revision 4952) +++ src/superio/smsc/smscsuperio/superio.c (working copy) @@ -61,6 +61,7 @@ #define SCH3112 0x7c #define SCH5307 0x81 /* Rebranded LPC47B397(?) */ #define SCH5027D 0x89 +#define SCH4304 0x90 /* SCH4304 */ /* Register defines */ #define DEVICE_ID_REG 0x20 /* Device ID register */ @@ -137,6 +138,7 @@ {SCH3112, {0, 3, 4, 5, -1, 7, -1, -1, -1, -1, -1, -1, 10, -1, -1}}, {SCH5307, {0, 3, 4, 5, -1, 7, -1, -1, 8, -1, -1, -1, 10, -1, -1}}, {SCH5027D, {0, 3, 4, 5, -1, 7, -1, -1, -1, -1, -1, -1, 10, -1, 11}}, + {SCH4304, {0, 3, 4, 5, -1, 7, -1, 11, -1, -1, -1, -1, 10, -1, -1}}, }; /**

4 8

[commit] r4968 - trunk/src/superio/smsc/smscsuperio
by svn＠coreboot.org 01 Dec '09

01 Dec '09

Author: uwe Date: 2009-12-01 00:53:06 +0100 (Tue, 01 Dec 2009) New Revision: 4968 Modified: trunk/src/superio/smsc/smscsuperio/superio.c Log: Add support for the SMSC SCH4304 Super I/O. Signed-off-by: Zheng Bao <zheng.bao(a)amd.com> Acked-by: Peter Stuge <peter(a)stuge.se> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/src/superio/smsc/smscsuperio/superio.c =================================================================== --- trunk/src/superio/smsc/smscsuperio/superio.c 2009-11-28 09:31:30 UTC (rev 4967) +++ trunk/src/superio/smsc/smscsuperio/superio.c 2009-11-30 23:53:06 UTC (rev 4968) @@ -61,6 +61,7 @@ #define SCH3112 0x7c #define SCH5307 0x81 /* Rebranded LPC47B397(?) */ #define SCH5027D 0x89 +#define SCH4304 0x90 /* SCH4304 */ /* Register defines */ #define DEVICE_ID_REG 0x20 /* Device ID register */ @@ -137,6 +138,7 @@ {SCH3112, {0, 3, 4, 5, -1, 7, -1, -1, -1, -1, -1, -1, 10, -1, -1}}, {SCH5307, {0, 3, 4, 5, -1, 7, -1, -1, 8, -1, -1, -1, 10, -1, -1}}, {SCH5027D, {0, 3, 4, 5, -1, 7, -1, -1, -1, -1, -1, -1, 10, -1, 11}}, + {SCH4304, {0, 3, 4, 5, -1, 7, -1, 11, -1, -1, -1, -1, 10, -1, -1}}, }; /**

1 0

GeodeLX RAM initialisation issue
by Nathan Williams 01 Dec '09

01 Dec '09

Hi I am trying to sort out a RAM issue with coreboot on a motherboard we have designed at my work. The board uses the AMD LX800 and CS5536 companion chipset. I have been using coreboot-v3 and based my board port on the Alix 1.C code. We have a SODIMM socket, so I used the initram.c from the amd/db800 code because it does SPD. The symptoms are that sometimes a boot will die during disable_car() in arch/x86/geodelx/stage1.c: /* OK, here is the theory: we should be able to copy * the data back over itself, and the wbinvd should then * flush to memory. Let's see. */ __asm__ __volatile__("cld; rep movsl" ::"D" (DCACHE_RAM_BASE), "S" (DCACHE_RAM_BASE), "c" (DCACHE_RAM_SIZE/4): "memory"); __asm__ __volatile__ ("wbinvd\n"); Sometimes it boots fine and appears to be quite stable. If I run software like mprime95 to "Torture Test" the system, it doesn't fail. However, there is one strange phenomenon that I've noticed. If I remove the RTC battery backup and Linux forces a fsck because the last boot time was in the future. If Linux fixes a couple of errors and reboots automatically in 5 seconds, during the reboot it's almost guaranteed that coreboot will get stuck in disable_car(). I don't know if this is useful, or just a coincidence. In my build I have also disabled the CMOS Option Table (CONFIG_OPTION_TABLE) in case something there might be causing the problem. Initially I thought it was a hardware problem with our PCBs, but have tested with a bios chip from an AMD reference design board (EmbeddedBIOS v5.3) which booted Linux fine without any problems, so I have concluded that my problem must be something I'm doing (or not doing) in coreboot. I have checked all the SPD values against the datasheet for the Hynix RAM chips (256MiB 333MHz). I tried using the non-SPD method as in the Alix 1.C code and specified all the RAM parameters. I have also tried to follow sdram_enable() and other functions in northbridge/amd/geodelx/raminit.c to check against the AMD LX databook's section 6.1.3 BIOS Initialization Sequence, though I admit I could have easily missed something here. I would be most grateful of any suggestions for helping me work out what's going wrong. Regards, Nathan

4 17

msrtool: freebsd support
by Andriy Gapon 30 Nov '09

30 Nov '09

Please review the following patch that adds FreeBSD support to msrtool. MSR values are obtained via /dev/cpuctl ioctl interface. Signed-off-by: Andriy Gapon <avg(a)icyb.net.ua> Index: msrtool.c =================================================================== --- msrtool.c (revision 4776) +++ msrtool.c (working copy) @@ -49,6 +49,7 @@ static struct sysdef allsystems[] = { { "linux", "Linux with /dev/cpu/*/msr", linux_probe, linux_open, linux_close, linux_rdmsr }, { "darwin", "OS X with DirectIO", darwin_probe, darwin_open, darwin_close, darwin_rdmsr }, + { "freebsd", "FreeBSD with /dev/cpuctl*", freebsd_probe, freebsd_open, freebsd_close, freebsd_rdmsr }, { SYSTEM_EOT } }; Index: Makefile.in =================================================================== --- Makefile.in (revision 4776) +++ Makefile.in (working copy) @@ -27,7 +27,7 @@ LDFLAGS = @LDFLAGS@ TARGETS = geodelx.o cs5536.o k8.o -SYSTEMS = linux.o darwin.o +SYSTEMS = linux.o darwin.o freebsd.o OBJS = $(PROGRAM).o msrutils.o sys.o $(SYSTEMS) $(TARGETS) all: $(PROGRAM) Index: msrtool.h =================================================================== --- msrtool.h (revision 4776) +++ msrtool.h (working copy) @@ -28,6 +28,10 @@ #define __DARWIN__ #include <DirectIO/darwinio.h> #endif +#if defined(__FreeBSD__) +#include <sys/ioctl.h> +#include <sys/cpuctl.h> +#endif #include <pci/pci.h> #define HEXCHARS "0123456789abcdefABCDEF" @@ -186,6 +190,12 @@ extern int darwin_close(uint8_t cpu); extern int darwin_rdmsr(uint8_t cpu, uint32_t addr, struct msr *val); +/* freebsd.c */ +extern int freebsd_probe(const struct sysdef *system); +extern int freebsd_open(uint8_t cpu, enum SysModes mode); +extern int freebsd_close(uint8_t cpu); +extern int freebsd_rdmsr(uint8_t cpu, uint32_t addr, struct msr *val); + /** target externs **/ /* geodelx.c */ Index: freebsd.c =================================================================== --- freebsd.c (revision 0) +++ freebsd.c (revision 0) @@ -0,0 +1,96 @@ +/* + * This file is part of msrtool. + * + * Copyright (c) 2009 coresystems GmbH + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + */ + +#include <sys/types.h> +#include <sys/stat.h> +#include <fcntl.h> +#include <unistd.h> +#include <string.h> +#include <errno.h> + +#include "msrtool.h" + +static int msr_fd[MAX_CORES] = {-1, -1, -1, -1, -1, -1, -1, -1}; + +int freebsd_probe(const struct sysdef *system) +{ +#ifdef __FreeBSD__ + struct stat st; + + return stat("/dev/cpuctl0", &st) == 0; +#else + return 0; +#endif +} + +int freebsd_open(uint8_t cpu, enum SysModes mode) +{ +#ifdef __FreeBSD__ + char devname[32]; + + if (cpu >= MAX_CORES) + return 0; + + snprintf(devname, sizeof(devname), "/dev/cpuctl%u", cpu); + msr_fd[cpu] = open(devname, O_RDONLY); + if (msr_fd[cpu] < 0) { + perror(devname); + return 0; + } + return 1; +#else + return 0; +#endif +} + +int freebsd_close(uint8_t cpu) +{ + if (cpu >= MAX_CORES) + return 0; + + if (msr_fd[cpu] != -1) + close(msr_fd[cpu]); + msr_fd[cpu] = -1; + return 1; +} + +int freebsd_rdmsr(uint8_t cpu, uint32_t addr, struct msr *val) +{ +#ifdef __FreeBSD__ + cpuctl_msr_args_t args; + + if (cpu >= MAX_CORES) + return 0; + + if (msr_fd[cpu] < 0) + return 0; + + args.msr = addr; + if (ioctl(msr_fd[cpu], CPUCTL_RDMSR, &args) < 0) { + perror("CPUCTL_RDMSR"); + return 0; + } + + val->hi = args.data >> 32; + val->lo = args.data & 0xffffffff; + return 1; +#else + return 0; +#endif +} -- Andriy Gapon

2 2

Atom platform porting problem.
by Scott.Hsiao 30 Nov '09

30 Nov '09

I am porting coreboot to a Intel Atom based mainboard which incorperate atom (N270) + 945GSE + it8718f. The initial progress of north bridge seems okay but I got error in the "dev_initialize" function. Here are the partial output: .... Initializing devices... Root Device init APIC_CLUSTER: 0 init malloc Enter, size 91, free_mem_ptr 0013b998 malloc 0013b998 start_eip=0x0000a000, offset=0x00100000, code_size=0x0000005b Initializing SMM handler... ... pmbase = 0x0500 SMI_STS: PM1 PM1_STS: WAK PWRBTN TMROF GPE0_STS: TCO_STS: ... raise SMI# Initializing CPU #0 CPU: vendor Intel device 106c2 CPU: family 06, model 1c, stepping 02 Using generic cpu ops (good) Enabling cache microcode_info: sig = 0x000106c2 pf=0x00000004 rev = 0x00000000 CPU: Intel(R) Core(TM) CPU N270 @ 1.60GHz. Setting fixed MTRRs(0-88) Type: UC Setting fixed MTRRs(0-16) Type: WB Setting fixed MTRRs(24-88) Type: WB DONE fixed MTRRs call enable_fixed_mtrr() Setting variable MTRR 0, base: 0MB, range: 512MB, type WB ADDRESS_MASK_HIGH=0xf Unexpected Exception: 13 @ 10:001025e9 - Halting Code: 0 eflags: 00010002 eax: e0000800 ebx: 0000000f ecx: 00000201 edx: 0000000f edi: e0000000 esi: 00000000 ebp: 0000000f esp: 00139df4 Please help to debug. Thanks, Scott Hsiao

1 0

← Newer
1
2
3
4
5
6
7
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot November 2009