PINE64 - Quartz64 Tutorials

Fixing the Quartz64 USB3 Port with the soldering iron

Sun, 04 Jun 2023 00:43:45 +0000

In this tutorial I will document what components i desolderd, to fix the flaky USB3 Port on the Quartz64.

To fix the issues with USB3 you need to disconnect the sata connector, it is messing with the USB3 connection.
This will disable the sata connector and you will only be left with a USB3 Connector (a working one tho).

WARNING: THIS CAN BREAK YOUR DEVICE AND THAT WILL BE YOUR FAULT
Only proceed if you have advanced soldering skills, the components are very small.

You need:

A hight power soldering iron (my Pinecil strugglet a faire bit)
A fine tip for the iron
Flux Paste

First locate the 4 resistors that connect the sata connector, i numberd them in this picture:

I simply applied flux paste on to the resistors and pushed them of there pads with the hot soldering iron.
After that USB3 should just work fine.

Installing Arch Linux ARM on the Quartz64

Mon, 06 Dec 2021 19:27:10 +0000

Hello everyone,

I wrote a guide on how to install Arch Linux ARM. Currently it's intended for experienced audiences. It still requires using qemu-user-static to install a custom kernel package, unless you have an already running aarch64 Arch Linux or Manjaro system handy, in which case you can forego the qemu-user-static dependency and just install the package with no additional steps in the arch-chroot.

You can find the guide on the Wiki, where I'll keep it updated: https://wiki.pine64.org/wiki/Installing_...e_Quartz64

Once kernel 5.16 releases, and Arch Linux ARM packages it, I'll update the guide to remove the currently scary part, and I'll declare it safe for anyone with a bit of Linux command line knowledge to follow.

Using PCF8574 I2C GPIO Expanders

Wed, 01 Dec 2021 08:48:13 +0000

Hi all,

I've begun writing a guide on the wiki on how to use the cheap ubiquitous 8-lane PCF8574 I2C GPIO Expander with the Quartz64 Model A:

https://wiki.pine64.org/wiki/Quartz64_Mo..._a_PCF8574

It should also be more generally applicable to other boards, if you adjust the used I2C controller. You don't need to speak any I2C protocol to use this at all; the Linux kernel handles it all for you!

I encourage anyone to edit the wiki article if they find a mistake, and expand the guide as is reasonable. I believe that collaboratively we can produce great guides for the board.

From open box to bash prompt

Wed, 27 Oct 2021 14:59:13 +0000

This should get you from unboxing to a console.

At the time of writing, the graphics output is not functional in the Manjaro builds (but looks to be in the Android 11 Production Test Build for Quartz64 model A SBC)

There is a hint that the default baud rate of the serial port is 1.5mbaud in a warning on the Quartz64 Wiki (emphasis added)

Quote:Warning: Software for the Quartz64 is still early in development, and therefore currently lacks features such as the ability to produce video output. You are strongly encouraged to procure a 3.3V UART serial adapter capable of running at 1.5 mbaud[], such as the woodpecker if you want to use a Quartz64 at this stage.

Make sure your adapter chipset supports 1.5 mbaud or higher. I happened to have (counterfeit?) CP2102 USB to TTL UART adapters which only go up to 1 mbaud. If your adapter does not support the higher baud rate, `screen` does not show an error, it just uses the highest supported baud rate of the chip.

Burn the Manjaro builds to a 2GB or larger microSD card (or eMMC if you purchased). As root run with the path of the SD card:

`xz -d < Manjaro-ARM-minimal-quartz64-bsp-20211025.img.xz - | dd of=/dev/sdX`

The serial port to use is described as UART2_RX_M0_DEBUG and UART2_TX_M0_DEBUG in the pinout.

Assuming you know your TTL adapter tty path, you have permissions to it and you have `screen` installed:

`screen /dev/ttyUSB0 1500000`

When booting, you should see activity from two LEDs next to the power button. If you only see It will start with a solid white and switch to a blinking red. Here is a video.

Boot and you should be presented with a setup menu.

Ethernet is set to use DHCP by default.

I switch to using SSH at this point.

Other info:

If you are using microSD and eMMC, there is a report it will attempt to boot from microSD first.

There is mention of a Debian build, but it may not be as convenient as the Manjaro setup

Installing Manjaro on EMMC

Sat, 02 Oct 2021 09:24:04 +0000

Hi,

I've been trying unsuccessfully to flash to eMMC the images from https://github.com/manjaro-arm/quartz64-...s/releases

In absence of any instruction, I thought that a simple dd would have been enough, but it does not look so.

Flashing the image the the SD card works well though! Is there something different to flash the image, or something more to do afterward?

The symptoms are that during the boot sequence, it just stops always at the same place, just after kernel start:

Code:
Starting kernel ... 

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] 

[    0.000000] Linux verGCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP PREEMPT Fri Sep 17 12:52:46 UTC 2021 

[    0.000ne64 RK3566 Quartz64-A Board 

[    0.000000] earlycon: uart8250 000] printk: bootconsole [uart8250] enabled 

[    3.048209] rockchip-usb2phy fe8a0000.usb2-phy: failed to cre[    3.067859] arm-scmi firmware:scmi: Failed. SCMI protocol 2e 

[    3.496594] arm-scmi firmware:scmi: Failed. SCMI protocol 19 not active. 

[    3.499908] arm-scmi firmware:scmi: Failed. SCMI protocol 17 [    3.561017] rockchip-dw-pcie 3c0000000.pcie: invalid resour) 

Starting version 249.4-1-arch

and then never goes farther...

