15h.org - User contributions [en]

ASUS KCMA-D8

2026-07-08T22:09:18Z

Sbrudenell: /* Kill-a-Watt Power Draw */

{{Infobox motherboard
|image = Asus-kcma-d8-top-64c7d3a66747d247126312.jpg
|image_size = 300

|introduced = 2010
|manufacturer = ASUS

|socket = 2x [[C32]]
|northbridge = 1x [[AMD SR5670]]
|southbridge = [[AMD SP5100]]
|superio = Winbond W83667HG-A
|bmc = ASPEED AST2050 (OpenBMC-compatible)
|bmcflash = Removable Module
|ram = 8 slots (4 channels) DDR3-1600 ECC UDIMM/RDIMM/LRDIMM
|bios = 2 MiB socketed DIP-8 (W25Q16V)
|formfactor =
SSI CEB, might fit in an ATX case that has 1 cm extra
|power = 1x 8-pin EPS

|slot1 = PCIe Gen2 x16
|slot2 = PCIe Gen2 x16 (electrically x8)
|slot3 = PCIe Gen2 x8 (electrically x4)
|slot4 = 32-bit Legacy PCI (5V)
|slot5 = 32-bit Legacy PCI (5V)
|slot6 = 32-bit Legacy PCI (5V)
|slot7 = ASUS [[PIKE2008]] Interface

|gpu = AST2050 Integrated VGA
|nic = 2x Intel 82574L Gigabit
|storagecontroller = SP5100's SATA2 (3.0 Gbps), no SAS unless [[PIKE2008]] installed
|usbcontroller = SP5100's onboard USB 2.0
|serial = One SIO-provided RS232, one virtual BMC console port
|audio = None (ASUS recommended a PCI sound card)
}}

Support for the KCMA-D8 motherboard by [[coreboot-15h]], 15h.org's downstream coreboot variant for fam15h systems, was recently completed.

== Open Source Firmware ==
Open source firmware for the KCMA-D8 is provided by [[coreboot-15h]] utilizing AMD's open source AGESA and CIMx releases for platform initialization. The git repository for the firmware can be reviewed [https://git.15h.org/mrothfuss/coreboot-15h here].

=== coreboot-15h ===
{{Excerpt|Coreboot-15h|[[ASUS KCMA-D8]]|hat=no}}

=== Missing Features ===
* SeaBIOS does not respond to keyboards behind a USB hub.
* Hibernation and Suspend/Resume are unsupported.
* Opteron 4100 series CPUs are unsupported.
* ASUS MIO audio cards are untested.

=== Flashing ===
To switch from the stock firmware to coreboot, [[External Flashing | external flashing]] is required. The DIP-8 flash chip is located at the bottom right corner of the board (labeled BIOS in the motherboard diagram). A 3.3V CH341a programmer can be used to flash coreboot onto the KCMA-D8. When switching to coreboot-15h from the OEM BIOS or coreboot, clearing the CMOS is required.

'''Clearing the CMOS'''
# Turn off the computer and disconnect the power cord
# Move the CLRTC1 jumper (located under PCI Slot 4) to positions 2-3
# Wait 20 seconds
# Restore the CLRTC1 jumper to positions 1-2
# Connect the power cord and turn on the computer

== Deployed Systems ==
* [[Ponos]]

== Motherboard Diagrams ==
[[File:KCMA-D8 Motherboard Diagram.png|frameless|400x400px]]
[[File:KCMA-D8 Motherboard BlockDiagram.png|frameless|400x400px]]

== Motherboard Components ==
=== Socket C32 ===
{{Excerpt|Socket C32|inline=yes|bold=yes}}
==== AMD Opteron 4100 Series ====
{{Excerpt|AMD Opteron 4100 Series|inline=yes|bold=yes}}
==== AMD Opteron 4200 and 4300 Series ====
{{Excerpt|AMD Opteron 4200 and 4300 Series|inline=yes|bold=yes}}
=== DDR3 Memory ===
[[File:KCMA-D8 Motherboard DDR3 Slots.png|frameless|600x600px]]

{{Excerpt|AGESA 15h|DDR3 Support|inline=yes|bold=yes}}

[[File:KCMA-D8 Motherboard DDR3 Voltage.png|frameless|600x600px]]

The KCMA-D8 provides an external method to override the BIOS DDR3 voltage. BIOS control is configured to select a voltage that maximizes performance for all DIMM modules attached to a socket. Forcing a different voltage may cause stability problems. Use the default jumper setting (1.5V / BIOS control) when using coreboot-15h.

=== PCIe 2.0 Slots ===
{| class="wikitable"
|+
!Slot
!Width
!Wired Lanes
!Notes
|-
|PCIe1
|x16
|x16
|
|-
|PCIe3
|x16
|x8
|
|-
|PCIe5
|x8
|x4
|Disabled if PIKE is occupied.
|}

=== PIKE Slots ===
The two PIKE slots, PIKE1 and PIKE2, are used together to attach an ASUS PIKE card to the KCMA-D8. This is required to utilize the 8 onboard SAS ports.

The [[PIKE2008]] card is recommended for most cases. This card offers 6Gbps SAS2/SATA3 support, which is faster than the 3Gbps SATA2 provided by the SP5100. The card can be flashed to [[IT Mode]], which allows the host operating system to access the drives individually. Other PIKE cards provide 3Gbps SAS1/SATA2 support.

The family of ASUS PIKE cards are just PCIe SAS host bus adapters with a proprietary PIKE connector. PIKE cards have no onboard SAS/SATA connectors. The motherboard's SAS ports are wired to the PIKE slots, and function as a proprietary wiring harness for the PIKE card. PIKE cards use common HBA chips (LSI or Marvell) supported in the Linux kernel.

PIKE cards are low-profile, and fit in a 1U chassis. The PIKE connector has a latch which anchors the card to the motherboard, so the card does not need to be fixed to the chassis. The PIKE slot is placed at the bottom of the motherboard, leaving space for e.g. an additional full-height card in a 90-degree riser.

SeaBIOS has limited support for SAS adapters including the [[PIKE2008]]. It cannot boot from them, unless the card's option ROM is executed. Option ROMs are disabled in the pre-built releases of coreboot-15h. LinuxBoot or other payloads may be able to boot from these cards.

'''Note''': On the KCMA-D8, The PIKE slot is shared with PCIe5 (only one may be used). So a standard HBA may be used in PCIe5 instead of a PIKE card, which may be better depending on your use case.
* Use another PCIe HBA if you want a mini-SAS connector
* Use an AHCI PCIe HBA if you want to boot from SATA3 drives (with SeaBIOS, without oproms) -- this is untested but should work
* Use a PIKE card if you are constrained on chassis space (if you need both an HBA and another full-height card in a 90-degree riser)

=== DIP-8 Socket ===
The DIP-8 Socket houses the mainboard's BIOS ROM. The following DIP-8 chips are known to work with coreboot on the KCMA-D8.

{| class="wikitable"
|+
!Model
!Size (MB)
!Size (Mb)
|-
|W25Q16BVAIG
|2
|16
|-
|W25Q64BVAIG
|8
|64
|-
|W25Q128FVIQ
|16
|128
|}

