August 2014 - coreboot - mail.coreboot.org

Re: [coreboot] Try to get Intel Atom based COMe-cXLi2 Kontron board running
by ron minnich Aug. 18, 2014

Aug. 18, 2014

These are not stupid questions at all. Have you considered getting an EM100? That would give you a little more debugging. A post card is about the single most useful thing to have in the early going, so you should probably get that before you go much further. Beep is a lot harder than it used to be. While simple code may work on Linux, there's a lot more going on under the hood, because the simple beep can be driven by a very complex audio pipeline. Beep may not be a good place to start. Here's a slightly bigger question: does it have to be an x86? Could it be ARM? Because here's a true story. I'm answering questions from some security researchers who *were* working on a haswell chromebook (Acer C720). Last week they realized that Intel was not going to make the blobs available for the memory startup (MRC) and the ME for haswell chromebooks. Those blobs are available for the sandy and ivybridge chromebooks, but nothing that came after. Result: all the researcher's work is moving to the Samsung ARM Chromeook because the ARM vendors tend to be a lot more helpful (save for AMD, nowadays; there are lots of unanswered questions there). I'm sad about that because Acer C720 is a great laptop and haswell is a great chipset, but what can you do? Note that the new Acer 13 is an ARM Tegra system that runs coreboot. So, just to be sure: it has to be an Atom? It's a much harder road than an ARM nowadays. ron

1 0

Try to get Intel Atom based COMe-cXLi2 Kontron board running
by Manuel Huber Aug. 18, 2014

Aug. 18, 2014

Hello coreboot community, I'm currently trying to add support for the cXLi2 COM Express board from Kontron (I'm working for TTTech Automotive GmbH). On IRC, I have already talked to members of the coreboot community and started to prepare the new board. I'm basing my work on the iWave/iWRainbowG6 (which is quite different). Most important components are: - Processor: Intel Atom Z520PT - Chipset: Intel SCH US15WPT (Poulsbo) - Super-IO: Winbond W83627HG - BIOS flash chip: SST49LF008A Unfortunately, there was no output on the serial line and I haven't got a POST card yet. So I thought it should be easy to get the chipset to beep. I checked under Linux (using the vendor BIOS) and in the datasheet and it seems to be correct. I added the beep code to romstage.cc:main(). But nothing happened... I checked again, and thought that maybe, the boot process gets stuck earlier, so I rewrote the beep-code in ASM and added it just after entering protected mode (which seems to be pretty early...) -> but again, no sound. (under Linux both, the asm code, and the C-code work). Beep code: diff --git a/src/cpu/x86/32bit/entry32.inc b/src/cpu/x86/32bit/entry32.inc index f74e1b8..d46b883 100644 --- a/src/cpu/x86/32bit/entry32.inc +++ b/src/cpu/x86/32bit/entry32.inc @@ -52,6 +52,18 @@ __protected_start: /* Save the BIST value */ movl %eax, %ebp + /* Beep ! */ + movb $0xb6, %al + outb %al, $0x43 + movb $0xa9, %al + outb %al, $0x52 + movb $0x04, %al + outb %al, $0x52 + inb $0x61, %al + orb $0x03, %al + outb %al, $0x61 + movl %ebp, %eax + post_code(POST_ENTER_PROTECTED_MODE) movw $ROM_DATA_SEG, %ax ---------------------------------------------------------------------- 0xb6 => 10 11 011 0 Timer2 | Write LSB then MSB | Square Wave Output | binary ---------------------------------------------------------------------- So I guess I'm doing something completely wrong. I have to use an external flash programmer (DATAMAN-48Pro2) to actually program the flash chip since the SCH and my vendor bios image block access to the chip. So I can't use flashrom to program the device. The Dataman just loads the coreboot.rom image and write it to the memory. I'm currently just using the iWRainbowG6 code base directly (I though there that maybe I got my Kconfigs and Makefiles wrong)... (I have already created the new board and of course I want to prepare my code to be able to push it upstream if it ever works) However, using the original BIOS (which also takes 8192KB) and flashing it with the DATAMAN can boot. Is there something I'm forgetting, shouldn't the 'beep' work? Am I missing some initialization code? Sorry if my questions | assumptions are somehow stupid. I hope you can help me and point me in the right direction. Best regards, Manuel

