martinayotte

I remember seeing some patches from @megi about USB3 PHY few days ago ...
We will get those probably in his 5.4.y branch later.

This means it is not "dev" ...
Try this one instead : https://dl.armbian.com/rockpi-4b/nightly/Armbian_5.99.191102_Rockpi-4b_Debian_buster_dev_5.3.0-rc4_minimal.7z
 

Yes ! It is using a U-Boot compatible with LPDDR4 ...

Maybe because you still use the RockPi4B DT and the LED pin is not the same as M4, you need to switch to to proper DT in /boot/armbianEnv.txt by adding this line :
fdtfile=rockchip/rk3399-nanopi-m4.dtb  

Right ! What I did to get eMMC running is I've frist removed it to get u-boot booting, stop it to get at the prompt, then I re-inserted the eMMC carefully while power still present , and boot the SDCard using "setenv devnum 1; run mmc_boot". When SD was booted and I've logged, I used "nand-sata-install" to install/clone the SDCard into eMMC ...

As mentioned in this thread and in another one, use RockPi image, it should boot ...
Then, after initial setup, root password and user creation, add this line "fdtfile=rockchip/rk3399-nanopi-m4.dtb" in /boot/armbianEnv.txt to get proper hardware setting.

As mentioned in this thread and in another one, use RockPi image, it should boot ...
Then, after initial setup, root password and user creation, add this line "fdtfile=rockchip/rk3399-nanopi-m4.dtb" in /boot/armbianEnv.txt to get proper hardware setting.

As mentioned in this thread and in another one, use RockPi image, it should boot ...
Then, after initial setup, root password and user creation, add this line "fdtfile=rockchip/rk3399-nanopi-m4.dtb" in /boot/armbianEnv.txt to get proper hardware setting.

If you look at schematic, you will see that the RJ45 socket of the OPiOne has an integrated transformer built-in ...

When trying to upgrade to newer branch, what I'm usually do when such duplicate nodes appears, instead of disabling patches, I comment out the duplicate offending nodes, and then compile.
Anyway, I will try to find some "missing time ingredient" in the following days, and Armbian will then be ready for a commit ...

Since the PCB itself doesn't route the extra address lines to the SoC, you can't expect to see bigger DDR size than the one provided by manufacturer.
And you're lucky that it still boot, because the extra address lines left unplugged on the DDR are floating, therefore any ESR on those lines could change the current bank and memory could becomes corrupted...

I will try to find some free time, which still the "missing ingredient" ...

Ok ! I will try in the next few days ...

One of my prefered boards is OPiPCPlus, but there is also OPiPlus2E and many others !
It all depends of what is your use-case ...

I did some private builds with that branch, the compile error is cause by AUFS patches, so I've disabled it by passing AUFS=no to compile.sh.
 

Since U-Boot needs to reside somewhere, and since NanoPi-M4 doesn't seem to have any SPI-NOR, it can only boot from either eMMC module, if you have one, or the SDCard, then RootFS can be located on nvme.

I think the Main DT doesn't specify the pin PA5, but the /boot/dtb/overlay/sun8i-h3-pwm.dtbo overlay does ...
So, better use that overlay, simply by adding "overlays=pwm" in the /boot/armbianEnv.txt and reboot.
I did some tests on my OPiZero and it worked, adjusting the period and duty-cycle, etc ...

If you modified a file and wish to revert to git version, simply do "git checkout -- <filename>" ...

My "delete" commit was due to duplicate nodes already present in @megous branch, but I didn't check if his commits was coming from mainstream and were healthy ...
It maybe not only DT issue, but from thermal driver, see here activities in his branch : https://github.com/megous/linux/commits/orange-pi-5.3/drivers/thermal/sun8i_thermal.c
 

No, I've an M2U and don't have the issue, as I've said it is probably that yours has a defective AP6212.
You can avoid DTB updates using "apt-mark hold linux-dtb-dev-meson64_5.94_arm64.deb" for example.

Personally, I will still boot from SD Card to push back the backup image into eMMC .
I don't know much about FEL mode, maybe it could work, but maybe not ...

Merged !

That should be pretty easy to fix by commenting or erasing the duplicate in our patch.
I will look at it ...
 
EDIT: removal of guilty patches is now done !
https://github.com/armbian/build/commit/b53556a5f1ada29169d08b6a106a01f87d763774

That should be pretty easy to fix by commenting or erasing the duplicate in our patch.
I will look at it ...
 
EDIT: removal of guilty patches is now done !
https://github.com/armbian/build/commit/b53556a5f1ada29169d08b6a106a01f87d763774

There is no need to do such backup, since your "rootfs" is on the HDD.
Simply reburn image on new SDCard, do the initial boot setup (passwd & new user), then edit /boot/armbianEnv.txt so that "rootdev=UUID=" point to you HDD according to "blkid" report.