January 2014 - coreboot - mail.coreboot.org

ASUS m5a88-v AGESA progress report
by darkdefende＠gmail.com Jan. 19, 2014

Jan. 19, 2014

I haven't got much further than when I posted on this mailing list. I still haven't found the exact cause to why the SATA ports dies when booting linux. However my main computer has died so I don't have any computer that I can use when I'm trying to get coreboot running on that mobo. But because that computer died I could use the GPU that survived to see if the pcie ports were working with my coreboot image. That wasn't the case so I suspect that the sata and pcie problems are because of the rs780 (northbridge) is not working correctly. I suspect that this is because I mix AGESA with code that were used before AGESA was in coreboot. Because no other board does this I suspected from the start that it would turn out ugly in the end. But it was worth a try :) I took a look on the northbridges that have been ported from pre-AGESA to AGESA boards. But it seems to me that I will not be able to port it myself as alot of the code seems to heavily rely on vendorcode that AMD as supplied to coreboot. (There is no vendorcode for rs780, I think) Because I think that I lack the necessary knowledge to port it over myself, and because I can't afford to buy a new computer to use for coreboot porting, I won't get much further. The code is still hosted on my github page: https://github.com/DarkDefender/coreboot What works is: CPU/RAM (tested with bulldozer and 16GB ram) Booting to Seabios/grub2 Booting from HDD/Usb with seabios/grub2 Runnig linux from usb with serial output What might work: PS2 keyboard (Didn't test it out as I had to do everything over serial but turning numlock on/off works as the LEDs responds to those key presses. And kernel panics trigger the LEDs to flash on it also.) Onboard LAN (The kernel seems to init it fine, but I didn't try to connect it to a network) What doesn't work: SATA ports when booting linux (Haven't tried any other OS) Onboard audio Onboard GPU Pcie ports (And I'm guessing the pci ports also) I don't know if I should try to push this code into coreboot or not. It's pretty non functional as I don't think anyone would be happy with running with only serial and having to use USB as the only main storage source. Anyways, It's been a fun ride. I would like to thank everybody that helped me in some way. I wouldn't gotten this far without you guys! :)

1 0

lzma: Deconding error = 1 for QEMU q35 with SeaBIOS
by Piotr Król Jan. 19, 2014

Jan. 19, 2014

Hi Coreboot experts, I'm trying to use latest Coreboot code(c9babb2) with QEMU(1cf892c) q35 and SeaBIOS(master). Unfortunately, I encounter lzma decoding error (log: http://pastebin.com/aPaPBjZQ) I tried to debug LzmaDecode and it looks like rep0 reach some big value in my case 0x14ed98 after going though lzmadecode.c loops and bitwise modifications. This triggers RC_INIT after checking condition and return LZMA_RESULT_DATA_ERROR: coreboot/payloads/libpayload/liblzma/lzmadecode.c: 379: if (rep0 > nowPos) 380: return LZMA_RESULT_DATA_ERROR; Is this known issue ? Any suggestion for fixing it ? I'm new to this group, so sorry for any confusion or misunderstanding that I introduced. Regards, Piotr

1 0

[RFC] Short license headers
by mrnuke Jan. 18, 2014

Jan. 18, 2014

## ## This file is part of the coreboot project. ## ## Copyright (C) 2014 Alexandru Gagniuc <email(a)addr.ess> ## ## This program is free software; you can redistribute it and/or modify ## it under the terms of the GNU General Public License as published by ## the Free Software Foundation; either version 2 of the License, or ## (at your option) any later version. ## ## 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 ## License headers are boring, redundant, and the more time you spend coding, the more annoying they get. You gave me a big COPYING file that tells me all I ever wanted to know about the license. You don't need to pull out a ruler and measure your manhood in every file, with a 20+ line pork that tells me nothing about what the file is about. You can tell me what the license is in 6 characters or less if you really want to. /* * Email describing why short headers are better * * Copyright (C) 2013 Alexandru Gagniuc <mr.nuke.me(a)gmail.com> * Subject to the GNU GPL v2, or (at your option) any later version. */ There, I've done all that in six lines, AND I've briefly told you what this file does. I've started using this style in the cubieboard/allwinner port. I have not seen any major complaints (in fact, only one minor notice that I'm doing it). It works great. * First, it forces me to think about what this file is about, which in turn gets me to think if it's really needed or not. I think I was able to get the allwinner code much better organized because of this one detail. * Second, it lets me focus on coding. * Third, I no longer need to scroll down to see what the file actually does. * Fourth, after weeks of thinking about it, I could not find one downside to the approach. As a result, I propose the following: 1. Update the coding guidelines to use the short header. 2. Enforce the new guidelines on new commits. 3. Kindly ask people to update the old headers to the new format (maybe someone smart enough can script this). 4. Remove copyright headers from trivial Kconfig and Makefile.inc. Which files you include in which stage is not really copyrightable anyway. On point (4) The arch/arm or arch/x86 makefiles are pretty comprehensive, so it makes sense to have copyright headers there, but that's about the only place I see where this makes any sense. Less legalese, more code. Let's do this. Alex [1] http://www.coreboot.org/Development_Guidelines#Common_License_Header

4 4

When does a file need a license header? (was: Change in coreboot[master]: uio_usbdebug: User-space-i/o framework for usbdebug)
by Paul Menzel Jan. 18, 2014

Jan. 18, 2014

Dear coreboot folks, Am Donnerstag, den 16.01.2014, 15:56 +0100 schrieb gerrit code review: […] > Change subject: uio_usbdebug: User-space-i/o framework for usbdebug > ...................................................................... > > > Patch Set 1: […] > http://review.coreboot.org/#/c/4695/1/util/uio_usbdebug/device/device_util.c > File util/uio_usbdebug/device/device_util.c: > > Line 1: > > No header? > No code? > > > http://review.coreboot.org/#/c/4695/1/util/uio_usbdebug/device/pci_device.c > File util/uio_usbdebug/device/pci_device.c: > > Line 1: > > No header? > No code? I always thought every manually created file in the repository should have license (header). I think that such a rule is not necessarily required but I am not a lawyer. The GPL notes [1] advise to do, but as written it seems not to be legally necessary [2]. So could you (Ron, Stefan?) please clarify what to do in coreboot’s case? Thanks, Paul [1] http://www.gnu.org/licenses/gpl-howto.html [2] http://stackoverflow.com/questions/3051651/open-source-licence-header-on-ea…

1 0

Re: [coreboot] Chromebox debugging.
by Kyösti Mälkki Jan. 17, 2014

Jan. 17, 2014

On 01/17/2014 01:01 PM, Timothy Potter wrote: > Hi, > I'm trying to get Coreboot with SeaBIOS running on a Chromebox. I > followed the page about compiling Coreboot for a Chomebook 550, assuming > they are similar in some respects. Unfortunately none of the builds have > booted. Just the blue power light comes on at best. > I'm wondering if anyone knows which is the USB Debug Port or the pin out > of the LPC bus connector? I've got one of those cheap Mini PCI Express > POST diagnostic cards but can't work out how to wire up. I've also got an > old Android phone with the ECHI debug gadget compiled into the kernel. I've > tried connecting that to every USB port on the Chromebox but never get any > output. > > Hope someone can help. > > Cheers, > Tim. > > > Hi Tim Did you apply the two patches for EHCI gadget available here: http://www.coreboot.org/EHCI_Gadget_Debug Try this without Chromebox first: Connect phone with any normal USB host. Run lsusb -v on the host to verify your Android exports USB debug descriptor. Then post system logs from both sides of the connection. Now for the physical USB port to use. If you can boot your Chromebox with the original flash image, a working port should appear as "usb 1-1.2" or "usb 2-1.2" in the system log when you connect any USB device. For coreboot configuration with Intel platform, HCD_INDEX=1 maps to 0:1d.0 and HCD_INDEX=2 maps to 0:1a.0. It's reversed order, like in the datasheets. Regards, Kyösti

1 0

Re: [coreboot] Chromebox debugging.
by John Lewis Jan. 17, 2014

Jan. 17, 2014

On 17/01/14 11:01, Timothy Potter wrote: > I've > also got an old Android phone with the ECHI debug gadget compiled into > the kernel. I've tried connecting that to every USB port on the > Chromebox but never get any output. > Hi Tim, Have you got "USB 2.0 EHCI debug dongle support" compiled on the coreboot side? If so, did you select "NET20DC and compatible" or "BeagleBone"? What kernel is the phone running? I assume because you have the EHCI debug gadget complied in the Android gadget is not? How does your phone react to the missing Android gadget? I gave up with that and purchased a BeagleBone Black in the end. Perhaps Kyösti can help or explain why this isn't going to work? Regards, John.

1 0

Chromebox debugging.
by Timothy Potter Jan. 17, 2014

Jan. 17, 2014

Hi, I'm trying to get Coreboot with SeaBIOS running on a Chromebox. I followed the page about compiling Coreboot for a Chomebook 550, assuming they are similar in some respects. Unfortunately none of the builds have booted. Just the blue power light comes on at best. I'm wondering if anyone knows which is the USB Debug Port or the pin out of the LPC bus connector? I've got one of those cheap Mini PCI Express POST diagnostic cards but can't work out how to wire up. I've also got an old Android phone with the ECHI debug gadget compiled into the kernel. I've tried connecting that to every USB port on the Chromebox but never get any output. Hope someone can help. Cheers, Tim.

1 0

Need help to find chip model (x60)
by Alan Smith Jan. 16, 2014

Jan. 16, 2014

Hello everyone, I'm new to this list! I just bought an old (but still fine) x60 (1707-CTO) to play with coreboot. I read the wiki page and a few threads on the mailing list but I'm still stuck in finding my chip model... Here's "flashrom -p internal -V" output: flashrom v0.9.7-r1711 on Linux 3.10-2-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.7.3, little endian Command line (3 args): ./flashrom -p internal -V Calibrating delay loop... OS timer resolution is 2 usecs, 943M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 994 us, 10000 myus = 13485 us, 8 myus = 9 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "1707WQ5" DMI string system-version: "ThinkPad X60" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "1707WQ5" DMI string baseboard-version: "Not Available" DMI string chassis-type: "Notebook" Laptop detected via DMI. Whitelisted laptop detected. Found chipset "Intel ICH7M" with PCI ID 8086:27b9. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x1 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x4 0xffc00000/0xff800000 FWH IDSEL: 0x4 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3020 0x00: 0x8004 (SPIS) 0x02: 0x4140 (SPIC) 0x04: 0x00000000 (SPIA) 0x08: 0x00bf41bf (SPID0) 0x0c: 0x00000000 (SPID0+4) 0x10: 0x00000000 (SPID1) 0x14: 0x00000000 (SPID1+4) 0x18: 0x00000000 (SPID2) 0x1c: 0x00000000 (SPID2+4) 0x20: 0x00000000 (SPID3) 0x24: 0x00000000 (SPID3+4) 0x28: 0x00000000 (SPID4) 0x2c: 0x00000000 (SPID4+4) 0x30: 0x00000000 (SPID5) 0x34: 0x00000000 (SPID5+4) 0x38: 0x00000000 (SPID6) 0x3c: 0x00000000 (SPID6+4) 0x40: 0x00000000 (SPID7) 0x44: 0x00000000 (SPID7+4) 0x50: 0x00000000 (BBAR) 0x54: 0x5006 (PREOP) 0x56: 0x163b (OPTYPE) 0x58: 0x05d80302 (OPMENU) 0x5c: 0x0001d8ab (OPMENU+4) 0x60: 0x80fff1f0 (PBR0) 0x64: 0x00000000 (PBR1) 0x68: 0x00000000 (PBR2) WARNING: SPI Configuration Lockdown activated. Reading OPCODES... done SPI Read Configuration: prefetching disabled, caching enabled, OK. The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L05PU, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L10PT, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L10PU, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L20PT, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L20PU, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L40PT, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L40PU, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L80P, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L16PT, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L16PU, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L512, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L010, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L080, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L016, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25L032, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25LQ16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for AMIC A25LQ64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF021, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF041A, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF081, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF081A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF321, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF321A, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DF641(A), 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25DQ161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25F512, 64 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F512A, 64 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F512B, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25F1024(A), 128 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F2048, 256 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25F4096, 512 kB: Invalid OPCODE 0x15, will not execute. Probing for Atmel AT25FS010, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT25FS040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF041, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF081A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF161, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26DF161A, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT26F004, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45CS1282, 16896 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB011D, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB021D, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB041D, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB081D, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB161D, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB321C, 4224 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB321D, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel AT45DB642D, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for ESMT F25L008A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B05, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B05T, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B10T, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B20T, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B40T, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B80T, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B16T, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B32T, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25B64T, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F05, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25F64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q80(A), 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q32(A/B), 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25Q128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25QH128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon EN25S64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25LQ32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q512, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q20(B), 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q40(B), 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q80(B), 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q16(B), 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q32(B), 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q64(B), 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25Q128B, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for GigaDevice GD25T80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F160S33B8, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F160S33T8, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F320S33B8, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F320S33T8, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F640S33B8, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Intel 25F640S33T8, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L2005(C), 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L4005(A/C), 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L8005/MX25V8005, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1605, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1605D/MX25L1608D, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1635D, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L1635E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3205(A), 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3206E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L3235D, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6405(D), 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L6445E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25L12805(D), 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U1635E, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U3235E/F, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix MX25U6435E/F, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P05-A, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P05, 64 kB: Invalid OPCODE 0x9f, will not execute. Invalid OPCODE 0x90, will not execute. probe_spi_res1: id 0xbf Probing for Micron/Numonyx/ST M25P10-A, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P10, 128 kB: Invalid OPCODE 0x9f, will not execute. Invalid OPCODE 0x90, will not execute. probe_spi_res1: id 0xbf Probing for Micron/Numonyx/ST M25P20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Invalid OPCODE 0x9f, will not execute. Invalid OPCODE 0x90, will not execute. probe_spi_res1: id 0xbf Probing for Micron/Numonyx/ST M25P40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Invalid OPCODE 0x9f, will not execute. Invalid OPCODE 0x90, will not execute. probe_spi_res1: id 0xbf Probing for Micron/Numonyx/ST M25P80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25P128, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PE16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M25PX64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST M45PE16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q016, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Nantronics N25S16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD256C, 32 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD512(C), 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD010(C), 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD020(C), 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LD040(C), 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res3: id1 0xbf41, id2 0xbf Probing for PMC Pm25LV010, 128 kB: probe_spi_res3: id1 0xbf41, id2 0xbf Probing for PMC Pm25LV010A, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV080B, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC Pm25LV016B, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW203A, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW403A, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0xbf, id2 0x41 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0xbf, id2 0x41 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0xbf, id2 0x41 Probing for Spansion S25FL004A, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL008A, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL016A, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL032A/P, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL064A/P, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL204K, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL208K, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL116K/S25FL216K, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Spansion S25FL128S......0, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0xbf, id2 0x41 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0xbf, id2 0x41 Probing for SST SST25VF010, 128 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF016B, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF032B, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF064C, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF040, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF040B, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25VF040B.REMS, 512 kB: Invalid OPCODE 0x90, will not execute. Probing for SST SST25VF080B, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF512, 64 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF010, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF020, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST SST25WF040, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q80.V, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q16.V, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q32.V, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q64.V, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q128.V, 16384 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q20.W, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q40.W, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q80.W, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q16.W, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q32.W, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25Q64.W, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X10, 128 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X20, 256 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X40, 512 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X80, 1024 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X16, 2048 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X32, 4096 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond W25X64, 8192 kB: Invalid OPCODE 0x9f, will not execute. Probing for Unknown SFDP-capable chip, 0 kB: Invalid OPCODE 0x5a, will not execute. Receiving SFDP signature failed. Probing for AMIC unknown AMIC SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Atmel unknown Atmel SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Eon unknown Eon SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Macronix unknown Macronix SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for PMC unknown PMC SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for SST unknown SST SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for ST unknown ST SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Sanyo unknown Sanyo SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Generic unknown SPI chip (RDID), 0 kB: Invalid OPCODE 0x9f, will not execute. Probing for Generic unknown SPI chip (REMS), 0 kB: Invalid OPCODE 0x90, will not execute. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Restoring MMIO space at 0xb76f6070 Thanks in advance! A. ------------------------------------------------- VFEmail.net - http://www.vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 1

Re: [coreboot] Strange Coreboot behaviors while building IVB Cougar Canyon Coreboot based upon intel.com/fsp IVB FSP
by Stojsavljevic, Zoran Jan. 13, 2014

Jan. 13, 2014

Solved! Thank you, Zoran _______ Most of The Time you should be “intel inside” to be capable to think “out of the box”. From: Marc Jones [mailto:marcj303@gmail.com] Sent: Friday, January 10, 2014 8:12 PM To: Stojsavljevic, Zoran Cc: coreboot(a)coreboot.org Subject: Re: [coreboot] Strange Coreboot behaviors while building IVB Cougar Canyon Coreboot based upon intel.com/fsp IVB FSP Is the descriptor binary in the second 4MB flash. The split flash is a little confusing, but handy as you can make changes to coreboot and not the descriptor and me. Do you get post codes? Marc On Fri, Jan 10, 2014 at 7:26 AM, Stojsavljevic, Zoran <zoran.stojsavljevic(a)intel.com<mailto:zoran.stojsavljevic@intel.com>> wrote: Hello, After long time, I am returning to this domain, in attempt to build valid Coreboot using git clone from Coreboot.org . I have two instances I cloned, one is v4.0-4966, another one is latest (cloned today) v4.0-5223 ... Here is what I have while building v4.0-4966 (.config attached to the email as CONFIG_4966): coreboot.rom: 8192 kB, bootblocksize 864, romsize 8388608, offset 0x400000 alignment: 64 bytes Name Offset Type Size cmos_layout.bin 0x400000 cmos_layout 1164 pci8086,0166.rom 0x4004c0 optionrom 65536 cpu_microcode_blob.bin 0x410500 microcode 32832 <<===== YES, microcode integrated fallback/romstage 0x4185c0 stage 31082 fallback/coreboot_ram 0x41ff80 stage 75924 fallback/payload 0x432880 payload 55177 config 0x440080 raw 4322 (empty) 0x4411c0 null 3403224 fsp.bin 0x77ffc0 (unknown) 393216 (empty) 0x7e0000 null 130072 Needless to say, for some reason reset vector does not start (I see no serial outputs from FSP even)! Here is what I have while building v4.0-5223 (.config attached to the email as CONFIG_5223): coreboot.rom: 8192 kB, bootblocksize 992, romsize 8388608, offset 0x400000 alignment: 64 bytes Name Offset Type Size cmos_layout.bin 0x400000 cmos_layout 1164 pci8086,0166.rom 0x4004c0 optionrom 65536 fallback/romstage 0x410500 stage 31583 fallback/coreboot_ram 0x4180c0 stage 75182 fallback/payload 0x42a6c0 payload 55156 config 0x437e80 raw 4419 (empty) 0x439000 null 3370904 cpu_microcode_blob.bin 0x76ffc0 microcode 0 <<===== NO microcode!!! (empty) 0x770000 null 65432 fsp.bin 0x77ffc0 (unknown) 393216 (empty) 0x7e0000 null 129944 The same: reset vector does not go! Strange. Any clues? Thank you, Zoran _______ Most of The Time you should be "intel inside" to be capable to think "out of the box". Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 -- coreboot mailing list: coreboot(a)coreboot.org<mailto:coreboot@coreboot.org> http://www.coreboot.org/mailman/listinfo/coreboot -- http://se-eng.com Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Re: [coreboot] Strange Coreboot behaviors while building IVB Cougar Canyon Coreboot based upon intel.com/fsp IVB FSP
by Patrick Georgi Jan. 13, 2014

Jan. 13, 2014

Am Freitag, den 10.01.2014, 14:26 +0000 schrieb Stojsavljevic, Zoran: > cpu_microcode_blob.bin 0x76ffc0 microcode 0 <<===== NO microcode!!! Please try http://review.coreboot.org/#/c/4646/ I can't completely verify it without downloading FSP, but it improves things in my tests. Regards, Patrick

2 1