u-boot rk356х (rockchip repository)

Sat, 24 Jul 2021 22:24:36 +0000

small instruction for building u-boot surrounded by aarch64:

Code:
git clone --depth=1 -b next-dev https://github.com/rockchip-linux/u-boot.git u-boot

git clone --depth=1 https://github.com/rockchip-linux/rkbin.git rkbin

cd u-boot

wget https://gitlab.com/sndwvs/images_build_kit/-/raw/arm/patch/u-boot/rk3568/01-add-u-boot-quartz64.patch

patch -p1 < 01-add-u-boot-quartz64.patch

ln -sf ../rkbin/bin/rk35/rk3568_bl31_v1.24.elf bl31.elf

ln -sf ../rkbin/bin/rk35/rk3568_bl32_v1.05.bin tee.bin

make rk3566-quartz64_defconfig

make -j4 && make -j4 u-boot.itb

tools/mkimage -n rk356x -T rksd -d ../rkbin/bin/rk35/rk3566_ddr_1056MHz_v1.08.bin:spl/u-boot-spl.bin idblock.bin

# write sdcard

dd if=idblock.bin of=/dev/mmcblk0 seek=64

dd if=u-boot.itb of=/dev/mmcblk0p1

when building on x86_64 system use cross compiler gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu.tar.xz and:

Code:
make CROSS_COMPILE=< PATH CROSS COMPILER/aarch64-none-linux-gnu- > -j4 && make CROSS_COMPILE=< PATH CROSS COMPILER/aarch64-none-linux-gnu- > -j4 u-boot.itb

Quote:U-Boot SPL board init
U-Boot SPL 2017.09-rk3566 (Jul 25 2021 - 00:51:44)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256+ OK
## Checking uboot 0x00a00000 ... sha256+ OK
## Checking fdt 0x00b23d18 ... sha256+ OK
## Checking atf-2 0xfdcc9000 ... sha256+ OK
## Checking atf-3 0xfdcd0000 ... sha256+ OK
## Checking optee 0x08400000 ... sha256+ OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 257.451 ms

INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-135-gcda1658bc-dirty:xsf
NOTICE: BL31: Built : 14:19:26, Jun 1 2021
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: pmu v1 is valid
INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz
INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz
INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz
INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 0
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
I/TC:
I/TC: Start rockchip platform init
I/TC: Rockchip release version: 1.0
I/TC: OP-TEE version: 3.6.0-307-g0b06ae94 #1 Fri May 7 01:52:27 UTC 2021 aarch64
I/TC: Initialized
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0xa00000
INFO: SPSR = 0x3c9

U-Boot 2017.09-rk3566 (Jul 25 2021 - 00:57:20 +0300)

Model: Pine64 RK3566 Quartz64 Board
PreSerial: 2, raw, 0xfe660000
DRAM: 7.7 GiB
Sysmem: init
Relocation Offset: ed354000, fdt: eb9f99f8
no mmc device at slot 1
dwmmc@fe2b0000: 1 (SD), dwmmc@fe2c0000: 2, sdhci@fe310000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 50Mhz
PartType: EFI
No misc partition
boot mode: None
FIT: No boot partition
No resource partition
Failed to load DTB
Failed to get kernel dtb, ret=-19
io-domain: OK

** Unable to use mmc 1:3 for loading the env **
Using default environment

Model: Pine64 RK3566 Quartz64 Board
rockchip_set_serialno: could not find efuse/otp device
CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
apll 816000 KHz
dpll 528000 KHz
gpll 1188000 KHz
cpll 1000000 KHz
npll 24000 KHz
vpll 24000 KHz
hpll 24000 KHz
ppll 100000 KHz
armclk 816000 KHz
aclk_bus 150000 KHz
pclk_bus 50000 KHz
aclk_top_high 300000 KHz
aclk_top_low 200000 KHz
hclk_top 150000 KHz
pclk_top 50000 KHz
aclk_perimid 300000 KHz
hclk_perimid 150000 KHz
pclk_pmu 50000 KHz
Net: clk_get_by_name(master_bus) failed: -22eqos_probe_resources() failed: -22No ethernet found.
Hit key to stop autoboot('CTRL+C'): 0
## Booting FIT Image FIT: No boot partition
FIT: No FIT image
Could not find misc partition
ANDROID: reboot reason: "(none)"
optee api revision: 2.0
TEEC: Waring: Could not find security partition
Not AVB images, AVB skip
android_image_load_by_partname: Can't find part: boot
Android image load failed
Android boot failed, error -1.
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
212 bytes read in 17 ms (11.7 KiB/s)
1: slarm64
Retrieving file: /Image
29239808 bytes read in 2476 ms (11.3 MiB/s)
append: root=/dev/mmcblk0p3 ro rootwait rootfstype=ext4 init=/sbin/init loglevel=4 earlycon=uart8250,mmio32,0xfe660000 console=tty1 console=ttyS2,1500000n8
Retrieving file: /dtb/rk3566-quartz64a.dtb
75961 bytes read in 85 ms (872.1 KiB/s)
Fdt Ramdisk skip relocation
## Flattened Device Tree blob at 0x0a100000
Booting using the fdt blob at 0x0a100000
'reserved-memory' ramoops@110000: addr=110000 size=f0000
Using Device Tree in place at 000000000a100000, end 000000000a1158b8
Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
Adding bank: 0x09400000 - 0xf0000000 (size: 0xe6c00000)
Adding bank: 0x100000000 - 0x200000000 (size: 0x100000000)
Total: 2980.864 ms

Starting kernel ...