3. Foundational Components

• 3.1. U-Boot
  • 3.1.1. Build Guide
    • 3.1.1.1. Setup
      • 3.1.1.1.1. Install host dependencies
      • 3.1.1.1.2. Getting the Source Code
      • 3.1.1.1.3. Setup Cross Compile Environment
    • 3.1.1.2. Build
      • 3.1.1.2.1. Build U-Boot
    • 3.1.1.3. Target Images
      • 3.1.1.3.1. Images
      • 3.1.1.3.2. Image Formats
    • 3.1.1.4. Boot Flow
    • 3.1.1.5. Environment
      • 3.1.1.5.1. U-Boot Environment
    • 3.1.1.6. RAM and Device Trees
      • 3.1.1.6.1. Available RAM for image download
      • 3.1.1.6.2. Device Trees
      • 3.1.1.6.3. SRAM memory Layout during initial bootloader stage
  • 3.1.2. User’s Guide
    • 3.1.2.1. USB Device Firmware Upgrade (DFU)
      • 3.1.2.1.1. USB Peripheral boot mode (SPL-DFU support)
    • 3.1.2.2. Booting over Ethernet (Ethernet RGMII)
      • 3.1.2.2.1. Booting U-Boot from the network
    • 3.1.2.3. SD, eMMC and USB
      • 3.1.2.3.1. Overview
      • 3.1.2.3.2. MMC
        • 3.1.2.3.2.1. Listing MMC devices
        • 3.1.2.3.2.2. MMC HW partitions
        • 3.1.2.3.2.3. Selecting MMC device and partitions
        • 3.1.2.3.2.4. View MMC partition contents
        • 3.1.2.3.2.5. MMC supported boot modes
        • 3.1.2.3.2.6. Flashing an MMC device using USB-DFU
        • 3.1.2.3.2.7. Flashing an SD card from a host PC
      • 3.1.2.3.3. USB
        • 3.1.2.3.3.1. Configuring USB in Host Mode
        • 3.1.2.3.3.2. Flash and boot SPL from USB storage
        • 3.1.2.3.3.3. Boot Linux from USB storage
        • 3.1.2.3.3.4. MMC support in u-boot
        • 3.1.2.3.3.5. Steps for working around SD card issues in u-boot
    • 3.1.2.4. USB Mass Storage
      • 3.1.2.4.1. Configuration requirements
      • 3.1.2.4.2. Usage
    • 3.1.2.5. OSPI/QSPI NOR/NAND
    • 3.1.2.6. UART
      • 3.1.2.6.1. Booting U-Boot from the console UART
    • 3.1.2.7. DDR
      • 3.1.2.7.1. Overview
      • 3.1.2.7.2. DDR Initialization
      • 3.1.2.7.3. DDR Temperature Monitoring
      • 3.1.2.7.4. Error Correction Code (ECC)
        • 3.1.2.7.4.1. ECC Handling
    • 3.1.2.8. RemoteProc
      • 3.1.2.8.1. Initialization
      • 3.1.2.8.2. Loading
      • 3.1.2.8.3. Starting
      • 3.1.2.8.4. Stop
      • 3.1.2.8.5. Lockstep and Split mode
      • 3.1.2.8.6. HS Devices
    • 3.1.2.9. U-Boot splash screen
      • 3.1.2.9.1. Features supported
        • 3.1.2.9.1.1. Enable the splash screen on ti-u-boot
        • 3.1.2.9.1.2. Display custom logo as splash screen
        • 3.1.2.9.1.3. Enable splash screen on upstream U-Boot
        • 3.1.2.9.1.4. Enable splash screen on a custom board based on AM62Px SoC
        • 3.1.2.9.1.5. Display image using U-Boot command line
        • 3.1.2.9.1.6. Run splash screen using OSPI NOR
        • 3.1.2.9.1.7. Display RLE compressed image
        • 3.1.2.9.1.8. Flicker free display across boot stages and Linux kernel
        • 3.1.2.9.1.9. Flicker free and persistent display until display server
        • 3.1.2.9.1.10. Panel-specific config fragments
        • 3.1.2.9.1.11. Build U-Boot with splash screen enabled
        • 3.1.2.9.1.12. Disable splash screen
    • 3.1.2.10. U-Boot Falcon Mode
      • 3.1.2.10.1. Extra Configuration
        • 3.1.2.10.1.1. OSPI boot:
        • 3.1.2.10.1.2. eMMC Boot:
      • 3.1.2.10.2. Boot time comparisons:
  • 3.1.3. Troubleshooting
    • 3.1.3.1. Debugging U-Boot and SPL
      • 3.1.3.1.1. Debug Example
        • 3.1.3.1.1.1. Setup
        • 3.1.3.1.1.2. Using OpenOCD & GDB
        • 3.1.3.1.1.3. Using CCS