1 0

coreboot for old mainboard
by Foli Ayivoh Aug. 17, 2014

Aug. 17, 2014

Hi, just wanted to know if I could install coreboot onto my old board? Thanks in advance! The requested data: board vendor: Shuttle board name: AN35N Ultra V1.1 CPU: AMD Athlon XP 3200+ northbridge: Nvidia nForce2 southbridge: Nvidia MCP vendor board info: http://www.shuttle.eu/_archive/older/en/an35n_faq.htm lspci -tvnn: -[0000:00]-+-00.0 NVIDIA Corporation nForce2 IGP2 [10de:01e0] +-00.1 NVIDIA Corporation nForce2 Memory Controller 1 [10de:01eb] +-00.2 NVIDIA Corporation nForce2 Memory Controller 4 [10de:01ee] +-00.3 NVIDIA Corporation nForce2 Memory Controller 3 [10de:01ed] +-00.4 NVIDIA Corporation nForce2 Memory Controller 2 [10de:01ec] +-00.5 NVIDIA Corporation nForce2 Memory Controller 5 [10de:01ef] +-01.0 NVIDIA Corporation nForce2 ISA Bridge [10de:0060] +-01.1 NVIDIA Corporation nForce2 SMBus (MCP) [10de:0064] +-02.0 NVIDIA Corporation nForce2 USB Controller [10de:0067] +-02.1 NVIDIA Corporation nForce2 USB Controller [10de:0067] +-02.2 NVIDIA Corporation nForce2 USB Controller [10de:0068] +-04.0 NVIDIA Corporation nForce2 Ethernet Controller [10de:0066] +-06.0 NVIDIA Corporation nForce2 AC97 Audio Controler (MCP) [10de:006a] +-08.0-[01-02]--+-04.0 Adaptec AIC-7892B U160/m [9005:0081] | +-07.0 Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller [1095:3512] +-09.0 NVIDIA Corporation nForce2 IDE [10de:0065] \-1e.0-[03]-- superiotool -dV: superiotool r6158 Found ITE IT8712F (id=0x8712, rev=0x5) at 0x2e flashrom -p internal -V: flashrom v0.9.7-r1711 on Linux 3.11.10-17-pae (i686) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.8.1 20130909 [gcc-4_8-branch revision 202388], little endian Command line (3 args): /usr/sbin/flashrom -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 901M loops per second, delay more than 10% too short (got 82% of expected delay), recalculating... 824M loops per second, delay more than 10% too short (got 75% of expected delay), recalculating... 1013M loops per second, 10 myus = 9 us, 100 myus = 163 us, 1000 myus = 919 us, 10000 myus = 33256 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: " " DMI string system-product-name: " " DMI string system-version: " " DMI string baseboard-manufacturer: "Shuttle Inc" DMI string baseboard-product-name: "AN35 " DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8712 on port 0x2e Found chipset "NVIDIA NForce2" with PCI ID 10de:0060. Enabling flash write... OK. Super I/O ID 0x8712 is not on the list of flash capable controllers. The following protocols are supported: Non-SPI. *** Probing output reduced to findings *** Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0xb0 Found Winbond flash chip "W49V002A" (256 kB, LPC) at physical address 0xfffc0000. Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0xb0 Found Winbond flash chip "W49V002A" (256 kB, LPC). No operations were specified. Restoring PCI config space for 00:01:0 reg 0x6d Restoring PCI config space for 00:01:0 reg 0x92

2 1

Re: [coreboot] f2a85m and e350m1 dmidecode
by David Hubbard Aug. 17, 2014

