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 

 

The binaries required to boot are the same between the GSRD and GSRD2.0.

 

 

First, lets check your kernel.itb that is stored in your mmc0.

In your host could you try out the command "  dumpimage -l  kernel.itb" and share the output?

 

In the device uboot stage, could you try printenv to see the uboot environment of the board?

 

 

Regards

tehjingy

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

      Hi pmarques

       

      It seems like the kernel.itb that you generated is incorrect.

      As you see the kernel.itb do not consist a configuration3 ( board 4) 

       

      e.g Pre-built Kernel.itb

       

       

      That is the configuration for the uboot environment.

      Could you try booting the board with the pre-built sdcard image?

       

      Regards

      tehjingy

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

      Hi pmarques 

       

      Did you managed to try out the pre-built kernel.itb?

       

      Regards

      tehjingy

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

        Hi tehjingy,

        Apologies for the delay,

        I just tried the pre-built sdcard image and the board boots fine.

        I have previously also managed to build the default image by following the workflow detailed here: Rebuilding GSRD 2.0 Binaries and it booted fine in our devkit.

        Then the only modifications I have made were:

        • Replaced the default Quartus project with our custom project;
        • Made a small modification to the Makefile in order to skip the IP simulation (removed highlights below):

        Best regards,

        PM.