• 3.2. Kernel
  • 3.2.1. Users Guide
    • 3.2.1.1. Overview
    • 3.2.1.2. Getting the Kernel Source Code
    • 3.2.1.3. Preparing to Build
      • 3.2.1.3.1. Setup Cross Compile Environment
      • 3.2.1.3.2. Cleaning the Kernel Sources
    • 3.2.1.4. Configuring the Kernel
      • 3.2.1.4.1. Using Default Configurations
      • 3.2.1.4.2. Customizing the Configuration
    • 3.2.1.5. Compiling the Sources
      • 3.2.1.5.1. Compiling the Kernel
      • 3.2.1.5.2. Compiling the Device Tree Binaries
      • 3.2.1.5.3. Compiling the Kernel Modules
    • 3.2.1.6. FIT Image
    • 3.2.1.7. Installing the Kernel
      • 3.2.1.7.1. Installing the Kernel Image and Device Tree Binaries
      • 3.2.1.7.2. Installing the Kernel Modules
  • 3.2.2. Kernel Drivers
    • 3.2.2.1. Audio
      • 3.2.2.1.1. Introduction
      • 3.2.2.1.2. Software Architecture
      • 3.2.2.1.3. McASP Configuration
        • 3.2.2.1.3.1. Device Tree Properties
        • 3.2.2.1.3.2. Capabilities Overview
        • 3.2.2.1.3.3. Configuration Scenarios
        • 3.2.2.1.3.4. Configuration Guidelines
        • 3.2.2.1.3.5. Codec Integration
        • 3.2.2.1.3.6. Runtime Behavior
      • 3.2.2.1.4. Generic commands and instructions
      • 3.2.2.1.5. Board-specific instructions
      • 3.2.2.1.6. Potential issues
      • 3.2.2.1.7. Additional Information
    • 3.2.2.2. CSI2RX
      • 3.2.2.2.1. Introduction
      • 3.2.2.2.2. Hardware Architecture
      • 3.2.2.2.3. Driver Architecture
        • 3.2.2.2.3.1. The Media Controller API
        • 3.2.2.2.3.2. Utilities to interact with the driver
        • 3.2.2.2.3.3. Building the driver
      • 3.2.2.2.4. Creating device tree nodes for sensor
      • 3.2.2.2.5. Enabling camera sensors
        • 3.2.2.2.5.1. Applying sensor overlays
        • 3.2.2.2.5.2. Capturing raw frames
        • 3.2.2.2.5.3. Capture to display
        • 3.2.2.2.5.4. Suspend to RAM
        • 3.2.2.2.5.5. CSI2RX testing details
    • 3.2.2.3. Crypto
      • 3.2.2.3.1. Introduction
      • 3.2.2.3.2. Crypto Implementation Options
        • 3.2.2.3.2.1. Choosing the Right Implementation
      • 3.2.2.3.3. Building the Drivers
      • 3.2.2.3.4. Using Cryptographic Hardware Accelerators from OpenSSL
      • 3.2.2.3.5. Using the TRNG Hardware Accelerator
      • 3.2.2.3.6. Hardware Accelerator testing
        • 3.2.2.3.6.1. Testing using the tcrypt module
        • 3.2.2.3.6.2. IPSec Testing
    • 3.2.2.4. MCAN
    • 3.2.2.5. MCRC64
    • 3.2.2.6. K3 DDR
      • 3.2.2.6.1. Introduction
      • 3.2.2.6.2. Building and Enabling the Driver
      • 3.2.2.6.3. Using the DDR Temperature Monitoring
    • 3.2.2.7. DSS
      • 3.2.2.7.1. Introduction
      • 3.2.2.7.2. Supported Devices
      • 3.2.2.7.3. Hardware Architecture
        • 3.2.2.7.3.1. Display Controller (DISPC)
        • 3.2.2.7.3.2. SoC Hardware Description
        • 3.2.2.7.3.3. Supported Features
      • 3.2.2.7.4. Driver Architecture
        • 3.2.2.7.4.1. Driver Features
      • 3.2.2.7.5. Driver Configuration
        • 3.2.2.7.5.1. Kernel Configuration Options
        • 3.2.2.7.5.2. Device Tree Node
      • 3.2.2.7.6. Driver Usage
        • 3.2.2.7.6.1. Loading tidss
        • 3.2.2.7.6.2. Using tidss
        • 3.2.2.7.6.3. Testing tidss
        • 3.2.2.7.6.4. tidss properties
        • 3.2.2.7.6.5. Buffers
        • 3.2.2.7.6.6. fbdev emulation (/dev/fb0)
    • 3.2.2.8. Enhanced capture (eCAP)
      • 3.2.2.8.1. Introduction
      • 3.2.2.8.2. Hardware overview
      • 3.2.2.8.3. Device instances
      • 3.2.2.8.4. Linux drivers
      • 3.2.2.8.5. Device tree node
      • 3.2.2.8.6. Pin configuration
      • 3.2.2.8.7. APWM mode
      • 3.2.2.8.8. Capture mode
      • 3.2.2.8.9. Troubleshooting eCAP
    • 3.2.2.9. EQEP
    • 3.2.2.10. GPIO
    • 3.2.2.11. I2C
    • 3.2.2.12. CPSW Ethernet
      • 3.2.2.12.1. Introduction
      • 3.2.2.12.2. Instances of the CPSW Subsystem
      • 3.2.2.12.3. TSN Documentation and Testing
      • 3.2.2.12.4. XDP and zero copy
    • 3.2.2.13. NETCONF/YANG
      • 3.2.2.13.1. Introduction
      • 3.2.2.13.2. Installation on Remote Machine
      • 3.2.2.13.3. Generic Execution
      • 3.2.2.13.4. Installing new YANG models
        • 3.2.2.13.4.1. Setup
    • 3.2.2.14. PWM
    • 3.2.2.15. OSPI/QSPI NOR/NAND
    • 3.2.2.16. SPI
    • 3.2.2.17. NAND
    • 3.2.2.18. MMCSD
      • 3.2.2.18.1. Introduction
      • 3.2.2.18.2. References
      • 3.2.2.18.3. Features
      • 3.2.2.18.4. Supported ultra high speed (UHS) modes
      • 3.2.2.18.5. Driver configuration
      • 3.2.2.18.6. MMC support in Linux
      • 3.2.2.18.7. Steps for working around SD card issues in Linux
      • 3.2.2.18.8. Listing MMC devices from Linux
      • 3.2.2.18.9. Create partitions in eMMC UDA
        • 3.2.2.18.9.1. Create “boot” partition
        • 3.2.2.18.9.2. Create “root” partition
      • 3.2.2.18.10. Formatting eMMC partitions from Linux
        • 3.2.2.18.10.1. Format to vfat
        • 3.2.2.18.10.2. Format to ext4
      • 3.2.2.18.11. Flash eMMC for MMCSD boot
        • 3.2.2.18.11.1. Flash to eMMC “boot” partition
        • 3.2.2.18.11.2. Flash to eMMC “root” partition
    • 3.2.2.19. DM TIMER
      • 3.2.2.19.1. Driver Sources
      • 3.2.2.19.2. Kernel Configuration
      • 3.2.2.19.3. Driver Usage
      • 3.2.2.19.4. Examples
    • 3.2.2.20. UART
      • 3.2.2.20.1. Introduction
      • 3.2.2.20.2. Driver Features
      • 3.2.2.20.3. Basic External loopback testing
    • 3.2.2.21. UBIFS
    • 3.2.2.22. USB
      • 3.2.2.22.1. Introduction
      • 3.2.2.22.2. TI SoC Integration
      • 3.2.2.22.3. Starter Kit (SK)
    • 3.2.2.23. Voltage & Thermal Management (VTM)
      • 3.2.2.23.1. Introduction
      • 3.2.2.23.2. Driver Features
      • 3.2.2.23.3. Finding More Information
    • 3.2.2.24. Watchdog
      • 3.2.2.24.1. Driver Configuration
        • 3.2.2.24.1.1. How to change timeout as kernel module parameter
        • 3.2.2.24.1.2. How to change timeout using DT property
      • 3.2.2.24.2. Kernel Configuration
      • 3.2.2.24.3. Driver Usage
  • 3.2.3. LTP-DDT Validation
  • 3.2.4. FAQs
• 3.3. Power Management
  • 3.3.1. Power Management Overview
  • 3.3.2. DFS
  • 3.3.3. CPUIdle
  • 3.3.4. Runtime PM
  • 3.3.5. Low Power Modes
    • 3.3.5.1. Overview
    • 3.3.5.2. Partial I/O
    • 3.3.5.3. I/O Only Plus DDR
    • 3.3.5.4. DeepSleep
    • 3.3.5.5. MCU Only
    • 3.3.5.6. Limitations
      • 3.3.5.6.1. Compatibility
  • 3.3.6. Wakeup Sources
    • 3.3.6.1. Real-Time Clock (RTC)
    • 3.3.6.2. MCU/WKUP GPIO
    • 3.3.6.3. Main I/O Daisy Chain
      • 3.3.6.3.1. Main UART
      • 3.3.6.3.2. Main GPIO
    • 3.3.6.4. WKUP I/O Daisy Chain
      • 3.3.6.4.1. WKUP UART I/O Daisy Chain
    • 3.3.6.5. WKUP UART
    • 3.3.6.6. USB Wakeup methods
      • 3.3.6.6.1. Host Mode Wakeup Events
        • 3.3.6.6.1.1. Wakeup via a device connect event
        • 3.3.6.6.1.2. Wakeup via a device disconnect event
        • 3.3.6.6.1.3. Via Remote wakeup event
      • 3.3.6.6.2. Device Mode Wakeup Events
        • 3.3.6.6.2.1. Wakeup via connect event
    • 3.3.6.7. MCU IPC based Wakeup
    • 3.3.6.8. CAN I/O Daisy Chain
    • 3.3.6.9. RTC I/O
      • 3.3.6.9.1. RTC I/O Pins 0 and 1
      • 3.3.6.9.2. RTC I/O Pin 2
    • 3.3.6.10. Confirming the Wakeup event type
  • 3.3.7. S/W Architecture of System Suspend
    • 3.3.7.1. Overview
    • 3.3.7.2. System diagram and components
      • 3.3.7.2.1. DeepSleep Entry
      • 3.3.7.2.2. DeepSleep Exit
    • 3.3.7.3. LPM constraints framework
      • 3.3.7.3.1. Types of Constraints
      • 3.3.7.3.2. How to set constraints
        • 3.3.7.3.2.1. Device Constraint
        • 3.3.7.3.2.2. Resume Latency Constraint
      • 3.3.7.3.3. Constraints and mode selection explained
    • 3.3.7.4. Learning Resources
  • 3.3.8. Debug Information
    • 3.3.8.1. Low Power Modes
      • 3.3.8.1.1. Decoding set constraint debug messages
  • 3.3.9. Upstream Status
    • 3.3.9.1. Pending Upstream Series
    • 3.3.9.2. Workarounds