=== ASPEED AST2050 ===
{{Excerpt|ASPEED AST2050|inline=yes|bold=yes}}

Remote administration features on the AST2050 are only activated when a firmware module (ASMB4 or ASMB5) is attached to the KGPE-D16 mainboard (BMC_FW1 slot).

=== AMD SR5670 ===
{{Excerpt|AMD SR5670|inline=yes|bold=yes}}
=== AMD SP5100 ===
{{Excerpt|AMD SP5100|inline=yes|bold=yes}}
=== Winbond W83667HG-A ===
{{Excerpt|Winbond W83667HG-A|hat=no}}
=== Nuvoton W83795G ===
{{Excerpt|Nuvoton W83795G/ADG|hat=no}}

== Kill-a-Watt Power Draw ==

[[User:Sbrudenell]] performed some power draw tests of the KCMA-D8 in various configurations. The following setup was used:

* Firmware: [[coreboot-15h]] 2026.05.04-v4.11-5d336ff7176
* Power was measured using a kill-a-watt in "watts" mode
* PSU: Supermicro PWS-351-1H (350W 1U 80 Plus Gold)
* DIMMs: M386B4G70DM0-YK04 (32GB 1600MHz ECC LRDIMM)
* CPU: 4365 EE
* No case/CPU fans (an external box fan was used for cooling)
* No PCIe or USB peripherals, except PIKE2008 as noted
* An ASMB4 module using OEM firmware was used
* DIMMs distributed evenly across memory channels
* Host booted to alpine linux liveusb (kernel 6.18.35)
* Default cpufreq driver and governor <nowiki>acpi-cpufreq</nowiki> and <nowiki>schedutil</nowiki> were used
* k10temp measured CPU temperature(s) at 25-30C at idle. After 10 minutes stress, they measured 40-45C
* CPU was stressed using `stress-ng --matrix 0`, and measured at different amounts of time since being idle
* The fam15_power reading in all cases was 15.47W per CPU at idle, and ~40.09W per CPU under stress
* With host power off (but ASMB4 online), the kill-a-watt read 4W in all cases
* The PIKE2008 module was used, but no drives or backplanes were connected.

{| class="wikitable sortable"
|+ Kill-a-Watt Power Draw
|-
! CPUs !! DIMMs !! PIKE2008 !! Idle (W) !! CPU Stress 10s (W) !! CPU Stress 10m (W)
|-
| 1 || 2 || N || 39 || 71 || ?
|-
| 2 || 2 || N || 61 || 125 || ?
|-
| 2 || 4 || N || 66 || 130 || ?
|-
| 2 || 8 || N || 72 || 138 || 142
|-
| 2 || 8 || Y || 79 || 145 || 148
|}

== Board View ==
Board views are available for the KCMA-D8. These files can be opened with [[OpenBoardView]].

[[File:Asus KCMA-D8 1.02 Schematics.zip]]

== References ==

ASUS KCMA-D8

2026-07-08T22:06:45Z

Sbrudenell:

{{Infobox motherboard
|image = Asus-kcma-d8-top-64c7d3a66747d247126312.jpg
|image_size = 300

|introduced = 2010
|manufacturer = ASUS

|socket = 2x [[C32]]
|northbridge = 1x [[AMD SR5670]]
|southbridge = [[AMD SP5100]]
|superio = Winbond W83667HG-A
|bmc = ASPEED AST2050 (OpenBMC-compatible)
|bmcflash = Removable Module
|ram = 8 slots (4 channels) DDR3-1600 ECC UDIMM/RDIMM/LRDIMM
|bios = 2 MiB socketed DIP-8 (W25Q16V)
|formfactor =
SSI CEB, might fit in an ATX case that has 1 cm extra
|power = 1x 8-pin EPS

|slot1 = PCIe Gen2 x16
|slot2 = PCIe Gen2 x16 (electrically x8)
|slot3 = PCIe Gen2 x8 (electrically x4)
|slot4 = 32-bit Legacy PCI (5V)
|slot5 = 32-bit Legacy PCI (5V)
|slot6 = 32-bit Legacy PCI (5V)
|slot7 = ASUS [[PIKE2008]] Interface

|gpu = AST2050 Integrated VGA
|nic = 2x Intel 82574L Gigabit
|storagecontroller = SP5100's SATA2 (3.0 Gbps), no SAS unless [[PIKE2008]] installed
|usbcontroller = SP5100's onboard USB 2.0
|serial = One SIO-provided RS232, one virtual BMC console port
|audio = None (ASUS recommended a PCI sound card)
}}

Support for the KCMA-D8 motherboard by [[coreboot-15h]], 15h.org's downstream coreboot variant for fam15h systems, was recently completed.

== Open Source Firmware ==
Open source firmware for the KCMA-D8 is provided by [[coreboot-15h]] utilizing AMD's open source AGESA and CIMx releases for platform initialization. The git repository for the firmware can be reviewed [https://git.15h.org/mrothfuss/coreboot-15h here].

=== coreboot-15h ===
{{Excerpt|Coreboot-15h|[[ASUS KCMA-D8]]|hat=no}}

=== Missing Features ===
* SeaBIOS does not respond to keyboards behind a USB hub.
* Hibernation and Suspend/Resume are unsupported.
* Opteron 4100 series CPUs are unsupported.
* ASUS MIO audio cards are untested.

=== Flashing ===
To switch from the stock firmware to coreboot, [[External Flashing | external flashing]] is required. The DIP-8 flash chip is located at the bottom right corner of the board (labeled BIOS in the motherboard diagram). A 3.3V CH341a programmer can be used to flash coreboot onto the KCMA-D8. When switching to coreboot-15h from the OEM BIOS or coreboot, clearing the CMOS is required.

'''Clearing the CMOS'''
# Turn off the computer and disconnect the power cord
# Move the CLRTC1 jumper (located under PCI Slot 4) to positions 2-3
# Wait 20 seconds
# Restore the CLRTC1 jumper to positions 1-2
# Connect the power cord and turn on the computer

== Deployed Systems ==
* [[Ponos]]

== Motherboard Diagrams ==
[[File:KCMA-D8 Motherboard Diagram.png|frameless|400x400px]]
[[File:KCMA-D8 Motherboard BlockDiagram.png|frameless|400x400px]]

== Motherboard Components ==
=== Socket C32 ===
{{Excerpt|Socket C32|inline=yes|bold=yes}}
==== AMD Opteron 4100 Series ====
{{Excerpt|AMD Opteron 4100 Series|inline=yes|bold=yes}}
==== AMD Opteron 4200 and 4300 Series ====
{{Excerpt|AMD Opteron 4200 and 4300 Series|inline=yes|bold=yes}}
=== DDR3 Memory ===
[[File:KCMA-D8 Motherboard DDR3 Slots.png|frameless|600x600px]]

{{Excerpt|AGESA 15h|DDR3 Support|inline=yes|bold=yes}}

[[File:KCMA-D8 Motherboard DDR3 Voltage.png|frameless|600x600px]]

The KCMA-D8 provides an external method to override the BIOS DDR3 voltage. BIOS control is configured to select a voltage that maximizes performance for all DIMM modules attached to a socket. Forcing a different voltage may cause stability problems. Use the default jumper setting (1.5V / BIOS control) when using coreboot-15h.

=== PCIe 2.0 Slots ===
{| class="wikitable"
|+
!Slot
!Width
!Wired Lanes
!Notes
|-
|PCIe1
|x16
|x16
|
|-
|PCIe3
|x16
|x8
|
|-
|PCIe5
|x8
|x4
|Disabled if PIKE is occupied.
|}

=== PIKE Slots ===
The two PIKE slots, PIKE1 and PIKE2, are used together to attach an ASUS PIKE card to the KCMA-D8. This is required to utilize the 8 onboard SAS ports.

The [[PIKE2008]] card is recommended for most cases. This card offers 6Gbps SAS2/SATA3 support, which is faster than the 3Gbps SATA2 provided by the SP5100. The card can be flashed to [[IT Mode]], which allows the host operating system to access the drives individually. Other PIKE cards provide 3Gbps SAS1/SATA2 support.

The family of ASUS PIKE cards are just PCIe SAS host bus adapters with a proprietary PIKE connector. PIKE cards have no onboard SAS/SATA connectors. The motherboard's SAS ports are wired to the PIKE slots, and function as a proprietary wiring harness for the PIKE card. PIKE cards use common HBA chips (LSI or Marvell) supported in the Linux kernel.

PIKE cards are low-profile, and fit in a 1U chassis. The PIKE connector has a latch which anchors the card to the motherboard, so the card does not need to be fixed to the chassis. The PIKE slot is placed at the bottom of the motherboard, leaving space for e.g. an additional full-height card in a 90-degree riser.

SeaBIOS has limited support for SAS adapters including the [[PIKE2008]]. It cannot boot from them, unless the card's option ROM is executed. Option ROMs are disabled in the pre-built releases of coreboot-15h. LinuxBoot or other payloads may be able to boot from these cards.

'''Note''': On the KCMA-D8, The PIKE slot is shared with PCIe5 (only one may be used). So a standard HBA may be used in PCIe5 instead of a PIKE card, which may be better depending on your use case.
* Use another PCIe HBA if you want a mini-SAS connector
* Use an AHCI PCIe HBA if you want to boot from SATA3 drives (with SeaBIOS, without oproms) -- this is untested but should work
* Use a PIKE card if you are constrained on chassis space (if you need both an HBA and another full-height card in a 90-degree riser)

=== DIP-8 Socket ===
The DIP-8 Socket houses the mainboard's BIOS ROM. The following DIP-8 chips are known to work with coreboot on the KCMA-D8.

{| class="wikitable"
|+
!Model
!Size (MB)
!Size (Mb)
|-
|W25Q16BVAIG
|2
|16
|-
|W25Q64BVAIG
|8
|64
|-
|W25Q128FVIQ
|16
|128
|}

=== ASPEED AST2050 ===
{{Excerpt|ASPEED AST2050|inline=yes|bold=yes}}

Remote administration features on the AST2050 are only activated when a firmware module (ASMB4 or ASMB5) is attached to the KGPE-D16 mainboard (BMC_FW1 slot).

=== AMD SR5670 ===
{{Excerpt|AMD SR5670|inline=yes|bold=yes}}
=== AMD SP5100 ===
{{Excerpt|AMD SP5100|inline=yes|bold=yes}}
=== Winbond W83667HG-A ===
{{Excerpt|Winbond W83667HG-A|hat=no}}
=== Nuvoton W83795G ===
{{Excerpt|Nuvoton W83795G/ADG|hat=no}}

== Kill-a-Watt Power Draw ==

[[User:Sbrudenell]] performed some power draw tests of the KCMA-D8 in various configurations. The following setup was used:

* Power was measured using a kill-a-watt in "watts" mode
* PSU: Supermicro PWS-351-1H (350W 1U 80 Plus Gold)
* DIMMs: M386B4G70DM0-YK04 (32GB 1600MHz ECC LRDIMM)
* CPU: 4365 EE
* No case/CPU fans (an external box fan was used for cooling)
* No PCIe or USB peripherals, except PIKE2008 as noted
* An ASMB4 module using OEM firmware was used
* DIMMs distributed evenly across memory channels
* Host booted to alpine linux liveusb (kernel 6.18.35)
* Default cpufreq driver and governor <nowiki>acpi-cpufreq</nowiki> and <nowiki>schedutil</nowiki> were used
* k10temp measured CPU temperature(s) at 25-30C at idle. After 10 minutes stress, they measured 40-45C
* CPU was stressed using `stress-ng --matrix 0`, and measured at different amounts of time since being idle
* The fam15_power reading in all cases was 15.47W per CPU at idle, and ~40.09W per CPU under stress
* With host power off (but ASMB4 online), the kill-a-watt read 4W in all cases
* The PIKE2008 module was used, but no drives or backplanes were connected.

{| class="wikitable sortable"
|+ Kill-a-Watt Power Draw
|-
! CPUs !! DIMMs !! PIKE2008 !! Idle (W) !! CPU Stress 10s (W) !! CPU Stress 10m (W)
|-
| 1 || 2 || N || 39 || 71 || ?
|-
| 2 || 2 || N || 61 || 125 || ?
|-
| 2 || 4 || N || 66 || 130 || ?
|-
| 2 || 8 || N || 72 || 138 || 142
|-
| 2 || 8 || Y || 79 || 145 || 148
|}

== Board View ==
Board views are available for the KCMA-D8. These files can be opened with [[OpenBoardView]].

[[File:Asus KCMA-D8 1.02 Schematics.zip]]

== References ==

AGESA 15h

2026-07-08T20:51:46Z

Sbrudenell: /* DDR3 Support */

== DDR3 Support ==
The vast majority of UDIMM, RDIMM, and LRDIMM DDR3 modules are expected to work without issue. So far only [[AGESA_15h#Incompatible_DDR3_Modules|one]] module has been found to be incompatible with the AGESA. The maximum RAM supported is 256 GB per CPU socket. RDIMM modules are recommended for motherboards that support them. The following is an incomplete list of tested modules. Review the deployed systems list for well tested hardware configurations.


{| class="wikitable"
|+
!Product
!ECC
!Type
!Capacity
!Speed
!Tester
|-
|Actica ACT4GHU72D8H1333S
|Yes
|UDIMM
|4 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Actica ACT8GHR72Q4H1600S
|Yes
|RDIMM
|8 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|ASint SLA302G08-GGNHC
|No
|UDIMM
|4 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|ELPIDA EBJ81RF4BDWD-DJ-F
|Yes
|RDIMM
|8 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Corsair TR3X6G1333C9
|No
|UDIMM
|2 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Crucial CT16G3ERSLD4160B
|Yes
|RDIMM
|16 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Crucial CT32G3ELSDQ4186D
|Yes
|LRDIMM
|32 GB
|1866 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Hynix HMT42GR7AFR4A-PB
|Yes
|RDIMM
|16 GB
|1600 MHz
|pkubaj
|-
|Hynix HMT84GL7MMR4A-H9
|Yes
|LRDIMM
|32 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Kingston KVR13N9S8/4
|No
|UDIMM
|4 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Kingston KVR16E11/8I
|Yes
|UDIMM
|8 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Kingston KVR1333D3D4R9S/4G
|Yes
|RDIMM
|4 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Kingston KVR16R11D4K4/32I
|Yes
|RDIMM
|8 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Micron MT36KSF2G72PZ-1G4E1
|Yes
|RDIMM
|16 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Micron MT36KSF2G72PZ-1G6E1FE
|Yes
|RDIMM
|16 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Micron MT36KSF2G72PZ-1G6N1KF
|Yes
|RDIMM
|16 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Nanya NT4GC64B8HG0NF-DI
|No
|UDIMM
|4 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M393B1K70DH0-YH9
|Yes
|RDIMM
|8 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M393B1G70QH0-YK0
|Yes
|RDIMM
|8 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M393B2K70DM0-YF8
|Yes
|RDIMM
|16 GB
|1066 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M393B2G70BH0-CK0
|Yes
|RDIMM
|16 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M393B4G70BM0-YH9
|Yes
|RDIMM
|32 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M393B4G70DM0-YH9
|Yes
|RDIMM
|32 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M386B4G70DM0-CMA
|Yes
|LRDIMM
|32 GB
|1866 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Samsung M386B4G70DM0-YK04
|Yes
|LRDIMM
|32 GB
|1600 MHz
|[[User:Sbrudenell|sbrudenell]]
|-
|Samsung M386B8G70DE0-YH93
|Yes
|LRDIMM
|64 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Super Talent W1333UB4GS
|No
|UDIMM
|4 GB
|1333 MHz
|[[User:Frantic|frantic]]
|-
|Super Talent W1333EB4GS
|Yes
|UDIMM
|4 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Super Talent W16RB8G4S
|Yes
|RDIMM
|8 GB
|1600 MHz
|[[User:Mrothfuss|mrothfuss]]
|-
|Super Talent W13RC16G4H
|Yes
|RDIMM
|16 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|}

=== Incompatible DDR3 Modules ===


{| class="wikitable"
|+
!Product
!ECC
!Type
!Capacity
!Speed
!Tester
!Remarks
|-
|OWC OWC1333D3MPE16G
|Yes
|RDIMM
|16 GB
|1333 MHz
|[[User:Mrothfuss|mrothfuss]]
|Designed for Apple Machines. SPD Data was incomplete.
|}

ASPEED AST2050

2026-07-04T23:01:09Z

Sbrudenell:

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== DIY Modules ==

The ASUS ASMB4 and ASMB5 modules are simply breakout boards for SPI flash. You can make these yourself.

Some PCB schematics are available [https://github.com/DanielG/asmb4 here].

PCBs are available for purchase [https://oshpark.com/shared_projects/jZLoDQ3Y here].

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>
$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access. The rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port. "Text mode" payloads like iPXE can thus be via serial-over-LAN, with no extra configuration in the payload.

You may need to change the BMC's baud rate. Under OEM BMC firmware, the best way is ipmitool:

<nowiki>
ipmitool -H bmcip -I lanplus sol set non-volatile-bit-rate 115.2
ipmitool -H bmcip -I lanplus sol set volatile-bit-rate 115.2</nowiki>

The following coreboot build config can be used for serial-over-LAN access:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, the BMC's network connectivity is momentarily disrupted. In particular when coreboot/SeaBIOS initialize devices, a serial-over-LAN session may get disrupted, and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them, making it impossible to boot from remote media. Using the separate "management LAN" interface fixes these problems. It may be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot for this case.

ASPEED AST2050

2026-07-04T22:58:23Z

Sbrudenell: /* Quirks */

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>
$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access. The rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port. "Text mode" payloads like iPXE can thus be via serial-over-LAN, with no extra configuration in the payload.

You may need to change the BMC's baud rate. Under OEM BMC firmware, the best way is ipmitool:

<nowiki>
ipmitool -H bmcip -I lanplus sol set non-volatile-bit-rate 115.2
ipmitool -H bmcip -I lanplus sol set volatile-bit-rate 115.2</nowiki>

The following coreboot build config can be used for serial-over-LAN access:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, the BMC's network connectivity is momentarily disrupted. In particular when coreboot/SeaBIOS initialize devices, a serial-over-LAN session may get disrupted, and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them, making it impossible to boot from remote media. Using the separate "management LAN" interface fixes these problems. It may be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot for this case.

ASPEED AST2050

2026-07-04T22:55:43Z

Sbrudenell: /* SSH Access */

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>
$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access. The rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port. "Text mode" payloads like iPXE can thus be via serial-over-LAN, with no extra configuration in the payload.

You may need to change the BMC's baud rate. Under OEM BMC firmware, the best way is ipmitool:

<nowiki>
ipmitool -H bmcip -I lanplus sol set non-volatile-bit-rate 115.2
ipmitool -H bmcip -I lanplus sol set volatile-bit-rate 115.2</nowiki>

The following coreboot build config can be used for serial-over-LAN access:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, it seems to momentarily take the BMC offline. In particular when coreboot/SeaBIOS initialize devices, the serial-over-LAN session may get disrupted and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them. Using the separate "management LAN" interface fixes these problems. It may also be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot.

ASPEED AST2050

2026-07-04T22:55:26Z

Sbrudenell: /* Serial-over-LAN */

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>

$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access. The rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port. "Text mode" payloads like iPXE can thus be via serial-over-LAN, with no extra configuration in the payload.

You may need to change the BMC's baud rate. Under OEM BMC firmware, the best way is ipmitool:

<nowiki>
ipmitool -H bmcip -I lanplus sol set non-volatile-bit-rate 115.2
ipmitool -H bmcip -I lanplus sol set volatile-bit-rate 115.2</nowiki>

The following coreboot build config can be used for serial-over-LAN access:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, it seems to momentarily take the BMC offline. In particular when coreboot/SeaBIOS initialize devices, the serial-over-LAN session may get disrupted and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them. Using the separate "management LAN" interface fixes these problems. It may also be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot.

ASPEED AST2050

2026-07-04T22:50:38Z

Sbrudenell: /* Serial-over-LAN */

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>

$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access. The rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port. "Text mode" payloads like iPXE can thus be via serial-over-LAN, with no extra configuration in the payload.

The following coreboot build config can be used for serial-over-LAN access:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, it seems to momentarily take the BMC offline. In particular when coreboot/SeaBIOS initialize devices, the serial-over-LAN session may get disrupted and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them. Using the separate "management LAN" interface fixes these problems. It may also be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot.

ASPEED AST2050

2026-07-04T22:50:07Z

Sbrudenell: /* Serial-over-LAN */

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>

$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access. The rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port. "Text mode" payloads like iPXE can thus be via serial-over-LAN, with no extra configuration in the payload.

The following coreboot build config can be used for this:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, it seems to momentarily take the BMC offline. In particular when coreboot/SeaBIOS initialize devices, the serial-over-LAN session may get disrupted and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them. Using the separate "management LAN" interface fixes these problems. It may also be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot.

ASPEED AST2050

2026-07-03T08:32:02Z

Sbrudenell:

The [[ASPEED AST2050|AST2050]] chipset is an Integrated Remote Management Processor introduced by ASPEED
Technology Inc. It is a high performance and highly integrated SOC device designed to support various
management functions required for server platforms which require baseboard management, virtual
storage functions, and/or KVM-over-IP functions.

Open source support for the [[ASPEED AST2050|AST2050]]'s VGA output (text-mode only) was implemented in coreboot by Raptor Engineering<ref>https://review.coreboot.org/c/coreboot/+/11937</ref>. Full VGA output support requires ASPEED's closed source VGABIOS to be included in the coreboot rom. A rudimentary port of [[OpenBMC]] was also developed by Raptor Engineering<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref>.

'''Official Documentation'''
* [https://15h.org/images/1/18/AST2050_Data_Sheet.pdf AST2050 Datasheet]
* [https://15h.org/images/6/64/Infineon-s25fl128p-128-mbit-3.0-v-flash-memory-datasheet-en.pdf S25FL128P Datasheet]

== OpenBMC ==
OpenBMC was developed by [[Raptor Engineering]] for the [[KGPE-D16]] and [[KCMA-D8]] motherboards<ref>https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php</ref> as an open source replacement to the closed source BMC firmware.

This version of OpenBMC for the AST2050 has had various components updated, removed, or reconfigured. Broken links to fetch dependencies have been fixed (as of 20251208). Review the git commits for more details.

'''Updated Components'''
* OpenSSH (from 6.7p1 to 8.7p1)
* OpenSSL (from 1.0.2d to 1.0.2r)

'''Removed Components'''
* fan-ctrl (inferior to native fan control)
* rest-api (insecure HTTP access to the BMC)
* ipmid (unsupported)
* sms-kcsd (unsupported)
* lmsensors (unsupported)
* flashrom (unsupported)

'''Configuration Changes'''
* ast2050-yocto-poky/meta/recipes-connectivity/openssh/openssh/sshd_config
** Password Authentication Disabled
* ast2050-yocto-poky/meta/recipes-core/base-files/base-files_3.0.14.bb
** Configured to install ast2050-yocto-poky/build/downloads/root_authorized_keys to /home/root/.ssh/authorized_keys
* ast2050-yocto-openbmc/meta-raptor/meta-asus/recipes-utils/openbmc-utils/openbmc-utils_%.bbappend
** Disabled autostarting the mainboard
* ast2050-yocto-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf
** Set the networking hostname to 'openbmc'

=== Compiling from source ===
Compilation has been tested on Debian 9.

'''Debian 9 Dependencies'''

<nowiki>
apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib autotools-dev build-essential chrpath socat libsdl1.2-dev xterm python cpio</nowiki>

'''Create the missing /etc/perl/find.pl file'''<ref>https://blog.kempj.co.uk/2015/09/missing-find-pl-compiling-oe/</ref>

<nowiki>
warn "Legacy library @{[(caller(0))[6]]} will be removed from the Perl core distribution in the next major release. Please install it from the CPAN distribution Perl4::CoreLibs. It is being used at @{[(caller)[1]]}, line @{[(caller)[2]]}.\n";

# This library is deprecated and unmaintained. It is included for
# compatibility with Perl 4 scripts which may use it, but it will be
# removed in a future version of Perl. Please use the File::Find module
# instead.

# Usage:
# require "find.pl";
#
# &find('/foo','/bar');
#
# sub wanted { ... }
# where wanted does whatever you want. $dir contains the
# current directory name, and $_ the current filename within
# that directory. $name contains "$dir/$_". You are cd'ed
# to $dir when the function is called. The function may
# set $prune to prune the tree.
#
# For example,
#
# find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune
#
# corresponds to this
#
# sub wanted {
# /^\.nfs.*$/ &&
# (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_)) &&
# int(-M _) > 7 &&
# unlink($_)
# ||
# ($nlink || (($dev,$ino,$mode,$nlink,$uid,$gid) = lstat($_))) &&
# $dev < 0 &&
# ($prune = 1);
# }
#
# Set the variable $dont_use_nlink if you're using AFS, since AFS cheats.

use File::Find ();

*name = *File::Find::name;
*prune = *File::Find::prune;
*dir = *File::Find::dir;
*topdir = *File::Find::topdir;
*topdev = *File::Find::topdev;
*topino = *File::Find::topino;
*topmode = *File::Find::topmode;
*topnlink = *File::Find::topnlink;

sub find {
&File::Find::find(\&wanted, @_);
}

1;</nowiki>

<code>/etc/perl/find.pl md5sum: 129bb8ba7bd008f350f1863a49034b7e</code>

'''Configuring and Compiling'''

<nowiki>
### Fetch Sources
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-poky.git ast2050-yocto-poky

cd ast2050-yocto-poky
git clone -b fido https://git.15h.org/mrothfuss/ast2050-yocto-openembedded.git meta-openembedded
git clone https://git.15h.org/mrothfuss/ast2050-yocto-openbmc.git meta-openbmc

### Setup Build
export TEMPLATECONF=meta-openbmc/meta-raptor/meta-asus/conf
source oe-init-build-env
cp -Rp ../local-aspeed.conf conf/local.conf
touch conf/sanity.conf

### Optional: Set root password
# The default root password is 0penBmc.
# Generate a new encrypted password string:
printf "%q\n" $(openssl passwd -1)
# Edit the config file (EXTRA_USERS_PARAMS), replace the password hash with the one you generated.
vim conf/local.conf

### Optional: Set the networking hostname
# The default is openbmc
vim ../meta-openbmc/common/recipes-connectivity/dhcp/files/dhclient.conf

### Required: Add your SSH key(s)
vim ./downloads/root_authorized_keys

### Build. Your ROM will be at tmp/deploy/images/asus/flash-asus-DATETIME
bitbake asus-image</nowiki>

=== Flashing the BMC ===
The BMC module can be flashed either internally or externally. Users report mixed results when flashing internally using [[Raptor Engineering]]'s method.

==== External Flashing ====
[[File:AST2050 BMC Flash.png|frameless|400x400px]]

Connect the BMC module's S25FL128P chip to an [[External Flashing|external flasher]] using the 8 pins that are shared between the SOIC16 and other SOIC8 chips (CS, DO, WP, GND, VCC, HOLD, CLK, and DI). Make sure your flasher is set to output 3.3V when flashing the BMC module.

<nowiki>
flashrom --programmer=ch341a_spi -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

==== Internal Flashing ====
[[Raptor Engineering]] released a custom version of [https://git.raptorengineering.com/git/ast2050-flashrom flashrom] that can flash the BMC module from an operating system running on the [[KGPE-D16]] or [[KCMA-D8]] motherboard.

<nowiki>
flashrom --programmer="ast1100:spibus=2" -c "S25FL128P......0" --verbose -w flash-asus-DATETIME</nowiki>

=== Using the BMC ===
Scan your network for a new device listening on port 22, then login with ssh. It can take up to 7 minutes for sshd to start on the first boot.
<nowiki>
nmap -p 22 10.0.0.1/24
ssh root@IPADDR</nowiki>

You can set the ethernet MAC address to match the one printed on the BMC module. The BMC IP will likely change after setting the MAC address and rebooting.
<nowiki>
fw_setenv ethaddr 01:23:45:67:89:ab
reboot</nowiki>

You can access COM2 with screen:
<nowiki>
screen -h 0 /dev/ttyS0 115200</nowiki>

You can use the asus_power.sh command to view/change power states.
<nowiki>
asus_power.sh status
asus_power.sh on
asus_power.sh reset
asus_power.sh off</nowiki>

=== Development Tips ===
Delete a previously built recipe
<nowiki>
bitbake -c cleansstate <recipe></nowiki>
Delete all previously built components
<nowiki>
rm -rf sstate-cache/ tmp/</nowiki>

== OEM Firmware ==

The ASMB4 and ASMB5 BMC firmware modules come with some OEM firmware.

=== Source Code ===

Partial source code for the OEM firmware is available as of writing from ASUS. It includes the source for some IPMI command handlers, so you can construct some raw OEM commands for ipmitool.

* [https://www.asus.com/supportonly/asmb4-ikvm/helpdesk_download/ ASMB4 source code]
* [https://www.asus.com/supportonly/asmb5-ikvm/helpdesk_download/ ASMB5 source code]

=== SSH Access ===

The OEM firmware includes SSH access, which is apparently undocumented.

The firmware's OpenSSH version is ancient. Modern SSH clients need to enable some deprecated options to connect.

<nowiki>
ssh -o KexAlgorithms=+diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa admin@bmc</nowiki>

On my firmware, the shell is busybox instead of smash. Some OEM binaries are around:

<nowiki>

$ ls /usr/local/bin/
IPMB LAN Timer cdserver discovery gpiotool peciapp smash webgo
IPMIMain MsgHndlr adviserd cpConf fdserver mkMiniMe pwmtachtool snmpd
KCS SOL adviserd_capture defaulthost flasher ncsiapp rtcapp ssmtp</nowiki>

There also appears to be a backdoor root password, distinct from the default "admin" account:

<nowiki>
$ cat /etc/shadow
root:$1$A17c6z5w$5OsdHjBn1pjvN6xXKDckq0:2:0:99999:7:0:99999:0
anonymous:$1$A17c6z5w$Ec7by585G3BAPJHK5dFCq.:2:0:99999:7:0:99999:2147482704</nowiki>

=== Serial-over-LAN ===

On the [[KCMA-D8]] and [[KGPE-D16]], the SuperIO's second serial port is normally routed to the rectangular connector on the board. When any BMC firmware module is connected, this serial port is instead routed to the AST2050 for BMC access, and the rectangular connector is disabled.

[[Coreboot-15h]] can be configured to use this second serial port. This allows serial-over-lan access to coreboot output and the SeaBIOS boot menu. SeaBIOS in turn sets up a VGA BIOS which redirects input and output to the serial port, so payloads like iPXE may also be used this way with no extra configuration.

The following coreboot build config can be used for this:

<nowiki>
--- configs/config.asus_kcma-d8_seabios_ucode_no-oproms_2mb 2026-06-17 19:41:00.108813619 +0000
+++ .config 2026-07-03 07:50:20.433551464 +0000
@@ -89,7 +89,7 @@
CONFIG_MAINBOARD_PART_NUMBER="KCMA-D8"
CONFIG_MAX_CPUS=16
CONFIG_CBFS_SIZE=0x200000
-CONFIG_UART_FOR_CONSOLE=0
+CONFIG_UART_FOR_CONSOLE=1
CONFIG_PAYLOAD_CONFIGFILE=""
CONFIG_MAINBOARD_VENDOR="ASUS"
CONFIG_HW_MEM_HOLE_SIZEK=0x200000
@@ -212,7 +212,7 @@
# CONFIG_PCIEXP_ASPM is not set
# CONFIG_PCIEXP_COMMON_CLOCK is not set
# CONFIG_PCIEXP_CLK_PM is not set
-CONFIG_TTYS0_BASE=0x3f8
+CONFIG_TTYS0_BASE=0x2f8
CONFIG_HPET_MIN_TICKS=0x37EE
CONFIG_UART_PCI_ADDR=0x0
# CONFIG_SOC_MEDIATEK_MT8173 is not set
@@ -548,7 +548,7 @@
#

#
-# Serial port base address = 0x3f8
+# Serial port base address = 0x2f8
#
# CONFIG_CONSOLE_SERIAL_921600 is not set
# CONFIG_CONSOLE_SERIAL_460800 is not set
@@ -629,7 +629,8 @@
# CONFIG_SEABIOS_OPROM_VGAONLY is not set
# CONFIG_SEABIOS_OPROM_ALL is not set
CONFIG_SEABIOS_BOOTORDER_FILE=""
-# CONFIG_SEABIOS_ADD_SERCON_PORT_FILE is not set
+CONFIG_SEABIOS_ADD_SERCON_PORT_FILE=y
+CONFIG_SEABIOS_SERCON_PORT_ADDR=0x2f8
CONFIG_PAYLOAD_VGABIOS_FILE="payloads/external/SeaBIOS/seabios/out/vgabios.bin"
CONFIG_SEABIOS_DEBUG_LEVEL=-1</nowiki>

=== Quirks ===

* '''Shared-LAN interferes with remote functions''': If the OEM BMC firmware is in "shared LAN" mode (the host and BMC share the LAN port), then any time the host (re-)initializes the ethernet controller, it seems to momentarily take the BMC offline. In particular when coreboot/SeaBIOS initialize devices, the serial-over-LAN session may get disrupted and not come back. Remote media functions are similarly disrupted long enough that SeaBIOS will not see them. Using the separate "management LAN" interface fixes these problems. It may also be that the OEM BMC firmware interacts better with OEM BIOS than it does with coreboot.

ASUS KCMA-D8

2026-06-21T22:02:34Z

Sbrudenell: /* PIKE Slots */

{{Infobox motherboard
|image = Asus-kcma-d8-top-64c7d3a66747d247126312.jpg
|image_size = 300

|introduced = 2010
|manufacturer = ASUS

|socket = 2x [[C32]]
|northbridge = 1x [[AMD SR5670]]
|southbridge = [[AMD SP5100]]
|superio = Winbond W83667HG-A
|bmc = ASPEED AST2050 (OpenBMC-compatible)
|bmcflash = Removable Module
|ram = 8 slots (4 channels) DDR3-1600 ECC UDIMM/RDIMM/LRDIMM
|bios = 2 MiB socketed DIP-8 (W25Q16V)
|formfactor =
SSI CEB, might fit in an ATX case that has 1 cm extra
|power = 1x 8-pin EPS

|slot1 = PCIe Gen2 x16
|slot2 = PCIe Gen2 x16 (electrically x8)
|slot3 = PCIe Gen2 x8 (electrically x4)
|slot4 = 32-bit Legacy PCI (5V)
|slot5 = 32-bit Legacy PCI (5V)
|slot6 = 32-bit Legacy PCI (5V)
|slot7 = ASUS [[PIKE2008]] Interface

|gpu = AST2050 Integrated VGA
|nic = 2x Intel 82574L Gigabit
|storagecontroller = SP5100's SATA2 (3.0 Gbps), no SAS unless [[PIKE2008]] installed
|usbcontroller = SP5100's onboard USB 2.0
|serial = One SIO-provided RS232, one virtual BMC console port
|audio = None (ASUS recommended a PCI sound card)
}}

Support for the KCMA-D8 motherboard by [[coreboot-15h]], 15h.org's downstream coreboot variant for fam15h systems, was recently completed.

== Open Source Firmware ==
Open source firmware for the KCMA-D8 is provided by [[coreboot-15h]] utilizing AMD's open source AGESA and CIMx releases for platform initialization. The git repository for the firmware can be reviewed [https://git.15h.org/mrothfuss/coreboot-15h here].

=== coreboot-15h ===
{{Excerpt|Coreboot-15h|[[ASUS KCMA-D8]]|hat=no}}

=== Missing Features ===
* SeaBIOS does not respond to keyboards behind a USB hub.
* Hibernation and Suspend/Resume are unsupported.
* Opteron 4100 series CPUs are unsupported.
* ASUS MIO audio cards are untested.

=== Flashing ===
To switch from the stock firmware to coreboot, [[External Flashing | external flashing]] is required. The DIP-8 flash chip is located at the bottom right corner of the board (labeled BIOS in the motherboard diagram). A 3.3V CH341a programmer can be used to flash coreboot onto the KCMA-D8. When switching to coreboot-15h from the OEM BIOS or coreboot, clearing the CMOS is required.

'''Clearing the CMOS'''
# Turn off the computer and disconnect the power cord
# Move the CLRTC1 jumper (located under PCI Slot 4) to positions 2-3
# Wait 20 seconds
# Restore the CLRTC1 jumper to positions 1-2
# Connect the power cord and turn on the computer

== Deployed Systems ==
* [[Ponos]]

== Motherboard Diagrams ==
[[File:KCMA-D8 Motherboard Diagram.png|frameless|400x400px]]
[[File:KCMA-D8 Motherboard BlockDiagram.png|frameless|400x400px]]

== Motherboard Components ==
=== Socket C32 ===
{{Excerpt|Socket C32|inline=yes|bold=yes}}
==== AMD Opteron 4100 Series ====
{{Excerpt|AMD Opteron 4100 Series|inline=yes|bold=yes}}
==== AMD Opteron 4200 and 4300 Series ====
{{Excerpt|AMD Opteron 4200 and 4300 Series|inline=yes|bold=yes}}
=== DDR3 Memory ===
[[File:KCMA-D8 Motherboard DDR3 Slots.png|frameless|600x600px]]

{{Excerpt|AGESA 15h|DDR3 Support|inline=yes|bold=yes}}

[[File:KCMA-D8 Motherboard DDR3 Voltage.png|frameless|600x600px]]

The KCMA-D8 provides an external method to override the BIOS DDR3 voltage. BIOS control is configured to select a voltage that maximizes performance for all DIMM modules attached to a socket. Forcing a different voltage may cause stability problems. Use the default jumper setting (1.5V / BIOS control) when using coreboot-15h.

=== PCIe 2.0 Slots ===
{| class="wikitable"
|+
!Slot
!Width
!Wired Lanes
!Notes
|-
|PCIe1
|x16
|x16
|
|-
|PCIe3
|x16
|x8
|
|-
|PCIe5
|x8
|x4
|Disabled if PIKE is occupied.
|}

=== PIKE Slots ===
The two PIKE slots, PIKE1 and PIKE2, are used together to attach an ASUS PIKE card to the KCMA-D8. This is required to utilize the 8 onboard SAS ports.

The [[PIKE2008]] card is recommended for most cases. This card offers 6Gbps SAS2/SATA3 support, which is faster than the 3Gbps SATA2 provided by the SP5100. The card can be flashed to [[IT Mode]], which allows the host operating system to access the drives individually. Other PIKE cards provide 3Gbps SAS1/SATA2 support.

The family of ASUS PIKE cards are just PCIe SAS host bus adapters with a proprietary PIKE connector. PIKE cards have no onboard SAS/SATA connectors. The motherboard's SAS ports are wired to the PIKE slots, and function as a proprietary wiring harness for the PIKE card. PIKE cards use common HBA chips (LSI or Marvell) supported in the Linux kernel.

PIKE cards are low-profile, and fit in a 1U chassis. The PIKE connector has a latch which anchors the card to the motherboard, so the card does not need to be fixed to the chassis. The PIKE slot is placed at the bottom of the motherboard, leaving space for e.g. an additional full-height card in a 90-degree riser.

SeaBIOS has limited support for SAS adapters including the [[PIKE2008]]. It cannot boot from them, unless the card's option ROM is executed. Option ROMs are disabled in the pre-built releases of coreboot-15h. LinuxBoot or other payloads may be able to boot from these cards.

'''Note''': On the KCMA-D8, The PIKE slot is shared with PCIe5 (only one may be used). So a standard HBA may be used in PCIe5 instead of a PIKE card, which may be better depending on your use case.
* Use another PCIe HBA if you want a mini-SAS connector
* Use an AHCI PCIe HBA if you want to boot from SATA3 drives (with SeaBIOS, without oproms) -- this is untested but should work
* Use a PIKE card if you are constrained on chassis space (if you need both an HBA and another full-height card in a 90-degree riser)

=== DIP-8 Socket ===
The DIP-8 Socket houses the mainboard's BIOS ROM. The following DIP-8 chips are known to work with coreboot on the KCMA-D8.

{| class="wikitable"
|+
!Model
!Size (MB)
!Size (Mb)
|-
|W25Q16BVAIG
|2
|16
|-
|W25Q64BVAIG
|8
|64
|-
|W25Q128FVIQ
|16
|128
|}

=== ASPEED AST2050 ===
{{Excerpt|ASPEED AST2050|inline=yes|bold=yes}}

Remote administration features on the AST2050 are only activated when a firmware module (ASMB4 or ASMB5) is attached to the KGPE-D16 mainboard (BMC_FW1 slot).

=== AMD SR5670 ===
{{Excerpt|AMD SR5670|inline=yes|bold=yes}}
=== AMD SP5100 ===
{{Excerpt|AMD SP5100|inline=yes|bold=yes}}
=== Winbond W83667HG-A ===
{{Excerpt|Winbond W83667HG-A|hat=no}}
=== Nuvoton W83795G ===
{{Excerpt|Nuvoton W83795G/ADG|hat=no}}

== Board View ==
Board views are available for the KCMA-D8. These files can be opened with [[OpenBoardView]].

[[File:Asus KCMA-D8 1.02 Schematics.zip]]

== References ==

ASUS KCMA-D8

2026-06-21T07:02:09Z

Sbrudenell: /* PIKE Slots */

{{Infobox motherboard
|image = Asus-kcma-d8-top-64c7d3a66747d247126312.jpg
|image_size = 300

|introduced = 2010
|manufacturer = ASUS

|socket = 2x [[C32]]
|northbridge = 1x [[AMD SR5670]]
|southbridge = [[AMD SP5100]]
|superio = Winbond W83667HG-A
|bmc = ASPEED AST2050 (OpenBMC-compatible)
|bmcflash = Removable Module
|ram = 8 slots (4 channels) DDR3-1600 ECC UDIMM/RDIMM/LRDIMM
|bios = 2 MiB socketed DIP-8 (W25Q16V)
|formfactor =
SSI CEB, might fit in an ATX case that has 1 cm extra
|power = 1x 8-pin EPS

|slot1 = PCIe Gen2 x16
|slot2 = PCIe Gen2 x16 (electrically x8)
|slot3 = PCIe Gen2 x8 (electrically x4)
|slot4 = 32-bit Legacy PCI (5V)
|slot5 = 32-bit Legacy PCI (5V)
|slot6 = 32-bit Legacy PCI (5V)
|slot7 = ASUS [[PIKE2008]] Interface

|gpu = AST2050 Integrated VGA
|nic = 2x Intel 82574L Gigabit
|storagecontroller = SP5100's SATA2 (3.0 Gbps), no SAS unless [[PIKE2008]] installed
|usbcontroller = SP5100's onboard USB 2.0
|serial = One SIO-provided RS232, one virtual BMC console port
|audio = None (ASUS recommended a PCI sound card)
}}

Support for the KCMA-D8 motherboard by [[coreboot-15h]], 15h.org's downstream coreboot variant for fam15h systems, was recently completed.

== Open Source Firmware ==
Open source firmware for the KCMA-D8 is provided by [[coreboot-15h]] utilizing AMD's open source AGESA and CIMx releases for platform initialization. The git repository for the firmware can be reviewed [https://git.15h.org/mrothfuss/coreboot-15h here].

=== coreboot-15h ===
{{Excerpt|Coreboot-15h|[[ASUS KCMA-D8]]|hat=no}}

=== Missing Features ===
* SeaBIOS does not respond to keyboards behind a USB hub.
* Hibernation and Suspend/Resume are unsupported.
* Opteron 4100 series CPUs are unsupported.
* ASUS MIO audio cards are untested.

=== Flashing ===
To switch from the stock firmware to coreboot, [[External Flashing | external flashing]] is required. The DIP-8 flash chip is located at the bottom right corner of the board (labeled BIOS in the motherboard diagram). A 3.3V CH341a programmer can be used to flash coreboot onto the KCMA-D8. When switching to coreboot-15h from the OEM BIOS or coreboot, clearing the CMOS is required.

'''Clearing the CMOS'''
# Turn off the computer and disconnect the power cord
# Move the CLRTC1 jumper (located under PCI Slot 4) to positions 2-3
# Wait 20 seconds
# Restore the CLRTC1 jumper to positions 1-2
# Connect the power cord and turn on the computer

== Deployed Systems ==
* [[Ponos]]

== Motherboard Diagrams ==
[[File:KCMA-D8 Motherboard Diagram.png|frameless|400x400px]]
[[File:KCMA-D8 Motherboard BlockDiagram.png|frameless|400x400px]]

== Motherboard Components ==
=== Socket C32 ===
{{Excerpt|Socket C32|inline=yes|bold=yes}}
==== AMD Opteron 4100 Series ====
{{Excerpt|AMD Opteron 4100 Series|inline=yes|bold=yes}}
==== AMD Opteron 4200 and 4300 Series ====
{{Excerpt|AMD Opteron 4200 and 4300 Series|inline=yes|bold=yes}}
=== DDR3 Memory ===
[[File:KCMA-D8 Motherboard DDR3 Slots.png|frameless|600x600px]]

{{Excerpt|AGESA 15h|DDR3 Support|inline=yes|bold=yes}}

[[File:KCMA-D8 Motherboard DDR3 Voltage.png|frameless|600x600px]]

The KCMA-D8 provides an external method to override the BIOS DDR3 voltage. BIOS control is configured to select a voltage that maximizes performance for all DIMM modules attached to a socket. Forcing a different voltage may cause stability problems. Use the default jumper setting (1.5V / BIOS control) when using coreboot-15h.

=== PCIe 2.0 Slots ===
{| class="wikitable"
|+
!Slot
!Width
!Wired Lanes
!Notes
|-
|PCIe1
|x16
|x16
|
|-
|PCIe3
|x16
|x8
|
|-
|PCIe5
|x8
|x4
|Disabled if PIKE is occupied.
|}

=== PIKE Slots ===
The two PIKE slots, PIKE1 and PIKE2, are used together to attach an ASUS PIKE module to the KCMA-D8. This is required to utilize the 8 onboard SAS ports.

The family of ASUS PIKE modules are just PCIe SAS host bus adapters, using the proprietary PIKE connector. The PIKE modules have no onboard SAS connectors. The motherboard's SAS ports are wired to the PIKE slots, and function as a proprietary wiring harness for the PIKE module. PIKE modules use common HBA chips (LSI or Marvell) supported in the Linux kernel.

The [[PIKE2008]] card is recommended if you just want to be able to use the SAS ports. This card offers 6Gbps SAS2/SATA3 support, which is faster than the 3Gbps SATA2 provided by the SP5100. The card can be flashed to [[IT Mode]], which allows the host operating system to access the drives individually. Other PIKE cards provide 3Gbps SAS1/SATA2 support.

SeaBIOS has limited support for the [[PIKE2008]] and all SAS adapters. It cannot boot from them, unless the card's option ROM is executed. Option ROMs are disabled in the pre-built releases of coreboot-15h.

'''Note''': On the KCMA-D8, The PIKE slot is shared with a x8 PCIe slot (only one may be used). The PIKE cards are thus not necessary to maximize the capabilities of the system, and may be better or worse depending on your use case:
* Use a PCIe HBA if you want a mini-SAS connector
* Use a non-SAS SATA3 PCIe HBA if you want to boot from SATA3 drives (untested but should work)

=== DIP-8 Socket ===
The DIP-8 Socket houses the mainboard's BIOS ROM. The following DIP-8 chips are known to work with coreboot on the KCMA-D8.

{| class="wikitable"
|+
!Model
!Size (MB)
!Size (Mb)
|-
|W25Q16BVAIG
|2
|16
|-
|W25Q64BVAIG
|8
|64
|-
|W25Q128FVIQ
|16
|128
|}

=== ASPEED AST2050 ===
{{Excerpt|ASPEED AST2050|inline=yes|bold=yes}}

Remote administration features on the AST2050 are only activated when a firmware module (ASMB4 or ASMB5) is attached to the KGPE-D16 mainboard (BMC_FW1 slot).

=== AMD SR5670 ===
{{Excerpt|AMD SR5670|inline=yes|bold=yes}}
=== AMD SP5100 ===
{{Excerpt|AMD SP5100|inline=yes|bold=yes}}
=== Winbond W83667HG-A ===
{{Excerpt|Winbond W83667HG-A|hat=no}}
=== Nuvoton W83795G ===
{{Excerpt|Nuvoton W83795G/ADG|hat=no}}

== Board View ==
Board views are available for the KCMA-D8. These files can be opened with [[OpenBoardView]].

[[File:Asus KCMA-D8 1.02 Schematics.zip]]

== References ==

ASPEED AST2050

2026-06-17T19:09:01Z

Sbrudenell: /* Compiling from source */

ASPEED AST2050

2026-06-17T19:07:59Z

Sbrudenell: /* Compiling from source */