Forum Discussion

pmarques's avatar
pmarques
Icon for New Contributor rankNew Contributor
7 months ago
Solved

Linux not booting - can't get kernel image

Hi, I'm having trouble booting to Linux after migrating a project to the newest GSRD 2.0 (Quartus 25.3).  I'm using an Agilex 5 FPGA E-Series 065B Premium Devkit. The project was based in the G...
Hps Boot
  • RolandoS_Altera's avatar
    RolandoS_Altera
    6 months ago

    Hi pmarques​ 

    From this thread, I see the the JTAG_USER_CODE is being set a 4 as it was set with that value in the example design used for the SD_CARD daughter card. I think that in the new design, this should be either 0 or undefined:

    You can find this value from Quartus in the Assignments >> Device >> Device and Pin Options >> General.

    Also you may find this in your .qsf: 

    set_global_assignment -name STRATIX_JTAG_USER_CODE 4

    So, you can either change this value to 0 or remove it. 

    There is some documentation about how this JTAG_USER_CODE was used in GSRD 1.0

    https://www.rocketboards.org/foswiki/Documentation/SingleImageBoot , Seems that something about this is still used in GSDR 2.0, but the board IDs changed in GSRD 2.0.

    In this file you will see how the kernel.itb is created. This includes 2 sets of images: board-0 and board-1. The USER_CODE=0 will use the board-0 configuration and USER_CODE=1 will use the board-1 configuration (it's the same but doesn't include the core.rbf in the kernel.itb. I am guessing that when this is not defined it will use also the board-0 configuration.

    https://github.com/altera-fpga/meta-altera-fpga/blob/main/meta-altera-bsp/recipes-kernel/linux/linux-socfpga-lts/fit_agilex5_kernel.its

     

     

     

tehjingy_Altera's avatar
tehjingy_Altera
Icon for Regular Contributor rankRegular Contributor
7 months ago

Hi pmarques 

 

The modification you make should just remove the simulation files and would not cause the board to not being boot up.

For now we could ignore the bootargs value in the env. This value will be overwritten by the boot_scripts (boot.scr <- part of the generated files)

 

When you are booting the board with the generated kernel.itb and printenv where board_id =0 , is it able to be booted? With this combination it is supposed to be able to boot.

 

Regards

tehjingy

 

 

pmarques's avatar
pmarques
Icon for New Contributor rankNew Contributor
7 months ago

Hi  tehjingy_Altera​,

Yes, the board boots successfully with a compiled default GSRD2.0 build. Printenv shows board_id=0.

Best regards,

PM.

  • tehjingy_Altera's avatar
    tehjingy_Altera
    Icon for Regular Contributor rankRegular Contributor
    7 months ago

    Hi pmarques 

     

    Could you point me to the file that you made the changes to and I will try to generate it using the GSRD2.0 build flow.

     

    Regards

    tehjingy

     

    • pmarques's avatar
      pmarques
      Icon for New Contributor rankNew Contributor
      7 months ago

      Hi tehjingy_Altera​,

      Do you mean the Makefile ? It's in "/agilex5_gsrd_20.enablement_sd/agilex5_soc_devkit_ghrd/Makefile".

      • tehjingy_Altera's avatar
        tehjingy_Altera
        Icon for Regular Contributor rankRegular Contributor
        6 months ago

        Hi pmarques​ 

        Just to confirm are you using the Pre built hardware design with GSRD2.0 generated uboot and linux kernel?

        If yes please do not mix the hardware design betweehn the GSRD1.0 and GSRD2.0

        Then GSRD2.0 removed the setting of the board_id and the GSRD1.0 still set the use of the board_id.

         

        Please try using the binaries generated for the GSRD2.0, hardware bitstream and software should not be mix and match between the 2.0 and 1.0.