Software Hardware Exchange Loop (SHEL)
Search documents
Hardware Handoff Using Software Hardware Exchange Loop (SHEL) Flow
AMD· 2025-11-11 20:17
Overview of AMD Embedded Development Framework - AMD Embedded Development Framework (EDF) explores the Software Hardware Exchange Loop (SHEL) flow [1] - The tutorial demonstrates generating an XSA from AMD Vivado design suite, building a system device tree, and creating a custom Linux image using the Yocto Project [1] SHEL and Hardware-Software Integration - SHEL streamlines hardware–software integration across AMD Vivado, Vitis tools, and open-source tools [1] - SHEL enables efficient handoff and deployment on AMD Versal™ VEK385 platforms [1] Resources and Contact - More information is available at https://www.amd.com/en/products/software/adaptive-socs-and-fpgas/embedded-software/embedded-development-framework.html [1] - Subscribe to AMD at https://bit.ly/Subscribe_to_AMD [1] - Join the AMD Red Team Discord Server: https://discord.gg/amd-gaming [1]
Hardware Handoff Using Software Hardware Exchange Loop (SHEL) Flow
AMD· 2025-11-03 17:01
SHEL Flow Overview - AMD's Software Hardware Exchange Loop (SHEL) flow facilitates hardware and software configuration data exchange among open-source and proprietary tools [2][3] - SHEL decouples hardware and software, ensuring synchronization across components like hardware, firmware, software, and operating systems [4] - SHEL translates AMD proprietary XSA into open-source hardware descriptions, allowing integration into existing processes [5] - SHEL enables industry standards like Yocto Project, Xen, OpenAMP, and Zephyr [6] Technical Implementation - The process starts with an XSA file from an AMD Vivado project, extracting the system device tree using SDTGen [6] - SDTGen translates proprietary output from AMD Vivado Design Suite into a stable, open-source format [7] - Gen-machine-conf processes device tree data into Linux build and configuration information within a Yocto Project environment [8] - A custom Linux OS is created based on the system device tree, using a prebuilt template BSP YAML file for VEK385 [21] - Bitbake recipes are run inside the Yocto Project to generate final products, including a boot bin and EDF Linux SD card image [28] Customization and Integration - Users can integrate AMD tools into their existing processes by using open-source hardware descriptions [5] - Customizations can be made to the OS by modifying the local conf file [25] - The gen-machine-conf command with a template parameter of the edited YAML file generates custom Linux build and configuration information [24]