New Contributor
Frequent ContributorHi,
Any specific reason to exclude the NIOS V from the design?
Also, have you changed the SPI clock frequency to 25MHz and 10 sec delay in drivers/mtd/spi/spi-nor-tiny.c as mentioned on rocketboard-https://www.rocketboards.org/foswiki/Documentation/HPSExampleDesignForAgilex7ISeriesDeKit2xRTileAnd1xFTile
Regards
Tiwari
New ContributorHi,
NIOS-V requires a license, which i haven't received yet . I saw in the netlist that HPS not dependent on it, so I removed it, please correct me if my i'm wrong and help me more why need NIOS-V in the GSRD.
I configuring the SPI clock frequency to 25MHz with a delay of 10 seconds in drivers/mtd/spi/spi-nor-tiny.c. I'm not sure how to confirm that this change has been applied to loaded image. Please provide a step to verify if any.
From what I understand qspi u-boot partion data pulls by SDM and stored in ARM's local RAM in AGIB027, which helps ARM to bootup further images partioned in the qspi.
Currently i'm trying below -
1. flash gsrd *.jic to qspi and check its boots up with linux image.
2. Generate an *_auto.sof file merged with u-boot-spl-dtb.hex - (recompiled the file using the procedure given in gsrd)
3. Use quartus programming tool to program *_auto.sof and see if ARM u-boot loads linux from aspi.
Please correct my procedure/my understanding.
Also, how do I load u-boot-spl-dtb.hex directly into HPS. Can this be achieved through system console tools?
Thanks,
Shivaji M
