You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to boot Linux on the cv32a6 running on the Nexys video target which has been recently added to the cva6 support. I followed the instructions from the Readme to build my image using make images and flashing the results on a 4Gb SD card using sudo -E make flash-sdcard SDDEVICE=<my_device>.
The OpenSBI firmware and the u-boot seem to execute properly but the boot process gets stuck at the execution of the bootcmd of u-boot to get the kernel. Here is what I get when booting :
When the countdown hits 0, it then hang there without output message. This corresponds to the execution of the boot command configured in u-boot : CONFIG_BOOTCOMMAND="mmc info; mmc read 90000000 100000 7000; setenv fdt_high 0xffffffff; bootm 90000000 - $(fdtcontroladdr)". I observe the same behavior if I manually run mmc command which try to access the mmc device (e.g mmc info, mmc dev, mmc read, ...) : the system gets stuck without error message.
In order to run on the new target, I had to add/modify a few files in the configuration :
Is there an existing CVA6-SDK task for this?
Task Description
Hello,
I am trying to boot Linux on the cv32a6 running on the Nexys video target which has been recently added to the cva6 support. I followed the instructions from the Readme to build my image using
make images
and flashing the results on a 4Gb SD card usingsudo -E make flash-sdcard SDDEVICE=<my_device>
.The OpenSBI firmware and the u-boot seem to execute properly but the boot process gets stuck at the execution of the bootcmd of u-boot to get the kernel. Here is what I get when booting :
When the countdown hits 0, it then hang there without output message. This corresponds to the execution of the boot command configured in u-boot :
CONFIG_BOOTCOMMAND="mmc info; mmc read 90000000 100000 7000; setenv fdt_high 0xffffffff; bootm 90000000 - $(fdtcontroladdr)"
. I observe the same behavior if I manually run mmc command which try to access the mmc device (e.g mmc info, mmc dev, mmc read, ...) : the system gets stuck without error message.In order to run on the new target, I had to add/modify a few files in the configuration :
u-boot/configs/openhwgroup_cv32a6_nexys_defconfig
:Changed uboot baudrate to match the baudrate required by the nexys uart.
Changed device tree target (see next point)
u-boot/arch/riscv/dts/cv32a6_nexys.dts
:Device tree built from https://github.com/openhwgroup/cva6/tree/master/corev_apu/fpga/src/bootrom
I wonder what may be the issue? Where should I look at?
Thank a lot in advance !
Description of Done
I am sorry, I used the "task" template where I should have used of a blank issue.
The text was updated successfully, but these errors were encountered: