Hi everyone,

I tried the 20.11.3 version of Armbian, I have manually updated the SPI with U-boot using armbian-config (after an apt update && apt upgrade), but it doesn't start from a PCIe NVME SSD :-/

Is there something that I have missed? Any idea is more than welcome !

Here is my serial - USB console output:

Spoiler

$ picocom -b 1500000 -r -l /dev/tty.usbserial-144310 

picocom v3.1

 

port is        : /dev/tty.usbserial-144310

flowcontrol    : none

baudrate is    : 1500000

parity is      : none

databits are   : 8

stopbits are   : 1

escape is      : C-a

local echo is  : no

noinit is      : no

noreset is     : yes

hangup is      : no

nolock is      : yes

send_cmd is    : sz -vv

receive_cmd is : rz -vv -E

imap is        : 

omap is        : 

emap is        : crcrlf,delbs,

logfile is     : none

initstring     : none

exit_after is  : not set

exit is        : no

 

Type [C-a] [C-h] to see available commands

Terminal ready

 

U-Boot TPL 2020.07-armbian (Dec 12 2020 - 02:09:32)

Channel 0: LPDDR4, 50MHz

BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB

Channel 1: LPDDR4, 50MHz

BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB

256B stride

256B stride

lpddr4_set_rate: change freq to 400000000 mhz 0, 1

lpddr4_set_rate: change freq to 800000000 mhz 1, 0

Trying to boot from BOOTROM

Returning to boot ROM...

 

U-Boot SPL 2020.07-armbian (Dec 12 2020 - 02:09:32 +0100)

Trying to boot from SPI

NOTICE:  BL31: v1.3(debug):42583b6

NOTICE:  BL31: Built : 07:55:13, Oct 15 2019

NOTICE:  BL31: Rockchip release version: v1.1

INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3

INFO:    Using opteed sec cpu_context!

INFO:    boot cpu mask: 0

INFO:    If lpddr4 need support multi frequency,

INFO:    please update loader!

INFO:    Current ctl index[0] freq=400MHz

INFO:    Current ctl index[1] freq=800MHz

INFO:    plat_rockchip_pmu_init(1190): pd status 3e

INFO:    BL31: Initializing runtime services

WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK

ERROR:   Error initializing runtime service opteed_fast

INFO:    BL31: Preparing for EL3 exit to normal world

INFO:    Entry point address = 0x200000

INFO:    SPSR = 0x3c9

 

U-Boot 2020.07-armbian (Dec 12 2020 - 02:09:32 +0100)

 

SoC: Rockchip rk3399

Reset cause: POR

Model: Pine64 RockPro64 v2.1

DRAM:  3.9 GiB

PMIC:  RK808 

MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0

Loading Environment from SPI Flash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB

*** Warning - bad CRC, using default environment

 

In:    serial

Out:   serial

Err:   serial

Model: Pine64 RockPro64 v2.1

Net:   eth0: ethernet@fe300000

Hit any key to stop autoboot:  0 

Card did not respond to voltage select!

Card did not respond to voltage select!

 

Device 0: Vendor: 0x1cc1 Rev: 32B3T8EA Prod: 2K422LAAKCKF        

            Type: Hard Disk     Capacity: 1953514.3 MB = 197.7 GB (4000797360 x 512)

... inow current device

Scanning nvme 0:3...

Found U-Boot script /boot/boot.scr

3185 bytes read in 2 ms (1.5 MiB/s)

## Executing script at 00500000

Boot script loaded from nvme 0

libfdt fdt_check_header(): FDT_ERR_BADMAGIC

No FDT memory address configured. Please configure

the FDT address via "fdt addr <address>" command.

Aborting!

Bad Linux ARM64 Image magic!

SCRIPT FAILED: continuing...

starting USB...

Bus usb@fe380000: USB EHCI 1.00

Bus usb@fe3a0000: USB OHCI 1.0

Bus usb@fe3c0000: USB EHCI 1.00

Bus usb@fe3e0000: USB OHCI 1.0

Bus dwc3: usb maximum-speed not found

Register 2000140 NbrPorts 2

Starting the controller

