Redferne

This board is doing its best to drive me totally bonkers. Still can't boot anything...  It sees NVME, it sees my USB, able to see all files are there, but it just doesn't fire up anything. More digging required, I guess. Used Armbian compiler for most, compiled initramfs with linux-next instructions, followed most recommendations here. 
 
At least I figured out that having the board plugged into my laptop to power it, if I type ums 0 nvme 0 from u-boot, I can access the nvme drive from my Ubuntu VM and fully manipulate it from there. Learning experience

Yep, I had a previous bl31.elf built, that was not the issue. I had to enable CONFIG_DM_KEYBOARD=y in my defconfig... Keyboard now works. Thanks for the help! Next step, boot from nvme.

I forgot to mention how to build ATF (Arm Trusted Firmware)
 
git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
 
make PLAT=rk3399 bl31
cp build/rk3399/release/bl31/bl31.elf ../u-boot
 
You need bl31.elf to build your u-boot!

Boot from SPI directly to NVME works:
 
Latest U-Boot v2021.01-rc4 + this patch:
rockchip: roc-pc-rk3399: fix boot from SPI flash on spi1
https://patchwork.kernel.org/project/linux-rockchip/list/?series=403611
 
To build uboot on roc-pc:
make roc-pc-mezzanine-rk3399_defconfig
make -j6
./tools/mkimage -n rk3399 -T rkspi -d tpl/u-boot-tpl.bin:spl/u-boot-spl.bin idbloader-spi.img
 
To deploy uboot on spi:
dd if=idbloader-spi.img of=spi.img
                  (#0x60000 = 393216 = 4096 * 96)
dd if=u-boot.itb of=spi.img bs=4096 seek=96
flashcp -v spi.img /dev/mtd0
 
in U-Boot:
edit boot_targets to have nvme0 as first entry
 
On NVME drive (e.g. Samsung 970EVOPlus):
 
/boot/extlinux/extlinux.conf:
 
label mainline-kernel
    kernel /boot/Image
    initrd /boot/Initrd
#    fdt /rk3399-roc-pc.dtb
    fdt /boot/rk3399-roc-pc-mezzanine.dtb
    append earlycon=uart8250,mmio32,0xff1a0000 console=tty1 console=ttyS2,1500000 swiotlb=1 root=/dev/nvme0n1p1 rootwait rw rootfstype=ext4 init=/sbin/init
 
ls /boot:
Image (Image-5.10.0-next-20201223)
Initrd (Initrd-5.10.0-next-20201223)
rk3399-roc-pc-mezzanine.dtb (rk3399-roc-pc-mezzanine.dtb-5.10.0-next-20201223)
 
Kernel built on roc-pc:
Latest linux-next
 
make -j6
make modules_install
kernelversion=`cat ./include/config/kernel.release`
cp .config /boot/config-$kernelversion
mkinitramfs -c gzip -o ./initramfs-$kernelversion $kernelversion
mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n initramfs -d ./initramfs-$kernelversion ./Initrd
cp arch/arm64/boot/Image /boot/Image
cp Initrd /boot
cp arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtb /boot
cp arch/arm64/boot/dts/rockchip/rk3399-roc-pc-mezzanine.dtb /boot
cp arch/arm64/boot/Image /boot/Image-$kernelversion
cp Initrd /boot/Initrd-$kernelversion
cp arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtb /boot/rk3399-roc-pc.dtb-$kernelversion
cp arch/arm64/boot/dts/rockchip/rk3399-roc-pc-mezzanine.dtb /boot/rk3399-roc-pc-mezzanine.dtb-$kernelversion
 
example .config:
config

If anyone is interested: I designed a new cover instead of the acrylic plate. I broke it because I tried to drill a hole into it to get access to the power pins:
 
I made a new one in Fusion 360 to be 3D-printed or laser cut: https://www.thingiverse.com/thing:4501621
With it you get access to all pins (power, PCIe, GPIO, serial and SPI) and the reset button. The picture is of version 1. The newer version on thingiverse has larger cutouts and holes.
 
 
 
 

Was in dire need of Armbian on my new toy, the HBP with a iMX8Q CPU ;-) The board features dual WWAN (PCIe + M.2) sockets for highspeed 3G/4G/5G modems with a SIM socket. The Debian build from SolidRun did not have any modem drivers enabled in the kernel so there was headache. Wipped up this WIP configuration and it builds and runs with:
```
$ ./compile.sh  BOARD=hummingboardpulse-imx8q BRANCH=legacy RELEASE=buster BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no
```
NOTE: It uses the HDMI and LPDDR4 binary blobs from NXP. You will get a prompt during build to accept the license.

The board is default configured to boot from SD using the Boot Select DIPs
 
_ _ ____ ____ _ _ __ ____ _____ | | | | __ ) | _ \ _ _| |___ ___ (_) \/ \ \/ ( _ ) | |_| | _ \ | |_) | | | | / __|/ _ \ | | |\/| |\ // _ \ | _ | |_) | | __/| |_| | \__ \ __/ | | | | |/ \ (_) | |_| |_|____/ |_| \__,_|_|___/\___| |_|_| |_/_/\_\___/ Welcome to Armbian buster with Linux 4.19.72-imx8-sr-imx8 System load: 0.41 1.82 1.38 Up time: 29 min Memory usage: 4 % of 2997MB IP: 192.168.10.148 CPU temp: 47°C Usage of /: 18% of 7.1G [ General system configuration (beta): armbian-config ] http://ix.io/27FC
 

I knew I would get the right people into this conversation.

Well, they have backported mesa to bionic-updates, up until 19.2 so far. So it is very likely that in the near future they will backport 19.3 too.
 
Maintaining our own package for mesa 19.3 would be a source for trouble, IMO.
I propose to disable glamor in /etc/X11/xorg.conf.d/01-armbian-defaults.conf, by adding something like this:
Section "Device" Identifier "Default Device" Driver "modesetting" Option "AccelMethod" "none" ### "glamor" to enable 3D acceleration, "none" to disable. EndSection This will do the trick for the time being, and will make it very easy to enable acceleration when the necessary libs are available.

I suggest adding a small patch for all u-boot for rk33xx. It allows to enable direct booting from USB media and significantly facilitates the use of RK33xx models for users. Allows you to easily launch any system from USB without the need for complex settings and manipulations with existing (main) systems on devices on SD or eMMC.
 
The entire path fits in two lines.
 
https://github.com/150balbes/Build-Armbian/blob/master/patch/u-boot/u-boot-arm-64/u-boot-0010-rk-usb-start.patch#L18

Checked the ability to install and normal operation of the Linux system in eMMC on TV boxes with H6. The next step is to add the installation script to the eMMC for the armbian generic image. Details can be seen in this topic. 
 
https://forum.freaktab.com/forum/tv-player-support/allwinner-tv-players/793034-libreelec-and-armbian-for-allwinner-tv-box?p=794681#post794681

@Redferne - try to add mem=2048M to the kernel cmdline - the eachlink h6 mini otherwise detects the memory wrong as 3gb although only 2gb are useable - thus it will crash as soon as it tries to access the part of the memory which does not really exist
 
best wishes - hexdump

@Panzerknacker What make/model EMMC you got? I have the 128GB which was delivered with the board. It's wierd the EMMC works in Linux but U-Boot SPL has issues. Wondering if there's patch somewhere... 
 
Edit: Many hours later...
 
Dug deep into the MMC code in UBoot and it seems there is a bug.. My EMMC will not negotiate success the advertised supported speed/mode (mmc: widths [8, 4, 1] modes [MMC legacy, MMC High Speed (26MHz), SD High Speed (50MHz), MMC High Speed (52MHz), MMC DDR52 (52MHz)] ). UBoot should revert back to the "safer" speed here: mmc.c#L2146, but it seems to be missing a call to mmc_set_clock(). I added the missing call and it successfully reverts back to "MMC High Speed (26MHz)" and EMMC can be read. Board finally boots on EMMC
trying mode MMC High Speed (26MHz) width 8 (at 26 MHz) CMD_SEND:6 ARG 0x03b70200 MMC_RSP_R1b 0x00800800 CMD_SEND:13 ARG 0x00010000 MMC_RSP_R1,5,6,7 0x00000900 CURR STATE:4 CMD_SEND:6 ARG 0x03b90100 MMC_RSP_R1b 0x00000800 CMD_SEND:13 ARG 0x00010000 MMC_RSP_R1,5,6,7 0x00000900 CURR STATE:4 CMD_SEND:8 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000900 selecting mode MMC High Speed (26MHz) (freq : 26 MHz) clock is enabled (26000000Hz) CMD_SEND:8 ARG 0x00000000 MMC_RSP_R1,5,6,7 0x00000900 switch to partitions #0, OK mmc0(part 0) is current device Now booted kernel and the EMMC works perfectly in HS400 ES mode?!?!
Welcome to Armbian buster with Linux 5.4.6-rockchip64 System load: 0.00 0.00 0.00 Up time: 1 min Memory usage: 3 % of 3868MB IP: 192.168.0.33 CPU temp: 36°C Usage of /: 2% of 113G root@roc:~# cat /sys/kernel/debug/mmc1/ios clock: 200000000 Hz actual clock: 200000000 Hz vdd: 7 (1.65 - 1.95 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 3 (8 bits) timing spec: 10 (mmc HS400 enhanced strobe) signal voltage: 1 (1.80 V) driver type: 0 (driver type B) Oh, and 5.4.7 is no good...
 

