Experiencing booting issues. Before issue updated GPIOs of SoC.
Here are the logs: DDR Version 1.30 20230417Inchannel 0CS = 0MR0=0x18MR4=0x2MR5=0x1MR - Pastebin.com
Experiencing booting issues. Before issue updated GPIOs of SoC.
Here are the logs: DDR Version 1.30 20230417Inchannel 0CS = 0MR0=0x18MR4=0x2MR5=0x1MR - Pastebin.com
Here, you can find some steps to follow
ext4load mmc 1:4 ${kernel_addr_r} Image-5.10.160-vaaman
ext4load mmc 1:4 ${fdt_addr_r} rk-kernel.dtb
setenv rootdev /dev/mmcblk1p8
setenv verbosity 4
setenv bootargs "console=ttyS2,1500000n8 loglevel=${verbosity} root=${rootdev} rw rootfstype=ext4 rootwait"
booti ${kernel_addr_r} - ${fdt_addr_r}
No Image-5.10.160-vaaman file present
In this case, If Kernel Image is not there in boot partition then,
you need to build the kernel Image first and then copy in the boot partition /dev/mmcblk1p4
Build Kernel For Vicharak Boards like Vaaman :
Build Vicharak Kernel from source | Vicharak
Copy the Kernel Image which you can find in out/arch/arm64/boot/Image
.
Connect Type-C to the USB cable from Vaaman to the host PC. you can access emmc storage by running this command.
mmc list
you can get the emmc number x
using mmc list
command.
ums 0 mmc x
In host PC, you can get all the partition of emmc storage.
Copy and rename as Image-5.10.160-vaaaman
in /dev/mmcblk1p4 partition.
Note : Run ls -l
command in /dev/mmcblk1p4 partition, verify that rk-kernel.dtb is linked with rk3399-vaaaman-linux.dtb
file.