• 3.4. Security
  • 3.4.1. Device Security
    • 3.4.1.1. Security Overview
    • 3.4.1.2. Security Domains
    • 3.4.1.3. Security Features at a Glance
  • 3.4.2. GP to HS-FS Migration Guide
    • 3.4.2.1. Overview
    • 3.4.2.2. Device types
    • 3.4.2.3. Processor SDK
    • 3.4.2.4. K3-image-gen
    • 3.4.2.5. U-Boot
    • 3.4.2.6. Linux Kernel
  • 3.4.3. Secure Boot
    • 3.4.3.1. Introduction
    • 3.4.3.2. Secure Boot Flow
    • 3.4.3.3. HS Boot Flow Tools
  • 3.4.4. SELinux - User Guide
    • 3.4.4.1. Introduction
    • 3.4.4.2. Filesystem Setup
      • 3.4.4.2.1. Yocto
      • 3.4.4.2.2. Debian
    • 3.4.4.3. Permissive mode Setup
    • 3.4.4.4. Enforcing mode Setup
    • 3.4.4.5. Integrating into Yocto for production
  • 3.4.5. Authenticated Boot User Guide
    • 3.4.5.1. Introduction
    • 3.4.5.2. Learning
      • 3.4.5.2.1. Root of Trust (RoT)
      • 3.4.5.2.2. Chain of Trust (CoT)
      • 3.4.5.2.3. Device Mapper
        • 3.4.5.2.3.1. dm-verity
        • 3.4.5.2.3.2. dm-crypt
    • 3.4.5.3. Setup
    • 3.4.5.4. Next steps
    • 3.4.5.5. See Also
  • 3.4.6. Memory Firewalls
    • 3.4.6.1. Overview
    • 3.4.6.2. What Happens During a Firewall Violation
    • 3.4.6.3. Triggering a Firewall Exception
    • 3.4.6.4. Enabling TIFS Logs
      • 3.4.6.4.1. Modify U-Boot Configuration
      • 3.4.6.4.2. Build and Deploy U-Boot
    • 3.4.6.5. Accessing TIFS Logs
    • 3.4.6.6. Interpreting TIFS Logs
  • 3.4.7. File System Encryption with fTPM
    • 3.4.7.1. Introduction
    • 3.4.7.2. Key features
    • 3.4.7.3. Concepts
      • 3.4.7.3.1. Root Filesystem Encryption
      • 3.4.7.3.2. Firmware TPM (fTPM)
      • 3.4.7.3.3. eMMC RPMB
    • 3.4.7.4. Implementation Details
      • 3.4.7.4.1. System Architecture
      • 3.4.7.4.2. Boot Process Flow
      • 3.4.7.4.3. Key Management Flow
      • 3.4.7.4.4. Encryption Process
    • 3.4.7.5. Setup
    • 3.4.7.6. dm-crypt performance
    • 3.4.7.7. Security Considerations
      • 3.4.7.7.1. Reference Implementation
      • 3.4.7.7.2. Further Enhancements
  • 3.4.8. Post-quantum cryptography
    • 3.4.8.1. Introduction
    • 3.4.8.2. Verifying post-quantum support
    • 3.4.8.3. Supported algorithms
      • 3.4.8.3.1. Key encapsulation
      • 3.4.8.3.2. Digital signatures
      • 3.4.8.3.3. Hash-based signatures
    • 3.4.8.4. Usage examples
      • 3.4.8.4.1. Generating keys and signing
      • 3.4.8.4.2. Hash-based key signing
      • 3.4.8.4.3. Self-signed certificate
    • 3.4.8.5. Testing the key exchange
      • 3.4.8.5.1. Generating a certificate
      • 3.4.8.5.2. Starting the server
      • 3.4.8.5.3. Connecting the client
      • 3.4.8.5.4. Handshake walkthrough
    • 3.4.8.6. Notes
    • 3.4.8.7. See also
