TimSmall

Tried the 4.4 images ( apt install linux-dtb-legacy-rockchip linux-image-legacy-rockchip ... which bricks it nicely, but during early boot it does at least I get some trace of the device: U-Boot 2020.07-armbian (Oct 19 2020 - 00:10:11 +0200) SoC: Rockchip rk3399 Reset cause: POR Model: FriendlyElec NanoPC-T4 DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: FriendlyElec NanoPC-T4 Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 18 ms (171.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 181 bytes read in 15 ms (11.7 KiB/s) 6557203 bytes read in 645 ms (9.7 MiB/s) 8565640 bytes read in 832 ms (9.8 MiB/s) 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... Device 0: Vendor: 0x144d Rev: 1L2QEXD7 Prod: S41GNX0M266030 Type: Hard Disk Capacity: 244198.3 MB = 238.4 GB (500118192 x 512) ... is now current device Scanning nvme 0:1... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus usb@fe3c0000: USB EHCI 1.00 Bus dwc3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus dwc3: 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@fe3c0000 for devices... 1 USB Device(s) found scanning bus dwc3 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 This looks like uboot finding it. It subsequently tries to network boot. Any tips for attempting to debug this further? What are the moving parts? Is it just going be kernel PCIe init/probe code, or is there rockchip firmware at play too? Cheers! Tim.

Thanks for the tip, but still the same thing with 5.4 unfortunately... I'll see if I can try an Intel 600p... [ 3.586527] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.586983] rockchip-pcie: probe of f8000000.pcie failed with error -110

Another data point, no luck with Samsung MZVLB256HAHQ-000L7 (Samsung PM981 256GB). root@nanopct4:~# uname -a ; dmesg | grep -i pci Linux nanopct4 5.9.10-rockchip64 #20.11 SMP PREEMPT Mon Nov 23 13:36:07 CET 2020 aarch64 GNU/Linux [ 0.006761] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created [ 1.513627] PCI: CLS 0 bytes, default 64 [ 2.591307] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.591331] OF: /pcie@f8000000: Missing device_type [ 2.591362] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.591382] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.592227] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.659843] ehci-pci: EHCI PCI platform driver [ 2.694337] ohci-pci: OHCI PCI platform driver [ 3.123462] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 3.123511] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 3.123531] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 3.124404] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 3.652733] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.653595] rockchip-pcie: probe of f8000000.pcie failed with error -110

FWIW. I did a quick test with Armbian_5.98.191003_Nanopct4_Debian_buster_dev_5.3.0-rc4_minimal.img and it booted and survived superficial testing (over ssh and serial console). No wifi device. I didn't test the video out.

Because the EC25 is a USB modem in a mini-PCIe formfactor, this should be completely independent of the PCIe support in the kernel (unless you have a card which also implements a PCIe to USB bridge, but I've not seen one of those). How are you attaching it physically to the RK3399? Did you try other USB devices, or maybe a USB to mini-PCIe carrier board?

I see that the "energy-aware scheduling" patch set got merged for the 5.0 kernel - this allows the mainline kernel to behave reasonably with asymetric multi-processor CPUs like the RK3399's A72/A53 big.LITTLE arrangement. Has anyone given it a spin on a T4 yet? Cheers, Tim.

BTW, what git tree should be used to get the latest work? The wiki still refers to https://github.com/bootlin/linux-cedrus/tree/cedrus/4.18/requests-api-v18-merge (August), but there is newer code in other branches e.g. https://github.com/bootlin/linux-cedrus/tree/cedrus/4.20/mpeg2 Thanks!

I know this wasn't in the original crowd funding goal set, but... I was wondering how difficult adding H6 support would be? It supports VP9, and 10 bit h.265 at 60fps/4k, as well as HDMI2.0 output, so it is perhaps of more interest for some?

Hi, I'd like to use kvm on the Orange Pi PC2, but the Armbian 4.14.12-sunxi64 kernel doesn't seem to enable it (or possibly the boot loader doesn't put the CPU in the right mode?). If I google: allwinner h5 kvm then the first hit shows a kernel boot log which shows kvm enabled on an Orange Pi PC2, so it looks like it's possible. I'm happy to recompile the kernel myself, but wanted to know if there were any gotchas that might mean this is disabled by default on purpose? Cheers, Tim.