Avenger96 Image Programming: Difference between revisions
Mschmoeller (talk | contribs) No edit summary |
Ageisreiter (talk | contribs) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 14: | Line 14: | ||
== Get the | == Get the image == | ||
| Line 53: | Line 53: | ||
Check the device informations on the right bottom side after a successful connection, then click on the "Open file" Header. | Check the device informations on the right bottom side after a successful connection, then click on the "Open file" Header. | ||
Choose the wanted flash layout from your Yocto build | Choose the wanted flash layout from your Yocto build. | ||
For example: FlashLayout_nor-emmc_stm32mp157a-av96-basic.tsv (U-Boot -> NOR-SPI, Linux -> eMMC) | For example: | ||
:''FlashLayout_nor-emmc_stm32mp157a-av96-basic.tsv'' (U-Boot -> NOR-SPI, Linux -> eMMC) | |||
These layouts you can find in the following directory of your build: | These layouts you can find in the following directory of your build: | ||
$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96/flashlayout_av96-weston/ | :''$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96/flashlayout_av96-weston/'' | ||
| Line 74: | Line 75: | ||
For Yocto this is the following directory: | For Yocto this is the following directory: | ||
$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96 | :''$YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96'' | ||
| Line 82: | Line 83: | ||
If you want to boot your device please don't forget to switch the boot mode. | If you want to boot your device please don't forget to switch the SPI boot mode. | ||
[[File:AV96-SPI-Boot.PNG|700px]] | |||
Latest revision as of 16:45, 20 August 2019
Introduction
This guide is about how to flash the AV96 board with STM32 Cube Programmer.
Install STM32 Cube Programmer
Download the installer from the official STM32 Cube Programmer site.
Follow ST's installation instructions.
Get the image
Build your own Yocto image by using the following source and on GitHub: AV96 Yocto Layer
Instructions how to build the image can be found in the repository readme.
Once you have built your own AV96 Yocto image, your build provides all the files you need to use the Cube Programmer.
Prepairing the target device
To get access to your target with the STM32 Cube Programmer you need to switch the AV96 boot mode to USB boot:
Then connect the USB-C interface of the AV96 board to your computer and power on your device.
Programm the image with STM32 Cube Programmer
Start the STM32 Cube Programmer Tool.
If your device is connected correctly, you should be able to see the available USB Port:
If not, check your connection and boot mode configuration, then press the refresh button on the right.
Continue by clicking the green "Connect" button on the right.
Check the device informations on the right bottom side after a successful connection, then click on the "Open file" Header.
Choose the wanted flash layout from your Yocto build.
For example:
- FlashLayout_nor-emmc_stm32mp157a-av96-basic.tsv (U-Boot -> NOR-SPI, Linux -> eMMC)
These layouts you can find in the following directory of your build:
- $YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96/flashlayout_av96-weston/
You should be able to see the files, destinations and address offsets which have to be programmed.
If you dont want them all to be flashed, unselect the checkboxes on the left of the wanted partition.
You need to choose the "Binaries path" of the images to be flashed by clicking on the browse button or fill it in manually.
For Yocto this is the following directory:
- $YOCTO_HOME/build-openstlinuxweston-stn32mp1-av96/tmp-glibc/deploy/images/stm32mp1-av96
At last click on "Download" to flash your device.
You will get a status message whether your flash process was successful or not.
If you want to boot your device please don't forget to switch the SPI boot mode.
