Evaluation Board - System Controller (SC)
Welcome to the updated System Controller Updates Wiki. You can find the legacy wiki here: Legacy System Controller Updates
1. Introduction
This page outlines the functions and features of the Evaluation Board System Controller (SC). The SC is an independent MPSoC-based subsystem on some evaluation boards that helps users evaluate the device under test (DUT). The DUT refers to the main SoC targeted by the evaluation board. For example, in VEK385, the DUT is the Versal Gen 2 VE3858 device.
2. Table of Contents
- 1 1. Introduction
- 2 2. Table of Contents
- 3 3. Overview
- 4 4. System Controller Software Version
- 5 5. Updating Your System Controller
- 6 6. Getting To Know Your System Controller
- 6.1 6.1 Board Evaluation and Management (BEAM) Tool
- 6.1.1 6.1.1 Overview
- 6.1.2 6.1.2 Board and requirements
- 6.1.3 6.1.3 Board setup and connections
- 6.1.4 6.1.4 Launching the BEAM GUI
- 6.1.5 6.1.5 GUI Pages
- 6.1.5.1 6.1.5.1 Home
- 6.1.5.2 6.1.5.2 About
- 6.1.5.3 6.1.5.3 Help
- 6.1.5.4 6.1.5.4 Get Logs
- 6.1.5.5 6.1.5.5 Export CSV
- 6.1.5.6 6.1.5.6 Test The Board
- 6.1.5.7 6.1.5.7 Test The Board → Board Settings
- 6.1.5.8 6.1.5.8 Test The Board → Board Interface Test
- 6.1.5.9 6.1.5.9 Test The Board → Linux File System
- 6.1.5.10 6.1.5.10 PM Dashboard
- 6.1.5.11 6.1.5.11 Versal Device Control
- 6.1.5.12 6.1.5.12 Set Mac Address
- 6.2 6.2 FAN Control
- 6.1 6.1 Board Evaluation and Management (BEAM) Tool
- 7 7. Debug Tips
- 8 8. Source Code
3. Overview
The System Controller (SC) acts as a cooperative support component to the DUT, while allowing the DUT to operate independently. The “domains” in the example evaluation board functional diagram below outline the independent functions within each subsystem. The SC has dedicated Ethernet, USB, and UART interfaces for user interaction. The DUT has its own peripherals, which vary based on its capabilities and the evaluation board features. For details on the DUT peripheral set, refer to the User Guide (UG) for your specific board. Figure 1 shows a functional diagram of the evaluation board, including the SC, the DUT, and typical peripherals and connections.
The SC design captured in this page uses a common architecture for the different evaluation boards. It provides most functionality and user workflows in a board agnostic manner, and any specific board references are for example only. The SC subsystem has its boot firmware pre-loaded to the SC QSPI device at the factory and should boot upon initial power-on of the evaluation board. However, it is highly recommended to update to the latest build posted here. The SC will automatically start a web-based user interface called BEAM or Board Evaluation and Management tool. The BEAM tool provides GUI based interaction with the board programmable features such as clocks, FMC functionality, power system configuration, and built-in-self-test (BIST) features.
The rest of this document details the SC update process, the Board Evaluation and Management Tool (BEAM), fan control, debug tips, and source code information.
4. System Controller Software Version
4.1 Overview
Recently, the system controller release name changed from SC Update x.y to YEAR_SC_Q#, where YEAR and Q# indicate the release year and quarter. For example, version 2026_SC_Q2 means it was released in the second quarter of 2026. The new naming also introduces an additional release version to track board support packages, labeled RPM_RELEASE_VERSION. The last SC Update using the SC Update x.y format was SC Update 8.1.
Starting 2026_SC_Q2, System Controller releases will track the eMMC Image version separately from the RPM (board support package) Release Version. A board has the latest System Controller update if both the eMMC Image Version and RPM Release Version match the latest Supported SC Release in Table 1.
4.2 Determine the System Controller Version Running on Your Board
To find your board's system controller version, open the About Page of your BEAM tool and check the eMMC Image Information section. If this section includes a RELEASE field, as highlighted in Figure 2, your board uses a system controller version in the SC Update x.y format. The release field shows your system controller version. If the RELEASE field is missing, as shown in Figure 3, your board uses a system controller version in the YEAR_SC_Q# format. The VERSION field in Figure 3 shows the eMMC/WIC image version, and the RPM_RELEASE_VERSION under the RPM Release Version section shows the board support package release version. Table 1 in section Evaluation Board - System Controller (SC) lists the latest supported SC version for each evaluation board.
For details on starting the BEAM GUI and its pages, see section Evaluation Board - System Controller (SC)
5. Updating Your System Controller
This section describes how to update the System Controller (SC) software on supported AMD evaluation boards. The content is organized by board type and focuses on identifying the latest SC version supported per board and the required update sequence.
5.1 Board-to-Version Mapping
The table below lists supported boards, their boot medium, the supported System Controller release, and the associated update flow.
Board | Boot Medium | Latest Supported SC Release | Required Update Steps | Download Links |
|---|---|---|---|---|
SCU200 VEK385 VRK160 VRK165 | eMMC + QSPI | eMMC Image Information RPM Release Version
|
| |
VEK280 VHK158 VPK120 VPK180 | eMMC + QSPI (see Note 1 below) | SC Update 7.1 |
| |
VCK190 VMK180 | SD Card | SC Update 7.1 |
|
Table 1: Board to SC Version Map
Note 1: The VPK120 and VPK180 include a System Controller BOOTMODE switch (SW11) for the SC that must be set to QSPI32 boot mode (set SW11 to ON, OFF, ON, ON) for factory out-of-box functionality. For details, see the "Default Switch Settings" section in the evaluation board user guide.
5.2 Update Sequence Overview
Most boards with a System Controller follow a three-phase software update sequence, each phase preparing the system for the next. The VCK190 and VMK180 update sequence involves only one step: updating the SD card image. Other boards follow this sequence:
Update QSPI Boot Firmware
Update AMD EDF SC Linux Image
Install Board Support Packages
5.3 Step 1: Update QSPI Boot Firmware
The QSPI boot firmware initializes the System Controller hardware and provides the bootloader environment for Linux. The QSPI image must match the target AMD EDF SC Linux version. Use the Image Recovery Tool to update the QSPI boot firmware. This web tool updates firmware and the AMD EDF SC Linux image.
5.3.1 Program QSPI Boot Firmware
Connect your SC ethernet port on your evaluation board to your workstation. Connect your workstation to the board UART port. Power on the board while holding the SC FWUEN pushbutton. The board will boot into the Image Recovery Tool. The program steps vary slightly depending on the Image Recovery Tool version running on your board. The Legacy Image Recovery is a baremetal application that boots on the System Controller, while the Revised Image Recovery tool is a Linux utility. To identify which version is running, inspect your SC UART output. If the output matches Figure 5, you have the Legacy Image Recovery Tool and should proceed to Evaluation Board - System Controller (SC) section. Otherwise, skip to Evaluation Board - System Controller (SC) section.
Figure 5: Legacy Image Recovery Tool boot messages on a VEK280
5.3.1.1 Legacy Image Recovery Tool
The Legacy Image Recovery Tool connects directly to your workstation using the static IP address 192.168.0.111 with a 255.255.255.0 netmask. Adjust your workstation's network settings for the Ethernet connection to access the board. Using your browser (Firefox recommended), navigate to http://192.168.0.111 to open the Image Recovery Tool. Figure 6 shows the tool on a VEK280.
Figure 6: Legacy Image Recovery Tool
Perform the following:
Download the QSPI boot firmware image matching your board from Table 1.
Under Recovery Image, Browse to the QSPI Boot firmware downloaded earlier and select it.
Then select Image A and click Upload.
Once the upload completes, you will see a success message confirming the task's completion. You have successfully updated your QSPI Boot firmware. Please proceed to Evaluation Board - System Controller (SC) section.
5.3.1.2 Revised Image Recovery Tool
The Revised Image Recovery Tool connected to your workstation does not boot with a static IP by default. It supports DHCP, so if your workstation runs a DHCP server, the tool acquires an IP automatically. Otherwise, configure a static IP by running these commands in the SC UART terminal:
ip addr flush dev eth0
ip addr add 192.168.0.111/24 dev eth0
ip link set dev eth0 up
ip route add default via 192.168.0.1This will configure the Image Recovery tool to use the static IP address 192.168.0.111 with a 255.255.255.0 netmask. Adjust your workstation's network settings for the Ethernet connection to access the board. Using your browser (Firefox recommended), navigate to http://192.168.0.111:8080 to open the Image Recovery Tool. Figure 7 shows the tool on a VEK385.
Perform the following:
Download the QSPI boot firmware image matching your board from Table 1.
Under Ethernet Recovery, Browse to the QSPI Boot firmware downloaded earlier and select it.
Then select Boot Image (BOOT.bin A/B image) and click Upload.
Once the upload completes, you will see a success message confirming the task's completion. You have successfully updated your QSPI Boot firmware.
5.4 Step 2: Update AMD EDF SC Linux Image
The system controller runs Linux and uses many Linux services. It updates the Linux image by writing new binaries to the eMMC. There are two methods to update the AMD EDF SC Linux image: RAUC-based update using a RAUC bundle (Evaluation Board - System Controller (SC)) or Image Recovery Tool update using a WIC image (Evaluation Board - System Controller (SC)). When available, update the Linux image using RAUC. Use Image Recovery Tool as a fallback.
5.4.1 Linux Image Update using RAUC (Preferred)
Most SC Update versions offer an easy way to upgrade your AMD EDF SC Linux Image using the preferred RAUC update mechanism. RAUC is a Linux update client for firmware updates. When available, RAUC provides a robust fail-safe A/B over-the-air upgrade. Using your browser, navigate to http://<BOARD_IP_ADDRESS> to open the Board Evaluation and Management Tool (BEAM). You can learn about BEAM in section Evaluation Board - System Controller (SC) . Figure 8 shows BEAM running on a VEK385.
You can get your BOARD_IP_ADDRESS using the ifconfig utility from the AMD EDF SC Linux terminal. If your board lacks an IP address, configure one using the system_config utility by running sudo system_config.sh from the AMD EDF SC Linux terminal. This utility lets you set a static or DHCP IP for your AMD EDF SC Linux.
Click on Test The Board, then Linux File System on the next page to open the Linux File System, as shown in Figure 9. If the Linux File System page is missing, skip this section and go to the Evaluation Board - System Controller (SC) section. Use the Image Recovery Tool to update your AMD EDF SC Linux Image.
To update your SC Linux to the latest supported AMD EDF SC Linux for your board, use the following instructions:
Download the RAUC Bundle for your board from Table 1.
From the Linux File System BEAM page, Browse to the downloaded RAUC Bundle and select it.
In the Update Bundle dropdown, select the uploaded RAUC Bundle and click Update. After the update completes, a success message confirms it.
Click Run On Next Boot, then click Reboot Device to boot the updated AMD EDF SC Linux.
Your AMD EDF SC Linux will reboot with the updated image. The update is complete.
5.4.2 Linux Image Update using Image Recovery Tool (Fallback)
If your Linux File System BEAM page is unavailable or your AMD EDF SC Linux fails to boot, update AMD EDF SC Linux using the Image Recovery Tool. Refer to section Evaluation Board - System Controller (SC) for instructions on launching, configuring, and accessing the Image Recovery Tool. Whether using the Legacy or Revised Image Recovery Tool, follow these steps:
Download the Linux image matching your board from Table 1. The Linux image is a compressed wic file (.wic.xz):
For SC Update 7.1, download the Linux Image
From SC Update 8.1 onward, the offline installer includes the AMD EDF SC Linux image (compressed wic) and board packages as a USB disk image. Download the Offline Installer (compressed IMG). Decompress the file, then burn the IMG to a USB disk using a tool like balenaEtcher - Flash OS images to SD cards & USB drives. After flashing, the USB disk contains the AMD EDF SC Linux image (compressed wic) and the board_packages folder.
From the Image Recovery Tool page,
For SC Update 7.1, decompress the wic image before use. Browse to the decompressed wic image and select it. Click Wic Image, then Upload
From SC Update 8.1 onward, use the compressed wic image as is. Do not decompress it. Browse to the compressed wic image and select it. Click Wic Image, then Upload
After upload, a success message confirms completion. You have updated your AMD EDF SC Linux Image.
Figures 10 and 11 show screen captures of the AMD EDF SC Linux Image update using the Legacy and Revised Image Recovery Tools.
Reboot your board. Your system should now boot
5.5 Step 3: Install Board Support Packages
All evaluation board running AMD EDF SC Linux use a command AMD EDF SC Linux image. The Linux image is augmented to support a particular board using board support packages. The last step of updating the system controller is to install the board support packages for a given board. The process of installing board support packages differs based on whether the board has access to the internet or not.
5.5.1 Board with Internet access (Online flow)
Using your browser, navigate to http://<BOARD_IP_ADDRESS> to open the Board Evaluation and Management Tool (BEAM). After updating the AMD EDF SC Linux Image, your board will have no packages installed and will display a page like Figure 12.
Click on Install Board Support. This fetches the relevant packages from AMD servers and installs them. A success message indicates completion. AMD EDF SC Linux will reboot afterward. When AMD EDF SC Linux finishes booting, the fan should quiet down, signaling a successful board support package installation.
5.5.2 Board without Internet access (Offline flow)
If your board cannot connect to the Internet, download and install the board support packages locally. Follow these steps:
Download and extract the board support packages
For SC Update 7.1, download the Update 7.1 Board Packages Offline Install package and decompress it using tar ("tar xvf PACKAGE_NAME.tar.gz"). Move the board_packages folder to a USB disk.
From SC Update 8.1 onward, the offline installer includes the AMD EDF SC Linux image (compressed wic) and board packages as a USB disk image. Download the Offline Installer (compressed IMG). Decompress the file, then burn the IMG to a USB disk using a tool like balenaEtcher - Flash OS images to SD cards & USB drives. After flashing, the USB disk contains the AMD EDF SC Linux image (compressed wic) and the board_packages folder.
Connect the USB disk to the SC USB connector on the board.
On your AMD EDF SC Linux terminal, mount the USB device to the /mnt folder using this command (assuming your USB device is /dev/sda1): sudo mount /dev/sda1 /mnt
On your AMD EDF SC Linux terminal, go to the board_packages folder (cd /mnt/board_packages) and install the board packages by running sudo ./setup_board.sh
Your board packages will install, and a success message will appear. AMD EDF SC Linux will then reboot automatically. When it finishes booting, the fan should quiet down, indicating successful installation.
5.5.3 Additional Steps for OSPI Utility for Board without Internet access (Offline flow)
One System Controller feature is programming the DUT OSPI device using the OSPI utility. When launched for the first time, the OSPI utility downloads the latest versions of key packages from GitHub. If the board lacks internet access or the servers are blocked, follow these steps to manually install the packages:
On an internet-connected workstation, download this package: https://github.com/Xilinx/embpf-bootfw-update-tool/releases/download/v5.0/bin.zip
Move bin.zip to the System Controller on the board under /usr/share/embpf-bootfw-update-tool.
Install the package by unzipping it: sudo unzip bin.zip.
These steps install the required packages for the OSPI utility. Programming OSPI should now work as expected. For OSPI utility access, see section Evaluation Board - System Controller (SC)
5.6 SD Card Image Update (VCK190/VMK180)
Some evaluation boards, like VCK190 and VMK180, use a microSD card interface instead of eMMC to store the Root File System and assets for secondary boot steps and loading the System Controller.
To set up the microSD card, download the SD Card Image for the VCK190/VMK180 from Table 1. Write it to a microSD using an image flashing tool like Balena Etcher on your workstation. After flashing, disconnect the microSD card from your workstation and insert it into the System Controller microSD slot at J206 on the Starter Kit. Do not insert it into the DUT slot at J302.
6. Getting To Know Your System Controller
6.1 Board Evaluation and Management (BEAM) Tool
6.1.1 Overview
BEAM is a web-based GUI application for monitoring and modifying evaluation board parameters. It connects to a web server on the system controller and offers a home screen with navigation to board-specific test interfaces and related product pages.
BEAM monitors and modifies board settings such as clock, rail voltage, power, system controller IO bank, and EEPROM. It lets users run a board interface test (BIT) suite tailored to the board to assess its interfaces and features. BEAM also supports loading a PDI on the DUT, programming the DUT OSPI, and controlling the DUT boot mode. Additionally, it provides links to Wiki information and relevant resources.
This section reviews the BEAM pages and their capabilities.
6.1.2 Board and requirements
Evaluation board kit
Ethernet cable
Workstation with Ethernet interface and web browser (e.g., Firefox or Chrome)
USB-C cable (or a Micro USB for VPK120)
Power adapter
6.1.3 Board setup and connections
Connect the workstation to the SC UART and SC dedicated Ethernet interface to access the system controller. The VEK385 board image below is a reference; other boards with the common SC implementation boot and operate similarly. See the Board Component Location section in the evaluation board User Guide for specific connection points.
Follow these steps to connect your workstation to the board as shown above:
Set up a Tera Term (or similar) session between the workstation COM port and the evaluation board's serial port. When connecting a cable to the debug port, use the highest of the three assigned COM ports for your terminal program. Configure the port to 115200,8,n,1. This session serves as the system controller UART terminal in this document. Refer to the Tera Term Terminal Emulator Installation Guide (UG1036) for download and installation instructions.
Connect the system controller LAN port to the same DHCP-enabled LAN as the workstation. If the network lacks a DHCP server, configure the system controller with a static IP using the utility system_config.sh. Run this command in the system controller UART session from the previous step:
sudo system_config.shIf you set a static IP address, configure your workstation with a matching static IP. Refer to your operating system documentation for instructions. Restart the board once both static IPs are set by executing this command in the SC UART terminal:
sudo reboot
6.1.4 Launching the BEAM GUI
After the AMD EDF SC Linux finishes booting, the BEAM Tool web address appears on the UART, as shown below. Open a web browser and go to that address.
6.1.5 GUI Pages
The BEAM tool GUI connects to the SC and evaluation board platform, launching the board-specific BEAM version automatically. The image below shows a VEK385 BEAM instance; your board-specific GUIs may vary slightly by BEAM version.
Different BEAM versions may vary in features and menu options.
6.1.5.1 Home
The BEAM Home page is the default landing page when a user navigates to the BEAM IP address in their browser. From the home page, users can access different areas of the tool, including Home, About, Help, Test The Board, PM Dashboard, and Versal Device Control. The home screen also features pictures and links to the DUT product page. Click the “Home” button at the top-right to return to this screen from any other area or tab. This section provides a quick overview of the tool's areas and their main functions.
6.1.5.2 About
The above About page is displayed when clicked on “About” on the right top in any screen. This page contains information about BEAM Tool.
6.1.5.3 Help
The Help page appears when you click “Help” at the top right of any screen. It provides information on various screens, applications, and known issues and bugs.
6.1.5.4 Get Logs
The Get Logs button on the Home page packages logs from the board’s system controller and downloads them to your workstation.
6.1.5.5 Export CSV
The Export CSV button on the Home page exports power, current, and voltage rail histories into a CSV file. The user selects a period to capture and triggers the operation with the Download button. At the end of the period, a CSV file downloads to the user’s workstation.
6.1.5.6 Test The Board
The “Test The Board” page shows a picture of the board and board details. It contains navigation links to Board Settings and Board Interface Test, and Linux File System pages. The junction temperature of the DUT is also reported on this page.
6.1.5.7 Test The Board → Board Settings
The “Board Settings” page lets you monitor and modify board settings such as clocks, voltage, power, SC IO banks, and EEPROM data. Click elements on the left to switch tabs.
BEAM lets users upload custom configuration clock files created by the clock chip vendor utility. Users interested in this option should consult the vendor utility documentation for details on generating the required configuration.
Under each tab, click “Get” to retrieve information or “Get All” to read all tab data. A green tick in the status column means success; a red cross means failure. Some tabs have sub-tabs to get, set, or reset system values. Click a sub-tab to access controls. Use “Get” to fetch values, “Set” to apply them, and “Restore” to reset defaults.
Hover over the “cross” or “tick” icon in the “Status” column for details on the Get/Set operation.
6.1.5.8 Test The Board → Board Interface Test
The Board Interface Test (BIT) page lists the interface tests for the board. Click “Run” to start a test. The progress bar shows the test status. Click “Run All” to run all selected tests.
Tests are divided into automated and interactive. Click the info icon next to each test for its description. Interactive tests require user input. Clicking one opens a pop-up with instructions to proceed and verify results. Click “Pass” if the test succeeds; otherwise, click “Fail.” The progress bar is yellow during testing, red if the test fails, and green if it passes.
Hover over the “cross” or “tick” icon beside the “Run” button to view the test result status message.
6.1.5.9 Test The Board → Linux File System
The Linux File System page was discussed in section Evaluation Board - System Controller (SC)
6.1.5.10 PM Dashboard
The PM Dashboard page displays current, voltage, and power readings for the board's power domains in a table. You can switch to a graphical view using the “Switch to Graph”.
6.1.5.11 Versal Device Control
The Versal Device Control Page lets users interact directly with the DUT by uploading a PDI, updating the OSPI device content connected to the DUT, setting the DUT boot mode, and opening a UART connection to the various PS and PL UART interfaces on the DUT.
6.1.5.12 Set Mac Address
The Set Mac Address page lets the user update the EEPROM-stored MAC addresses for the DUT.
6.2 FAN Control
This section details the Evaluation Board System Controller's active fan control.
6.2.1 Physical Board Jumpers
The evaluation boards include physical jumpers that let users select whether the fan PWM control and tachometer signals connect to the SC or the DUT. The SC fan control works only if users configure the jumpers correctly. Refer to the evaluation board user guide for proper jumper settings.
6.2.2 Default Behavior
The SC and evaluation board start automatically at SC boot if the user meets these requirements:
User sets the physical jumpers correctly
User loads the corresponding DUT BSP default image and sets the DUT boot mode correctly
SC 2022.2 or later System Controller Linux image is loaded to SC eMMC
6.2.3 DUT Dependency
The DUT in the evaluation boards on this page exposes its temperature via the SysMon remote monitor I2C interface. To activate the DUT SysMon remote monitor, a device configuration file or "PDI" must be loaded to the DUT, enabling and configuring the I2C interface as expected by SC. Without a PDI or with a PDI that does not enable the SysMon external I2C interface, the SC cannot remotely read the DUT temperature. Remote temperature read scenarios are shown in the figure below.
If the SC fails to read the remote temperature, it will default to full fan speed. When the remote temperature is unreadable, the System Controller application no longer displays the DUT temperature in the BEAM GUI.
6.2.4 BEAM GUI Behavior
The BEAM GUI shows the DUT temperature when available from the SysMon remote temperature interface. If the DUT remote temperature is unavailable, the BEAM does not display a temperature. Since the BEAM serves as a common GUI for both SC fan-controlled platforms described on this page and legacy boards (VCK190/VMK180), it has three display states:
Supported board with correctly configured PDI loaded to DUT. Temperature appears in the upper left corner.
Supported board lacks a properly configured PDI loaded to DUT. Temperature is not displayed and shows as "-".
Unsupported board. Temperature shows as "NA".
6.2.5 Vivado Board Files & DUT BSPs
The evaluation boards on this page have Vivado board files and DUT (Petalinux/EDF) BSP configurations that include the DUT SysMon remote I2C interface, aligned with SC fan control application requirements. For users customizing Vivado and PDI file generation, the following Vivado CIPS configurations must be met for SC fan control to work:
Enable SysMon I2C external interface
Set SysMon I2C external address to 0x18
Next, set the I2C bus to the IO pins “PCM_MIO 39..40”
7. Debug Tips
7.1 General Debug Tips
This section outlines common debug tips and limitations of the System Controller and BEAM functionality.
If an error occurs or information is incomplete when reading SFP data, check your SFP part datasheet to confirm it supports the full SNIA management interface data. Some management functions are missing in SFP loopback modules.
If the SC gets a new IP address at every boot, it uses a randomized MAC address. Upgrade your QSPI image. See section Evaluation Board - System Controller (SC)
7.2 Fan Control Debug Tips
Failure modes and debug tips:
Failure Description | Failure Remedy |
|---|---|
SC BEAM displays DUT temperature but does not regulate fan speed. |
|
SC BEAM does not display DUT temperature ("-") and does not control the SC fan. |
|
SC console shows the following message: /usr/sbin/fancontrol: line 543: read: read error: 0: Input/output error Error reading temperature from ///sys/class/hwmon/hwmon1/temp1_input Aborting and restoring fans... Verify fans returned to full speed |
|
SC BEAM shows "NA" | This board does not support SC-based remote temperature reading or active fan control. |
SC-based fan control stops working when loading a new PDI, though BEAM GUI still shows temperature readings. | Restart the fancontrol process on the SC console with this command: sudo systemctl restart fancontrol |
8. Source Code
The System Controller code is all provided as open-source code on GitHub. The table below lists the various repositories:
Application | GitHub Link |
|---|---|
SCWeb - BEAM WebUI | |
sc_app - System Controller backend and cli applications | |
RAFT - Power management backend library and API | |
Power Management Dashboard | |
DFX Manager - Program PL on boot and load dynamic device tree overlays | |
LabTools - XVC, hw_manager, cs_server | |
ChipScopy | |
U-Boot | |
Linux Kernel | |
Firmware | |
Yocto Manifests |
|
Yocto meta-system-controller | |
versal-sc-firmware | |
embpf-bootfw-update-tool | |
image-recovery-linux |
