STM32MP157 Discovery Kit¶

FoundriesFactory CI Build¶

Including STM OpenEmbedded layer requires accepting EULA. When building locally it is enough to accept EULA using interactive prompt. When building in CI this isn’t possible. To enable EULA acceptance in the CI job, EULA_stm32mp1disco variable needs to be set in the factory-config.yml:

...
lmp:
  params:
    ...
    EULA_stm32mp1disco: "1"
    ...

factory-config.yml can be found in ci-scripts.git repository that is created for each factory.

Preparation¶

Ensure you replace the <factory> placeholder below with the name of your Factory.

Download necessary files from https://app.foundries.io/factories/<factory>/targets
1. Click the latest Target with the platform-devel Trigger.
2. Expand the run in the Runs section which corresponds with the name of the board and download the Factory image for that machine.
  
  E.g: lmp-factory-image-<machine-name>.wic.gz

Flashing¶

Now, flash the lmp-factory-image-stm32mp1-disco.wic.gz retrieved from the previous section to an SD Card. This contains the system image that the device will boot.

Determine the disk you want to flash by finding the device with the SIZE that matches your flash drive in the list below. Be sure to ignore partitions (where TYPE is part). Save the NAME for your flash drive to be used in a later step as the disk path. e.g: /dev/mmcblk0, /dev/sdb:

lsblk -po +MODEL

Example Output:

$ lsblk -po +MODEL
NAME             MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT                 MODEL
/dev/mmcblk0     179:0    0  29.8G  0 disk
├─/dev/mmcblk0p1 179:1    0  41.6M  0 part /mnt/boot
└─/dev/mmcblk0p2 179:2    0  29.8G  0 part /mnt/otaroot
/dev/zram0       254:0    0    26G  0 disk /out
/dev/nvme0n1     259:0    0 953.9G  0 disk                            SSDPEKKF010T8 NVMe INTEL 1024GB

Flash the disk.

Replace <system-image> with the path to your system image.

Replace /dev/mmcblk<X> with your chosen disk path.

gunzip -c <system-image> | sudo dd of=/dev/mmcblk<X> bs=4M iflag=fullblock oflag=direct status=progress

Determine the disk you want to flash by finding the device with the SIZE that matches your flash drive in the list below. Be sure to ignore partitions (lines without the * in the SIZE). Save the IDENTIFIER for your flash drive to be used in a later step as the disk path. e.g: /dev/disk3:

diskutil list

Example Output:

$ diskutil list
/dev/disk3 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *15.5 GB    disk3
   1:             Windows_FAT_32 boot                    45.7 MB    disk3s1
   2:                      Linux                         15.5 GB    disk3s2

Flash the disk.

Replace <system-image> with the path to your system image.

Replace /dev/disk<X> with your chosen disk path.

gunzip -c <system-image> | sudo dd of=/dev/disk<X> bs=4M

Windows has no dd like tool built into the operating system to flash your image to disk. In this case, we recommend you download and use either Win32 Disk Imager or Rufus.

Note

Your system image is in a compressed wic.gz format. To follow these next steps, you must extract it using a tool like 7zip which will leave you with a .wic image file.

Using Rufus

Download and run Rufus.
Select your disk.
SELECT your <system-image>.
START the flash procedure.

Using Win32 Disk Imager

Download and run Win32 Disk Imager as Administrator.
Click the blue folder icon.
Select your <system-image>
Select your disk via the Device dropdown.
Click Write
Wait for the image to finish writing, and a Write Successful dialog will appear.

Remove the flash drive from the host and insert/connect it into the board.
Power on the board to boot the new image.

Boot mode¶

STM32MP157C-DK2 board has a dip switch that controls boot mode. Dip switch covers BOOT0 and BOOT2 signals. They both have to be turned ON for the board to boot from SD card.