Introduction

Build BSP Images and SDK for the Ahsoka platform.

Images supported

• OpenSTLinux line of Openview products

Openview.OpenSTLinux

1. Getting Started

1.1 Build Requirements

This image relies on the OpenEmbedded/Yocto build system that is provided through Bitbake and OpenEmbedded-Core layers.
Build machine requirements:

• Ubuntu 22.04
  or
• WSL2 with Ubuntu 22.04 VM
  It is necessary to update from the default machine resources allocated by WSL2 to the Ubuntu VM
  Modify .wslconfig in the %UserProfile% directory. We recommend 24GB if possible:

  # Settings apply across all Linux distros running on WSL 2
  [wsl2]
  
  # Limits VM memory to use no more than 24 GB, this can be set as whole numbers using GB or MB
  memory=24GB
  

  The Yocto build consumes a large amount of disk space as well. The default location for WSL disk images is your primary hard drive. If you want to move this to a secondary hard drive, you can follow these instructions.

1.2 Git Configuration

Set global git config info or some recipes will fail to fetch:

• git config --global user.email "you@example.com"
• git config --global user.name "Your Name"

We use git sub-modules for the various layers included in the Yocto build. Therefore it is necessary to ensure the sub-modules are populated:

• git submodule update --init --recursive

1.3 Openview Yocto Layer

Our layer is found in:
./OpenView.OpenSTLinux/layers/meta-st/meta-hlio-rcd/
Changes to our Yocto layer (held in a separate repository) requires committing and pushing those changes in the sub-module and then updating this repository with the new commit sha for the sub-module.

2. Build and Deploy

2.1 Build Script

From the OpenView.OpenSTLinux directory, run local.sh.
This script will:

• install the necessary dependencies
• create the appropriate versioning
• build the base image
• build the SDK

2.2 Outputs

The BSP and SDK are available in the ./OpenView.OpenSTLinux/output/ directory as:

• image.{version}.zip
• sdk.{version}.zip

2.3 Flashing BSP to the target board

The STM32 Cube Programmer is required.
The target board must be placed in DFU mode:

• Use a large magnet over the back corner of the target device nearest the USB-C connector.
• Cycle power with the magnet in place.

Unzip the image zip file and run the flash.sh script from the unzipped directory.

2.4 Cross Compiling with the SDK

The SDK must be installed to cross compile for the Openview display.

• Unzip the sdk zip file.
• If needed, change the permissions on the SDK installation script so that it is executable:
  chmod +x hlio-image-rcd-base-hlio-rcd-stm32mp1-hlio-rcd-x86_64-toolchain-4.0.2-snapshot.sh
• Run the SDK installation script
  • Use the -d {SDK installation directory absolute path} option to specify the absolute path to the directory in which you want to install the SDK ({SDK installation directory}):
    ./hlio-image-rcd-base-hlio-rcd-stm32mp1-hlio-rcd-x86_64-toolchain-4.0.2-snapshot.sh -d <working directory absolute path>/<sdk-dir-name>
• The SDK environment setup script must be run once in each new working terminal in which you cross-compile:
  source <SDK installation directory>/environment-setup-cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi