how can I boot completely from sd and get rid of the green screen. I want to use mandjaro. When the green screen problem is completely resolved. Please detailed instructions, I just do not know English well and it’s hard for me to understand the firmware
Here are some options I have posted.
which Android should I use?
You either need to use mainline u-boot or chainload mainline u-boot from the vendor u-boot; this is done via the boot autoscript files and a new (mainline) u-boot file.
Hi @chewitt i have question 4u maybe u can know solution some times ago i have test it and …
- i can boot vendor u-boot from mainline u-boot by chainloading via
- i can boot mainline u-boot from mainline u-boot by chainloading via
- but i cant boot mainline u-boot from vendor u-boot its freezed …
kvim3l#ver U-Boot 2015.01-g6ab671a0b4-dirty (Jan 04 2020 - 13:03:09) aarch64-none-elf-gcc (crosstool-NG linaro-1.13.1-4.8-2013.11 - Linaro GCC 2013.10) 4.8.3 20131111 (prerelease) GNU ld (crosstool-NG linaro-1.13.1-4.8-2013.11 - Linaro GCC 2013.10) 220.127.116.1130610 Linaro 2013.10-4 kvim3l#load mmc 0 $loadaddr u-boot.ml.bin reading u-boot.ml.bin kvim3l#go $loadaddr 696103 bytes read in 43 ms (15.4 MiB/s) ## Starting application at 0x01080000 ... .......FREEEEEZZZZ..............
checked again today on VIM2! same fail if we try load mainline uboot from vendor !!! may be smbdy have some ideas about it
kvim2#load mmc 0 $loadaddr u-boot.vim2.bin && go $loadaddr reading u-boot.vim2.bin 664369 bytes read in 41 ms (15.5 MiB/s) ## Starting application at 0x01080000 ... initcall sequence 00000000010e6410 failed at call 0000000001015550 (err=16864592) ### ERROR ### Please RESET the board ###
PS: but chainload vendor uboot from mainline still works !
IMHO chainloading is not required on any Khadas board because mainline u-boot supports all of your boards. Just write an image with mainline u-boot direct to the eMMC, boot using a simple extlinux.conf and avoid all the autoscript and multi-boot complexity. If people want to run another distro … go write that image (with appopriate u-boot) to eMMC instead. I’m not entirely surprised things don’t work from vendor u-boot.
mainline uboot supported all boards but with many limits
for example spifc - like many other things not work
So what’s your plan to add spifc support to mainline u-boot?