I've been (trying) to move the Tinker and MiQi u-boots to 2020.07, however if I use any of the following:

 

A MiQi,

A Tinker S

an image for a Tinker S

an image for a Tinker on a Tinker S

 

I get stuck in the initramfs busybox with it telling me the filesystem is toast.  The only 2020.07 combo I've gotten to boot is the Tinker with the non-eMMC supporting u-boot.  As for clues, I haven't found any, the u-boot source code is of course very well organized for debugging purposes  :lol:.

 

If anyone has an idea about what could be going on with this let me know, I'm shelving the effort to think about other stuff.

Hmm, strange, I'm currently using u-boot-2020.10-rc4 (similar to 2020.07) on rk3288 and don't see any problems starting u-boot and the system. Can you try running my image and show the UART log ? I have observed a similar problem with starting the system on rk3399 (rocky 4b) from the SD card due to the kernel configuration features.

I got a sencond hand tinker board. and plan to falsh mainline u-boot.

 

find 

 

Quote

Flashing
--------

1. Package the image with U-Boot TPL/SPL
-----------------------------------------

SD Card
^^^^^^^

All Rockchip platforms (except rk3128 which doesn't use SPL) are now
supporting a single boot image using binman and pad_cat.

To write an image that boots from a SD card (assumed to be /dev/sda):

.. code-block:: bash

        sudo dd if=u-boot-rockchip.bin of=/dev/sda seek=64
        sync

eMMC
^^^^

 

due to tinker board don't have emmc, thus SDcard boot.

so can I use this instruction directly.