• 3.5. Filesystem
• 3.6. Tools
  • 3.6.1. Development Tools
    • 3.6.1.1. Processor SDK Linux Top-Level Makefile
    • 3.6.1.2. Processor SDK Linux GCC Toolchain
    • 3.6.1.3. Creating SD Cards
    • 3.6.1.4. Processor SDK Linux Setup Script
  • 3.6.2. Pin Mux Tools
  • 3.6.3. Flash via Fastboot
    • 3.6.3.1. Installing Snagfactory
    • 3.6.3.2. Building bootloader binaries for Recovery
    • 3.6.3.3. Connections
      • 3.6.3.3.1. How to use Snagfactory
  • 3.6.4. Flash via Ethernet
    • 3.6.4.1. Get Tool
      • 3.6.4.1.1. SDK installer
      • 3.6.4.1.2. Clone repository
    • 3.6.4.2. Important files
    • 3.6.4.3. Requirements on host PC
    • 3.6.4.4. Building bootloader binaries for flashing and Ethernet Boot
    • 3.6.4.5. Getting ready to flash
    • 3.6.4.6. Environment variable text file for flashing
  • 3.6.5. Flash via UART
  • 3.6.6. RPi 40-pin header programming
    • 3.6.6.1. 40-pin header default configuration
    • 3.6.6.2. Repositories
    • 3.6.6.3. Additional References
