coreboot March 2014

coreboot@coreboot.org

57 participants
180 discussions

Re: [coreboot] Hey
by Vladimir 'φ-coder/phcoder' Serbinenko 20 Mar '14

20 Mar '14

On 20.03.2014 13:27, Shant Kehyeian wrote: > Yess you are saying it right... > So I installed the coreboot source code and I compiled it with GRUB2 so > ...Do you think that I will get the grub options while the boot process ? > Thank you... > I don't know how you managed to compile GRUB2 for ARM coreboot but it's unlikely to work. I'm under impression that you compile for wrong mainboard altogether (you've chosen mobo in make menuconfig, right?) > > On Thu, Mar 20, 2014 at 12:23 PM, Vladimir 'φ-coder/phcoder' Serbinenko > <phcoder(a)gmail.com <mailto:phcoder@gmail.com>> wrote: > > On 20.03.2014 13:10, Shant Kehyeian wrote: > > In fact I do need the SeaBios not the GRUB2 to be able to boot > from usb > > with live CD which I can format and install my preferred OS... > > > I think you're missing the "ARM" part. Only ARM distros have any chance > to work. Given fragmentation of ARM it may even mean that only > Linux-based works on your machine. > > > > On Thu, Mar 20, 2014 at 4:05 PM, Vladimir 'φ-coder/phcoder' Serbinenko > > <phcoder(a)gmail.com <mailto:phcoder@gmail.com> > <mailto:phcoder@gmail.com <mailto:phcoder@gmail.com>>> wrote: > > > > On 20.03.2014 12:12, Shant Kehyeian wrote: > > > Hello, > > > I have Samsung ARM chromebook series 3 "Snow" and I am > trying to flesh > > > it and change the boot process. > > > So I build a coreboot.rom for that, but before I start to do > that I > > > would like to ask about the payload. When I did the "make > > menuconfig" it > > > wasn't by default the SeaBios., there wasn't at all ...there was > > GRUB 2 > > > and I selected it...so My question is would it work as > SeaBios to boot > > > from usb ? > > There is no arm-coreboot GRUB2 port currently. > > > Thank you. > > > > > > > > > > > > > > >

1 0

Re: [coreboot] Hey
by Vladimir 'φ-coder/phcoder' Serbinenko 20 Mar '14

20 Mar '14

On 20.03.2014 13:10, Shant Kehyeian wrote: > In fact I do need the SeaBios not the GRUB2 to be able to boot from usb > with live CD which I can format and install my preferred OS... > I think you're missing the "ARM" part. Only ARM distros have any chance to work. Given fragmentation of ARM it may even mean that only Linux-based works on your machine. > > On Thu, Mar 20, 2014 at 4:05 PM, Vladimir 'φ-coder/phcoder' Serbinenko > <phcoder(a)gmail.com <mailto:phcoder@gmail.com>> wrote: > > On 20.03.2014 12:12, Shant Kehyeian wrote: > > Hello, > > I have Samsung ARM chromebook series 3 "Snow" and I am trying to flesh > > it and change the boot process. > > So I build a coreboot.rom for that, but before I start to do that I > > would like to ask about the payload. When I did the "make > menuconfig" it > > wasn't by default the SeaBios., there wasn't at all ...there was > GRUB 2 > > and I selected it...so My question is would it work as SeaBios to boot > > from usb ? > There is no arm-coreboot GRUB2 port currently. > > Thank you. > > > > > > >

1 0

Re: [coreboot] Hey
by Peter Stuge 20 Mar '14

20 Mar '14

Shant Kehyeian wrote: > Ahhh...So how will I use the coreboot for "Snow"... Wait or pay for someone to publish exact steps which you can reproduce. > I mean If I build SeaBios on Arm architecture and use it...would it be > useful ? SeaBIOS can not be built for ARM. As I wrote, BIOS is x86-specific. > Could you please give me a solution to use the coreboot and boot my > own Ubuntu or Fedora on my ARM samsung chromebook ? Nope, I can't. //Peter

2 1

Re: [coreboot] Hey
by Vladimir 'φ-coder/phcoder' Serbinenko 20 Mar '14

20 Mar '14

On 20.03.2014 12:12, Shant Kehyeian wrote: > Hello, > I have Samsung ARM chromebook series 3 "Snow" and I am trying to flesh > it and change the boot process. > So I build a coreboot.rom for that, but before I start to do that I > would like to ask about the payload. When I did the "make menuconfig" it > wasn't by default the SeaBios., there wasn't at all ...there was GRUB 2 > and I selected it...so My question is would it work as SeaBios to boot > from usb ? There is no arm-coreboot GRUB2 port currently. > Thank you. > >

1 0

Re: [coreboot] Hey
by Peter Stuge 20 Mar '14

20 Mar '14

