Forum Discussion
Hi,
This is a great explanation, probably the best one yet. I have been having issues creating the SD card image for the Agilex 7 DK-SI-AGI027FA dev board. The ARRIA10 and CycloneV days where much easier to deal with and I wish INTEL would take ownership of the SD card image build flow for both Baremetal/RTOS and for OS bring ups. Dealing with Rocketboards.org's instructions is hit and miss, many detailed steps are left out and it is very time consuming to get it all working.
I have followed the instructions to the letter but still having issues with either the build flows from GSRD for Agilex 7 I-Series Transceiver-SoC DevKit (4x F-Tile) | Documentation | RocketBoards.org , is different from the one provided in Building Bootloader for Agilex 7 | Documentation | RocketBoards.org.
If you follow the latest build flow release 24.1, then partition 1 ends up with three files:
boot.scr.uimg
kernet.itb
u-boot.itb
The core.rbf and device tree (dtb file ) files are no longer copied to the FAT32 image separately, it seems to me that the Kernel image file (Image), the device tree, and core RBF files are combined into one file called kernel.itb. Then a boot.scr.uimg appears again.
I personally prefer the method you discussed, because this way is easier to change the RBF and DTB files, as supposed to combining them into one fiile.
Could you please break down the new build flow and explain all changes done in partition 1 with the same level of detail. Where did the Core RBF and DTB file go and how is the kernel.itb made?
Also is the u-boot device tree file (socfpga_agilex_socdk-u-boot.dtsi) related to or derived from the HPS' device tree files (socfpga_agilex_socdk.dts and socfpga_agilex.dtsi) ?
Thanks again for the post and help.
Alex FV