This README file contains information on the contents of the meta-octavo-osd32mp1 layer.

Please see the corresponding sections below for details.

Dependencies
============

  URI: https://github.com/STMicroelectronics/meta-st-stm32mp
  branch: dunfell

  URI: https://github.com/STMicroelectronics/meta-st-openstlinux
  branch: dunfell

  URI: https://github.com/STMicroelectronics/meta-st-scripts
  branch: dunfell
  
  URI: https://github.com/STMicroelectronics/meta-st-scripts
  branch: dunfell
  
  URI: https://github.com/openembedded/openembedded-core.git
  branch: dunfell

  URI: git://github.com/openembedded/meta-openembedded.git
  branch: dunfell
  
  URI: https://github.com/meta-qt5/meta-qt5
  branch: dunfell

  URI: https://github.com/openembedded/bitbake.git
  branch: dunfell
  
Patches
=======

Please submit any patches against the meta-octavo-osd32mp1 layer here

Maintainer: Neeraj Dantu <dantuguf14105(at)gmail.com>

Prerequisites
=================
sudo apt-get update
sudo apt-get install -y git curl gpg python-is-python3
sudo apt-get install -y build-essential chrpath diffstat gawk gcc-multilib libegl1-mesa libgmp-dev libmpc-dev libsdl1.2-dev libssl-dev pylint python3-git python3-jinja2 python3-pip socat texinfo xterm
sudo snap install git-repo

- Please make sure you have at least 50GB of free disk space
- The layer was tested on Ubuntu 18.04 and Ubuntu 20.04
- Building an image may take a while based on machine capabilities

Getting Started
=================

I. Adding the meta-octavo layer to your build
  Get Distribution Package: 
  - repo init -u https://github.com/STMicroelectronics/oe-manifest.git -b refs/tags/openstlinux-5.10-dunfell-mp1-21-03-31
  - repo sync
  
  Initialize environment
  - DISTRO=openstlinux-weston MACHINE=stm32mp1 source layers/meta-st/scripts/envsetup.sh
  
  Clone this repo
  - git clone https://github.com/octavosystems/meta-octavo-osd32mp1/
  
  Add layer to your build environment
  - bitbake-layers add-layer <PATH TO THIS REPO>
  
  Change MACHINE in <BUILD_FOLDER>/conf/local.conf
  - MACHINE = "osd32mp1-brk"  for OSD32MP1-BRK
  - MACHINE = "osd32mp1-red"  for OSD32MP1-RED
  - MACHINE = "osd32mp1-red-v1_2" for OSD32MP1-RED V1.2
  - MACHINE = "osd32mp1-1g-red-v1_2" for OSD32MP1-1G-RED V1.2

II. Misc
  Generate image
  - bitbake octavo-image-weston

III. Program the board
  You will need Cube Programmer(>v2.4): https://www.st.com/en/development-tools/stm32cubeprog.html.
  For Linux:
  - cd <BUILD_FOLDER>/tmp-glibc/deploy/images/\$MACHINE
  - Set boot mode to USB
  - Make sure you have an SD card in the SD card slot to program
  - Connect the board to Host computer
  - STM32_Programmer_CLI -l USB
 
  This should provide board information:
     -------------------------------------------------------------------
                        STM32CubeProgrammer v2.5.0                  
      -------------------------------------------------------------------

=====  DFU Interface   =====

Total number of available STM32 device in DFU mode: 1

  Device Index           : USB1
  USB Bus Number         : 003
  USB Address Number     : 003
  Product ID             : DFU in HS Mode @Device ID /0x500, @Revision ID /0x0000
  Serial number          : 002500403239511337383434
  Firmware version       : 0x0110
  Device ID              : 0x0500

  Program the board
  - STM32_Programmer_CLI -c port=USB1 -w flashlayout_octavo-image-weston/trusted/FlashLayout_sdcard_stm32mp157c-osd32mp1-brk-trusted.tsv
  - STM32_Programmer_CLI -c port=USB1 -w flashlayout_octavo-image-weston/trusted/FlashLayout_sdcard_stm32mp157c-osd32mp1-red-trusted.tsv
  - STM32_Programmer_CLI -c port=USB1 -w flashlayout_octavo-image-weston/trusted/FlashLayout_sdcard_stm32mp157c-osd32mp1-red-v1_2-trusted.tsv
  
  To Flash on Windows, use cp_image_files.py:
  Usage: 
    -b <Path to build directory>
    -d <Path to destination directory>
  - When copying files from Linux to Windows, there are no symbolic links so you have to rename the .ext4 files to remove anything between "osd32mp1-brk/red" and ".ext4"
  
  
Known Issues
=================
repo init error: https://stackoverflow.com/questions/65193998/syntaxerror-invalid-syntax-to-repo-init-in-the-aosp-code