Hi, Shant Kehyeian wrote: > I have Samsung ARM chromebook .. > I would like to ask about the payload. When I did the "make menuconfig" > it wasn't by default the SeaBios., there wasn't at all ...there was > GRUB 2 and I selected it...so My question is would it work as SeaBios > to boot from usb ? No. SeaBIOS is a BIOS implementation and BIOS is fortunately x86-specific. The method used by BIOSes to boot from USB doesn't apply at all on other machines. Unless someone provides a well-tested recipe for creating a full working solution to replace what was shipped on your device I would very strongly discourage you from experimenting with firmware unless you are prepared to spend many days on doing recovery and years on learning, as well as maybe a hundred USD/EUR/GBP on tools. //Peter

2 1

Hey
by Shant Kehyeian 20 Mar '14

20 Mar '14

Hello, I have Samsung ARM chromebook series 3 "Snow" and I am trying to flesh it and change the boot process. So I build a coreboot.rom for that, but before I start to do that I would like to ask about the payload. When I did the "make menuconfig" it wasn't by default the SeaBios., there wasn't at all ...there was GRUB 2 and I selected it...so My question is would it work as SeaBios to boot from usb ? Thank you.

1 0

Re: [coreboot] GSoC-2014 Coreboot project
by Allen Yan 20 Mar '14

20 Mar '14

Hi, David, When at AsusTek Suzhou, my work is mainly responsible for bios porting and fixing bug. There were four mainboards P5KPL-S, P5QL-E, P5QL-SE, P5QL. All based on Intel platform and AMI Legacy BIOS Core In the second half year of 2008, I worked on pre-development of EFI-BIOS for ASUS mainboard. I wrote a Dual bootblock module and added NTFS support(read only) for AutoRecovery module using AMI Apito platform (based on EFI). Interesting experience, but memories will fade! Details can't be remembered clearly. >As Vladimir said, if the chipset is unsupported then writing MRC for it will be a very long and difficult process. If the chipset is supported then adding mainboard support may be a relatively simple task that not sufficient for GSoC. Do we need to write MRC by ourselves in coreboot? Isn't MRC code supported by Intel? >If you have experience with UEFI, perhaps you can implement features that are missing in our Tianocore support: http://www.coreboot.org/TianoCore . Implementing UEFI CBFS driver and GOP driver are very clear goal. questions: I don't know whether coreboot or some payload implement common flash interface for flash programming software. If not, why? >https://trello.com/b/pEdlwYTb/tiano-payload It seems that Tiano payload is a very activity project. I think I can try my best to implement one feature or twp for the project! Like use a seperate Fv in CBFS as Fault Tolerant Variable Storage Look forward to your kind advice! On 3/20/14, David Hendricks <dhendrix(a)google.com> wrote: > Hi Jinyi, > Can you provide more details about your work as a BIOS engineer? > > As Vladimir said, if the chipset is unsupported then writing MRC for it > will be a very long and difficult process. If the chipset is supported then > adding mainboard support may be a relatively simple task that not > sufficient for GSoC. > > If you have experience with UEFI, perhaps you can implement features that > are missing in our Tianocore support: http://www.coreboot.org/TianoCore . > > > On Wed, Mar 19, 2014 at 6:06 AM, Allen Yan <lexkde(a)gmail.com> wrote: > >> Hi, >> I am Jinyi Yan , a second year PhD candidate from Shanghai Institute >> of Micro-system and Information Technology, Chinese Academy of >> Sciences. I used to be a mainboard BIOS engineer in ASUS Technology >> Suzhou Co., Ltd for about two years (2007.7~2009.2). My major now is >> optoelectronics. But I have a lot of fun while programming, in my >> heart the working experience of being a BIOS engineer is still very >> exciting. >> I think GsoC is a nice platform for me to participate the open source >> community. When I search the GsoC projects and organizations, the >> coreboot and flashrom projects are definitely the right choices for >> me. I have a spare ASUS P5KPL PC at my hand, but the chipset is not in >> the support list of coreboot project. >> As Stefan Tauner's suggestion, maybe porting coreboot to new mainboard >> or implementing advanced coreboot features on exsiting mainboards are >> nice too. >> Now I'm not very familiar with the program structure of coreboot, so I >> expect your guidence and hope to contribute for coreboot and flashrom >> even if my application is not accpeted. >> Thanks! Look forward to your kind advice! >> Regards, >> Jinyi Yan >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> http://www.coreboot.org/mailman/listinfo/coreboot >> > > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. >

1 0

Will coreboot work on my machine?
by Paolo Caroni 20 Mar '14

20 Mar '14

