Forum Discussion
Linux not booting - can't get kernel image
- 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.
Hi again tehjingy_Altera,
I don't know if you had to opportunity to see my previous reply but in the meantime I've been doing some more testing.
I just compiled a fresh default build as described in Rebuilding GSRD 2.0 Binaries. and compared the kernel.itb dump and the printenv output with my custom project.
The kernel.itb dump is the same but the printenv output has some differences:
board_id=4 instead of 0;
Different bootargs;
bootfstype, fileaddr and filesize parameters are missing entirely.
Do you know what could be causing this ? I'm attaching the printenv log files.
Best regards,
PM.
- tehjingy_Altera7 months ago
Regular Contributor
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
- pmarques7 months ago
New Contributor
Hi tehjingy_Altera,
Yes, the board boots successfully with a compiled default GSRD2.0 build. Printenv shows board_id=0.
Best regards,
PM.
- tehjingy_Altera7 months ago
Regular Contributor
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
- tehjingy_Altera6 months ago
Regular Contributor
Hi pmarques
Thanks for you patience!
I managed to reproduce the issue here.
It seems like the board_id was not updated to reflect the new kernel.itb configuration.
Let me try out some changes on my end before I shared it to you.