• 3.7. IPC for AM62Px
  • 3.7.1. Software Dependencies to Get Started
  • 3.7.2. Typical Boot Flow on AM62Px for ARM Linux users
  • 3.7.3. Getting Started with IPC Linux Examples
  • 3.7.4. Booting Remote Cores from Linux console/User space
  • 3.7.5. DMA memory Carveouts
  • 3.7.6. Changing the Memory Map
  • 3.7.7. RPMsg Char Driver
  • 3.7.8. ti-rpmsg-char library
  • 3.7.9. RPMsg examples:
• 3.8. Graphics and Display
  • 3.8.1. Introduction
    • 3.8.1.1. General Features
    • 3.8.1.2. Software architecture
    • 3.8.1.3. Graphics demos
  • 3.8.2. Rogue debug info
  • 3.8.3. Rogue power management info
    • 3.8.3.1. Active power management
    • 3.8.3.2. Suspend and resume
  • 3.8.4. Build guide
    • 3.8.4.1. Proprietary stack
      • 3.8.4.1.1. Proprietary kernel module
        • 3.8.4.1.1.1. Building the proprietary kernel module
      • 3.8.4.1.2. Proprietary user space components
        • 3.8.4.1.2.1. Installing the proprietary user space components
      • 3.8.4.1.3. Proprietary mesa components
        • 3.8.4.1.3.1. Building the proprietary mesa components
      • 3.8.4.1.4. Using the proprietary stack
    • 3.8.4.2. Open source stack
      • 3.8.4.2.1. Open source kernel module
      • 3.8.4.2.2. Open source firmware
      • 3.8.4.2.3. Open source mesa components
      • 3.8.4.2.4. Using the open source stack
  • 3.8.5. Display
    • 3.8.5.1. Finding the connector ID
    • 3.8.5.2. Finding the plane ID
    • 3.8.5.3. Using the connector ID and plane ID
  • 3.8.6. OpenGL ES
  • 3.8.7. Vulkan
  • 3.8.8. OpenCL
  • 3.8.9. Qt graphics framework
    • 3.8.9.1. Demos
    • 3.8.9.2. Qt platform abstraction
    • 3.8.9.3. Running Qt applications with the Weston In-Vehicle Infotainment shell
  • 3.8.10. GTK+ graphics framework
    • 3.8.10.1. Demos
  • 3.8.11. Weston
    • 3.8.11.1. Starting Weston with Emptty
    • 3.8.11.2. Starting Weston manually
    • 3.8.11.3. Stopping Weston
    • 3.8.11.4. Running Weston clients
    • 3.8.11.5. Running multimedia with Wayland sink
    • 3.8.11.6. Using in-vehicle infotainment shell feature
    • 3.8.11.7. Screenshots
  • 3.8.12. PowerVR tools
    • 3.8.12.1. PVRTune
    • 3.8.12.2. PVRCarbon
• 3.9. Multimedia Video Codec
  • 3.9.1. Introduction
  • 3.9.2. Software Architecture
    • 3.9.2.1. Software Stack of Accelerated Codec Encoding/Decoding
    • 3.9.2.2. Linux Kernel Drivers
    • 3.9.2.3. GStreamer Plugins for Multimedia
      • 3.9.2.3.1. V4L2 Video Encoder/Decoder
  • 3.9.3. Encoder and Decoder Capabilities
  • 3.9.4. GStreamer Pipelines
  • 3.9.5. FFmpeg Plugins for Multimedia
    • 3.9.5.1. ffmpeg
      • 3.9.5.1.1. Help Flags
      • 3.9.5.1.2. Stream Specific Flags
    • 3.9.5.2. ffplay
    • 3.9.5.3. ffprobe
    • 3.9.5.4. Example Commands
  • 3.9.6. MPV Plugins for Multimedia
    • 3.9.6.1. Useful Flags
    • 3.9.6.2. Example Commands
  • 3.9.7. Memory Requirement
  • 3.9.8. Performance metrics
  • 3.9.9. Calculation of Performance metrics using native driver API
  • 3.9.10. Calculation of Performance metrics using gstreamer
    • 3.9.10.1. Latency
    • 3.9.10.2. Performance
  • 3.9.11. DMA Buffer Import/Export