USB XHCI 1.10

scanning bus usb@fe380000 for devices... 1 USB Device(s) found

scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found

scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found

scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found

scanning bus dwc3 for devices... 1 USB Device(s) found

       scanning usb for storage devices... 0 Storage Device(s) found

 

Device 0: unknown device

Speed: 1000, full duplex

BOOTP broadcast 1

BOOTP broadcast 2

BOOTP broadcast 3

BOOTP broadcast 4

BOOTP broadcast 5

BOOTP broadcast 6

DHCP client bound to address 192.168.1.201 (5776 ms)

*** ERROR: `serverip' not set

Cannot autoissing environment variable: pxeuuid

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/01-36-ba-2b-e0-95-c0

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A801C9

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A801C

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A801

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A80

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A8

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0A

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C0

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/C

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm-rk3399-rockpro64_rk3399

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm-rk3399

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm

Speed: 1000, full duplex

*** ERROR: `serverip' not set

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default

Speed: 1000, full duplex

*** ERROR: `serverip' not set

Config file not found

Speed: 1000, full duplex

BOOTP broadcast 1

DHCP client bound to address 192.168.1.201 (17 ms)

*** ERROR: `serverip' not set

Cannot autoload with TFTPGET

Speed: 1000, full duplex

BOOTP broadcast 1

DHCP client bound to address 192.168.1.201 (46 ms)

