Hi ! Ive just joined the mailing list, to see if it is possible to get an Asus G1 (laptop) use coreboot.
I recently killed my bios doing some experiments, so i desoldered the chip, and put a nice socket. (it is a PLCC32). Also i have the equipment needed to program this chip, so no worries there.
Details :
- Laptop : Asus G1 , first revisions. IMPORTANT NOTE: Video card is a Geforce Go 7700 512MB, and video bios is integrated as a module in bios rom (amibios) - Attached lspci outpu - No super io chip (it seems) - PLCC32 SST49LF004B (49LF004B-33-4C-NH Rev CA, according to specs it is lpc/fwh) - Host bridge: Intel Corporation Mobile 945GM/PM/GMS - South Bridge : ICH7 Family
- Bios : http://ivn.cl/software/asus_g1.rom (read with flasrom)
Actually, running linux 64bits, with no problems. (i just want a fater startup, and see if there is any way to break the memory remapping function non existant in asus rom... 4GB ram installed, only 2.9 Usable , and... try some other OS)
Thanks :)
# dmidecode 2.10 SMBIOS 2.3 present. 35 structures occupying 1474 bytes. Table at 0x000FC610.
Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: G1AS.209 Release Date: 07/20/2007 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 512 kB Characteristics: ISA is supported PCI is supported PC Card (PCMCIA) is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 8.12
Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK Computer Inc. Product Name: G1 Version: 1.0 Serial Number: SSN12345678901234567 UUID: 39A20E00-5737-1480-BF5A-001A92EFF856 Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M.
Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK Computer Inc. Product Name: G1 Version: 1.0 Serial Number: BSN12345678901234567 Asset Tag: To Be Filled By O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To Be Filled By O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0
Handle 0x0003, DMI type 3, 21 bytes Chassis Information Manufacturer: ASUSTeK Computer Inc. Type: Notebook Lock: Not Present Version: Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0
Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Other Manufacturer: Intel ID: F6 06 00 00 FF FB EB BF Signature: Type 0, Family 6, Model 15, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Hyper-threading technology) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz Voltage: 3.3 V 2.9 V External Clock: 668 MHz Max Speed: 2004 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Socket 423 L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: Not Provided Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: To Be Filled By O.E.M.
Handle 0x0005, DMI type 7, 19 bytes Cache Information Socket Designation: L1-Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Varies With Memory Address Location: Internal Installed Size: 64 kB Maximum Size: 64 kB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: Unknown Error Correction Type: Single-bit ECC System Type: Data Associativity: 4-way Set-associative
Handle 0x0006, DMI type 7, 19 bytes Cache Information Socket Designation: L2-Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Varies With Memory Address Location: Internal Installed Size: 4096 kB Maximum Size: 4096 kB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 4-way Set-associative
Handle 0x0007, DMI type 5, 20 bytes Memory Controller Information Error Detecting Method: None Error Correcting Capabilities: None Supported Interleave: One-way Interleave Current Interleave: One-way Interleave Maximum Memory Module Size: 1024 MB Maximum Total Memory Size: 2048 MB Supported Speeds: Other 70 ns 60 ns 50 ns Supported Memory Types: Standard DIMM SDRAM Memory Module Voltage: 3.3 V Associated Memory Slots: 2 0x0008 0x0009 Enabled Error Correcting Capabilities: None
Handle 0x0008, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM0 Bank Connections: 0 1 Current Speed: Unknown Type: Standard DIMM SDRAM Installed Size: 2048 MB (Double-bank Connection) Enabled Size: 2048 MB (Double-bank Connection) Error Status: OK
Handle 0x0009, DMI type 6, 12 bytes Memory Module Information Socket Designation: DIMM1 Bank Connections: 2 3 Current Speed: Unknown Type: Standard DIMM SDRAM Installed Size: 2048 MB (Double-bank Connection) Enabled Size: 2048 MB (Double-bank Connection) Error Status: OK
Handle 0x000A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: PS2Mouse External Connector Type: PS/2 Port Type: Mouse Port
Handle 0x000B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: Keyboard External Connector Type: PS/2 Port Type: Keyboard Port
Handle 0x000C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A2 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB
Handle 0x000D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB
Handle 0x000E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J4A1 Internal Connector Type: None External Reference Designator: LPT 1 External Connector Type: DB-25 male Port Type: Parallel Port ECP/EPP
Handle 0x000F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A1 Internal Connector Type: None External Reference Designator: COM A External Connector Type: DB-9 male Port Type: Serial Port 16550A Compatible
Handle 0x0010, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6A1 Internal Connector Type: None External Reference Designator: Audio Mic In External Connector Type: Mini Jack (headphones) Port Type: Audio Port
Handle 0x0011, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6A1 Internal Connector Type: None External Reference Designator: Audio Line In External Connector Type: Mini Jack (headphones) Port Type: Audio Port
Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6A1 Internal Connector Type: None External Reference Designator: Audio Line Out External Connector Type: Mini Jack (headphones) Port Type: Audio Port
Handle 0x0013, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J5A1 Internal Connector Type: None External Reference Designator: USB3 External Connector Type: Access Bus (USB) Port Type: USB
Handle 0x0014, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J5A1 Internal Connector Type: None External Reference Designator: USB4 External Connector Type: Access Bus (USB) Port Type: USB
Handle 0x0015, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6B1 - AUX IN Internal Connector Type: On Board Sound Input From CD-ROM External Reference Designator: Not Specified External Connector Type: None Port Type: Audio Port
Handle 0x0016, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6B2 - CDIN Internal Connector Type: On Board Sound Input From CD-ROM External Reference Designator: Not Specified External Connector Type: None Port Type: Audio Port
Handle 0x0017, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6J2 - PRI IDE Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other
Handle 0x0018, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6J1 - SEC IDE Internal Connector Type: On Board IDE External Reference Designator: Not Specified External Connector Type: None Port Type: Other
Handle 0x0019, DMI type 13, 22 bytes BIOS Language Information Installable Languages: 1 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1
Handle 0x001A, DMI type 15, 35 bytes System Event Log Area Length: 4 bytes Header Start Offset: 0x0000 Header Length: 2 bytes Data Start Offset: 0x0002 Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port Access Address: Index 0x046A, Data 0x046C Status: Invalid, Not Full Change Token: 0x00000000 Header Format: No Header Supported Log Type Descriptors: 6 Descriptor 1: End of log Data Format 1: OEM-specific Descriptor 2: End of log Data Format 2: OEM-specific Descriptor 3: End of log Data Format 3: OEM-specific Descriptor 4: End of log Data Format 4: OEM-specific Descriptor 5: End of log Data Format 5: OEM-specific Descriptor 6: End of log Data Format 6: OEM-specific
Handle 0x001B, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 4 GB Error Information Handle: Not Provided Number Of Devices: 2
Handle 0x001C, DMI type 19, 15 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000B80003FF Range Size: 3014657 kB Physical Array Handle: 0x001B Partition Width: 0
Handle 0x001D, DMI type 17, 27 bytes Memory Device Array Handle: 0x001B Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: DIMM Set: None Locator: DIMM0 Bank Locator: BANK0 Type: SDRAM Type Detail: Synchronous Speed: Unknown Manufacturer: Manufacturer0 Serial Number: SerNum0 Asset Tag: AssetTagNum0 Part Number: PartNum0
Handle 0x001E, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0007FFFFFFF Range Size: 2 GB Physical Device Handle: 0x001D Memory Array Mapped Address Handle: 0x001C Partition Row Position: 1 Interleaved Data Depth: 1
Handle 0x001F, DMI type 17, 27 bytes Memory Device Array Handle: 0x001B Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 2048 MB Form Factor: DIMM Set: None Locator: DIMM1 Bank Locator: BANK1 Type: SDRAM Type Detail: Synchronous Speed: Unknown Manufacturer: Manufacturer1 Serial Number: SerNum1 Asset Tag: AssetTagNum1 Part Number: PartNum1
Handle 0x0020, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00080000000 Ending Address: 0x000FFFFFFFF Range Size: 2 GB Physical Device Handle: 0x001F Memory Array Mapped Address Handle: 0x001C Partition Row Position: 1 Interleaved Data Depth: 1
Handle 0x0021, DMI type 32, 20 bytes System Boot Information Status: No errors detected
Handle 0x0022, DMI type 127, 4 bytes End Of Table
-[0000:00]-+-00.0 Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] +-01.0-[0000:01]----00.0 nVidia Corporation GeForce Go 7700 [10de:0397] +-1b.0 Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] +-1c.0-[0000:02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] +-1c.3-[0000:03]----00.0 Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] +-1d.0 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] +-1d.1 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] +-1d.2 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] +-1d.3 Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] +-1d.7 Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] +-1e.0-[0000:04-08]--+-01.0 Ricoh Co Ltd RL5c476 II [1180:0476] | +-01.1 Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] | +-01.2 Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] | -01.3 Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] +-1f.0 Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] -1f.2 Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller [8086:27c4]
superiotool r4356 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 ITE Super I/O (init=standard) 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=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 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 No Super I/O found
Ivan Barrera A. wrote:
Ive just joined the mailing list, to see if it is possible to get an Asus G1 (laptop) use coreboot.
Maybe. You could try a coreboot image for kontron/986lcd-m and see if you get any serial output. But please check where the serial port is on the kontron board, it may be on a superio, which may not be available on the G1 - in that case you need another debug output method..
//Peter
Peter Stuge escribió:
Ivan Barrera A. wrote:
Ive just joined the mailing list, to see if it is possible to get an Asus G1 (laptop) use coreboot.
Maybe. You could try a coreboot image for kontron/986lcd-m and see if you get any serial output. But please check where the serial port is on the kontron board, it may be on a superio, which may not be available on the G1 - in that case you need another debug output method..
The G1 does not have any serial port :/ (and havent find any on the mainboard).
I guess the screen output will have problems due to the integrated video rom... Is there any way to initialize video in this cases ?
//Peter
Ivan Barrera A. wrote:
you need another debug output method..
The G1 does not have any serial port :/ (and havent find any on the mainboard).
I guess the screen output will have problems due to the integrated video rom... Is there any way to initialize video in this cases ?
I'm afraid video is useless for debugging. It is enabled as the very last thing coreboot does. You need to be able to follow every step of coreboot as it runs.
Are there any other usable signals on the board? One bit is enough.
If you have budget for a PromICE it can interpret sequences of reads from the (emulated) flash chip as a debug write.
Or if you have VHDL skills and a bit of free time, you can add that functionality to the Artec LPC dongle or your favorite FPGA devkit.
//Peter
Peter Stuge escribió:
Ivan Barrera A. wrote:
you need another debug output method..
The G1 does not have any serial port :/ (and havent find any on the mainboard).
I guess the screen output will have problems due to the integrated video rom... Is there any way to initialize video in this cases ?
I'm afraid video is useless for debugging. It is enabled as the very last thing coreboot does. You need to be able to follow every step of coreboot as it runs.
Are there any other usable signals on the board? One bit is enough.
MMMh.... Need to check that. What kind of signals can be of use ? leds ? or more low-level
If you have budget for a PromICE it can interpret sequences of reads from the (emulated) flash chip as a debug write.
Tried to find pricing on that... havent found one. Do you happen to know how much it costs ?
Or if you have VHDL skills and a bit of free time, you can add that functionality to the Artec LPC dongle or your favorite FPGA devkit.
Interesting. However, that would require even more time xD I think i'll try the image you suggested soon, and see what it does. First i need to install another laptop to be the "programming station" in case everything goes wrong.
//Peter
On Thu, 2009-07-02 at 16:03 -0400, Ivan Barrera A. wrote:
Peter Stuge escribió:
Ivan Barrera A. wrote:
you need another debug output method..
The G1 does not have any serial port :/ (and havent find any on the mainboard).
I guess the screen output will have problems due to the integrated video rom... Is there any way to initialize video in this cases ?
I'm afraid video is useless for debugging. It is enabled as the very last thing coreboot does. You need to be able to follow every step of coreboot as it runs.
Are there any other usable signals on the board? One bit is enough.
MMMh.... Need to check that. What kind of signals can be of use ? leds ? or more low-level
If you have budget for a PromICE it can interpret sequences of reads from the (emulated) flash chip as a debug write.
Tried to find pricing on that... havent found one. Do you happen to know how much it costs ?
Or if you have VHDL skills and a bit of free time, you can add that functionality to the Artec LPC dongle or your favorite FPGA devkit.
Interesting. However, that would require even more time xD I think i'll try the image you suggested soon, and see what it does. First i need to install another laptop to be the "programming station" in case everything goes wrong.
Hi,
I think this could be a good testcase for SerialICE http://www.coreboot.org/pipermail/coreboot-announce/2009-June/000002.html
What do you think?
Cristi
Cristi Magherusan wrote:
I think this could be a good testcase for SerialICE What do you think?
I think it's difficult to use SerialICE without a serial port. :\
//Peter
Peter Stuge escribió:
Cristi Magherusan wrote:
I think this could be a good testcase for SerialICE What do you think?
I think it's difficult to use SerialICE without a serial port. :\
Well... instead of keep trying to find a way to mentally use a serial port, ive decided this weekend to just give it a try.
Im compiling coreboot-v2 using FILO as a payload, and, integrating the video blob (rom) that ive got before. (and i was tinkering with).
1 weird thing :
after compiling coreboot-v2 (rev 4397) , the make file in coreboot-v2/targets/kontron/986lcd-m/kontron_986lcd_m incorrectly had ./cbfs/cbfstool ./coreboot.rom add-payload ../payload.elf fallback/payload $(CBFS_COMPRESS_FLAG) (../payload.elf) in line 43. This made make complain about ../payload.elf beign an unknown target, and if put it there, cbfstool complained about not finding it. Just replaced with ./payload.elf.
I'll be tinkering with the dsdt.asl , to see if i can get my own for my laptop now.
Tomorrow (or the day after) i'll be opening my laptop yet again for cleaning. i'll let you know if i killed the laptop.. if it did something... or if it did nothing, but still looked cool :D
PS: I think (just think) it shoulndt matter if im using the laptop screen (lvds) or external monitor (dvi/vga) right ? or should i use only the lvds screen ? PS1: In the event that coreboot loads, and filo does get executed but no screen or there is no visible sign of "work"... what could be a good idea to try ? (added some specs in the end of this mail) PS2: The SST 49LF004B is 4mbit (512KB). How can i know what is the max size and type of chip i can put on it ? ive seen someone using a SST 49LF160C on a motherboard that also used the 49LF004B.
My laptop has the following put on :
- 4GB Ram = 2x2GB same brand,speed,timings. Also have to test 2X512MB same everything. - SSD Disk on Sata port 1. - Cdrom unit on Ide port 1. - Compact flash adapter on pcmcia port - PCI sd/mmc reader (ricoh) - Integrated r8169 network card. - Integrated modem (dont know which.. never used it) - lots of extra leds. - USB ports... i have Lots of USB adapters.. serial, parallel (only printer mode), eth, bluetooth (integrated), oled display (integrated), etc.
Ive contacted the vendor (Asus) many times before on the issue of bios recovery. They are not helpful on anything beside windows/software problems. (more than that... they havent been able to tell me how to access the bootblock on my bios, because some asus-media feature kicks in first)
//Peter
Peter Stuge escribió:
Ivan Barrera A. wrote:
Ive just joined the mailing list, to see if it is possible to get an Asus G1 (laptop) use coreboot.
Maybe. You could try a coreboot image for kontron/986lcd-m and see if you get any serial output. But please check where the serial port is on the kontron board, it may be on a superio, which may not be available on the G1 - in that case you need another debug output method..
First hickup : flashrom is able to read from the flash chip.. but cannot erase/write it.
I'll have to do all the procedure with the programmer.
[root@G1 kontron_986lcd_m]# flashrom -r /tmp/read.rom Calibrating delay loop... OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... OK. Found chip "SST SST49LF004A/B" (512 KB) at physical address 0xfff80000. Reading flash... done.
[root@G1 kontron_986lcd_m]# flashrom -w coreboot.rom Calibrating delay loop... OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... OK. Found chip "SST SST49LF004A/B" (512 KB) at physical address 0xfff80000. Note: If the following flash access fails, try -m <vendor>:<mainboard>. ERASE FAILED!
[root@G1 kontron_986lcd_m]# flashrom -m kontron:986lcd_m -w coreboot.rom Calibrating delay loop... OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... OK.
Unknown vendor:board from coreboot table or -m option: kontron:986lcd_m
Found chip "SST SST49LF004A/B" (512 KB) at physical address 0xfff80000. ERROR: Your firmware image (KONTRON:986LCD-M) does not appear to be correct for the detected mainboard (kontron:986lcd_m)
Override with --force if you are absolutely sure that you are using a correct image for this mainboard or override the detected values with --mainboard <vendor>:<mainboard>.
[root@G1 kontron_986lcd_m]# flashrom -m kontron:986lcd_m -w coreboot.rom --force Calibrating delay loop... OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... OK.
Unknown vendor:board from coreboot table or -m option: kontron:986lcd_m
Found chip "SST SST49LF004A/B" (512 KB) at physical address 0xfff80000. WARNING: This firmware image does not seem to fit to this machine - forcing it. ERASE FAILED!
Ivan Barrera A. wrote:
flashrom is able to read from the flash chip.. but cannot erase/write it.
Please run flashrom -V to get more debugging info. Maybe it's possible to add a board enable for the system, but I somehow doubt it.
//Peter
Peter Stuge escribió:
Ivan Barrera A. wrote:
flashrom is able to read from the flash chip.. but cannot erase/write it.
Please run flashrom -V to get more debugging info. Maybe it's possible to add a board enable for the system, but I somehow doubt it.
I included more info of the system in the first mail of the thread ;)
[root@G1 ~]# flashrom -V Calibrating delay loop... 268M loops per second, 100 myus = 198 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0xbf, id2 0x60 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 Am29F080B, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0xbf, id2 0x60
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 0xbf, id2 0x60
Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 0xbf, id2 0x60
Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for AMIC A25L40P, 512 KB: 4b ID not supported on this SPI controller
Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 MX25L1635D, 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 MX25L3235D, 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 MX25L12805, 16384 KB: spi_command called, but no SPI chipset/strapping detected
Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0xbf, id2 0x60
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 0xbf, id2 0x60
Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 SST25VF040.REMS, 512 KB: spi_command called, but no SPI chipset/strapping detected
Probing for SST SST25VF040B.REMS, 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 0xbf, id2 0x60
Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Found chip "SST SST49LF004A/B" (512 KB) at physical address 0xfff80000.
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 SST49LF020, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 0xbf, id2 0x60 Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for ST M29W040B, 512 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xbf, id2 0x60 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xbf, id2 0x60 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 0x81, id2 0xfb 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 0xbf, id2 0x60 Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xbf, id2 0x60 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, did 0x60 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 operations were specified.
Peter Stuge escribió:
Ivan Barrera A. wrote:
flashrom is able to read from the flash chip.. but cannot erase/write it.
Please run flashrom -V to get more debugging info. Maybe it's possible to add a board enable for the system, but I somehow doubt it.
I included more info of the system in the first mail of the thread ;)
[root@G1 ~]# flashrom -V Calibrating delay loop... 268M loops per second, 100 myus = 198 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0xbf, id2 0x60 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 Am29F080B, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0xbf, id2 0x60
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 0xbf, id2 0x60
Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 0xbf, id2 0x60
Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for AMIC A25L40P, 512 KB: 4b ID not supported on this SPI controller
Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 MX25L1635D, 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 MX25L3235D, 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 MX25L12805, 16384 KB: spi_command called, but no SPI chipset/strapping detected
Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xbf, id2 0x60
Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0xbf, id2 0x60
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 0xbf, id2 0x60
Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 SST25VF040.REMS, 512 KB: spi_command called, but no SPI chipset/strapping detected
Probing for SST SST25VF040B.REMS, 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 0xbf, id2 0x60
Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation
Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Found chip "SST SST49LF004A/B" (512 KB) at physical address 0xfff80000.
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 SST49LF020, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0xbf, id2 0x60
Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0xbf, id2 0x60
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 0xbf, id2 0x60 Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for ST M29W040B, 512 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0xbf, id2 0x60 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0xbf, id2 0x60 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 0x81, id2 0xfb 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 0xbf, id2 0x60 Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, id2 0x60 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0xbf, id2 0x60 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0xbf, id2 0x60 Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0xbf, id2 0x60 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 0xbf, did 0x60 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 operations were specified.
Ivan Barrera A. wrote:
Please run flashrom -V to get more debugging info. Maybe it's possible to add a board enable for the system, but I somehow doubt it.
I included more info of the system in the first mail of the thread ;)
Sorry. :\ Thanks for indulging me.
[root@G1 ~]# flashrom -V Calibrating delay loop... 268M loops per second, 100 myus = 198 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled
This basically says all lights are green, and writing isn't stopped in any way by the chipset.
It would be interesting if you could measure voltage on the flash chip pins 7 and 8. GND is on pin 16 and 28. Pin 1 is top center by the small mark on the chip, numbering is counter clockwise.
//Peter
Peter Stuge escribió:
Ivan Barrera A. wrote:
Please run flashrom -V to get more debugging info. Maybe it's possible to add a board enable for the system, but I somehow doubt it.
I included more info of the system in the first mail of the thread ;)
Sorry. :\ Thanks for indulging me.
[root@G1 ~]# flashrom -V Calibrating delay loop... 268M loops per second, 100 myus = 198 us. OK. No coreboot table found. Found chipset "Intel ICH7M", enabling flash write... BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1
Root Complex Register Block address = 0xfed1c000 GCS = 0xc64: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC) Top Swap : not enabled
This basically says all lights are green, and writing isn't stopped in any way by the chipset.
It would be interesting if you could measure voltage on the flash chip pins 7 and 8. GND is on pin 16 and 28. Pin 1 is top center by the small mark on the chip, numbering is counter clockwise.
Thats just with the laptop on, or when trying to read/write using flashrom ? I'll be able to do this later tonight (or tomorrow) when i finally make the test.
Ivan Barrera A. wrote:
It would be interesting if you could measure voltage on the flash chip pins 7 and 8. GND is on pin 16 and 28. Pin 1 is top center by the small mark on the chip, numbering is counter clockwise.
Thats just with the laptop on, or when trying to read/write using flashrom ? I'll be able to do this later tonight (or tomorrow) when i finally make the test.
Just with the laptop on is fine for starters, but it would be interesting to watch them also while running flashrom. (Just flashrom without any flags is ok.)
//Peter
Ivan Barrera A. escribió:
Hi ! Ive just joined the mailing list, to see if it is possible to get an Asus G1 (laptop) use coreboot.
I recently killed my bios doing some experiments, so i desoldered the chip, and put a nice socket. (it is a PLCC32). Also i have the equipment needed to program this chip, so no worries there.
Details :
- Laptop : Asus G1 , first revisions. IMPORTANT NOTE: Video card is a
Geforce Go 7700 512MB, and video bios is integrated as a module in bios rom (amibios)
- Attached lspci outpu
- No super io chip (it seems)
- PLCC32 SST49LF004B (49LF004B-33-4C-NH Rev CA, according to specs it is
lpc/fwh)
Host bridge: Intel Corporation Mobile 945GM/PM/GMS
South Bridge : ICH7 Family
Bios : http://ivn.cl/software/asus_g1.rom (read with flasrom)
No go for this one :( Flashed coreboot v2 (kontron), added video rom, adjusted for 512KB. flashrom didnt work, so i used my programmer with the corresponding FWH/LPC+ adaptor.
System turned on. Blank screen.
Wasnt able to measure voltages on the chip socket, as my voltimeter battery died.. so it will be for another time.