• 3.10. Hypervisor
  • 3.10.1. Jailhouse
    • 3.10.1.1. Overview
    • 3.10.1.2. Enabling hypervisor on AM62Px platform
    • 3.10.1.3. Building Jailhouse Image for AM62Px platform
      • 3.10.1.3.1. Building Jailhouse Image using Yocto
      • 3.10.1.3.2. Building Jailhouse using TI SDK Installer
    • 3.10.1.4. Generate SD Card Image for Jailhouse
    • 3.10.1.5. Booting the SD Card Image
    • 3.10.1.6. Pre-built components in Jailhouse Image
    • 3.10.1.7. Jailhouse Interface
    • 3.10.1.8. Running Jailhouse Demos on AM62Px
      • 3.10.1.8.1. Host Setup
      • 3.10.1.8.2. Running Linux Demo
      • 3.10.1.8.3. Run Crash Test To Detect Inmate Failure
      • 3.10.1.8.4. Adding custom demos or applications in Inmate Filesystem
      • 3.10.1.8.5. Running Shared Memory Demo
      • 3.10.1.8.6. Running Ethernet Demo
      • 3.10.1.8.7. Running Baremetal Demos
        • 3.10.1.8.7.1. Running UART Demo
        • 3.10.1.8.7.2. Running GIC Demo
    • 3.10.1.9. Memory Reservation
    • 3.10.1.10. Hardware Modules Reservation
    • 3.10.1.11. Root-cell configuration
    • 3.10.1.12. Performance
      • 3.10.1.12.1. Cache Benchmark
• 3.11. Virtualization
  • 3.11.1. Docker Linux Container Runtime
    • 3.11.1.1. Overview
    • 3.11.1.2. Exploring Docker In Processor SDK
      • 3.11.1.2.1. Booting the Docker Filesystem
      • 3.11.1.2.2. Configuring the Docker daemon
      • 3.11.1.2.3. Docker Hello World
    • 3.11.1.3. Docker References
• 3.12. Machine Learning
  • 3.12.1. TensorFlow Lite (LiteRT)
    • 3.12.1.1. Introduction
    • 3.12.1.2. Features
    • 3.12.1.3. Inference backends and delegates
      • 3.12.1.3.1. Built-in kernels / CPU Delegate
      • 3.12.1.3.2. XNNPACK Delegate
    • 3.12.1.4. Benchmark Tool for TFLite Model
      • 3.12.1.4.1. How to run benchmark using CPU delegate
      • 3.12.1.4.2. How to run benchmark using XNNPACK delegate
    • 3.12.1.5. Performance Numbers of Benchmark Tool
    • 3.12.1.6. Example Applications
  • 3.12.2. ONNX Runtime
    • 3.12.2.1. Introduction
    • 3.12.2.2. Supported version
    • 3.12.2.3. ONNX Runtime test applications
      • 3.12.2.3.1. Running benchmark_model
  • 3.12.3. Arm NN
    • 3.12.3.1. Introduction
    • 3.12.3.2. Supported versions
  • 3.12.4. Arm Compute Library
    • 3.12.4.1. Introduction
    • 3.12.4.2. Supported versions
    • 3.12.4.3. Arm Compute Library Testing
  • 3.12.5. NNStreamer
    • 3.12.5.1. Introduction
    • 3.12.5.2. Supported versions
    • 3.12.5.3. Testing NNStreamer
• 3.13. ARM Trusted Firmware-A
• 3.14. OP-TEE
  • 3.14.1. Getting the OP-TEE Source Code
  • 3.14.2. Setup Cross Compile Environment
  • 3.14.3. Building OP-TEE OS
    • 3.14.3.1. Building the OP-TEE image
    • 3.14.3.2. Building the OP-TEE image with debug parameters
    • 3.14.3.3. Building OP-TEE with Pseudo RNG drivers
    • 3.14.3.4. OP-TEE Secure Storage
  • 3.14.4. Getting OP-TEE Client source code
  • 3.14.5. Building u-boot with OP-TEE OS