*** ERROR: `serverip' not set

Cannot autoload with TFTPGET

SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB

device 0 offset 0xffe000, size 0x2000

SF: 8192 bytes @ 0xffe000 Read: OK

## Executing script at 00500000

Wrong image format for "source" command

SCRIPT FAILED: continuing...

=>

 

Kind regards,

Baptiste

Did it work as U-Boot was still on a SD card?

Yes, it still works (with the eMMC card).

On 12/27/2020 at 2:24 AM, Baptiste said:

Is there something that I have missed?

SPI boot feature was enabled for Rockpi4 boards which is why its in the menu, but perhaps we should add one IF. So far we have no plans to support RockPro64.

On 12/29/2020 at 12:17 PM, Igor said:

So far we have no plans to support RockPro64.

Well... I apparently enabled it also for RockPro64 by accident while doing some merges between branches ;-)

I had the intention to do this at some point anyway...

 

On 12/27/2020 at 2:24 AM, Baptiste said:

Is there something that I have missed? Any idea is more than welcome !

Are you sure that your nvme0n1p3 partition contains all files in /boot dir?

It seems like it is not loading /boot/uInitrd, /boot/Image or /boot/dtb/rockchip/rk3399-rockpro64.dtb although /boot/boor.scr is loaded.

If you are sure you have those files (did you move your Armbian there with nand-sata-install?) maybe u-boot has issues reading from this particular drive.

I see it's ADATA SX8200 Pro and I had no confirmation that it works properly in SPI/NVMe scenario but that also means nothing - maybe no-one simply reported it yet.

@Piter75, Just FYI,  Booting  a a Samsumg pm980 nvme from spi_flash with your new 20.10 u-boot (from your   

rockchip64-u-boot-v2020.10 branch         )  works most of the time.   This is a build made from playing with the desktop stuff, hirsute with gnome...

 

Spoiler

U-Boot TPL 2020.10-armbian (Jan 01 2021 - 16:45:25)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.10-armbian (Jan 01 2021 - 16:45:25 -0500)
Trying to boot from SPI
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    If lpddr4 need support multi frequency,
INFO:    please update loader!
INFO:    Current ctl index[0] freq=400MHz
INFO:    Current ctl index[1] freq=800MHz
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

U-Boot 2020.10-armbian (Jan 01 2021 - 16:45:25 -0500)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB
PMIC:  RK808 
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 3 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 Timeout poll on interrupt endpoint

Timeout poll on interrupt endpoint
Card did not respond to voltage select!
Timeout poll on interrupt endpoint
Card did not respond to voltage select!
Timeout poll on interrupt endpoint

Device 0: Vendor: 0x144d Rev: EXD7101Q Prod: S444NE0K603440      
            Type: Hard Disk
            Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Timeout poll on interrupt endpoint
Scanning nvme 0:1...
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
Found U-Boot script /boot/boot.scr
3185 bytes read in 2 ms (1.5 MiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
165 bytes read in 2 ms (80.1 KiB/s)
15062500 bytes read in 28 ms (513 MiB/s)
28449280 bytes read in 51 ms (532 MiB/s)
75990 bytes read in 3 ms (24.2 MiB/s)
Timeout poll on interrupt endpoint
Timeout poll on interrupt endpoint
2698 bytes read in 3 ms (877.9 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3dc0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15062436 Bytes = 14.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f10b2000, end f1f0f5a4 ... OK
   Loading Device Tree to 00000000f1037000, end 00000000f10b1fff ... OK

Starting kernel ...

Armbian 21.02.0-trunk Hirsute ttyS2 

rockpro64 login: 
 

It normally works--every once in a while it seems to not get past  

 

 Booting using the fdt blob at 0x1f00000

 

not sure what is causing that yet,  or the constant :

 

Timeout poll on interrupt endpoint

 

I did manually clear previous spi_flash and used nand-sata-install  to install the build and new  spi flash.  

I've also noticed that when asked to update spi flash,  it seems like the script will error if it doesn't find an spi_flash,  but does not try to erase it if it has been written,  andwill fail without any error message if  a  program already exists there...

 

I apologize in advance if the spoiler is not hide-able--I can't seem to make that happen 

@belfastraven thanks for testing!

Would you be also able to test SPI/NVMe with one of the official Armbian images?

v20.11.3 already have the rkspi_loader.img bundled ;-)

 

8 hours ago, belfastraven said:

every once in a while it seems to not get past  

 

 Booting using the fdt blob at 0x1f00000

I have noticed that one too while testing v2020.10 switch yesterday. It fails also with simple SD boot.

For me it was 3 failures with 3 tries but it was already late and I decided to look into that on one of the coming days.

 

8 hours ago, belfastraven said:

or the constant :

Timeout poll on interrupt endpoint

I did not notice this one with my ROCK Pi 4 tests. For proper RockPro64 tests I still need to get the passthrough PCIE to m.2 card.

 

8 hours ago, belfastraven said:

I've also noticed that when asked to update spi flash,  it seems like the script will error if it doesn't find an spi_flash

I will verify the not found spi flash scenario. Do you mean that the SPI chip was not recognised and there was no error in the nand-sata-install?

 

8 hours ago, belfastraven said:

but does not try to erase it if it has been written,  andwill fail without any error message if  a  program already exists...

Do you mean it does not work without manual clearing the SPI before nand-sata-install?

Strange, I specifically chosen to use dd with /dev/mtdblock0 for writing so that mtd-utils dependency was not needed and verified that it clears the blocks before writing new content.

But still... this is pretty fresh so maybe I missed something.

7 hours ago, piter75 said:

@belfastraven thanks for testing!

Would you be also able to test SPI/NVMe with one of the official Armbian images?

v20.11.3 already have the rkspi_loader.img bundled ;-)

I will test later today with an official image

7 hours ago, piter75 said:

 

I

I will verify the not found spi flash scenario. Do you mean that the SPI chip was not recognised and there was no error in the nand-sata-install?

No I mean that you will get an error if the device doesn't have (pysically)  an API_FLASH unit,  

 

Do you mean it does not work without manual clearing the SPI before nand-sata-install?

Yes--I believe that to be the case.   You certainly know more about this than I do,  but I found that if I already had something written to SPI_FLASH  ( I was playing with sigmaris's build)  the if I used the NAND_SATA_INSTALL update the SPI_FLASH.  It would return almost immediately with no error and obviously not having written the flash....  If I cleared it first,  it did come back after a while that it had written the flash.    I can certainly try again and see what happens.  

     

7 hours ago, piter75 said:

Strange, I specifically chosen to use dd with /dev/mtdblock0 for writing so that mtd-utils dependency was not needed and verified that it clears the blocks before writing new content.

But still... this is pretty fresh so maybe I missed something.

 

@piter85,  here's result of testing with official build,  which uses 20.7, u-boot, I see:

 

Bourd booted fine without all of those""Timeout poll on interrupt endpoint"  spams,  using nand-sata-install overwrote the spi_flash just fine ( as you can see :-) )     and without this error,  which I imagine would have been fixed by your most recent patch anyway?

 

Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

 

 

Spoiler

-Boot TPL 2020.07-armbian (Dec 12 2020 - 02:09:32)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.07-armbian (Dec 12 2020 - 02:09:32 +0100)
Trying to boot from SPI
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    If lpddr4 need support multi frequency,
INFO:    please update loader!
INFO:    Current ctl index[0] freq=400MHz
INFO:    Current ctl index[1] freq=800MHz
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

U-Boot 2020.07-armbian (Dec 12 2020 - 02:09:32 +0100)

SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPI Flash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Pine64 RockPro64 v2.1
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
Card did not respond to voltage select!

Device 0: Vendor: 0x144d Rev: EXD7101Q Prod: S444NE0K603440      
            Type: Hard Disk
            Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)
... is now current device
Scanning nvme 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 2 ms (1.5 MiB/s)
## Executing script at 00500000
Boot script loaded from nvme 0
165 bytes read in 2 ms (80.1 KiB/s)
15788878 bytes read in 30 ms (501.9 MiB/s)
27507200 bytes read in 50 ms (524.7 MiB/s)
75803 bytes read in 3 ms (24.1 MiB/s)
2698 bytes read in 2 ms (1.3 MiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15788814 Bytes = 15.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f0ff8000, end f1f06b0e ... OK
   Loading Device Tree to 00000000f0f7d000, end 00000000f0ff7fff ... OK

Starting kernel ...

[    7.927446] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
[   10.176477] Bluetooth: hci0: command 0x0c03 tx timeout
[   18.400471] Bluetooth: hci0: BCM: Reset failed (-110)
[   20.812505] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   20.813004] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
[   20.814478] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   20.814975] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
[   20.816344] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   20.816944] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
[   20.818487] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   20.818984] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
[   20.820589] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   20.821086] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
[   20.822781] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   20.823279] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
[   20.874651] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.875145] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.879467] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.879975] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.882323] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.882828] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.885386] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.885895] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.887769] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.888263] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.892113] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.892645] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.901997] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.902492] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.903935] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.904600] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.906022] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.906515] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.907968] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.908490] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.910050] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.910543] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.913290] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.913786] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.921297] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.921791] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.927416] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.927911] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.928934] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.929426] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.935687] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.936181] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.941726] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.942221] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[   20.943164] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[   20.943656] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22

Armbian 20.11.3 Focal ttyS2

rockpro64 login: [   26.084515] rockchip-i2s ff890000.i2s: Fail to set mclk -22

 

46 minutes ago, belfastraven said:

here's result of testing with official build,  which uses 20.7, u-boot

Thanks for testing!

 

46 minutes ago, belfastraven said:

without this error,  which I imagine would have been fixed by your most recent patch anyway?

The boot hanging issue has a workaround now in the rockchip64-u-boot-v2020.10 branch indeed and the board boots consistently for me again.

I don't know if it also fixed those "Timeout poll on interrupt endpoint" errors - I did not observe them with v2020.10.

 

52 minutes ago, belfastraven said:

Loading Environment from SPIFlash... Invalid bus 0 (err=-19)

This is also fixed in the branch with the patch from Sigmaris.

 

I will also definitely add some polish to the nand-sata-install writing process.

Did do apt update; apt upgrade on rockpro64 today and it did hangs on booting kernel....

 

Did use UART serial to connect and =>ums 0 mmc 0 - and USB 3 male and USB C male to connect to the USB-C on rockpro64,  the emmc came up as a /dev/sda1 on the host computer.   Did sudo mount /dev/sda1 /mnt/sda1, cd /mnt/sda1/boot,  ls -alh and uInitrd was linked to uInitrd-5-10-12-rockchip65 but Image was wrongly linked to vlinux-4.4.213-rockchip6, then, sudo rm Image, ln -s vmlinuz-5.10.12-rockship64 and reboot and it did boot successfully after the upgrade.