> Am 02.02.2020 um 23:01 schrieb Sebastian Reitenbach > <sebas...@l00-bugdead-prods.de>: > > > dd if=miniroot66.fs of=/dev/rsd2c > mount /dev/sd2i /mnt > mkdir /mnt/rockchip > cp /usr/local/share/dtb/arm64/rockchip/rk3328-rock64.dtb /mnt/rockchip > umount /mnt > dd if=/usr/local/share/u-boot/rock64-rk3328/idbloader.img of=/dev/sd2c seek=64 > dd if=/usr/local/share/u-boot/rock64-rk3328/u-boot.itb of=/dev/sd2c seek=16384 >
should be : dd if=miniroot66.fs of=/dev/rsd2c bs=1m dd if=/usr/local/share/u-boot/rock64-rk3328/idbloader.img of=/dev/sd2c bs=512 seek=64 conv=sync dd if=/usr/local/share/u-boot/rock64-rk3328/u-boot.itb of=/dev/sd2c bs=512 seek=16384 conv=sync > the device itself boots the u-boot-erase-spi-rock64.img from > ayufan-rock64/linux-u-boot > Normally u-boot-erase-spi-rock64.img from ayufan is used to erase(delete) the onboard-SPI-flash , not to boot from. If you had erased the SPI you can only boot from SD-card`s u-boot. If you didn’t finish the erase ( so that the SPI is further loaded with ayufan`s u-boot) you should short GPIO- pins 20+21 to be able to boot from the SD-card`s u-boot. Regards Klaus
