15h.org - Recent changes [en]

ASUS KCMA-D8

Sbrudenell — Wed, 08 Jul 2026 22:09:18 GMT

Kill-a-Watt Power Draw

@@ Line 156: / Line 156: @@
 === Nuvoton W83795G ===
 {{Excerpt|Nuvoton W83795G/ADG|hat=no}}
 == Board View ==

AGESA 15h

Mrothfuss — Wed, 08 Jul 2026 21:16:53 GMT

← Older revision		Revision as of 21:16, 8 July 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			This page provides technical details for AMD's "Orochi" open source AGESA for [[Family 15h#Overview\|Bulldozer and Piledriver]] CPUs.

			== Debugging ==
			To enable debugging, the following make menuconfig options are recommended:
			* Chipset > Enable AGESA Debugging = ON
			* Chipset > Debug AGESA Config = ON
			* Chipset > Debug AGESA CPU Code = ON
			* Chipset > Debug AGESA HT Code = ON
			* Chipset > Debug AGESA MEM Status = ON
			* Chipset > Debug AGESA MEM Flow = ON
			* Chipset > Debug AGESA MEM Registers = OFF
			* Chipset > Debug AGESA S3 Code = OFF
			* Console > Default console log level = 7 (DEBUG)

			The availability of debugging methods will vary by motherboard. Using the COM1 port is most ideal if supported. Every device supports [[EHCI Debugging\|EHCI debugging]], but this method can be slower and quirky.

	== 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.		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.

AGESA 15h

Sbrudenell — Wed, 08 Jul 2026 20:51:46 GMT

DDR3 Support

← Older revision		Revision as of 20:51, 8 July 2026
Line 184:		Line 184:
	\|1866 MHz		\|1866 MHz
	\|[[User:Mrothfuss\|mrothfuss]]		\|[[User:Mrothfuss\|mrothfuss]]
			\|-
			\|Samsung M386B4G70DM0-YK04
			\|Yes
			\|LRDIMM
			\|32 GB
			\|1600 MHz
			\|[[User:Sbrudenell\|sbrudenell]]
	\|-		\|-
	\|Samsung M386B8G70DE0-YH93		\|Samsung M386B8G70DE0-YH93

ASPEED AST2050

Sbrudenell — Sat, 04 Jul 2026 23:01:09 GMT

← Older revision		Revision as of 23:01, 4 July 2026
(6 intermediate revisions by the same user not shown)
Line 186:		Line 186:
	<nowiki>		<nowiki>
	rm -rf sstate-cache/ tmp/</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.