Forum Discussion
Hi,
Ok I understand the "full test" image also failed to configure over JTAG but we lack more detailed information why.
Can you please confirm the Quartus version you use?
I assume you are using the HPs 1st mode configuration, please confirm.
In this case can you stop at u-boot prompt and manually run fpga load, e.g. according to the u-boot bootcmd (CONFIG_BOOTCOMMAND environment example) in https://altera-fpga.github.io/rel-25.1/embedded-designs/agilex-5/e-series/modular/boot-examples/ug-linux-boot-agx5e-modular/#boot-from-sd-card
CONFIG_BOOTCOMMAND="load mmc 0:1 \${loadaddr} ghrd.core.rbf; fpga load 0 \${loadaddr} \${filesize};bridge enable;..
In case of failure it should report an error code and related details, see an example capture below:
Regards,
Stefan
It is Quartus 24.3. Yes it is in HPS First mode.
When executing the command you mentioned, I get this result:
SOCFPGA_AGILEX5 # fpga load 0 ${fpgadata} ${fpgadatasize} .............................................................FPGA reconfiguration failed! Command 'load' failed: Error -110
- StefanG_Altera4 months ago
Occasional Contributor
Hi,
Could you try "bridge disable" before "fpga load" at u-boot prompt?
My understanding is that the configuration error reporting feature is incorporated in v25.1 embedded SW package (need to confirm).
Could you try to compile your FPGA design (GHRD) with Quartus Pro 25.1 and build u-boot from our v25.1 fork?
git clone -b QPDS25.1_REL_GSRD_PR https://github.com/altera-fpga/u-boot-socfpga
As in the Agilex 5 Premium Development Kit Example in https://altera-fpga.github.io/rel-25.1/embedded-designs/agilex-5/e-series/premium/boot-examples/ug-linux-boot-agx5e-premium/#boot-from-sd-card
You would need to include your defconfig (configs/socfpga_agilex5_atuma5_defconfig, include/configs/socfpga_agilex5_atuma5.h) and device trees in arch/arm/dts (socfpga_agilex5_atuma5.dts, socfpga_agilex5_atuma5-u-boot.dtsi).
Regards,
Stefan
- K6064 months ago
Contributor
Hi
I have discovered that replacing the line:
.intel_directphy_gts_0_o_rx_parallel_data_o_rx_parallel_data (gts_o_rx_parallel_data)with
.intel_directphy_gts_0_o_rx_parallel_data_o_rx_parallel_data (32'b0)Lets the system boot - based on this; what would you recommend?