1Aspeed family boards (``*-bmc``, ``ast2500-evb``, ``ast2600-evb``) 2================================================================== 3 4The QEMU Aspeed machines model BMCs of various OpenPOWER systems and 5Aspeed evaluation boards. They are based on different releases of the 6Aspeed SoC : the AST2400 integrating an ARM926EJ-S CPU (400MHz), the 7AST2500 with an ARM1176JZS CPU (800MHz) and more recently the AST2600 8with dual cores ARM Cortex-A7 CPUs (1.2GHz). 9 10The SoC comes with RAM, Gigabit ethernet, USB, SD/MMC, USB, SPI, I2C, 11etc. 12 13AST2400 SoC based machines : 14 15- ``palmetto-bmc`` OpenPOWER Palmetto POWER8 BMC 16- ``quanta-q71l-bmc`` OpenBMC Quanta BMC 17- ``supermicrox11-bmc`` Supermicro X11 BMC 18 19AST2500 SoC based machines : 20 21- ``ast2500-evb`` Aspeed AST2500 Evaluation board 22- ``romulus-bmc`` OpenPOWER Romulus POWER9 BMC 23- ``witherspoon-bmc`` OpenPOWER Witherspoon POWER9 BMC 24- ``sonorapass-bmc`` OCP SonoraPass BMC 25- ``fp5280g2-bmc`` Inspur FP5280G2 BMC 26- ``g220a-bmc`` Bytedance G220A BMC 27- ``yosemitev2-bmc`` Facebook YosemiteV2 BMC 28 29AST2600 SoC based machines : 30 31- ``ast2600-evb`` Aspeed AST2600 Evaluation board (Cortex-A7) 32- ``tacoma-bmc`` OpenPOWER Witherspoon POWER9 AST2600 BMC 33- ``rainier-bmc`` IBM Rainier POWER10 BMC 34- ``fuji-bmc`` Facebook Fuji BMC 35- ``bletchley-bmc`` Facebook Bletchley BMC 36- ``fby35-bmc`` Facebook fby35 BMC 37- ``qcom-dc-scm-v1-bmc`` Qualcomm DC-SCM V1 BMC 38- ``qcom-firework-bmc`` Qualcomm Firework BMC 39 40Supported devices 41----------------- 42 43 * SMP (for the AST2600 Cortex-A7) 44 * Interrupt Controller (VIC) 45 * Timer Controller 46 * RTC Controller 47 * I2C Controller, including the new register interface of the AST2600 48 * System Control Unit (SCU) 49 * SRAM mapping 50 * X-DMA Controller (basic interface) 51 * Static Memory Controller (SMC or FMC) - Only SPI Flash support 52 * SPI Memory Controller 53 * USB 2.0 Controller 54 * SD/MMC storage controllers 55 * SDRAM controller (dummy interface for basic settings and training) 56 * Watchdog Controller 57 * GPIO Controller (Master only) 58 * UART 59 * Ethernet controllers 60 * Front LEDs (PCA9552 on I2C bus) 61 * LPC Peripheral Controller (a subset of subdevices are supported) 62 * Hash/Crypto Engine (HACE) - Hash support only. TODO: HMAC and RSA 63 * ADC 64 * Secure Boot Controller (AST2600) 65 * eMMC Boot Controller (dummy) 66 * PECI Controller (minimal) 67 * I3C Controller 68 69 70Missing devices 71--------------- 72 73 * Coprocessor support 74 * PWM and Fan Controller 75 * Slave GPIO Controller 76 * Super I/O Controller 77 * PCI-Express 1 Controller 78 * Graphic Display Controller 79 * MCTP Controller 80 * Mailbox Controller 81 * Virtual UART 82 * eSPI Controller 83 84Boot options 85------------ 86 87The Aspeed machines can be started using the ``-kernel`` and ``-dtb`` options 88to load a Linux kernel or from a firmware. Images can be downloaded from the 89OpenBMC jenkins : 90 91 https://jenkins.openbmc.org/job/ci-openbmc/lastSuccessfulBuild/ 92 93or directly from the OpenBMC GitHub release repository : 94 95 https://github.com/openbmc/openbmc/releases 96 97To boot a kernel directly from a Linux build tree: 98 99.. code-block:: bash 100 101 $ qemu-system-arm -M ast2600-evb -nographic \ 102 -kernel arch/arm/boot/zImage \ 103 -dtb arch/arm/boot/dts/aspeed-ast2600-evb.dtb \ 104 -initrd rootfs.cpio 105 106The image should be attached as an MTD drive. Run : 107 108.. code-block:: bash 109 110 $ qemu-system-arm -M romulus-bmc -nic user \ 111 -drive file=obmc-phosphor-image-romulus.static.mtd,format=raw,if=mtd -nographic 112 113Options specific to Aspeed machines are : 114 115 * ``execute-in-place`` which emulates the boot from the CE0 flash 116 device by using the FMC controller to load the instructions, and 117 not simply from RAM. This takes a little longer. 118 119 * ``fmc-model`` to change the FMC Flash model. FW needs support for 120 the chip model to boot. 121 122 * ``spi-model`` to change the SPI Flash model. 123 124For instance, to start the ``ast2500-evb`` machine with a different 125FMC chip and a bigger (64M) SPI chip, use : 126 127.. code-block:: bash 128 129 -M ast2500-evb,fmc-model=mx25l25635e,spi-model=mx66u51235f 130 131 132Aspeed minibmc family boards (``ast1030-evb``) 133================================================================== 134 135The QEMU Aspeed machines model mini BMCs of various Aspeed evaluation 136boards. They are based on different releases of the 137Aspeed SoC : the AST1030 integrating an ARM Cortex M4F CPU (200MHz). 138 139The SoC comes with SRAM, SPI, I2C, etc. 140 141AST1030 SoC based machines : 142 143- ``ast1030-evb`` Aspeed AST1030 Evaluation board (Cortex-M4F) 144 145Supported devices 146----------------- 147 148 * SMP (for the AST1030 Cortex-M4F) 149 * Interrupt Controller (VIC) 150 * Timer Controller 151 * I2C Controller 152 * System Control Unit (SCU) 153 * SRAM mapping 154 * Static Memory Controller (SMC or FMC) - Only SPI Flash support 155 * SPI Memory Controller 156 * USB 2.0 Controller 157 * Watchdog Controller 158 * GPIO Controller (Master only) 159 * UART 160 * LPC Peripheral Controller (a subset of subdevices are supported) 161 * Hash/Crypto Engine (HACE) - Hash support only. TODO: HMAC and RSA 162 * ADC 163 * Secure Boot Controller 164 * PECI Controller (minimal) 165 166 167Missing devices 168--------------- 169 170 * PWM and Fan Controller 171 * Slave GPIO Controller 172 * Mailbox Controller 173 * Virtual UART 174 * eSPI Controller 175 * I3C Controller 176 177Boot options 178------------ 179 180The Aspeed machines can be started using the ``-kernel`` to load a 181Zephyr OS or from a firmware. Images can be downloaded from the 182ASPEED GitHub release repository : 183 184 https://github.com/AspeedTech-BMC/zephyr/releases 185 186To boot a kernel directly from a Zephyr build tree: 187 188.. code-block:: bash 189 190 $ qemu-system-arm -M ast1030-evb -nographic \ 191 -kernel zephyr.elf 192 193Facebook Yosemite v3.5 Platform and CraterLake Server (``fby35``) 194================================================================== 195 196Facebook has a series of multi-node compute server designs named 197Yosemite. The most recent version released was 198`Yosemite v3 <https://www.opencompute.org/documents/ocp-yosemite-v3-platform-design-specification-1v16-pdf>`__. 199 200Yosemite v3.5 is an iteration on this design, and is very similar: there's a 201baseboard with a BMC, and 4 server slots. The new server board design termed 202"CraterLake" includes a Bridge IC (BIC), with room for expansion boards to 203include various compute accelerators (video, inferencing, etc). At the moment, 204only the first server slot's BIC is included. 205 206Yosemite v3.5 is itself a sled which fits into a 40U chassis, and 3 sleds 207can be fit into a chassis. See `here <https://www.opencompute.org/products/423/wiwynn-yosemite-v3-server>`__ 208for an example. 209 210In this generation, the BMC is an AST2600 and each BIC is an AST1030. The BMC 211runs `OpenBMC <https://github.com/facebook/openbmc>`__, and the BIC runs 212`OpenBIC <https://github.com/facebook/openbic>`__. 213 214Firmware images can be retrieved from the Github releases or built from the 215source code, see the README's for instructions on that. This image uses the 216"fby35" machine recipe from OpenBMC, and the "yv35-cl" target from OpenBIC. 217Some reference images can also be found here: 218 219.. code-block:: bash 220 221 $ wget https://github.com/facebook/openbmc/releases/download/openbmc-e2294ff5d31d/fby35.mtd 222 $ wget https://github.com/peterdelevoryas/OpenBIC/releases/download/oby35-cl-2022.13.01/Y35BCL.elf 223 224Since this machine has multiple SoC's, each with their own serial console, the 225recommended way to run it is to allocate a pseudoterminal for each serial 226console and let the monitor use stdio. Also, starting in a paused state is 227useful because it allows you to attach to the pseudoterminals before the boot 228process starts. 229 230.. code-block:: bash 231 232 $ qemu-system-arm -machine fby35 \ 233 -drive file=fby35.mtd,format=raw,if=mtd \ 234 -device loader,file=Y35BCL.elf,addr=0,cpu-num=2 \ 235 -serial pty -serial pty -serial mon:stdio \ 236 -display none -S 237 $ screen /dev/tty0 # In a separate TMUX pane, terminal window, etc. 238 $ screen /dev/tty1 239 $ (qemu) c # Start the boot process once screen is setup. 240