configs/beaglev_fire: add support for BeagleV Fire
PATCH v2 1/1 configs/beaglev_fire: add support for BeagleV Fire
Add support for the BeagleV Fire, the Beagleboard SBC powered by Microchip's PolarFire SoC.
The configuration file is beaglev_fire_defconfig. It builds a bootable kernel image with an embedded root file system. The image built can be flashed to the board using the eMMC.
The yaml configuration file is used by the hss payload generator. It maps the ELF binaries or binary blobs to the application hart.
The image generator script sets the partitions of the image.
The image tree souce file creates a FIT image.
The post image script creates the payload using the payload generator host package and finally, creates the FIT image using the ITS after the kernel build. It also creates the BMAP file for use with the BMAP command line tool to transfer the image to the board.
The U-Boot script and additional U-Boot configurations ensure that U-Boot behaves as expected for the BeagleV-Fire and boots the FIT image.
The rootfs-overlay contains script for updating the BeagleV-Fire gateware.
The README.txt documents how to build and boot the Beagle-V Fire with this configuration. It also explains how to program a custom bitstream.
---
v1 -> v2:
- README updates
- renamed U-Boot boot script
- combined gateware update scripts
- replaced mtd_debug with flash_erase and dd in gateware update script
- fixed genimage for initramfs image generation
- removed unused target packages
--- DEVELOPERS | 2 + board/beaglev_fire/README.txt | 134 ++++++++++++++++++ board/beaglev_fire/beaglev_fire.its | 55 +++++++ board/beaglev_fire/boot.cmd | 15 ++ board/beaglev_fire/config.yaml | 28 ++++ board/beaglev_fire/genimage.cfg | 35 +++++ board/beaglev_fire/post-image.sh | 14 ++ .../usr/share/microchip/update-gateware.sh | 32 +++++ board/beaglev_fire/uboot-fragment.config | 3 + configs/beaglev_fire_defconfig | 32 +++++ 10 files changed, 350 insertions(+) create mode 100644 board/beaglev_fire/README.txt create mode 100644 board/beaglev_fire/beaglev_fire.its create mode 100644 board/beaglev_fire/boot.cmd create mode 100644 board/beaglev_fire/config.yaml create mode 100644 board/beaglev_fire/genimage.cfg create mode 100755 board/beaglev_fire/post-image.sh create mode 100644 board/beaglev_fire/rootfs-overlay/usr/share/microchip/update-gateware.sh create mode 100644 board/beaglev_fire/uboot-fragment.config create mode 100644 configs/beaglev_fire_defconfig
DEVELOPERS +2 -0
@@ -1489,7 +1489,9 @@ F: package/swaybg/ F: package/yad/ N: Jamie Gibbons <[email protected]> +F: board/beaglev_fire/ F: board/microchip/mpfs_icicle/ +F: configs/beaglev_fire_defconfig F: configs/microchip_mpfs_icicle_defconfig F: package/microchip-hss-payload-generator/
board/beaglev_fire/README.txt new file +134 -0
135 lines not on this page · raw message
board/beaglev_fire/beaglev_fire.its new file +55 -0
55 lines not on this page · raw message
board/beaglev_fire/boot.cmd new file +15 -0
@@ -0,0 +1,15 @@ +# this assumes ${scriptaddr} is already set!! + +# Try to boot a fitImage from eMMC/SD + +setenv fdt_high 0xffffffffffffffff +setenv initrd_high 0xffffffffffffffff + +load mmc 0:${distro_bootpart} ${scriptaddr} beaglev_fire.itb; +bootm start ${scriptaddr}#kernel_dtb; +bootm loados ${scriptaddr}; +# Try to load a ramdisk if available inside fitImage +bootm ramdisk; +bootm prep; +fdt set /soc/ethernet@20110000 mac-address ${beaglevfire_mac_addr0}; +bootm go;
board/beaglev_fire/config.yaml new file +28 -0
@@ -0,0 +1,28 @@ +# +# HSS Payload Generator - buildroot configuration file +# + +# First, we can optionally set a name for our image, otherwise one will be created dynamically +set-name: 'PolarFire-SoC-HSS::U-Boot' + +# +# Next, we'll define the entry point addresses for each hart, as follows: +# +hart-entry-points: {u54_1: '0x80200000', u54_2: '0x80200000', u54_3: '0x80200000', u54_4: '0x80200000'} +# +# Finally, we'll define a payloads (source binary file) that will be placed at certain regions in memory +# The payload section is defined with the keyword payloads, and then a number of individual +# payload descriptors. +# +# Each payload has a name (path to its ELF/bin file), an owner-hart, and optionally 1-3 secondary-harts. +# +# Additionally, it has a privilege mode in which it will start execution. +# * Valid privilege modes are PRV_M, PRV_S and PRV_U. +# +# +# In this case, the only payload is the u-boot s-mode binary. +# +# Case only matters for the ELF path names, not the keywords. +# +payloads: + u-boot.bin: {exec-addr: '0x80200000', owner-hart: u54_1, secondary-hart: u54_2, secondary-hart: u54_3, secondary-hart: u54_4, priv-mode: prv_s}
board/beaglev_fire/genimage.cfg new file +35 -0
@@ -0,0 +1,35 @@ +# Image for eMMC boot on the Microchip PolarFire SOC BeagleV-Fire Board +# +image boot.vfat { + vfat { + files = { + "beaglev_fire.itb", + } + + file boot.scr { + image = "boot.scr" + } + } + size = 60M +} + +image sdcard.img { + hdimage { + partition-table-type = "gpt" + } + + partition uboot { + partition-type-uuid = 21686148-6449-6E6F-744E-656564454649 + image = "payload.bin" + } + + partition kernel { + partition-type-uuid = 0FC63DAF-8483-4772-8E79-3D69D8477DE4 + bootable = "true" + image = "boot.vfat" + } + + partition root { + image = "rootfs.ext4" + } +}
board/beaglev_fire/post-image.sh new file +14 -0
@@ -0,0 +1,14 @@ +#!/bin/bash +set -e + +HSS_PAYLOAD_GENERATOR="${HOST_DIR}"/bin/hss-payload-generator +MKIMAGE="${HOST_DIR}"/bin/mkimage +BOARD_DIR="$(pwd)"/"${0%/*}" + +pushd "${BINARIES_DIR}" +"${HSS_PAYLOAD_GENERATOR}" -c "${BOARD_DIR}"/config.yaml payload.bin +cp "${BOARD_DIR}"/beaglev_fire.its "${BINARIES_DIR}"/beaglev_fire.its +gzip -9 Image -c > Image.gz +"${MKIMAGE}" -f beaglev_fire.its beaglev_fire.itb +popd +support/scripts/genimage.sh -c "${BOARD_DIR}"/genimage.cfg
board/beaglev_fire/rootfs-overlay/usr/share/microchip/update-gateware.sh new file +32 -0
@@ -0,0 +1,32 @@ +#!/bin/sh + +if [ ! -e "$1"/mpfs_bitstream.spi ]; then + echo "No gateware file found." + exit 1 +fi + +if [ ! -d /lib/firmware ] +then + mkdir /lib/firmware +fi + +cp "$1"/mpfs_dtbo.spi /lib/firmware/mpfs_dtbo.spi +cp "$1"/mpfs_bitstream.spi /lib/firmware/mpfs_bitstream.spi + +mount -t debugfs none /sys/kernel/debug + +# Trash existing device tree overlay in case the rest of the process fails: +flash_erase /dev/mtd0 0 1024 + +# # Write device tree overlay +dd if=/lib/firmware/mpfs_dtbo.spi of=/dev/mtd0 seek=1024 + +# Fake the presence of a golden image for now. +dd if=/dev/zero of=/dev/mtd0 count=4 bs=1 + +# Initiate FPGA update. +echo 1 > /sys/kernel/debug/fpga/microchip_exec_update + +# Reboot Linux for the gateware update to take effect. +# FPGA reprogramming takes places between Linux shut-down and HSS restarting the board. +reboot
board/beaglev_fire/uboot-fragment.config new file +3 -0
@@ -0,0 +1,3 @@ +CONFIG_USE_BOOTARGS=y +CONFIG_BOOTARGS="root=/dev/mmcblk0p3 rootwait uio_pdrv_genirq.of_id=generic-uio" +CONFIG_MPFS_PRIORITISE_QSPI_BOOT=n
configs/beaglev_fire_defconfig new file +32 -0
@@ -0,0 +1,32 @@ +BR2_riscv=y +BR2_RISCV_ISA_RVC=y +BR2_KERNEL_HEADERS_VERSION=y +BR2_DEFAULT_KERNEL_VERSION="6.1.30" +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y +BR2_SYSTEM_DHCP="eth0" +BR2_ROOTFS_OVERLAY="board/beaglev_fire/rootfs-overlay/" +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/beaglev_fire/post-image.sh" +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,linux4microchip,linux,linux-6.1-mchp+fpga)/linux4microchip+fpga-2024.02.tar.gz" +BR2_LINUX_KERNEL_DEFCONFIG="mpfs" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="microchip/mpfs-beaglev-fire" +BR2_PACKAGE_MTD=y +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,polarfire-soc,u-boot)linux4microchip+fpga-2024.02.tar.gz" +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="beaglev_fire" +BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES="board/beaglev_fire/uboot-fragment.config" +BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_NEEDS_OPENSSL=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR=y +BR2_PACKAGE_HOST_MTOOLS=y +BR2_PACKAGE_HOST_UBOOT_TOOLS=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_FIT_SUPPORT=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT_SOURCE="board/beaglev_fire/boot.cmd"
Signature · 6 lines
2.34.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Romain Naour via buildroot
AppliedHello Jamie, All,
Le 18/06/2024 à 10:05, Jamie Gibbons via buildroot a écrit :
Quoted 22 lines
Add support for the BeagleV Fire, the Beagleboard SBC powered by Microchip's PolarFire SoC.
The configuration file is
beaglev_fire_defconfig. It builds a bootable kernel image with an embedded root file system. The image built can be flashed to the board using the eMMC.The yaml configuration file is used by the hss payload generator. It maps the ELF binaries or binary blobs to the application hart.
The image generator script sets the partitions of the image.
The image tree souce file creates a FIT image.
The post image script creates the payload using the payload generator host package and finally, creates the FIT image using the ITS after the kernel build. It also creates the BMAP file for use with the BMAP command line tool to transfer the image to the board.
The U-Boot script and additional U-Boot configurations ensure that U-Boot behaves as expected for the BeagleV-Fire and boots the FIT image.
Quoted 8 lines
The rootfs-overlay contains script for updating the BeagleV-Fire gateware.
The README.txt documents how to build and boot the Beagle-V Fire with this configuration. It also explains how to program a custom bitstream.
Signed-off-by Jamie Gibbons <[email protected]>Reviewed-by Valentina Fernandez <[email protected]>
Thanks for the detailled commit log and explanation about the beaglev_fire bringup!
A new board/beagleboard directory has been added recently for beagleboneai64 and beagleplay bards. I plan to move all existing beagleboard boards (beagleboardx15 beaglebone beagleboneai beaglev) to it.
So I moved all beaglev_fire board files to board/beagleboard.
Enabling BR2_DOWNLOAD_FORCE_CHECK_HASHES is now required in order to chech the hash of downloaded archives when a custom version is used.
I enabled BR2_DOWNLOAD_FORCE_CHECK_HASHES and added all required hash files.
Quoted 415 lines
---
v1 -> v2:
- README updates
- renamed U-Boot boot script
- combined gateware update scripts
- replacedmtd_debugwithflash_eraseand dd in gateware update script
- fixed genimage for initramfs image generation
- removed unused target packages--- DEVELOPERS | 2 + board/beaglev_fire/README.txt | 134 ++++++++++++++++++ board/beaglev_fire/beaglev_fire.its | 55 +++++++ board/beaglev_fire/boot.cmd | 15 ++ board/beaglev_fire/config.yaml | 28 ++++ board/beaglev_fire/genimage.cfg | 35 +++++ board/beaglev_fire/post-image.sh | 14 ++ .../usr/share/microchip/update-gateware.sh | 32 +++++ board/beaglev_fire/uboot-fragment.config | 3 + configs/beaglev_fire_defconfig | 32 +++++ 10 files changed, 350 insertions(+) create mode 100644 board/beaglev_fire/README.txt create mode 100644 board/beaglev_fire/beaglev_fire.its create mode 100644 board/beaglev_fire/boot.cmd create mode 100644 board/beaglev_fire/config.yaml create mode 100644 board/beaglev_fire/genimage.cfg create mode 100755 board/beaglev_fire/post-image.sh create mode 100644 board/beaglev_fire/rootfs-overlay/usr/share/microchip/update-gateware.sh create mode 100644 board/beaglev_fire/uboot-fragment.config create mode 100644 configs/beaglev_fire_defconfigDEVELOPERS +2
-0@@ -1489,7 +1489,9 @@ F: package/swaybg/ F: package/yad/ N: Jamie Gibbons <[email protected]> +F: board/beaglev_fire/ F: board/microchip/mpfs_icicle/ +F: configs/beaglev_fire_defconfig F: configs/microchip_mpfs_icicle_defconfig F: package/microchip-hss-payload-generator/board/beaglev_fire/README.txt new file +134
-0@@ -0,0 +1,134 @@ +Beagle-V Fire +============== + +BeagleV Fire is a low-cost RISC-V 64-bit based platform, powered by +Microchip's PolarFire SoC. This file describes how to use the +pre-defined Buildroot configuration for the Beagle-V Fire board. + +Further information about the Beagle-V Fire can be found at +https://docs.beagleboard.org/latest/boards/beaglev/fire/index.html. + + +Building +======== + +Configure Buildroot using the default board configuration: + + '$ make beaglev_fire_defconfig' + +Customise the build as necessary: + + '$ make menuconfig' + +Start the build: + + '$ make' + + +Result of the build +=================== + +Once the build has finished you will have the following files: + + output/images/ + +-- boot.scr + +-- boot.vfat + +-- Image + +-- Image.gz + +-- beaglev_fire.itb + +-- beaglev_fire.its + +-- mpfs-beaglev-fire.dtb + +-- payload.bin + +-- rootfs.ext2 + +-- rootfs.ext4 + +-- rootfs.tar + +-- sdcard.img + +-- u-boot.bin + + +Flashing the image to your eMMC +=============================== + +By default Buildroot builds an image suitable for the eMMC. The first partition +of this image contains a U-Boot binary, embedded in a Hart Software Services +(HSS) payload. The second partition contains a FAT filesystem with a U-Boot env +and an ITB file containing the kernel and the device tree. The third partition +contains the file system. This image can be written directly to the eMMC. + +To do so, follow the below steps: + +1. Connect to BeagleV-Fire UART debug port using a 3.3v USB to UART bridge. + +2. Now you can run `tio <port>` in a terminal window to access the UART debug +port connection. + e.g `tio /dev/ttyUSB4` + +3. Once you are connected properly, you can press the Reset button which will +show you a progress bar. + +4. Press any key in the terminal application to stop the HSS from booting. This +will give you access to the HSS command line interface and a ">>" for input +will be displayed in the terminal. + +5. Type `usbdmsc` in the HSS command line interface. The HSS `usbdmsc` command +exposes the eMMC as a USB mass storage device using the USB type C connector. +If successful, a message saying "USB Host connected" will be displayed. + +6. The eMMC should now appear as mass storage device/drive on your host PC, as +it is mounted through your USB type C connector. + +7. Now, all you need to do is dd the image to the eMMC, which can be done with +the following command on your development host: + + '$ sudo dd if=output/images/sdcard.img of=/dev/sdX bs=1M' + +You will have to replace /dev/sdX by the actual device name of your eMMC. +Please, be especially cautious not to overwrite the wrong drive as this cannot +be undone. + +8. Once the image transfer has completed you can type `CTRL+C` to disconnect +your device. + +9. Finally, type `boot` or reset your board to boot your new Linux image. + +Customize BeagleV-Fire Cape Gateware Using Verilog (Optional) +============================================================= + +To customize your Beagle-V Fire gateware please follow the guide below to +create your custom bitstream (steps 1 - 6): +https://docs.beagleboard.org/latest/boards/beaglev/fire/demos-and-tutorials/gateware/customize-cape-gateware-verilog.html + + + Program BeagleV-Fire With Your Custom Bitstream with Buildroot + ============================================================== + + After following the steps 1-6 from the above tutorial, you should now have a + artifacts.zip file on your local host. + + Unzip the downloaded artifacts.zip file. + + Go to the custom FPGA design directory: + 'cd artifacts/bitstreams/my_custom_fpga_design' + + On your Linux host development computer, copy the bitstream to BeagleV-Fire + board, replacing </path/to/your/> with the path to your BeagleV-Fire root file + system. + 'cp -r ./LinuxProgramming /path/to/your/buildroot/board/beaglev_fire/rootfs-overlay/etc/' + + To apply these changes to your image, make sure to re-build it with: + `make` + + Then, re-flash your image - to ensure you have the necessary firmware files - by + following the above section "Flashing the image to your eMMC". + + On BeagleV-Fire, + 1. Make your update gateware script executable + 'chmod +x /usr/share/microchip/update-gateware.sh' + 2. Create a firmware directory + 'mkdir /lib/firmware' + 3. Change to the directory of your gateware script + `cd /usr/share/microchip/` + 3. initiate the reprogramming of the FPGA with your gateware bitstream: + './update-gateware.sh /etc/LinuxProgramming/' + + Wait for a couple of minutes for the BeagleV-Fire to reprogram itself.board/beaglev_fire/beaglev_fire.its new file +55
-0@@ -0,0 +1,55 @@ +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) +/* + * Flattened Image Tree file for BVF + * + * Copyright (C) 2024 Microchip Technology Inc. and its subsidiaries. + * + */ + +/dts-v1/; + +/ { + description = "U-Boot fitImage for the BeagleV-Fire"; + #address-cells = <2>; + + images { + kernel { + description = "Linux kernel"; + data = /incbin/("./Image.gz"); + type = "kernel"; + arch = "riscv"; + os = "linux"; + compression = "gzip"; + load = <0x80200000>; + entry = <0x80200000>; + hash-1 { + algo = "sha256"; + }; + }; + base_fdt { + description = "Flattened Device Tree blob"; + data = /incbin/("./mpfs-beaglev-fire.dtb"); + type = "flat_dt"; + arch = "riscv"; + compression = "none"; + load = <0x8a000000>; + hash-1 { + algo = "sha256"; + }; + }; + }; + + configurations { + default = "kernel_dtb"; + kernel_dtb { + description = "1 Linux kernel, FDT blob"; + kernel = "kernel"; + fdt = "base_fdt"; + }; + + base_dtb { + description = "Base FDT blob for BeagleV-Fire board"; + fdt = "base_fdt"; + }; + }; +};board/beaglev_fire/boot.cmd new file +15
-0@@ -0,0 +1,15 @@ +# this assumes ${scriptaddr} is already set!! + +# Try to boot a fitImage from eMMC/SD + +setenv fdt_high 0xffffffffffffffff +setenv initrd_high 0xffffffffffffffff + +load mmc 0:${distro_bootpart} ${scriptaddr} beaglev_fire.itb; +bootm start ${scriptaddr}#kernel_dtb; +bootm loados ${scriptaddr}; +# Try to load a ramdisk if available inside fitImage +bootm ramdisk; +bootm prep; +fdt set /soc/ethernet@20110000 mac-address ${beaglevfire_mac_addr0}; +bootm go;board/beaglev_fire/config.yaml new file +28
-0@@ -0,0 +1,28 @@ +# +# HSS Payload Generator - buildroot configuration file +# + +# First, we can optionally set a name for our image, otherwise one will be created dynamically +set-name: 'PolarFire-SoC-HSS::U-Boot' + +# +# Next, we'll define the entry point addresses for each hart, as follows: +# +hart-entry-points: {u54_1: '0x80200000', u54_2: '0x80200000', u54_3: '0x80200000', u54_4: '0x80200000'} +# +# Finally, we'll define a payloads (source binary file) that will be placed at certain regions in memory +# The payload section is defined with the keyword payloads, and then a number of individual +# payload descriptors. +# +# Each payload has a name (path to its ELF/bin file), an owner-hart, and optionally 1-3 secondary-harts. +# +# Additionally, it has a privilege mode in which it will start execution. +# * Valid privilege modes are PRV_M, PRV_S and PRV_U. +# +# +# In this case, the only payload is the u-boot s-mode binary. +# +# Case only matters for the ELF path names, not the keywords. +# +payloads: + u-boot.bin: {exec-addr: '0x80200000', owner-hart: u54_1, secondary-hart: u54_2, secondary-hart: u54_3, secondary-hart: u54_4, priv-mode: prv_s}board/beaglev_fire/genimage.cfg new file +35
-0@@ -0,0 +1,35 @@ +# Image for eMMC boot on the Microchip PolarFire SOC BeagleV-Fire Board +# +image boot.vfat { + vfat { + files = { + "beaglev_fire.itb", + } + + file boot.scr { + image = "boot.scr" + } + } + size = 60M +} + +image sdcard.img { + hdimage { + partition-table-type = "gpt" + } + + partition uboot { + partition-type-uuid = 21686148-6449-6E6F-744E-656564454649 + image = "payload.bin" + } + + partition kernel { + partition-type-uuid = 0FC63DAF-8483-4772-8E79-3D69D8477DE4 + bootable = "true" + image = "boot.vfat" + } + + partition root { + image = "rootfs.ext4" + } +}board/beaglev_fire/post-image.sh new file +14
-0@@ -0,0 +1,14 @@ +#!/bin/bash +set -e + +HSS_PAYLOAD_GENERATOR="${HOST_DIR}"/bin/hss-payload-generator +MKIMAGE="${HOST_DIR}"/bin/mkimage +BOARD_DIR="$(pwd)"/"${0%/*}" + +pushd "${BINARIES_DIR}" +"${HSS_PAYLOAD_GENERATOR}" -c "${BOARD_DIR}"/config.yaml payload.bin +cp "${BOARD_DIR}"/beaglev_fire.its "${BINARIES_DIR}"/beaglev_fire.its +gzip -9 Image -c > Image.gz +"${MKIMAGE}" -f beaglev_fire.its beaglev_fire.itb +popd +support/scripts/genimage.sh -c "${BOARD_DIR}"/genimage.cfgboard/beaglev_fire/rootfs-overlay/usr/share/microchip/update-gateware.sh new file +32
-0@@ -0,0 +1,32 @@ +#!/bin/sh + +if [ ! -e "$1"/mpfs_bitstream.spi ]; then + echo "No gateware file found." + exit 1 +fi + +if [ ! -d /lib/firmware ] +then + mkdir /lib/firmware +fi + +cp "$1"/mpfs_dtbo.spi /lib/firmware/mpfs_dtbo.spi +cp "$1"/mpfs_bitstream.spi /lib/firmware/mpfs_bitstream.spi + +mount -t debugfs none /sys/kernel/debug + +# Trash existing device tree overlay in case the rest of the process fails: +flash_erase /dev/mtd0 0 1024 + +# # Write device tree overlay +dd if=/lib/firmware/mpfs_dtbo.spi of=/dev/mtd0 seek=1024 + +# Fake the presence of a golden image for now. +dd if=/dev/zero of=/dev/mtd0 count=4 bs=1 + +# Initiate FPGA update. +echo 1 > /sys/kernel/debug/fpga/microchip_exec_update + +# Reboot Linux for the gateware update to take effect. +# FPGA reprogramming takes places between Linux shut-down and HSS restarting the board. +rebootboard/beaglev_fire/uboot-fragment.config new file +3
-0@@ -0,0 +1,3 @@ +CONFIG_USE_BOOTARGS=y +CONFIG_BOOTARGS="root=/dev/mmcblk0p3 rootwait uio_pdrv_genirq.of_id=generic-uio" +CONFIG_MPFS_PRIORITISE_QSPI_BOOT=nconfigs/beaglev_fire_defconfig new file +0
-0
configs/beaglev_fire_defconfig line 4
Quoted 4 lines
configs/beaglev_fire_defconfig new file +4
-0@@ -0,0 +1,32 @@ +BR2_riscv=y +BR2_RISCV_ISA_RVC=y +BR2_KERNEL_HEADERS_VERSION=y +BR2_DEFAULT_KERNEL_VERSION="6.1.30"
Is any reason to use this specific kernel version for linux-headers? Instead we prefer using BR2_KERNEL_HEADERS_AS_KERNEL with BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y.
Quoted 7 lines
configs/beaglev_fire_defconfig new file +7
-0+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y +BR2_SYSTEM_DHCP="eth0" +BR2_ROOTFS_OVERLAY="board/beaglev_fire/rootfs-overlay/" +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/beaglev_fire/post-image.sh" +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,linux4microchip,linux,linux-6.1-mchp+fpga)/linux4microchip+fpga-2024.02.tar.gz"
configs/beaglev_fire_defconfig line 21
Quoted 10 lines
configs/beaglev_fire_defconfig new file +10
-0+BR2_LINUX_KERNEL_DEFCONFIG="mpfs" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="microchip/mpfs-beaglev-fire" +BR2_PACKAGE_MTD=y +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,polarfire-soc,u-boot)linux4microchip+fpga-2024.02.tar.gz"
Can you check if we should use u-boot-mchp repository instead? the polarfire-soc one has been archived recently (Jul 5, 2024).
https://github.com/linux4microchip/u-boot-mchp
For now, I keep the url as is.
configs/beaglev_fire_defconfig line 28
Quoted 7 lines
configs/beaglev_fire_defconfig new file +7
-0+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="beaglev_fire" +BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES="board/beaglev_fire/uboot-fragment.config" +BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_NEEDS_OPENSSL=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR=y +BR2_PACKAGE_HOST_MTOOLS=y
BR2_PACKAGE_HOST_DOSFSTOOLS=y is needed to provide mkdosfs (host variant).
Applied to master whith that added, thanks.
Best regards,
Romain
configs/beaglev_fire_defconfig line 32
Quoted 4 lines
configs/beaglev_fire_defconfig new file +4
-0+BR2_PACKAGE_HOST_UBOOT_TOOLS=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_FIT_SUPPORT=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT_SOURCE="board/beaglev_fire/boot.cmd"
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Romain,
Quoted 53 lines · Romain Naour
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
Hello Jamie, All,
Quoted 29 lines · Jamie Gibbons via buildroot
Add support for the BeagleV Fire, the Beagleboard SBC powered by Microchip's PolarFire SoC.
The configuration file is
beaglev_fire_defconfig. It builds a bootable kernel image with an embedded root file system. The image built can be flashed to the board using the eMMC.The yaml configuration file is used by the hss payload generator. It
maps the ELF binaries or binary blobs to the application hart.The image generator script sets the partitions of the image.
The image tree souce file creates a FIT image.
The post image script creates the payload using the payload generator
host package and finally, creates the FIT image using the ITS after the
kernel build. It also creates the BMAP file for use with the BMAP command line tool to transfer the image to the board.The U-Boot script and additional U-Boot configurations ensure that U-Boot behaves as expected for the BeagleV-Fire and boots the FIT image.
The rootfs-overlay contains script for updating the BeagleV-Fire gateware.
Quoted 8 lines
The README.txt documents how to build and boot the Beagle-V Fire with
this configuration. It also explains how to program a custom bitstream.Signed-off-by Jamie Gibbons <[email protected]>Reviewed-by Valentina FernandezThanks for the detailled commit log and explanation about the
beaglev_firebringup!A new board/beagleboard directory has been added recently for beagleboneai64
and beagleplay bards. I plan to move all existing beagleboard boards (beagleboardx15 beaglebone beagleboneai beaglev) to it. So I moved allbeaglev_fireboard files to board/beagleboard.
Quoted 6 lines
Enabling
BR2_DOWNLOAD_FORCE_CHECK_HASHESis now required in order to chech the
hash of downloaded archives when a custom version is used.I enabled
BR2_DOWNLOAD_FORCE_CHECK_HASHESand added all required hash files.
Apologies for the late response, other work took precedence. Thanks a million for all your work on this to get it over-the-line and applied to master! Happy with all the changes. Greatly appreciated!
Quoted 519 lines
Quoted 485 lines
---
v1 -> v2:
- README updates
- renamed U-Boot boot script
- combined gateware update scripts
- replacedmtd_debugwithflash_eraseand dd in gateware update script
- fixed genimage for initramfs image generation
- removed unused target packages
---
DEVELOPERS | 2 + board/beaglev_fire/README.txt | 134
++++++++++++++++++
board/beaglev_fire/beaglev_fire.its | 55 +++++++ board/beaglev_fire/boot.cmd | 15 ++ board/beaglev_fire/config.yaml | 28 ++++ board/beaglev_fire/genimage.cfg | 35 +++++ board/beaglev_fire/post-image.sh | 14 ++ .../usr/share/microchip/update-gateware.sh | 32 +++++ board/beaglev_fire/uboot-fragment.config | 3 + configs/beaglev_fire_defconfig | 32 +++++10 files changed, 350 insertions(+)create mode 100644
board/beaglev_fire/README.txtcreate mode 100644 board/beaglev_fire/beaglev_fire.its create mode 100644 board/beaglev_fire/boot.cmd create mode 100644board/beaglev_fire/config.yamlcreate mode 100644 board/beaglev_fire/genimage.cfg create mode 100755board/beaglev_fire/post-image.shcreate mode 100644 board/beaglev_fire/rootfs-overlay/usr/share/microchip/update-gateware.shcreate mode 100644board/beaglev_fire/uboot-fragment.configcreate mode 100644 configs/beaglev_fire_defconfigDEVELOPERS +0
-0@@ -1489,7 +1489,9 @@ F: package/swaybg/F: package/yad/
N: Jamie Gibbons <[email protected]>
+F: board/beaglev_fire/
F: board/microchip/mpfs_icicle/
+F: configs/beaglev_fire_defconfig
F: configs/microchip_mpfs_icicle_defconfig
F: package/microchip-hss-payload-generator/board/beaglev_fire/README.txt new file +4
-0@@ -0,0 +1,134 @@ +Beagle-V Fire +============== + +BeagleV Fire is a low-cost RISC-V 64-bit based platform, poweredby
board/beaglev_fire/README.txt new file +5
-0+Microchip's PolarFire SoC. This file describes how to use the +pre-defined Buildroot configuration for the Beagle-V Fire board. + +Further information about the Beagle-V Fire can be found at +https://docs.beagleboard.org/latest/boards/beaglev/fire/index.html.
board/beaglev_fire/README.txt new file +43
-0+ + +Building +======== + +Configure Buildroot using the default board configuration: + + '$ make beaglev_fire_defconfig' + +Customise the build as necessary: + + '$ make menuconfig' + +Start the build: + + '$ make' + + +Result of the build +=================== + +Once the build has finished you will have the following files: + + output/images/ + +-- boot.scr + +-- boot.vfat + +-- Image + +-- Image.gz + +-- beaglev_fire.itb + +-- beaglev_fire.its + +-- mpfs-beaglev-fire.dtb + +-- payload.bin + +-- rootfs.ext2 + +-- rootfs.ext4 + +-- rootfs.tar + +-- sdcard.img + +-- u-boot.bin + + +Flashing the image to your eMMC +=============================== + +By default Buildroot builds an image suitable for the eMMC. Thefirst partition
+of this image contains a U-Boot binary, embedded in a Hart Software Services
+(HSS) payload. The second partition contains a FAT filesystem with a U-Boot env
+and an ITB file containing the kernel and the device tree. The third partition
+contains the file system. This image can be written directly to the eMMC.board/beaglev_fire/README.txt new file +4
-0+ +To do so, follow the below steps: + +1. Connect to BeagleV-Fire UART debug port using a 3.3v USB toUART bridge.
+
+2. Now you can runtio <port>in a terminal window to access the UART debugboard/beaglev_fire/README.txt new file +4
-0+port connection. + e.g `tio /dev/ttyUSB4` + +3. Once you are connected properly, you can press the Reset buttonwhich will
board/beaglev_fire/README.txt new file +3
-0+show you a progress bar. + +4. Press any key in the terminal application to stop the HSS frombooting. This
+will give you access to the HSS command line interface and a ">>" for inputboard/beaglev_fire/README.txt new file +3
-0+will be displayed in the terminal. + +5. Type `usbdmsc` in the HSS command line interface. The HSS
usbdmsccommand
+exposes the eMMC as a USB mass storage device using the USB type C connector.
+If successful, a message saying "USB Host connected" will be displayed.
+
+6. The eMMC should now appear as mass storage device/drive on your host PC, asboard/beaglev_fire/README.txt new file +3
-0+it is mounted through your USB type C connector. + +7. Now, all you need to do is dd the image to the eMMC, which canbe done with
board/beaglev_fire/README.txt new file +5
-0+the following command on your development host: + + '$ sudo dd if=output/images/sdcard.img of=/dev/sdX bs=1M' + +You will have to replace /dev/sdX by the actual device name ofyour eMMC.
+Please, be especially cautious not to overwrite the wrong drive as this cannotboard/beaglev_fire/README.txt new file +3
-0+be undone. + +8. Once the image transfer has completed you can type `CTRL+C` todisconnect
board/beaglev_fire/README.txt new file +3
-0+your device. + +9. Finally, type `boot` or reset your board to boot your new Linuximage.
board/beaglev_fire/README.txt new file +5
-0+ +Customize BeagleV-Fire Cape Gateware Using Verilog (Optional) +============================================================= + +To customize your Beagle-V Fire gateware please follow the guidebelow to
board/beaglev_fire/README.txt new file +2
-0+create your custom bitstream (steps 1 - 6): +https://docs.beagleboard.org/latest/boards/beaglev/fire/demos-and-tutorials/gateware/customize-cape-gateware-verilog.html
board/beaglev_fire/README.txt new file +6
-0+ + + Program BeagleV-Fire With Your Custom Bitstream with Buildroot + ============================================================== + + After following the steps 1-6 from the above tutorial, youshould now have a
+ artifacts.zip file on your local host.board/beaglev_fire/README.txt new file +7
-0+ + Unzip the downloaded artifacts.zip file. + + Go to the custom FPGA design directory: + 'cd artifacts/bitstreams/my_custom_fpga_design' + + On your Linux host development computer, copy the bitstream toBeagleV-Fire
+ board, replacing </path/to/your/> with the path to your BeagleV- Fire root file
+ system.
+ 'cp -r ./LinuxProgramming /path/to/your/buildroot/board/beaglev_fire/rootfs-overlay/etc/' +
+ To apply these changes to your image, make sure to re-build it with:
+make
+
+ Then, re-flash your image - to ensure you have the necessary firmware files - by
+ following the above section "Flashing the image to your eMMC". +
+ On BeagleV-Fire,
+ 1. Make your update gateware script executable
+ 'chmod +x/usr/share/microchip/update-gateware.sh' + 2. Create a firmware directory
+ 'mkdir/lib/firmware'
+ 3. Change to the directory of your gateware script +cd /usr/share/microchip/
+ 3. initiate the reprogramming of the FPGA with your gateware bitstream:
+ './update-gateware.sh/etc/LinuxProgramming/'
+
+ Wait for a couple of minutes for the BeagleV-Fire to reprogram itself.
\ No newline at end of fileboard/beaglev_fire/beaglev_fire.its new file +5
-0@@ -0,0 +1,55 @@ +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) +/* + * Flattened Image Tree file for BVF + * + * Copyright (C) 2024 Microchip Technology Inc. and itssubsidiaries.
+ *
+ */board/beaglev_fire/beaglev_fire.its new file +23
-0+ +/dts-v1/; + +/ { + description = "U-Boot fitImage for the BeagleV-Fire"; + #address-cells = <2>; + + images { + kernel { + description = "Linux kernel"; + data = /incbin/("./Image.gz"); + type = "kernel"; + arch = "riscv"; + os = "linux"; + compression = "gzip"; + load = <0x80200000>; + entry = <0x80200000>; + hash-1 { + algo = "sha256"; + }; + }; + base_fdt { + description = "Flattened Device Treeblob";
+ data = /incbin/("./mpfs-beaglev- fire.dtb");
+ type = "flat_dt";
+ arch = "riscv";
+ compression = "none";
+ load = <0x8a000000>;
+ hash-1 {
+ algo = "sha256"; + };
+ };
+ };
+
+ configurations {
+ default = "kernel_dtb";
+kernel_dtb{
+ description = "1 Linux kernel, FDT blob";
+ kernel = "kernel";
+ fdt = "base_fdt";
+ };
+
+base_dtb{
+ description = "Base FDT blob for BeagleV-Fire board";
+ fdt = "base_fdt";
+ };
+ };board/beaglev_fire/beaglev_fire.its new file +1
-0+};board/beaglev_fire/boot.cmd new file +14
-0@@ -0,0 +1,15 @@ +# this assumes ${scriptaddr} is already set!! + +# Try to boot a fitImage from eMMC/SD + +setenv fdt_high 0xffffffffffffffff +setenv initrd_high 0xffffffffffffffff + +load mmc 0:${distro_bootpart} ${scriptaddr} beaglev_fire.itb; +bootm start ${scriptaddr}#kernel_dtb; +bootm loados ${scriptaddr}; +# Try to load a ramdisk if available inside fitImage +bootm ramdisk; +bootm prep; +fdt set /soc/ethernet@20110000 mac-address${beaglevfire_mac_addr0};
board/beaglev_fire/boot.cmd new file +1
-0+bootm go;board/beaglev_fire/config.yaml new file +5
-0@@ -0,0 +1,28 @@ +# +# HSS Payload Generator - buildroot configuration file +# + +# First, we can optionally set a name for our image, otherwise onewill be created dynamically
board/beaglev_fire/config.yaml new file +4
-0+set-name: 'PolarFire-SoC-HSS::U-Boot' + +# +# Next, we'll define the entry point addresses for each hart, asfollows:
board/beaglev_fire/config.yaml new file +2
-0+# +hart-entry-points: {u54_1: '0x80200000', u54_2: '0x80200000',
u54_3: '0x80200000',u54_4: '0x80200000'}board/beaglev_fire/config.yaml new file +2
-0+# +# Finally, we'll define a payloads (source binary file) that willbe placed at certain regions in memory
+# The payload section is defined with the keyword payloads, and then a number of individualboard/beaglev_fire/config.yaml new file +3
-0+# payload descriptors. +# +# Each payload has a name (path to its ELF/bin file), an owner-hart, and optionally 1-3 secondary-harts.
board/beaglev_fire/config.yaml new file +2
-0+# +# Additionally, it has a privilege mode in which it will startexecution.
board/beaglev_fire/config.yaml new file +9
-0+# * Valid privilege modes are PRV_M, PRV_S and PRV_U. +# +# +# In this case, the only payload is the u-boot s-mode binary. +# +# Case only matters for the ELF path names, not the keywords. +# +payloads: + u-boot.bin: {exec-addr: '0x80200000', owner-hart: u54_1,secondary-hart:
u54_2, secondary-hart:u54_3, secondary-hart:u54_4, priv-mode:prv_s}board/beaglev_fire/genimage.cfg new file +1
-0@@ -0,0 +1,35 @@ +# Image for eMMC boot on the Microchip PolarFire SOC BeagleV-FireBoard
board/beaglev_fire/genimage.cfg new file +21
-0+# +image boot.vfat { + vfat { + files = { + "beaglev_fire.itb", + } + + file boot.scr { + image = "boot.scr" + } + } + size = 60M +} + +image sdcard.img { + hdimage { + partition-table-type = "gpt" + } + + partition uboot { + partition-type-uuid = 21686148-6449-6E6F-744E-656564454649
+ image = "payload.bin"
+ }
+
+ partition kernel {
+ partition-type-uuid = 0FC63DAF-8483-4772-8E79- 3D69D8477DE4
+ bootable = "true"
+ image = "boot.vfat"
+ }board/beaglev_fire/genimage.cfg new file +5
-0+ + partition root { + image = "rootfs.ext4" + } +}board/beaglev_fire/post-image.sh new file +9
-0@@ -0,0 +1,14 @@ +#!/bin/bash +set -e + +HSS_PAYLOAD_GENERATOR="${HOST_DIR}"/bin/hss-payload-generator +MKIMAGE="${HOST_DIR}"/bin/mkimage +BOARD_DIR="$(pwd)"/"${0%/*}" + +pushd "${BINARIES_DIR}" +"${HSS_PAYLOAD_GENERATOR}" -c "${BOARD_DIR}"/config.yamlpayload.bin
+cp "${BOARD_DIR}"/beaglev_fire.its
"${BINARIES_DIR}"/beaglev_fire.itsboard/beaglev_fire/post-image.sh new file +4
-0+gzip -9 Image -c > Image.gz +"${MKIMAGE}" -f beaglev_fire.its beaglev_fire.itb +popd +support/scripts/genimage.sh -c "${BOARD_DIR}"/genimage.cfg(quoted diff) +0
-0
overlay/usr/share/microchip/update-gateware.shb/board/beaglev_fire/rootfs-overlay/usr/share/microchip/update-gateware.sh
new file mode 100644
index 0000000000..f455037b60board/beaglev_fire/rootfs-overlay/usr/share/microchip/update- new file +0
-0
gateware.shboard/beaglev_fire/rootfs-overlay/usr/share/microchip/update- new file +18
-0@@ -0,0 +1,32 @@ +#!/bin/sh + +if [ ! -e "$1"/mpfs_bitstream.spi ]; then + echo "No gateware file found." + exit 1 +fi + +if [ ! -d /lib/firmware ] +then + mkdir /lib/firmware +fi + +cp "$1"/mpfs_dtbo.spi /lib/firmware/mpfs_dtbo.spi +cp "$1"/mpfs_bitstream.spi /lib/firmware/mpfs_bitstream.spi + +mount -t debugfs none /sys/kernel/debug + +# Trash existing device tree overlay in case the rest of theprocess fails:
board/beaglev_fire/rootfs-overlay/usr/share/microchip/update- new file +13
-0+flash_erase /dev/mtd0 0 1024 + +# # Write device tree overlay +dd if=/lib/firmware/mpfs_dtbo.spi of=/dev/mtd0 seek=1024 + +# Fake the presence of a golden image for now. +dd if=/dev/zero of=/dev/mtd0 count=4 bs=1 + +# Initiate FPGA update. +echo 1 > /sys/kernel/debug/fpga/microchip_exec_update + +# Reboot Linux for the gateware update to take effect. +# FPGA reprogramming takes places between Linux shut-down and HSSrestarting the board.
board/beaglev_fire/rootfs-overlay/usr/share/microchip/update- new file +1
-0+rebootboard/beaglev_fire/uboot-fragment.config new file +2
-0@@ -0,0 +1,3 @@ +CONFIG_USE_BOOTARGS=y +CONFIG_BOOTARGS="root=/dev/mmcblk0p3 rootwaituio_pdrv_genirq.of_id=generic-uio"
board/beaglev_fire/uboot-fragment.config new file +1
-0+CONFIG_MPFS_PRIORITISE_QSPI_BOOT=nconfigs/beaglev_fire_defconfig new file +0
-0configs/beaglev_fire_defconfig line 4
Quoted 4 lines
configs/beaglev_fire_defconfig new file +4
-0@@ -0,0 +1,32 @@ +BR2_riscv=y +BR2_RISCV_ISA_RVC=y +BR2_KERNEL_HEADERS_VERSION=y +BR2_DEFAULT_KERNEL_VERSION="6.1.30"Is any reason to use this specific kernel version for linux-headers? Instead we prefer using
BR2_KERNEL_HEADERS_AS_KERNELwith BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y.Quoted 19 lines
configs/beaglev_fire_defconfig new file +7
-0+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y +BR2_SYSTEM_DHCP="eth0" +BR2_ROOTFS_OVERLAY="board/beaglev_fire/rootfs-overlay/" +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/beaglev_fire/post-image.sh" +BR2_LINUX_KERNEL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL=y +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(callgithub,linux4microchip,linux,linux-6.1-
mchp+fpga)/linux4microchip+fpga-2024.02.tar.gz"configs/beaglev_fire_defconfig new file +10
-0+BR2_LINUX_KERNEL_DEFCONFIG="mpfs" +BR2_LINUX_KERNEL_DTS_SUPPORT=y +BR2_LINUX_KERNEL_INTREE_DTS_NAME="microchip/mpfs-beaglev-fire" +BR2_PACKAGE_MTD=y +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_UBOOT=y +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL=y +BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION="$(call github,polarfire-Quoted 1 line
soc,u-boot)linux4microchip+fpga-2024.02.tar.gz"
Can you check if we should use u-boot-mchp repository instead? the polarfire-soc
one has been archived recently (Jul 5, 2024).
Quoted 3 lines
https://github.com/linux4microchip/u-boot-mchp
For now, I keep the url as is.
Yes, this change got made after I submitted this patch so just wanted to get it applied before making further changes. Sending a patch to update it now.
Thanks again,
Jamie.
Quoted 15 lines
configs/beaglev_fire_defconfig line 28
Quoted 9 lines
configs/beaglev_fire_defconfig new file +2
-0+BR2_TARGET_UBOOT_BOARD_DEFCONFIG="beaglev_fire" +BR2_TARGET_UBOOT_CONFIG_FRAGMENT_FILES="board/beaglev_fire/uboot-fragment.config"
configs/beaglev_fire_defconfig new file +5
-0+BR2_TARGET_UBOOT_NEEDS_DTC=y +BR2_TARGET_UBOOT_NEEDS_OPENSSL=y +BR2_PACKAGE_HOST_GENIMAGE=y +BR2_PACKAGE_HOST_MICROCHIP_HSS_PAYLOAD_GENERATOR=y +BR2_PACKAGE_HOST_MTOOLS=yBR2_PACKAGE_HOST_DOSFSTOOLS=y is needed to provide mkdosfs (host variant).
Applied to master whith that added, thanks.
Quoted 9 lines
Best regards,
RomainQuoted 5 lines
configs/beaglev_fire_defconfig new file +4
-0+BR2_PACKAGE_HOST_UBOOT_TOOLS=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_FIT_SUPPORT=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT=y +BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT_SOURCE="board/beaglev_fire/boot.cmd"
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot