Files
server/usr/share/doc/qemu-system-common/system/arm/aspeed.html
2026-01-07 20:52:11 +01:00

441 lines
30 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!DOCTYPE html>
<html class="writer-html5" lang="en" data-content_root="../../">
<head>
<meta charset="utf-8" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Aspeed family boards (*-bmc, ast2500-evb, ast2600-evb) &mdash; QEMU Debian 1:8.2.2+ds-0ubuntu1.11 documentation</title>
<link rel="stylesheet" type="text/css" href="../../_static/pygments.css?v=fa44fd50" />
<link rel="stylesheet" type="text/css" href="../../_static/css/theme.css?v=86f27845" />
<link rel="stylesheet" type="text/css" href="../../_static/theme_overrides.css?v=08e6c168" />
<link rel="shortcut icon" href="../../_static/qemu_32x32.png"/>
<script src="../../_static/jquery.js?v=8dae8fb0"></script>
<script src="../../_static/_sphinx_javascript_frameworks_compat.js?v=2cd50e6c"></script>
<script src="../../_static/documentation_options.js?v=802af9f6"></script>
<script src="../../_static/doctools.js?v=888ff710"></script>
<script src="../../_static/sphinx_highlight.js?v=dc90522c"></script>
<script src="../../_static/custom.js?v=2ab9f71d"></script>
<script src="../../_static/js/theme.js"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="Banana Pi BPI-M2U (bpim2u)" href="bananapi_m2u.html" />
<link rel="prev" title="Arm Versatile Express boards (vexpress-a9, vexpress-a15)" href="vexpress.html" />
</head>
<body class="wy-body-for-nav">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side">
<div class="wy-side-scroll">
<div class="wy-side-nav-search" style="background: #802400" >
<a href="../../index.html" class="icon icon-home">
QEMU
<img src="../../_static/qemu_128x128.png" class="logo" alt="Logo"/>
</a>
<div class="version">
8.2.2
</div>
<div role="search">
<form id="rtd-search-form" class="wy-form" action="../../search.html" method="get">
<input type="text" name="q" placeholder="Search docs" aria-label="Search docs" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div><div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="Navigation menu">
<p class="caption" role="heading"><span class="caption-text">Contents:</span></p>
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="../../about/index.html">About QEMU</a></li>
<li class="toctree-l1 current"><a class="reference internal" href="../index.html">System Emulation</a><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="../introduction.html">Introduction</a></li>
<li class="toctree-l2"><a class="reference internal" href="../invocation.html">Invocation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../device-emulation.html">Device Emulation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../keys.html">Keys in the graphical frontends</a></li>
<li class="toctree-l2"><a class="reference internal" href="../mux-chardev.html">Keys in the character backend multiplexer</a></li>
<li class="toctree-l2"><a class="reference internal" href="../monitor.html">QEMU Monitor</a></li>
<li class="toctree-l2"><a class="reference internal" href="../images.html">Disk Images</a></li>
<li class="toctree-l2"><a class="reference internal" href="../virtio-net-failover.html">QEMU virtio-net standby (net_failover)</a></li>
<li class="toctree-l2"><a class="reference internal" href="../linuxboot.html">Direct Linux Boot</a></li>
<li class="toctree-l2"><a class="reference internal" href="../generic-loader.html">Generic Loader</a></li>
<li class="toctree-l2"><a class="reference internal" href="../guest-loader.html">Guest Loader</a></li>
<li class="toctree-l2"><a class="reference internal" href="../barrier.html">QEMU Barrier Client</a></li>
<li class="toctree-l2"><a class="reference internal" href="../vnc-security.html">VNC security</a></li>
<li class="toctree-l2"><a class="reference internal" href="../tls.html">TLS setup for network services</a></li>
<li class="toctree-l2"><a class="reference internal" href="../secrets.html">Providing secret data to QEMU</a></li>
<li class="toctree-l2"><a class="reference internal" href="../authz.html">Client authorization</a></li>
<li class="toctree-l2"><a class="reference internal" href="../gdb.html">GDB usage</a></li>
<li class="toctree-l2"><a class="reference internal" href="../replay.html">Record/replay</a></li>
<li class="toctree-l2"><a class="reference internal" href="../managed-startup.html">Managed start up options</a></li>
<li class="toctree-l2"><a class="reference internal" href="../bootindex.html">Managing device boot order with bootindex properties</a></li>
<li class="toctree-l2"><a class="reference internal" href="../cpu-hotplug.html">Virtual CPU hotplug</a></li>
<li class="toctree-l2"><a class="reference internal" href="../pr-manager.html">Persistent reservation managers</a></li>
<li class="toctree-l2 current"><a class="reference internal" href="../targets.html">QEMU System Emulator Targets</a><ul class="current">
<li class="toctree-l3 current"><a class="reference internal" href="../target-arm.html">Arm System emulator</a><ul class="current">
<li class="toctree-l4"><a class="reference internal" href="../target-arm.html#choosing-a-board-model">Choosing a board model</a></li>
<li class="toctree-l4 current"><a class="reference internal" href="../target-arm.html#board-specific-documentation">Board-specific documentation</a></li>
<li class="toctree-l4"><a class="reference internal" href="../target-arm.html#emulated-cpu-architecture-support">Emulated CPU architecture support</a></li>
<li class="toctree-l4"><a class="reference internal" href="../target-arm.html#arm-cpu-features">Arm CPU features</a></li>
</ul>
</li>
<li class="toctree-l3"><a class="reference internal" href="../target-avr.html">AVR System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-m68k.html">ColdFire System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-mips.html">MIPS System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-ppc.html">PowerPC System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-openrisc.html">OpenRISC System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-riscv.html">RISC-V System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-rx.html">RX System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-s390x.html">s390x System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-sparc.html">Sparc32 System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-sparc64.html">Sparc64 System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-i386.html">x86 System emulator</a></li>
<li class="toctree-l3"><a class="reference internal" href="../target-xtensa.html">Xtensa System emulator</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../security.html">Security</a></li>
<li class="toctree-l2"><a class="reference internal" href="../multi-process.html">Multi-process QEMU</a></li>
<li class="toctree-l2"><a class="reference internal" href="../confidential-guest-support.html">Confidential Guest Support</a></li>
<li class="toctree-l2"><a class="reference internal" href="../vm-templating.html">QEMU VM templating</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="../../user/index.html">User Mode Emulation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../tools/index.html">Tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../interop/index.html">System Emulation Management and Interoperability</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../specs/index.html">System Emulation Guest Hardware Specifications</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../devel/index.html">Developer Information</a></li>
</ul>
</div>
</div>
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap"><nav class="wy-nav-top" aria-label="Mobile navigation menu" style="background: #802400" >
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="../../index.html">QEMU</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content">
<div role="navigation" aria-label="Page navigation">
<ul class="wy-breadcrumbs">
<li><a href="../../index.html" class="icon icon-home" aria-label="Home"></a></li>
<li class="breadcrumb-item"><a href="../index.html">System Emulation</a></li>
<li class="breadcrumb-item"><a href="../targets.html">QEMU System Emulator Targets</a></li>
<li class="breadcrumb-item"><a href="../target-arm.html">Arm System emulator</a></li>
<li class="breadcrumb-item active">Aspeed family boards (<code class="docutils literal notranslate"><span class="pre">*-bmc</span></code>, <code class="docutils literal notranslate"><span class="pre">ast2500-evb</span></code>, <code class="docutils literal notranslate"><span class="pre">ast2600-evb</span></code>)</li>
<li class="wy-breadcrumbs-aside">
<a href="https://gitlab.com/qemu-project/qemu/blob/master/docs/system/arm/aspeed.rst" class="fa fa-gitlab"> Edit on GitLab</a>
</li>
</ul>
<hr/>
</div>
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
<section id="aspeed-family-boards-bmc-ast2500-evb-ast2600-evb">
<h1>Aspeed family boards (<code class="docutils literal notranslate"><span class="pre">*-bmc</span></code>, <code class="docutils literal notranslate"><span class="pre">ast2500-evb</span></code>, <code class="docutils literal notranslate"><span class="pre">ast2600-evb</span></code>)<a class="headerlink" href="#aspeed-family-boards-bmc-ast2500-evb-ast2600-evb" title="Link to this heading"></a></h1>
<p>The QEMU Aspeed machines model BMCs of various OpenPOWER systems and
Aspeed evaluation boards. They are based on different releases of the
Aspeed SoC : the AST2400 integrating an ARM926EJ-S CPU (400MHz), the
AST2500 with an ARM1176JZS CPU (800MHz) and more recently the AST2600
with dual cores ARM Cortex-A7 CPUs (1.2GHz).</p>
<p>The SoC comes with RAM, Gigabit ethernet, USB, SD/MMC, USB, SPI, I2C,
etc.</p>
<p>AST2400 SoC based machines :</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">palmetto-bmc</span></code> OpenPOWER Palmetto POWER8 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">quanta-q71l-bmc</span></code> OpenBMC Quanta BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">supermicrox11-bmc</span></code> Supermicro X11 BMC</p></li>
</ul>
<p>AST2500 SoC based machines :</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">ast2500-evb</span></code> Aspeed AST2500 Evaluation board</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">romulus-bmc</span></code> OpenPOWER Romulus POWER9 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">witherspoon-bmc</span></code> OpenPOWER Witherspoon POWER9 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">sonorapass-bmc</span></code> OCP SonoraPass BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">fp5280g2-bmc</span></code> Inspur FP5280G2 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">g220a-bmc</span></code> Bytedance G220A BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">yosemitev2-bmc</span></code> Facebook YosemiteV2 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">tiogapass-bmc</span></code> Facebook Tiogapass BMC</p></li>
</ul>
<p>AST2600 SoC based machines :</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">ast2600-evb</span></code> Aspeed AST2600 Evaluation board (Cortex-A7)</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">tacoma-bmc</span></code> OpenPOWER Witherspoon POWER9 AST2600 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">rainier-bmc</span></code> IBM Rainier POWER10 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">fuji-bmc</span></code> Facebook Fuji BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">bletchley-bmc</span></code> Facebook Bletchley BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">fby35-bmc</span></code> Facebook fby35 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">qcom-dc-scm-v1-bmc</span></code> Qualcomm DC-SCM V1 BMC</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">qcom-firework-bmc</span></code> Qualcomm Firework BMC</p></li>
</ul>
<section id="supported-devices">
<h2>Supported devices<a class="headerlink" href="#supported-devices" title="Link to this heading"></a></h2>
<blockquote>
<div><ul class="simple">
<li><p>SMP (for the AST2600 Cortex-A7)</p></li>
<li><p>Interrupt Controller (VIC)</p></li>
<li><p>Timer Controller</p></li>
<li><p>RTC Controller</p></li>
<li><p>I2C Controller, including the new register interface of the AST2600</p></li>
<li><p>System Control Unit (SCU)</p></li>
<li><p>SRAM mapping</p></li>
<li><p>X-DMA Controller (basic interface)</p></li>
<li><p>Static Memory Controller (SMC or FMC) - Only SPI Flash support</p></li>
<li><p>SPI Memory Controller</p></li>
<li><p>USB 2.0 Controller</p></li>
<li><p>SD/MMC storage controllers</p></li>
<li><p>SDRAM controller (dummy interface for basic settings and training)</p></li>
<li><p>Watchdog Controller</p></li>
<li><p>GPIO Controller (Master only)</p></li>
<li><p>UART</p></li>
<li><p>Ethernet controllers</p></li>
<li><p>Front LEDs (PCA9552 on I2C bus)</p></li>
<li><p>LPC Peripheral Controller (a subset of subdevices are supported)</p></li>
<li><p>Hash/Crypto Engine (HACE) - Hash support only. TODO: HMAC and RSA</p></li>
<li><p>ADC</p></li>
<li><p>Secure Boot Controller (AST2600)</p></li>
<li><p>eMMC Boot Controller (dummy)</p></li>
<li><p>PECI Controller (minimal)</p></li>
<li><p>I3C Controller</p></li>
</ul>
</div></blockquote>
</section>
<section id="missing-devices">
<h2>Missing devices<a class="headerlink" href="#missing-devices" title="Link to this heading"></a></h2>
<blockquote>
<div><ul class="simple">
<li><p>Coprocessor support</p></li>
<li><p>PWM and Fan Controller</p></li>
<li><p>Slave GPIO Controller</p></li>
<li><p>Super I/O Controller</p></li>
<li><p>PCI-Express 1 Controller</p></li>
<li><p>Graphic Display Controller</p></li>
<li><p>MCTP Controller</p></li>
<li><p>Mailbox Controller</p></li>
<li><p>Virtual UART</p></li>
<li><p>eSPI Controller</p></li>
</ul>
</div></blockquote>
</section>
<section id="boot-options">
<h2>Boot options<a class="headerlink" href="#boot-options" title="Link to this heading"></a></h2>
<p>The Aspeed machines can be started using the <code class="docutils literal notranslate"><span class="pre">-kernel</span></code> and <code class="docutils literal notranslate"><span class="pre">-dtb</span></code> options
to load a Linux kernel or from a firmware. Images can be downloaded from the
OpenBMC jenkins :</p>
<blockquote>
<div><p><a class="reference external" href="https://jenkins.openbmc.org/job/ci-openbmc/lastSuccessfulBuild/">https://jenkins.openbmc.org/job/ci-openbmc/lastSuccessfulBuild/</a></p>
</div></blockquote>
<p>or directly from the OpenBMC GitHub release repository :</p>
<blockquote>
<div><p><a class="reference external" href="https://github.com/openbmc/openbmc/releases">https://github.com/openbmc/openbmc/releases</a></p>
</div></blockquote>
<p>To boot a kernel directly from a Linux build tree:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>qemu-system-arm<span class="w"> </span>-M<span class="w"> </span>ast2600-evb<span class="w"> </span>-nographic<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-kernel<span class="w"> </span>arch/arm/boot/zImage<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-dtb<span class="w"> </span>arch/arm/boot/dts/aspeed-ast2600-evb.dtb<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-initrd<span class="w"> </span>rootfs.cpio
</pre></div>
</div>
<p>To boot the machine from the flash image, use an MTD drive :</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>qemu-system-arm<span class="w"> </span>-M<span class="w"> </span>romulus-bmc<span class="w"> </span>-nic<span class="w"> </span>user<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-drive<span class="w"> </span><span class="nv">file</span><span class="o">=</span>obmc-phosphor-image-romulus.static.mtd,format<span class="o">=</span>raw,if<span class="o">=</span>mtd<span class="w"> </span>-nographic
</pre></div>
</div>
<p>Options specific to Aspeed machines are :</p>
<blockquote>
<div><ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">execute-in-place</span></code> which emulates the boot from the CE0 flash
device by using the FMC controller to load the instructions, and
not simply from RAM. This takes a little longer.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">fmc-model</span></code> to change the default FMC Flash model. FW needs
support for the chip model to boot.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">spi-model</span></code> to change the default SPI Flash model.</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">bmc-console</span></code> to change the default console device. Most of the
machines use the <code class="docutils literal notranslate"><span class="pre">UART5</span></code> device for a boot console, which is
mapped on <code class="docutils literal notranslate"><span class="pre">/dev/ttyS4</span></code> under Linux, but it is not always the
case.</p></li>
</ul>
</div></blockquote>
<p>To use other flash models, for instance a different FMC chip and a
bigger (64M) SPI for the <code class="docutils literal notranslate"><span class="pre">ast2500-evb</span></code> machine, run :</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>-M<span class="w"> </span>ast2500-evb,fmc-model<span class="o">=</span>mx25l25635e,spi-model<span class="o">=</span>mx66u51235f
</pre></div>
</div>
<p>When more flexibility is needed to define the flash devices, to use
different flash models or define all flash devices (up to 8), the
<code class="docutils literal notranslate"><span class="pre">-nodefaults</span></code> QEMU option can be used to avoid creating the default
flash devices.</p>
<p>Flash devices should then be created from the command line and attached
to a block device :</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>qemu-system-arm<span class="w"> </span>-M<span class="w"> </span>ast2600-evb<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-blockdev<span class="w"> </span>node-name<span class="o">=</span>fmc0,driver<span class="o">=</span>file,filename<span class="o">=</span>/path/to/fmc0.img<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-device<span class="w"> </span>mx66u51235f,bus<span class="o">=</span>ssi.0,cs<span class="o">=</span>0x0,drive<span class="o">=</span>fmc0<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-blockdev<span class="w"> </span>node-name<span class="o">=</span>fmc1,driver<span class="o">=</span>file,filename<span class="o">=</span>/path/to/fmc1.img<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-device<span class="w"> </span>mx66u51235f,bus<span class="o">=</span>ssi.0,cs<span class="o">=</span>0x1,drive<span class="o">=</span>fmc1<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-blockdev<span class="w"> </span>node-name<span class="o">=</span>spi1,driver<span class="o">=</span>file,filename<span class="o">=</span>/path/to/spi1.img<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-device<span class="w"> </span>mx66u51235f,cs<span class="o">=</span>0x0,bus<span class="o">=</span>ssi.1,drive<span class="o">=</span>spi1<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-nographic<span class="w"> </span>-nodefaults
</pre></div>
</div>
<p>In that case, the machine boots fetching instructions from the FMC0
device. It is slower to start but closer to what HW does. Using the
machine option <code class="docutils literal notranslate"><span class="pre">execute-in-place</span></code> has a similar effect.</p>
<p>To change the boot console and use device <code class="docutils literal notranslate"><span class="pre">UART3</span></code> (<code class="docutils literal notranslate"><span class="pre">/dev/ttyS2</span></code>
under Linux), use :</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>-M<span class="w"> </span>ast2500-evb,bmc-console<span class="o">=</span>uart3
</pre></div>
</div>
</section>
</section>
<section id="aspeed-minibmc-family-boards-ast1030-evb">
<h1>Aspeed minibmc family boards (<code class="docutils literal notranslate"><span class="pre">ast1030-evb</span></code>)<a class="headerlink" href="#aspeed-minibmc-family-boards-ast1030-evb" title="Link to this heading"></a></h1>
<p>The QEMU Aspeed machines model mini BMCs of various Aspeed evaluation
boards. They are based on different releases of the
Aspeed SoC : the AST1030 integrating an ARM Cortex M4F CPU (200MHz).</p>
<p>The SoC comes with SRAM, SPI, I2C, etc.</p>
<p>AST1030 SoC based machines :</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">ast1030-evb</span></code> Aspeed AST1030 Evaluation board (Cortex-M4F)</p></li>
</ul>
<section id="id1">
<h2>Supported devices<a class="headerlink" href="#id1" title="Link to this heading"></a></h2>
<blockquote>
<div><ul class="simple">
<li><p>SMP (for the AST1030 Cortex-M4F)</p></li>
<li><p>Interrupt Controller (VIC)</p></li>
<li><p>Timer Controller</p></li>
<li><p>I2C Controller</p></li>
<li><p>System Control Unit (SCU)</p></li>
<li><p>SRAM mapping</p></li>
<li><p>Static Memory Controller (SMC or FMC) - Only SPI Flash support</p></li>
<li><p>SPI Memory Controller</p></li>
<li><p>USB 2.0 Controller</p></li>
<li><p>Watchdog Controller</p></li>
<li><p>GPIO Controller (Master only)</p></li>
<li><p>UART</p></li>
<li><p>LPC Peripheral Controller (a subset of subdevices are supported)</p></li>
<li><p>Hash/Crypto Engine (HACE) - Hash support only. TODO: HMAC and RSA</p></li>
<li><p>ADC</p></li>
<li><p>Secure Boot Controller</p></li>
<li><p>PECI Controller (minimal)</p></li>
</ul>
</div></blockquote>
</section>
<section id="id2">
<h2>Missing devices<a class="headerlink" href="#id2" title="Link to this heading"></a></h2>
<blockquote>
<div><ul class="simple">
<li><p>PWM and Fan Controller</p></li>
<li><p>Slave GPIO Controller</p></li>
<li><p>Mailbox Controller</p></li>
<li><p>Virtual UART</p></li>
<li><p>eSPI Controller</p></li>
<li><p>I3C Controller</p></li>
</ul>
</div></blockquote>
</section>
<section id="id3">
<h2>Boot options<a class="headerlink" href="#id3" title="Link to this heading"></a></h2>
<p>The Aspeed machines can be started using the <code class="docutils literal notranslate"><span class="pre">-kernel</span></code> to load a
Zephyr OS or from a firmware. Images can be downloaded from the
ASPEED GitHub release repository :</p>
<blockquote>
<div><p><a class="reference external" href="https://github.com/AspeedTech-BMC/zephyr/releases">https://github.com/AspeedTech-BMC/zephyr/releases</a></p>
</div></blockquote>
<p>To boot a kernel directly from a Zephyr build tree:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>qemu-system-arm<span class="w"> </span>-M<span class="w"> </span>ast1030-evb<span class="w"> </span>-nographic<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-kernel<span class="w"> </span>zephyr.elf
</pre></div>
</div>
</section>
</section>
<section id="facebook-yosemite-v3-5-platform-and-craterlake-server-fby35">
<h1>Facebook Yosemite v3.5 Platform and CraterLake Server (<code class="docutils literal notranslate"><span class="pre">fby35</span></code>)<a class="headerlink" href="#facebook-yosemite-v3-5-platform-and-craterlake-server-fby35" title="Link to this heading"></a></h1>
<p>Facebook has a series of multi-node compute server designs named
Yosemite. The most recent version released was
<a class="reference external" href="https://www.opencompute.org/documents/ocp-yosemite-v3-platform-design-specification-1v16-pdf">Yosemite v3</a>.</p>
<p>Yosemite v3.5 is an iteration on this design, and is very similar: theres a
baseboard with a BMC, and 4 server slots. The new server board design termed
“CraterLake” includes a Bridge IC (BIC), with room for expansion boards to
include various compute accelerators (video, inferencing, etc). At the moment,
only the first server slots BIC is included.</p>
<p>Yosemite v3.5 is itself a sled which fits into a 40U chassis, and 3 sleds
can be fit into a chassis. See <a class="reference external" href="https://www.opencompute.org/products/423/wiwynn-yosemite-v3-server">here</a>
for an example.</p>
<p>In this generation, the BMC is an AST2600 and each BIC is an AST1030. The BMC
runs <a class="reference external" href="https://github.com/facebook/openbmc">OpenBMC</a>, and the BIC runs
<a class="reference external" href="https://github.com/facebook/openbic">OpenBIC</a>.</p>
<p>Firmware images can be retrieved from the Github releases or built from the
source code, see the READMEs for instructions on that. This image uses the
“fby35” machine recipe from OpenBMC, and the “yv35-cl” target from OpenBIC.
Some reference images can also be found here:</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>wget<span class="w"> </span>https://github.com/facebook/openbmc/releases/download/openbmc-e2294ff5d31d/fby35.mtd
$<span class="w"> </span>wget<span class="w"> </span>https://github.com/peterdelevoryas/OpenBIC/releases/download/oby35-cl-2022.13.01/Y35BCL.elf
</pre></div>
</div>
<p>Since this machine has multiple SoCs, each with their own serial console, the
recommended way to run it is to allocate a pseudoterminal for each serial
console and let the monitor use stdio. Also, starting in a paused state is
useful because it allows you to attach to the pseudoterminals before the boot
process starts.</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span>$<span class="w"> </span>qemu-system-arm<span class="w"> </span>-machine<span class="w"> </span>fby35<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-drive<span class="w"> </span><span class="nv">file</span><span class="o">=</span>fby35.mtd,format<span class="o">=</span>raw,if<span class="o">=</span>mtd<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-device<span class="w"> </span>loader,file<span class="o">=</span>Y35BCL.elf,addr<span class="o">=</span><span class="m">0</span>,cpu-num<span class="o">=</span><span class="m">2</span><span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-serial<span class="w"> </span>pty<span class="w"> </span>-serial<span class="w"> </span>pty<span class="w"> </span>-serial<span class="w"> </span>mon:stdio<span class="w"> </span><span class="se">\</span>
<span class="w"> </span>-display<span class="w"> </span>none<span class="w"> </span>-S
$<span class="w"> </span>screen<span class="w"> </span>/dev/tty0<span class="w"> </span><span class="c1"># In a separate TMUX pane, terminal window, etc.</span>
$<span class="w"> </span>screen<span class="w"> </span>/dev/tty1
$<span class="w"> </span><span class="o">(</span>qemu<span class="o">)</span><span class="w"> </span>c<span class="w"> </span><span class="c1"># Start the boot process once screen is setup.</span>
</pre></div>
</div>
</section>
</div>
</div>
<footer><div class="rst-footer-buttons" role="navigation" aria-label="Footer">
<a href="vexpress.html" class="btn btn-neutral float-left" title="Arm Versatile Express boards (vexpress-a9, vexpress-a15)" accesskey="p" rel="prev"><span class="fa fa-arrow-circle-left" aria-hidden="true"></span> Previous</a>
<a href="bananapi_m2u.html" class="btn btn-neutral float-right" title="Banana Pi BPI-M2U (bpim2u)" accesskey="n" rel="next">Next <span class="fa fa-arrow-circle-right" aria-hidden="true"></span></a>
</div>
<hr/>
<div role="contentinfo">
<p>&#169; Copyright 2025, The QEMU Project Developers.</p>
</div>
Built with <a href="https://www.sphinx-doc.org/">Sphinx</a> using a
<a href="https://github.com/readthedocs/sphinx_rtd_theme">theme</a>
provided by <a href="https://readthedocs.org">Read the Docs</a>.
<!-- Empty para to force a blank line after "Built with Sphinx ..." -->
<p></p>
<p>This documentation is for QEMU version 8.2.2.</p>
<p><a href="../../about/license.html">QEMU and this manual are released under the
GNU General Public License, version 2.</a></p>
</footer>
</div>
</div>
</section>
</div>
<script>
jQuery(function () {
SphinxRtdTheme.Navigation.enable(true);
});
</script>
</body>
</html>