martinayotte

You need to figure out which log is getting too big in /var/log, then from that log, figure out which application doing so much logging, and maybe tweak the config of this application to be less verbose ...

Normally, even if 001-boot-order-prioritize-sd.patch is still present, if you erase the first 1MB of the SD (filling it with zeros), it won't try to boot from SD since it doesn't find the u-boot magic numbers.

Start by reading https://docs.armbian.com/Developer-Guide_Build-Preparation/ Just be aware, it won't be 5.1.15 any more, but 5.5.y ...

No ! Impossible ...

As I said, don't mix NEO and NEO2 images, they don't have the same CPU ! The picture you've provided shows that your board is a NEO not a NEO2, so, use the proper image ...

Merged ...

Maybe somewhere is this location : https://dl.armbian.com/_old/

Not from what we can see on schematic, those are SPI1 pins, UART1 pins are 10 & 11. http://wiki.friendlyarm.com/wiki/images/8/8a/Schematic_NanoPi_Duo-v1.1.pdf

This seems to show that filesystem is probably corrupted ... EDIT: Since you wrote : This means you are trying several SDCards, but is the eMMC on the Rock64 still active ? Because eMMC has boot priority over SDCard. You should then place a jumper on 2 pins header or disconnect the eMMC module from the board ...

I'm seeing in your boot log "Armbian Linux 3.4.113-sun8i", this is a Legacy image, and Legacy images doesn't support DT overlays at all ! You should try with Mainline "current" or "dev" images ...

No, since fixup.scr is per family, not per board, and you listing shows the presence of rockchip-fixup.scr. I still don't understand why we are seeing FDT_ERR_NOTFOUND in u-boot logs ... Could you stop u-boot and provide the output of "printenv" ? EDIT: I think I've found a clue about FDT_ERR_NOTFOUND... Most of those overlays were written with RK3399 in perpective, but looking at Main DT using "fdtdump /boot/dtb/rockchip/rk3328-roc-cc.dtb", I don't see any "uart4", as well as "spi1/spi2/spi3", there is only one SPI0, so it is probably why the overlay refuse to be loaded ... You will then need a custom overlay that only try to touch SPI0.

Also, don't mix up between NEO and NEO2, they are not the same processors, the first is a H3 and the second H5, so using the wrong image make them not booting at all ...

This is not an Armbian image ... Try one of those : https://dl.armbian.com/nanopineo2/

Quote from https://linux-sunxi.org/H6 : As you can read, it is an hardware issue, nothing about Armbian images. I doubt anyone spend time to hack existing SATA or SSD drivers to make it work with H6 PCIe address space limitation.

Armbian doesn't have any Legacy kernel for H6. NAND chips are kind of obsolete, which is why Mainline kernels don't support those. Modern boards are now using eMMC...

Maybe get more details by setting "verbose=7" in /boot/armbianEnv.txt ...

Such "spi-spidev0" overlay doesn't exist by default. Did you wrote your own ? The one that exist is : overlays=spi-spidev param_spidev_spi_bus=0 Also, your u-boot log is truncated, we don't see the part where overlays are loaded ...

NAND is not supported in any Mainline kernel, only in Legacy ...

No needs ! But check the presence of this folder "ls -l /boot/dtb/rockchip/overlay/", I suspect it is not there since you got FDT_ERR_NOTFOUND ...

Yes, if SDCard is bigger than eMMC, simply use "dd" ...

So, somehow, the overlay didn't do its job ! Let see when you will get the USB-TTL dongle ...

It should, but just at left of the prompt, since doesn't include a newline, it should either "disabled" or "okay" .

No ! U-Boot logs are only seen thru Serial Debug ! What " cat /proc/device-tree/spi@ff190000/status " is reporting ?

That depends ... You can have such bash script too started /etc/rc.local : #!/bin/bash echo none >/sys/class/leds/blue\:heartbeat/trigger while true; do echo 0 > /sys/class/leds/blue\:heartbeat/brightness sleep 0.25 echo 255 > /sys/class/leds/blue\:heartbeat/brightness sleep 0.25 done Then, it will toogle/flash and will stop if kernel is frozen ...

Did you have done a backup of Android before installing Armbian ?