After reading the FAQ of coreboot, I decided to write here. ##Step 1: board vendor= asus board name= tuv4x CPU= Intel celeron 1.2GHz (but probably in the future I can put a VIA C3 1.2 Ghz) Northbridge= VIA VT82C694T Southbridge= VIA VT82C686B Sata controller= VIA VT6421A (added on PCI slot) ##Step2: -[0000:00]-+-00.0 VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] [1106:0691] +-01.0-[01]----00.0 S3 Inc. 86c365, 86c366 [Trio 3D] [5333:8904] +-04.0 VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] +-04.1 VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] +-04.2 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-04.3 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-04.4 VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] [1106:3057] +-05.0 C-Media Electronics Inc CMI8738/CMI8768 PCI Audio [13f6:0111] +-07.0 VIA Technologies, Inc. VT6421 IDE/SATA Controller [1106:3249] \-0a.0 Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] ##Step3: superiotool r6637 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=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=standard) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) 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 NSC Super I/O at 0x164e... Failed. Returned data: port=0xff, port+1=0xff Probing for Nuvoton Super I/O at 0x164e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x164e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x2e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x2e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x4e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x4e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 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... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff 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 Probing for VIA Super I/O at 0x3f0... Super I/O enabled, Super I/O configuration disabled Found VIA VT82C686A/VT82C686B (id=0x003c, rev=0x00) at 0x3f0 Probing for Server Engines Super I/O at 0x2e... Failed. Returned data: id=0xffff, rev=0xff ##Step4: flashrom v0.9.5.2-r1546 on Linux 3.2.0-4-686-pae (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (3 args): /usr/sbin/flashrom -p internal -V Calibrating delay loop... OS timer resolution is 2 usecs, 635M loops per second, 10 myus = 10 us, 100 myus = 98 us, 1000 myus = 995 us, 10000 myus = 9797 us, 8 myus = 9 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "System Manufacturer" DMI string system-product-name: "System Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "TUV4X" DMI string baseboard-version: "REV 1.xx" DMI string chassis-type: "Tower" Found chipset "VIA VT82C69x" with PCI ID 1106:0691. Enabling flash write... OK - searching further chips. Found chipset "VIA VT82C686A/B" with PCI ID 1106:0686. Enabling flash write... OK. The following protocols are supported: Non-SPI. Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for EMST F49B002UA, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0xffff, id2 0x00ff Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0x24, id2 0x2d, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0x24, id2 0x2d, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0x24, id2 0x2d Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0x03, id2 0x65, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0x25, id2 0x68, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x24, id2 0xea, id1 parity violation, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Restoring PCI config space for 00:04:0 reg 0x40 Restoring PCI config space for 00:04:0 reg 0x43 ##Step5: http://support.asus.com/download.aspx?SLanguage=en-us&m=tuv4x Thank you very much for your job, cheers, Paolo

2 1

Re: [coreboot] GSoC-2014 Coreboot project
by David Hendricks 19 Mar '14

19 Mar '14

Hi Jinyi, Can you provide more details about your work as a BIOS engineer? As Vladimir said, if the chipset is unsupported then writing MRC for it will be a very long and difficult process. If the chipset is supported then adding mainboard support may be a relatively simple task that not sufficient for GSoC. If you have experience with UEFI, perhaps you can implement features that are missing in our Tianocore support: http://www.coreboot.org/TianoCore . On Wed, Mar 19, 2014 at 6:06 AM, Allen Yan <lexkde(a)gmail.com> wrote: > Hi, > I am Jinyi Yan , a second year PhD candidate from Shanghai Institute > of Micro-system and Information Technology, Chinese Academy of > Sciences. I used to be a mainboard BIOS engineer in ASUS Technology > Suzhou Co., Ltd for about two years (2007.7~2009.2). My major now is > optoelectronics. But I have a lot of fun while programming, in my > heart the working experience of being a BIOS engineer is still very > exciting. > I think GsoC is a nice platform for me to participate the open source > community. When I search the GsoC projects and organizations, the > coreboot and flashrom projects are definitely the right choices for > me. I have a spare ASUS P5KPL PC at my hand, but the chipset is not in > the support list of coreboot project. > As Stefan Tauner's suggestion, maybe porting coreboot to new mainboard > or implementing advanced coreboot features on exsiting mainboards are > nice too. > Now I'm not very familiar with the program structure of coreboot, so I > expect your guidence and hope to contribute for coreboot and flashrom > even if my application is not accpeted. > Thanks! Look forward to your kind advice! > Regards, > Jinyi Yan > > -- > coreboot mailing list: coreboot(a)coreboot.org > http://www.coreboot.org/mailman/listinfo/coreboot > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

GSoC 2014 project Debug environment
by Kyösti Mälkki 19 Mar '14

19 Mar '14

Hi! GSoC 2013 was nice so I decided to apply again and hopefully continue on the same topic around debugging environment. Enhance early coreboot debugging Short description: The traditional way for coreboot developer to make a port for new mainboard is to add more messages on debug console and make changes until things worked. This approach is unusable for those community contributors who have no access to the full source of their coreboot system. My proposal attacks this problem by making SerialICE and/or remote GDB easily available early in coreboot, either over serial UART or USB EHCI debug, for most platforms from the coreboot supported mainboards -list. Full proposal text is available for comments is here: http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/kmalkki/… Thanks, Kyösti

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
18
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 March 2014