RT,

i am trying to use git and aarch64 tools to compile a lastest u-boot by my own,but ,it failed.

there're the steps i was doing:

 

1. downloads the latest u-boot source code from offical web:

       git clone git://git.denx.de/u-boot.git

 

2.downloads the ARM Trusted Firmware from offcial web:

       git clone https://github.com/ARM-software/arm-trusted-firmware

 

3.compile the ATF for BL31 by using this cmd:

        sudo make CROSS_COMPILE=aarch64-linux-gnu- PLAT=sun50i_h6 all

and then move the BL31 file into the u-boot root fold.

 

4. compile the u-boot for H6 by using this cmd:

       sudo make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- orangepi_lite2_defconfig

       sudo make

 

5.burn the u-boot-sunxi-with-spl.bin file on SD card following the README.sunxi64 file

       dd if=u-boot-sunxi-with-spl.bin of=/dev/sdx bs=8k seek=1

 

6.plug in the sd card and connect the uart port and power on,i think and i am sure the default baudrate is 115200,

but when i open the terminal and try to read and debug the u-boot,it displayed as blow:

 

"

膂秜?第曤W -#1?!?!!?!%縠ey濆?y,XWm颟Y纣?搔f鞗df氭停搾MO5Z&?挺?矻歀2撡33N檍曋?攻K/]媬~{紊觙斐─蓲懗逃痔L嫣1ff瞟黍骃娉姒鍸?,XW阱℡骟?搔f袒﹔'Q摀?:ど$$M~迿麚%?驧&?LM?,XW阱?篌?e觙?    猟蓳SU?蓱s筫r潴?騠檽揙鏆SI覔搾1摔2IS撜蓅K蒕?y?W隍?篌螗K+Y篌ed疑扡觵邋歃櫈=y統経i疕H眼鲋謑碇Vm旉V龆諺-赩谥谥獀?鷞徽竖膂鲔鲋鲮+V冬鰈熘霮?鲻鲋黼?娫U蕑
:
妀T脲難_U嬁靠}''-##5縪摽痀Uc暉m隤+镾右?m?姫?岛V雡[}e嬁繚縬-{咫YY^丙U5氇胨u?曞-V雊!=7-#1縰#-!#%5#?!%縮}W＃？U踊蔜?*竖?mm?[けT谠?鶸鲻鲻Vo/V蜒丙T谠?鶸鲻鲻Vo创禧T谠?鶸鲻鲻Vo央j鬕猨艋t轸氇ti

篢鳆埚镲镫?镲稃??FDKQч?在t蚤?iR羲鹶??%9熆-?5#?5-95咫档k?氷:j胡趖詑?i译鯷[+?=-#1縐Y{＃ｅ隿!?!#!''5?!#7咫UY{??!57？_'5=5?5勘;?=笨3-ｅ?=-#1縐Y{＃ｅ隿!?!#!''5?!#7咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁5-7咫%--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31煙煙煙熷隿!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31煙煙煙咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31煙煙熷隿!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31煙煙咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31煙熷隿!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31煙咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31熷隿!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31?53='?%?#-咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31?53='?%咫c!?/5#5?!#7ｅ?--#1?#-!#%5#?=-=;'5嬁;!!3-'5咫[5-5-#1?-'5嬁5'-#?31?53='咫c!?/5#5?!#7ｅ難!#3-1?-'5?!?!#7咫=-#1縐Y{＃ｅ隿!?!#!''5?!#7咫c!?/5#5?!#7ｅ?"

 

(sorry for unable to paste the sreenshot.....)

 

i can't read anything...

 

can you help me?

thx so much!!!

i tried to solve it from google

 

some said the CPU CLK is incorret, but i don't know how to check it.....

6 hours ago, Ayuan_H0n9 said:

i am trying to use git and aarch64 tools to compile a lastest u-boot by my own,but ,it failed.

Why you don't use Armbian build script to create a working u-boot ?

i tried,but failed the same, even cant read a word, that is the question

 

so i have to make sure that the serial port works fine and i can read the debug info

 

can you give me one more hand? thank y

5 hours ago, Ayuan_H0n9 said:

can you give me one more hand?

Did you tried the images from there : https://dl.armbian.com/orangepilite2/

 

i tried the latest bionic image but failed ,let me tried the debian image now 

I tried a few also, can anyone point out a definitely working image? I've heard that some images need more power than common USB chargers provide, which I find kinda strange.

 

Anyway, out of those that are provided on official site I have OrangePi_Lite2_Ubuntu16.04_Desktop_Xfce_Beta.tar.gz and OrangePi_Lite2_Android_7.0_en_gapps_v1.3.img.tar.gz working.

 

I don't expect HDMI to work, but those that I tried didn't even give green LED.

haha me too~

when i done burned those two images and power on, nothing happened,it's so wired.....

that is why i planed to compile a u-boot and kernel from the offical site

i don't use HDMI, uart port is okay, also console

I was wrong, it works fine https://forum.armbian.com/topic/9107-lite2-can-someone-share-a-working-image-with-me/

 

I have two USB ethernet devices, one worked, one didn't. In USB2 port though, not USB3.