Please let me clarify how to use polarfire-soc-buildroot-sdk (commit 6514a11) with the latest HSS booting from SD card.
So far, I installed the HSS, which was prepared as “Default/hss.elf” of HSS GitHub repo (release 2020.10), to eNVM by SoftConsole-v6.4/extras/mpfs/mpfs-program-bootmode.sh.
P.S. I wrote there was
Default/hss.elfin the HSS distribution, but it wasn’t correct. I guess I built it by myself. Sorry.
And regarding FlashPro programming, I chose Icicle-Kit-sdcard-2020.10-HSS_0_99_13.zip mentioned in this page.
By flashing Linux image which is also mentioned in the web page above (I believe this is built by OpenEmbedded/Yocto), I confirmed that Linux booted fine.
So now, I’m finally trying to evaluate Buildroot procedure.
After reading through polarfire-soc-buildroot-sdk document and Makefile, I found the following three make targets.
In either case, rootfs won’t look copied to SD card. I also found target “format-rootfs-image” and found it is dd’ing rootfs.bin to
However, for the target “format-boot-loader”,
$(PART3) is for opensbi. For the target “format-icicle-sd-image”, ext4 partition is used to store
$(uboot_s_scr), instead of vfat partition.
After all, my questions are, if we use HSS and booting from SD-card,
- What kind of GPT partitions are required? (HSS payload, vfat and ext4?)
- Can we place
$(uboot_s_scr)and rootfs in the same ext4 partition?
- Do we still need
$(opensbi)even using HSS?
Thank you for your suggestion.