martinayotte

http://linux-sunxi.org/images/e/e0/Orange-Pi-Zero-Schanetics-v1_11.pdf
or
http://www.orangepi.org/download/orange_pi-zero-v1_11.pdf

You need to install DT compiler from : http://ftp.debian.org/debian/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-3_arm64.deb
 
Backup /boot/dtb/rockchip/rk3399-rockpi4b.dtb into /boot/dtb/rockchip/rk3399-rockpi4b.dtb-ORIG
 
Decompile the DTB into DTS :
dtc -@ -I dtb -O dts -o rk3399-rockpi4b.dts-4.20.0 /boot/dtb/rockchip/rk3399-rockpi4b.dtb Edit the file rk3399-rockpi4b.dts-4.20.0 by changing all the serial node from "disabled" to "okay", then recompile DTB :
dtc -@ -I dts -O dtb -o /boot/dtb/rockchip/rk3399-rockpi4b.dtb rk3399-rockpi4b.dts-4.20.0  

Without any logs, it is difficult to understand which issue you're facing, because it should work as is ...

I don't have one either, mine is v1, but yes that should be the trick ...

Maybe later ... I don't want to get indigestion doing too much branch switching ...

SPI Update done ! Now working perfectly ! I've booted my USB dongle without any eMMC or SDCard ...
 
Many Thanks !
 

SPI Update done ! Now working perfectly ! I've booted my USB dongle without any eMMC or SDCard ...
 
Many Thanks !
 

On 5.1.y, it has been changed to /sys/devices/platform/leds/leds/orangepi:red:power/trigger

First, install the DT compiler : http://ftp.debian.org/debian/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-3_arm64.deb
Next, copy the /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb into /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb-ORIG as backup.
Third, decompile it into DTS :
dtc -@ -I dtb -O dts -o /root/sun50i-h6-orangepi-one-plus.dts-5.1.0 /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb Fourth, edit the file /root/sun50i-h6-orangepi-one-plus.dts-5.1.0 by adding this in the aliases node :  ethernet0 = "/soc/ethernet@5020000";
Fifth, recompile the DTB and reboot :
dtc -@ -I dts -O dtb -o /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb /root/sun50i-h6-orangepi-one-plus.dts-5.1.0 About "cpu-freq", I don't really know, I'm not the expert on this one ...

First, install the DT compiler : http://ftp.debian.org/debian/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-3_arm64.deb
Next, copy the /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb into /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb-ORIG as backup.
Third, decompile it into DTS :
dtc -@ -I dtb -O dts -o /root/sun50i-h6-orangepi-one-plus.dts-5.1.0 /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb Fourth, edit the file /root/sun50i-h6-orangepi-one-plus.dts-5.1.0 by adding this in the aliases node :  ethernet0 = "/soc/ethernet@5020000";
Fifth, recompile the DTB and reboot :
dtc -@ -I dts -O dtb -o /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb /root/sun50i-h6-orangepi-one-plus.dts-5.1.0 About "cpu-freq", I don't really know, I'm not the expert on this one ...

Another Good Catch !
We had a fix done almost 2 months ago, by adding missing alias in DT, but it seems that this was lost during the switch from 5.0.y to 5.1.y ...
Fix committed : https://github.com/armbian/build/commit/7cd2f9ff58a5bb9e4b8296b32d8796fccbd0338b
 

None of my 12 card have one too. I've never seen that message ...
But googling this message reveal that people were facing either corruptions or defects.
Try another card, it will help to figure out !

No ! Look at the schematic ...
They are out and controlled by the SATA controller so it can switch them off by software.
 
 

I use VM to run Windows. I don't use any native Windows since more than 12 years, I think my first VM was Windows 2000, I have a backup of that VM somewhere ...

Not related !
But Good Catch !
The status was "disabled" and "phy" missing ...
Fixed for tomorrow's build !

I think @Igor added that restriction few days ago : new comers with less then 5 posts can't post in Development subforum.
 

I don't see such crash on my Pine64 with 5.1.0 ...
 
EDIT : I don't see such crash on my OrangePiWin either with 5.1.0 ...

It is not actually provided in any DT nodes ...
I will add it in the following days, directly in main DT, without any needs for overlay.
Then, you will need to take a new nightly image ...

Edit the /boot/armbianEnv.txt to add more verbosity with "verbosity=7" and "console=serial" and repost the logs ...
Please, check the other thread here and my following posts, something strange :
 
 

Strangely, I've put back the original DTB and it still working ...
I will try again with a "virgin" image.
 
EDIT : I took another SDCard, reburned 5.0.10, and this time, although still showing those "cpufreq" error, it booted successfully, although "filesystem resize" took more time than usual ...

As I don't want to undo the work I've done for 5.1.y, I've decided to download https://dl.armbian.com/orangepioneplus/nightly/Armbian_5.83.190502_Orangepioneplus_Debian_stretch_dev_5.0.10.7z instead.
Effectively, it seems broken, stopping/freezing during boot with the following errors :
[ 6.550967] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 912000 KHz [ 6.558474] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1080000 KHz This must have been introduced between 5.0.7 and 5.0.10 ... I will investigate a bit more ...
 
EDIT : I found something, replacing the 5.0.10 DTB by the one of 5.0.7 allows booting successfully ! ... I will compare them ...

As I don't want to undo the work I've done for 5.1.y, I've decided to download https://dl.armbian.com/orangepioneplus/nightly/Armbian_5.83.190502_Orangepioneplus_Debian_stretch_dev_5.0.10.7z instead.
Effectively, it seems broken, stopping/freezing during boot with the following errors :
[ 6.550967] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 912000 KHz [ 6.558474] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 1080000 KHz This must have been introduced between 5.0.7 and 5.0.10 ... I will investigate a bit more ...
 
EDIT : I found something, replacing the 5.0.10 DTB by the one of 5.0.7 allows booting successfully ! ... I will compare them ...

That is what I do all the time, the nand-sata-install is working fine.
Then, if I wish to boot from SDCard, even if U-Boot is start booting from eMMC as priority, I'm stopping it with <spacebar>, then do "mmc list" to see SDCard number, and do "setenv devnum 1" followed with "run mmc_boot", it will then continue booting from SDCard ...

No problem, as I said the resulting "dmas = <0xa8 0xf 0xa8 0xf>;" is good !
No worries ! But that would be a good opportunity and challenge ...

Right ! Every SoC users should have a USB-TTL Serial dongle nearby !
(I've more than 10 of them, leaving them connected on all boards where I do frequent updates)
My OrangePi3 is currently working with 5.1.0-rc4 from eMMC ...