пн, 20 мая 2019 г. в 20:11, Vagrant Cascadian <vagr...@debian.org>: > > On 2019-05-19, Matwey V. Kornilov wrote: > > The ROCK64 is a credit card size SBC based on Rockchip RK3328 > > Quad-Core ARM Cortex A53. > > > > This series allow building u-boot SPL and u-boot.itb for Rock64 > > board. The proprietary TPL is stil required for deploy: > > > > ./tools/mkimage -n rk3328 -T rksd \ > > -d ./rkbin/bin/rk33/rk3328_ddr_333MHz_v1.14.bin idbloader.img > > cat ./spl/u-boot-spl.bin >> idbloader.img > > dd if=idbloader.img of=/dev/sdcard seek=64 conv=notrunc > > dd if=u-boot.itb of=/dev/sdcard seek=16384 conv=notrunc > > Could you add a patch documenting this in doc/README.rockchip or a > board-specific README? That would be more useful than having to search > the git commit messages or mailing list archives. > > > Tested this patch series against v2019.07-rc2, and I was able to pxe > boot fine, but unfortunately was unable to boot from microSD. > > I presume this is caused by some other change since v2019.07-rc1, since > the earlier rock64 patches worked fine with microSD on v2019.07-rc1.\
Thanks for the report. This series is based on 98b3156b0df4 At least bootefi works fine for me. Do v1 patches works for you on v2019.07-rc2? > > Scanning mmc 1:6... > Found /boot/extlinux/extlinux.conf > Retrieving file: /boot/extlinux/extlinux.conf > 1953 bytes read in 4 ms (476.6 KiB/s) > U-Boot menu > 1: Debian GNU/Linux kernel 5.1.0-trunk-arm64 > 2: Debian GNU/Linux kernel 5.1.0-trunk-arm64 (rescue target) > 3: Debian GNU/Linux kernel 5.0.0-trunk-arm64 > 4: Debian GNU/Linux kernel 5.0.0-trunk-arm64 (rescue target) > 5: Debian GNU/Linux kernel 4.19.0-5-arm64 > 6: Debian GNU/Linux kernel 4.19.0-5-arm64 (rescue target) > Enter choice: 1 > 1: Debian GNU/Linux kernel 5.1.0-trunk-arm64 > Retrieving file: /boot/initrd.img-5.1.0-trunk-arm64 > ** fs_devread read error - block > Skipping l0 for failure retrieving initrd > 2: Debian GNU/Linux kernel 5.1.0-trunk-arm64 (rescue target) > Retrieving file: /boot/initrd.img-5.1.0-trunk-arm64 > *** ERROR: Can't read GPT Entries *** > GPT: Failed to allocate memory for PTE > part_get_info_efi: *** ERROR: Invalid GPT *** > *** ERROR: Can't read GPT header *** > > I enabled CONFIG_CMD_CACHE=y and tried "dcache off" but that didn't > appear to help anything. Any other suggestions? > > > live well, > vagrant -- With best regards, Matwey V. Kornilov _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