Aug. 17, 2014

On Sun, Aug 17, 2014 at 8:43 PM, The Gluglug <info(a)gluglug.org.uk> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > thanks! Do you know anyone with an e350m1? > Hmm, I think you can find some recent emails that mention the e350m1, within the last 6 months, by looking at the coreboot mailing list archive. I can't remember off the top of my head, though. > On 18/08/14 04:43, David Hubbard wrote: > > For f2a85 BIOS rev 5103 (an older version): > > > > # dmidecode 2.11 SMBIOS 2.7 present. 66 structures occupying 2602 > > bytes. Table at 0x000EB330. > > > > Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: > > American Megatrends Inc. Version: 5103 Release Date: 09/19/2012 > > Address: 0xF0000 Runtime Size: 64 kB ROM Size: 8192 kB > > Characteristics: PCI is supported BIOS is upgradeable BIOS > > shadowing is allowed 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) ACPI is supported USB > > legacy is supported BIOS boot specification is supported Targeted > > content distribution is supported UEFI is supported BIOS Revision: > > 4.6 > > > > Handle 0x0001, DMI type 1, 27 bytes System Information > > Manufacturer: System manufacturer Product Name: System Product > > Name Version: System Version Serial Number: System Serial Number > > UUID: [redacted] Wake-up Type: Power > > Switch SKU Number: SKU Family: To be filled by O.E.M. > > > > Handle 0x0002, DMI type 2, 15 bytes Base Board Information > > Manufacturer: ASUSTeK COMPUTER INC. Product Name: F2A85-M Version: > > Rev X.0x Serial Number: 000000000000000 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, 22 bytes Chassis Information > > Manufacturer: Chassis Manufacture Type: Desktop Lock: Not Present > > Version: Chassis Version Serial Number: Chassis Serial Number Asset > > Tag: Asset-1234567890 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 SKU Number: To be filled by O.E.M. > > > > Handle 0x0004, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: PS/2 Keyboard/Mouse Internal > > Connector Type: None External Reference Designator: PS/2 > > Keyboard/Mouse External Connector Type: PS/2 Port Type: Keyboard > > Port > > > > Handle 0x0005, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB34 Internal Connector Type: None > > External Reference Designator: USB34 External Connector Type: > > Access Bus (USB) Port Type: USB > > > > Handle 0x0006, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SPDIFO Internal Connector Type: > > None External Reference Designator: SPDIFO External Connector Type: > > Other Port Type: Other > > > > Handle 0x0007, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: HDMI Internal Connector Type: None > > External Reference Designator: HDMI port External Connector Type: > > Other Port Type: Other > > > > Handle 0x0008, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: D-SUB Internal Connector Type: None > > External Reference Designator: D-SUB port External Connector Type: > > Other Port Type: Other > > > > Handle 0x0009, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: DVI Internal Connector Type: None > > External Reference Designator: DVI port External Connector Type: > > Other Port Type: Other > > > > Handle 0x000A, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: ESATA Internal Connector Type: None > > External Reference Designator: ESATA External Connector Type: > > SAS/SATA Plug Receptacle Port Type: SATA > > > > Handle 0x000B, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB3_12 Internal Connector Type: > > None External Reference Designator: USB3_12 External Connector > > Type: Access Bus (USB) Port Type: USB > > > > Handle 0x000C, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: LAN Internal Connector Type: None > > External Reference Designator: LAN External Connector Type: RJ-45 > > Port Type: Network Port > > > > Handle 0x000D, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB12 Internal Connector Type: None > > External Reference Designator: USB12 External Connector Type: > > Access Bus (USB) Port Type: USB > > > > Handle 0x000E, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: Audio_Line_In Internal Connector > > Type: None External Reference Designator: Audio_Line_In External > > Connector Type: Mini Jack (headphones) Port Type: Audio Port > > > > Handle 0x000F, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: Audio_Line_Out Internal Connector > > Type: None External Reference Designator: Audio_Line_Out External > > Connector Type: Mini Jack (headphones) Port Type: Audio Port > > > > Handle 0x0010, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: Audio_Mic_In 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: Audio_Center/Sub Internal Connector > > Type: None External Reference Designator: Audio_Center/Sub External > > Connector Type: Mini Jack (headphones) Port Type: Audio Port > > > > Handle 0x0012, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: Audio_Rear Internal Connector Type: > > None External Reference Designator: Audio_Rear External Connector > > Type: Mini Jack (headphones) Port Type: Audio Port > > > > Handle 0x0013, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: Audio_Side Internal Connector Type: > > None External Reference Designator: Audio_Side External Connector > > Type: Mini Jack (headphones) Port Type: Audio Port > > > > Handle 0x0014, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_1 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x0015, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_2 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x0016, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_3 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x0017, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_4 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x0018, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_5 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x0019, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_6 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x001A, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SATA6G_7 Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x001B, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: ESATA6G Internal Connector Type: > > SAS/SATA Plug Receptacle External Reference Designator: Not > > Specified External Connector Type: None Port Type: SATA > > > > Handle 0x001C, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB3_34 Internal Connector Type: > > Access Bus (USB) External Reference Designator: Not Specified > > External Connector Type: None Port Type: USB > > > > Handle 0x001D, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB78 Internal Connector Type: > > Access Bus (USB) External Reference Designator: Not Specified > > External Connector Type: None Port Type: USB > > > > Handle 0x001E, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB910 Internal Connector Type: > > Access Bus (USB) External Reference Designator: Not Specified > > External Connector Type: None Port Type: USB > > > > Handle 0x001F, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB34 Internal Connector Type: > > Access Bus (USB) External Reference Designator: Not Specified > > External Connector Type: None Port Type: USB > > > > Handle 0x0020, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: USB56 Internal Connector Type: > > Access Bus (USB) External Reference Designator: Not Specified > > External Connector Type: None Port Type: USB > > > > Handle 0x0021, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: PANEL Internal Connector Type: > > Other External Reference Designator: Not Specified External > > Connector Type: None Port Type: Other > > > > Handle 0x0022, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: COM1 Internal Connector Type: 9 Pin > > Dual Inline (pin 10 cut) External Reference Designator: Not > > Specified External Connector Type: None Port Type: Other > > > > Handle 0x0023, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: SPDIF_OUT Internal Connector Type: > > Other External Reference Designator: Not Specified External > > Connector Type: None Port Type: Other > > > > Handle 0x0024, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: AAFP Internal Connector Type: Mini > > Jack (headphones) External Reference Designator: Not Specified > > External Connector Type: None Port Type: Audio Port > > > > Handle 0x0025, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: CPU_FAN Internal Connector Type: > > Other External Reference Designator: Not Specified External > > Connector Type: None Port Type: Other > > > > Handle 0x0026, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: CHA_FAN Internal Connector Type: > > Other External Reference Designator: Not Specified External > > Connector Type: None Port Type: Other > > > > Handle 0x0027, DMI type 8, 9 bytes Port Connector Information > > Internal Reference Designator: PWR_FAN Internal Connector Type: > > Other External Reference Designator: Not Specified External > > Connector Type: None Port Type: Other > > > > Handle 0x0028, DMI type 9, 17 bytes System Slot Information > > Designation: PCIEX16_1 Type: 32-bit PCI Express Current Usage: In > > Use Length: Short ID: 1 Characteristics: 3.3 V is provided Opening > > is shared PME signal is supported Bus Address: 0000:00:01.0 > > > > Handle 0x0029, DMI type 9, 17 bytes System Slot Information > > Designation: PCIEX1_2 Type: 32-bit PCI Express Current Usage: In > > Use Length: Short ID: 2 Characteristics: 3.3 V is provided Opening > > is shared PME signal is supported Bus Address: 0000:00:1c.4 > > > > Handle 0x002A, DMI type 9, 17 bytes System Slot Information > > Designation: PCI1 Type: 32-bit PCI Current Usage: In Use Length: > > Short ID: 3 Characteristics: 3.3 V is provided Opening is shared > > PME signal is supported Bus Address: 0000:00:1c.6 > > > > Handle 0x002B, DMI type 9, 17 bytes System Slot Information > > Designation: PCIEX16_2 Type: 32-bit PCI Express Current Usage: In > > Use Length: Short ID: 4 Characteristics: 3.3 V is provided Opening > > is shared PME signal is supported Bus Address: 0000:00:01.0 > > > > Handle 0x002C, DMI type 10, 10 bytes On Board Device 1 Information > > Type: Video Status: Enabled Description: To Be Filled By O.E.M. > > On Board Device 2 Information Type: Ethernet Status: Enabled > > Description: To Be Filled By O.E.M. On Board Device 3 Information > > Type: Sound Status: Enabled Description: To Be Filled By O.E.M. > > > > Handle 0x002D, DMI type 11, 5 bytes OEM Strings String 1: To Be > > Filled By O.E.M. > > > > Handle 0x002E, DMI type 12, 5 bytes System Configuration Options > > Option 1: To Be Filled By O.E.M. > > > > Handle 0x002F, DMI type 16, 23 bytes Physical Memory Array > > Location: System Board Or Motherboard Use: System Memory Error > > Correction Type: None Maximum Capacity: 8 GB Error Information > > Handle: Not Provided Number Of Devices: 4 > > > > Handle 0x0030, DMI type 19, 31 bytes Memory Array Mapped Address > > Starting Address: 0x00000000000 Ending Address: 0x003FFFFFFFF Range > > Size: 16 GB Physical Array Handle: 0x002F Partition Width: 255 > > > > Handle 0x0031, DMI type 17, 34 bytes Memory Device Array Handle: > > 0x002F Error Information Handle: Not Provided Total Width: 64 bits > > Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None > > Locator: DIMM_A1 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: > > Synchronous Unbuffered (Unregistered) Speed: 800 MHz Manufacturer: > > Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum1 Part > > Number: F3-17000CL11-4GBXL Rank: 2 Configured Clock Speed: Unknown > > > > Handle 0x0032, DMI type 20, 35 bytes Memory Device Mapped Address > > Starting Address: 0x00000000000 Ending Address: 0x000FFFFFFFF Range > > Size: 4 GB Physical Device Handle: 0x0031 Memory Array Mapped > > Address Handle: 0x0030 Partition Row Position: 1 > > > > Handle 0x0033, DMI type 17, 34 bytes Memory Device Array Handle: > > 0x002F Error Information Handle: Not Provided Total Width: 64 bits > > Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None > > Locator: DIMM_A2 Bank Locator: A1_BANK1 Type: DDR3 Type Detail: > > Synchronous Unbuffered (Unregistered) Speed: 800 MHz Manufacturer: > > Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum0 Part > > Number: F3-17000CL11-4GBXL Rank: 2 Configured Clock Speed: 39335 > > MHz > > > > Handle 0x0034, DMI type 20, 35 bytes Memory Device Mapped Address > > Starting Address: 0x00100000000 Ending Address: 0x001FFFFFFFF Range > > Size: 4 GB Physical Device Handle: 0x0033 Memory Array Mapped > > Address Handle: 0x0030 Partition Row Position: 1 > > > > Handle 0x0035, DMI type 17, 34 bytes Memory Device Array Handle: > > 0x002F Error Information Handle: Not Provided Total Width: 64 bits > > Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None > > Locator: DIMM_B1 Bank Locator: A1_BANK2 Type: DDR3 Type Detail: > > Synchronous Unbuffered (Unregistered) Speed: 800 MHz Manufacturer: > > Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum2 Part > > Number: F3-17000CL11-4GBXL Rank: 2 Configured Clock Speed: Unknown > > > > Handle 0x0036, DMI type 20, 35 bytes Memory Device Mapped Address > > Starting Address: 0x00200000000 Ending Address: 0x002FFFFFFFF Range > > Size: 4 GB Physical Device Handle: 0x0035 Memory Array Mapped > > Address Handle: 0x0030 Partition Row Position: 1 > > > > Handle 0x0037, DMI type 17, 34 bytes Memory Device Array Handle: > > 0x002F Error Information Handle: Not Provided Total Width: 64 bits > > Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None > > Locator: DIMM_B2 Bank Locator: A1_BANK3 Type: DDR3 Type Detail: > > Synchronous Unbuffered (Unregistered) Speed: 800 MHz Manufacturer: > > Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum3 Part > > Number: F3-17000CL11-4GBXL Rank: 2 Configured Clock Speed: 1 MHz > > > > Handle 0x0038, DMI type 20, 35 bytes Memory Device Mapped Address > > Starting Address: 0x00300000000 Ending Address: 0x003FFFFFFFF Range > > Size: 4 GB Physical Device Handle: 0x0037 Memory Array Mapped > > Address Handle: 0x0030 Partition Row Position: 1 > > > > Handle 0x0039, DMI type 32, 20 bytes System Boot Information > > Status: No errors detected > > > > Handle 0x003A, DMI type 41, 11 bytes Onboard Device Reference > > Designation: Onboard IGD Type: Video Status: Enabled Type > > Instance: 1 Bus Address: 0000:00:02.0 > > > > Handle 0x003B, DMI type 41, 11 bytes Onboard Device Reference > > Designation: Onboard LAN Type: Ethernet Status: Enabled Type > > Instance: 1 Bus Address: 0000:00:19.0 > > > > Handle 0x003C, DMI type 41, 11 bytes Onboard Device Reference > > Designation: Onboard 1394 Type: Other Status: Enabled Type > > Instance: 1 Bus Address: 0000:03:1c.2 > > > > Handle 0x003D, DMI type 7, 19 bytes Cache Information Socket > > Designation: L1 CACHE Configuration: Enabled, Not Socketed, Level > > 1 Operational Mode: Write Back Location: Internal Installed Size: > > 192 kB Maximum Size: 192 kB Supported SRAM Types: Pipeline Burst > > Installed SRAM Type: Pipeline Burst Speed: 1 ns Error Correction > > Type: Multi-bit ECC System Type: Unified Associativity: 2-way > > Set-associative > > > > Handle 0x003E, DMI type 7, 19 bytes Cache Information Socket > > Designation: L2 CACHE Configuration: Enabled, Not Socketed, Level > > 2 Operational Mode: Write Back Location: Internal Installed Size: > > 4096 kB Maximum Size: 4096 kB Supported SRAM Types: Pipeline Burst > > Installed SRAM Type: Pipeline Burst Speed: 1 ns Error Correction > > Type: Multi-bit ECC System Type: Unified Associativity: 16-way > > Set-associative > > > > Handle 0x0047, DMI type 4, 42 bytes Processor Information Socket > > Designation: FM2 Type: Central Processor Family: <OUT OF SPEC> > > Manufacturer: AuthenticAMD ID: 31 0F 61 00 FF FB 8B 17 Version: AMD > > A10-6800K APU with Radeon(tm) HD Graphics Voltage: 1.3 V External > > Clock: 100 MHz Max Speed: 4100 MHz Current Speed: 4100 MHz Status: > > Populated, Enabled Upgrade: <OUT OF SPEC> L1 Cache Handle: 0x003D > > L2 Cache Handle: 0x003E L3 Cache Handle: Not Provided Serial > > Number: Not Specified Asset Tag: Not Specified Part Number: Not > > Specified Core Count: 4 Core Enabled: 4 Thread Count: 4 > > Characteristics: 64-bit capable > > > > Handle 0x0048, DMI type 13, 22 bytes BIOS Language Information > > Language Description Format: Long Installable Languages: 8 > > en|US|iso8859-1 fr|FR|iso8859-1 es|ES|iso8859-1 de|DE|iso8859-1 > > ru|RU|iso8859-5 ja|JP|unicode zh|TW|unicode zh|CN|unicode Currently > > Installed Language: en|US|iso8859-1 > > > > Handle 0x0049, DMI type 127, 4 bytes End Of Table > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJT8XZ1AAoJEP9Ft0z50c+Uqt8IALfc2WPv27t1LqqoW5h3Db5n > Nkfv1IIu/yungrFLuigu93HcnDO7Xg4A4rboWOhbiOyNIFAc35lPeyJ/wtv4qhjX > 3Oo+NJ3IFJMuFSRK7/PikIPcb8fEAwbmmEkKWn0c9s2QtmHmdxmaEcY6jQ9GPdNs > lrMY/jUjUgJxcgHMidPw55xAL+0m9c9VhLuaenk9xX1EvdFU/fk4QuftpX5bGdAS > FDtOxIxTv/HQ0yGnUKfcDx8p7BYae3lv2g7QR5u/GEZKon72hlmtc9PvYAPH0wda > NTj8u+wI2sX5vx+mdi2K05F6hI4Ic2jKaI7SavImFCUXTOIAcKDkW81PY8dkctI= > =X277 > -----END PGP SIGNATURE----- >

1 0

f2a85m and e350m1 dmidecode
by The Gluglug Aug. 17, 2014

Aug. 17, 2014

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can someone with one of these boards attach their dmidecode output (from factory bios)? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT8XS7AAoJEP9Ft0z50c+U268H/RmIiirFcC9GadB8v/94mkq6 beiXEMqwOPTb7+vC4JF2AsQ7n7pFLY8GRoox2LlcbyPdJMt5UEun1mlpndB381Sb SNaNzUZjxfnGVZPxsNx5PaAlzBfBC2ZjwJrW/Mk8iTdZrsVRINulMOooI6ohW66X iN+mtzz4ns/csGKrXKzcr0B01zMIbqVVPSGdHJzq29o+tUbMRL4LCVU7/vSOLn4V 8OwkwlZETJEBxDFGH/vR75wOFb+uX6BGPf3E18Cegz/N90f6fYScVkeovMetXaum cGyb8lH/04QJX90C08tx1IMjlOlEDenn2CUn6idvfXftuvCCpvyXD8XAgSZgmWQ= =JpFo -----END PGP SIGNATURE-----

1 0

Re: [coreboot] qemu-armv7: memcpy to ROMSTAGE_BASE
by Piotr Król Aug. 16, 2014

Aug. 16, 2014

On Sat, Aug 16, 2014 at 01:15:05PM -0700, ron minnich wrote: > The ROMSTAGE on ARM is expected to be SRAM. When you know the SRAM > address for a given mainboard, you need to set it up in Kconfig for > *just* that mainboard. > > Nice work, I think you're getting close! Thanks :) Meanwhile I was able to boot qemu-armv7. It was all about memory map. All changes that I did: --- a/src/mainboard/emulation/qemu-armv7/Kconfig +++ b/src/mainboard/emulation/qemu-armv7/Kconfig @@ -64,11 +64,11 @@ config DRAM_SIZE_MB config BOOTBLOCK_BASE hex - default 0x00010000 + default 0x00000000 config ROMSTAGE_BASE hex - default 0x00020000 + default 0x48040000 config RAMSTAGE_BASE hex @@ -88,11 +88,11 @@ config CBFS_ROM_OFFSET config STACK_TOP hex - default 0x0007ff00 + default 0x4803ff00 config STACK_BOTTOM hex - default 0x00040000 + default 0x48000000 config STACK_SIZE hex I also asked qemu developers about vexpress-a9 memory map [1] and submit a noob-like blog post about debugging session of this issue [2]. If you want I can commit above changes (after I figure out how to use gerrit and all that stuff). This of course mean that '-bios' option in qemu-system-arm should be used. One last questions which bootloader you will suggest to boot Linux kernel ? U-Boot ? Or maybe it is possible to boot it directly from coreboot ? Is there tutorial/manual how to do that ? [1] http://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg02599.html [2] http://pietrushnic.github.io/blog/2014/08/07/debugging-coreboot-for-qemu-ar…