If you're building 5.4.y, try tag:v5.4.6 instead. I couldn't get latest master to boot properly on this board.

Not sure this a bug, but the following patch made my EMMC revert back to MMC High Speed (26MHz) after failing @ MMC High Speed (52MHz).
diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c index f683b52e..2e01c75f 100644 --- a/drivers/mmc/mmc.c +++ b/drivers/mmc/mmc.c @@ -2139,11 +2143,14 @@ static int mmc_select_mode_and_width(struct mmc *mmc, uint card_caps) if (!err) return 0; error: + pr_debug("error: %d\n", err); mmc_set_signal_voltage(mmc, old_voltage); /* if an error occured, revert to a safer bus mode */ mmc_switch(mmc, EXT_CSD_CMD_SET_NORMAL, EXT_CSD_BUS_WIDTH, EXT_CSD_BUS_WIDTH_1); mmc_select_mode(mmc, MMC_LEGACY); + mmc_set_clock(mmc, mmc->tran_speed, + MMC_CLK_ENABLE); mmc_set_bus_width(mmc, 1); } }  

In the new year, I plan to focus on improving and developing Armbian-TV  (Armbian-TV is a version that is based on the official Armbian, aimed at improved support for media capabilities and ease of use by ordinary users) support for the platforms Rockchip and Allwinner  (perhaps a few more platforms will be added that are not yet in use). To do this, I have already ordered several popular models based on rk3399 (NanoPC T4, RockPi 4, Renegade-Elite), in a complete set with obligatory Support of nvme carriers (I consider this support essentially important, for transition of TV boxes and SBS to the category of mini-PC, as highly effective and improved replacement of the usual PC). I'm plan to buy several more models on Allwinner (I'm still evaluating the capabilities of the selected models). 
I had plans to buy some more models based on rk3399 from other manufacturers, but there were problems with delivery and / or payment for my country.
 
If anyone has any suggestions for models that I should consider, I'm willing to listen to reasonable descriptions of the models.

There is special driver work done in their kernel to cover an unsupported I2C buck/boost converter that provides the 12V rail on this board, and for reasons I'm digging into, the fusb302 driver is a complete mess after they moved it out of staging, it has a lot of odd behaviors and a completely new set of requirements for the device tree.  I temporarily ran it back to the staging driver for our mainline expert builds (limited improvement), but am working on the proper driver.

A huge kudos to @piter75 who commited a csc for this board 👍😍 Did not have the time or energy get my efforts to bear fruit. Was probably to focused on getting the U-Boot TPL+SPL combo working. Maybe this board finally gets the love it so desperately needs. Once again. Thank you for Armbian and all the work everyone puts in! 

A huge kudos to @piter75 who commited a csc for this board 👍😍 Did not have the time or energy get my efforts to bear fruit. Was probably to focused on getting the U-Boot TPL+SPL combo working. Maybe this board finally gets the love it so desperately needs. Once again. Thank you for Armbian and all the work everyone puts in! 

A huge kudos to @piter75 who commited a csc for this board 👍😍 Did not have the time or energy get my efforts to bear fruit. Was probably to focused on getting the U-Boot TPL+SPL combo working. Maybe this board finally gets the love it so desperately needs. Once again. Thank you for Armbian and all the work everyone puts in! 

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.
 

Ran sbc-bench (thanks @tkaiser).
RockPI4B: http://ix.io/1UXk
ROC-RK3399-PC: http://ix.io/1UXl
Have only glanced over the results, but the Renegade Elite seems on par with the RockPI4B.
 
Still want to get 5.3.x to run properly and get the TPL from U-Boot v2019.10-x working before commiting a wip.
Hoping to get some time this weekend.

Ran sbc-bench (thanks @tkaiser).
RockPI4B: http://ix.io/1UXk
ROC-RK3399-PC: http://ix.io/1UXl
Have only glanced over the results, but the Renegade Elite seems on par with the RockPI4B.
 
Still want to get 5.3.x to run properly and get the TPL from U-Boot v2019.10-x working before commiting a wip.
Hoping to get some time this weekend.

During all my board migrations under 5.0.y, I've seen that copying OS into eMMC using "nand-sata-install", it now much faster !!!
I don't know if it 5.0.y related or if some tweaks have been done to "nand-sata-install", but time shrink from 20minutes to 4 or 5minutes...

The tour was successful ... So, the commit is now done !
 
I'm now going back to the task of getting rid of old U-Boot SPL 2017.09-armbian ...

Done !
https://github.com/armbian/build/commit/fa232d17ed1488bd19be4dbc9f7f3b174f85ef73