1 0

qemu-armv7: memcpy to ROMSTAGE_BASE
by Piotr Król Aug. 16, 2014

Aug. 16, 2014

Hi all, during debugging of qemu-armv7 I found that coreboot performs memcpy to ROMSTAGE_BASE area. This is in src/arch/armv7/memcpy.S: 3: PLD( pld [r1, #124] ) 4: ldr8w r1, r3, r4, r5, r6, r7, r8, ip, lr, abort=20f subs r2, r2, #32 str8w r0, r3, r4, r5, r6, r7, r8, ip, lr, abort=20f bge 3b r0 at this moment (for qemu-armv7) is 0x10000 (ROMSTAGE_BASE). Is it ok that ROM area is used as storage during memory copying ? Shouldn't it be considered read only ? Am I missing something here ? Because coreboot execute from RAM this is not the problem but when I try to execute it from flash ('-bios' option) I'm unable to boot because qemu emulates flash as read only area. Is it ok to move ROMSTAGE_BASE to SRAM or this is violation of general rule ? Thanks, Piotr

2 1

nvidia/tegra build tool
by Isaac Aug. 15, 2014

Aug. 15, 2014

The new nvidia/tegra124 support requires a build tool from NVIDIA called cbootimage (https://github.com/NVIDIA/cbootimage) I'm not sure of the best way to add support into coreboot so I'd like to get some feedback. Would it make sense to just add it into the util directory and build as needed?

5 4

Re: [coreboot] board_status.sh output from PC Engines ALIX 2c3
by Paul Menzel Aug. 15, 2014

Aug. 15, 2014

Am Mittwoch, den 13.08.2014, 23:25 +0100 schrieb Sevan / Venture37: > > On 12 August 2014 07:11, Paul Menzel <paulepanter(a)users.sourceforge.net> wrote: > >> Thanks a lot. Could you please enable CBMEM console (menu Console) and > >> time stamp capture (menu General)? Please check if CBMEM console is > >> enabled in your payload (GRUB/SeaBIOS) too. > > > > Sure, will build a new image tonight & post up the results for you. > > done, this time there was no coreboot_timestamp.txt created You did not enable time stamp collection. You need to enable them. Please verify with the following command. $ grep TIMES .config CONFIG_COLLECT_TIMESTAMPS=y > http://pastebin.com/16LBAfBL Thanks. Could you please attach the files to save the work to create and cop- paste the contents manually? In my opinion paste bin services are only useful for IRC. For emails you should always paste directly or attach the content. Thanks, Paul PS: It’d be great if you opened a separate thread about your issue with `board_status.sh -u`. Thanks, Paul

2 1

Re: [coreboot] [Heads up] CPU_ADDR_BITS set to 36 bits again on most Intel device
by Paul Menzel Aug. 14, 2014

Aug. 14, 2014

Am Dienstag, den 12.08.2014, 11:01 +0100 schrieb WANG FEI: > I noticed this issue before, Kconfig will take default CPU_ADDR_BITS with > the value 32 in src\cpu\intel\model_106cx\Kconfig instead of the value 36 > src\cpu\x86\Kconfig. To avoid this issue, you have to override > CPU_ADDR_BITS in your own Kconfig file same as what Baytrail project has > done. Indeed. As the change set #6535 [1] has been submitted, you do not need to do that anymore. Thanks, Paul PS: Did you report that issue to the list? It might have been fixed earlier if you had done that. [1] http://review.coreboot.org/6535

2 1