PINE64 - User contributions [en]

Ox64

2024-06-23T15:54:25Z

Giorez:

[[File:Ox64_board.jpg|thumb|right|The Ox64]]
[[File:Ox64 pinout.png|thumb|Pinout of the production version]]
[[File:RISC-V.png|thumb|right|Powered by RISC-V]]

The '''Ox64''' is a RISC-V based single-board computer based on the Bouffalo Lab BL808 RISC-V SoC with C906 64-bit and E907/E902 32-bit CPU cores supported by 64 MB of embedded PSRAM memory, and with built-in WiFi, Bluetooh and Zigbee radio interfaces. The Ox64 comes in a breadboard-friendly form-factor, has a microSD card slot, a USB 2.0 Type-C port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/openbouffalo/buildroot_bouffalo buildroot] bringing all the work below together with a bootable kernel and updated filesystem images for SD cards
* [https://github.com/smaeul/u-boot/tree/bl808 U-Boot] and [https://github.com/smaeul/opensbi/tree/bl808 OpenSBI] work by Smauel
* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others

Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

* [https://github.com/bouffalolab/bl808_linux Linux for BL808]
* [https://wiki.pine64.org/wiki/File:Linux_BL808.pdf Installation Instructions for Linux on BL808 (Chinese)]
* [https://wiki.pine64.org/wiki/File:Linux_BL808_en.pdf Installation Instructions for Linux on BL808 (machine translated to English)]

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/bouffalolab/bl_mcu_sdk BL808 MCU SDK]
* [https://dev.bouffalolab.com/download BLDevCube Flashing Tool for Windows, macOS and Ubuntu x64]
* [https://wiki.pine64.org/wiki/File:Ox64_BL808UART_connect.pdf Ox64 UART Flashing Guide], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/bl808_demo_event.bin BL808 Demo Firmware: bl808_demo_event.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/whole_flash_data.bin BL808 UART Log Firmware: whole_flash_data.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/BL808.DVK.Quick.Start.pdf BL808 DVK Quick Start]
* [https://github.com/bouffalolab/bl808_linux/tree/main/opensbi-0.6-808 OpenSBI for BL808]
* [https://github.com/bouffalolab/bl-pac/tree/main/bl808 Rust Peripheral Access Crate (PAC) for BL808]
* [https://github.com/bouffalolab/bl-pac/blob/main/bl808/bl808.svd System View Description (SVD) for BL808]

== SoC and Memory Specification ==

[[File:Bouffalo_Lab_icon.png|right]]

Based on the [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]

[[File:BL808_Block_Diagram.jpg|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 480 MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head E907 320 MHz 32-bit RISC-V CPU:

* Supports RISC-V RV32IMAFCP instruction set
* Supports RISC-V 32-bit/16-bit mixed instruction set
* Supports RISC-V machine mode and user mode
* Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
* Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
* Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
* 32K instruction cache, two-way set associative structure
* 16K data cache, two-way set associative structure
* See [https://www.t-head.cn/product/e907?lang=en here]

T-Head E902 150 MHz 32-bit RISC-V CPU:

* See [https://www.t-head.cn/product/e902?lang=en here]

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100 Mbit/s Ethernet (optional, on expansion board)

=== Storage ===
* On-board 16 Mbit (2 MB) or 128 Mbit (16 MB) XSPI NOR flash memory
* MicroSD, supports SDHC and SDXC (only on the 128 Mbit version)

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO pins, including SPI, I2C and UART functionality, possible I2S and GMII expansion
* Dual-lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* Microphone (optional, on the camera module)
* Speaker (optional, on the camera module)

== Board Information, Schematics and Certifications ==
[[File:Ox64 ethphy.png|thumb|Pinout for wiring ethernet PHY to EMAC]]

* Baseboard dimensions: 51 mm x 21 mm x 19 mm x 3.5 mm (breadboard friendly)
* Input power: 5 V, 0.5 A through the microUSB or USB-C ports

Production version schematic:

* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221018.pdf Ox64 Schematic 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221018.pdf Ox64 PCB Component placement(ToP) 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221018.pdf Ox64 PCB Component placement(Bottom) 20221018 v1.1]

Prototype (dispatched to developers) schematic:
* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==

Bouffalo BL808 SoC information:
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf Bouffalo Lab BL808 SoC Datasheet]
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_RM/en/BL808_RM_en_1.3.pdf Bouffalo Lab BL808 SoC Reference Manual]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevice 16Mb XSPI-Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevice 128Mb XSPI-Flash Datasheet]
* [https://wiki.pine64.org/images/5/5d/W25Q128JW_RevB_11042019-1761358.pdf Winbond 128Mb QSPI-Flash Datasheet] (W25Q128JWSQ)

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Compatible UARTs when in bootloader mode ==

When the Ox64 is in bootloader mode, some UARTs are unable to communicate with it. When this is the case, utilities such as BLDevCube are unable to actually program the device. If you see "Shake hand fail" and an empty ack, and your device is in bootloader mode, then it is likely an incompatible UART.

The below devices have been tested and verified as working:
* Raspberry Pi Pico - running the following [https://github.com/sanjay900/ox64-uart/releases/tag/v1.1 UART firmware] (GP4 and GP5 are used for port 0, GP12 and GP13 for port 1)
* Compiled binary for Pi Pico and connectivity diagram is [https://github.com/Kris-Sekula/Pine64_Ox64_SBC/tree/main/uart here]
* ESP32 with CP210x - bridge the EN pin to ground to disable the ESP32 itself, and then connect the TX on the esp32 to 14 on the Ox64 and RX to pin 15. Note that only baud rate 115200 works, and this doesn't seem to work for everyone)
* Stand-alone CP2102 dongle works at 115200 baud. Brand used was HiLetgo.
* STM32F401 BlackPill - running the [https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2 Black Magic Debug] firmware
* STM32F103C8T6 BluePill - running Black Magic Debug.
* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
* Some CH340G based adapters work and some don't.

== Resources and Articles ==
* [https://youtube.com/watch?v=czRtF-UNiEY A short video] on how to connect to the Ox64, flash and boot
* [https://youtu.be/vPAk5sq_Ilc Another video] that covers soldering pins, connecting via Pi Pico and flashing Linux and U-Boot
* [https://wiki.pine64.org/images/5/59/How_to_Run_Ox64.pdf Step-by-step tutorial] for how to build, flash and run Ox64
* [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff First batch of Ox64 won't appear as USB serial port]
* [https://gist.github.com/lupyuen/2087e9b3fb40aab5e0795bb02a265a3b First batch of Ox64 tested OK with CH340C/G]
* [https://www.robertlipe.com/bl808-not-symmetric/ First thoughts on the (a)symmetry of Bouffalo Labs BL808 as in Pine64 Ox64]
* [https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html The $8 linux computer (with picoprobe-rp2040 programming instructions)]
* [https://github.com/p4ddy1/pine_ox64/blob/main/build_toolchain_macos.md Building the Xuantie GNU Toolchain for Ox64 on macOS and Apple Silicon]

Ox64 BL808 RISC-V SBC articles by [https://lupyuen.codeberg.page/ Lup Yuen LEE]:
* [https://lupyuen.codeberg.page/articles/ox64.html Booting Linux and (maybe) Apache NuttX RTOS]
* [https://lupyuen.codeberg.page/articles/ox2.html Starting Apache NuttX real-time operating system]
* [https://lupyuen.codeberg.page/articles/mmu.html Sv39 Memory Management Unit]
* [https://lupyuen.codeberg.page/articles/app.html NuttX Apps and Initial RAM Disk]
* [https://lupyuen.codeberg.page/articles/plic2.html UART Interrupt and Platform-Level Interrupt Controller (PLIC)]
* [https://lupyuen.codeberg.page/articles/plic3.html Fixing the UART Interrupt and Platform-Level Interrupt Controller]
* [https://www.hackster.io/lupyuen/8-risc-v-sbc-on-a-real-time-operating-system-ox64-nuttx-474358 $8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX]
* [https://lupyuen.codeberg.page/articles/nim.html Nim on a Real-Time Operating System: Apache NuttX RTOS + Ox64 BL808 SBC]

Git repositories:
* [https://github.com/sfranzyshen/arduino-bl808 Community made Arduino Core specifically for the Bouffalo Labs BL808 RISC-V MCU] (initial development has been postponed until further notice)

== Development Efforts ==
* [https://twitter.com/gamelaster/status/1583916501400068096 Ox64 boots Linux successfully]
* [https://twitter.com/btashton/status/1586381334439923713?t=w5xRRUR74HGK2O1Zg_aFyw&s=19 Brennan Ashton is porting Apache NuttX RTOS and OpenAMP (Asymmetric Multiprocessing) to BL808]
* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

== Building ==
Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

$ mkdir -p ~/ox64
$ cd ~/ox64
$ git clone https://github.com/buildroot/buildroot
$ git clone https://github.com/openbouffalo/buildroot_bouffalo

Define an environment variable for the Buildroot Bouffalo overlay path:

$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo

Change directory into the cloned Buildroot folder:

$ cd ~/ox64/buildroot

Apply the default configuration for Pine64 Ox64:

$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig

Use the `menuconfig` tool to adjust the build settings:

$ make menuconfig

Within `menuconfig`, configure the following:

* Select `Target Options`
* Enable `Integer Multiplication and Division (M)`
* Enable `Atomic Instructions (A)` using space key
* Enable `Single-precision Floating-point (F)`
* Enable `Double-precision Floating-point (D)`
* Select `Target ABI`, set it to `lp64d` and `press Exit`
* Select `Toolchain`, enable `Fortran support`, enable `OpenMP support`, and Save & Exit

Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.

$ make

Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

== Flashing ==
This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

=== Prepare images for flashing ===

Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.

$ mkdir -p ~/ox64/openbouffalo
$ cd ~/ox64/openbouffalo
$ wget https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ tar -xvzf bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ cd ~/ox64/openbouffalo/firmware
$ xz -v -d -k sdcard-pine64_ox64_full_defconfig.img.xz
$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img

==== Optional: create a combined SoC image ====

Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ fallocate -l 0x800000 bl808-combined.bin
$ dd conv=notrunc if=m0_lowload_bl808_m0.bin of=bl808-combined.bin
$ dd conv=notrunc if=d0_lowload_bl808_d0.bin of=bl808-combined.bin seek=$((0x100000))B
$ cat bl808-firmware.bin >> bl808-combined.bin

==== Check that you have the required files for flashing ====

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ ls -1 *808*.bin *.img

Expected files:

* `bl808-combined.bin` -- If you created the combined image.
* `bl808-firmware.bin` -- OpenSBI and UBoot DTB files. Runs on the D0 core.
* `d0_lowload_bl808_d0.bin` -- Startup code for the D0 core.
* `m0_lowload_bl808_m0.bin` -- Startup code for the M0 core.
* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.

=== Set up your UART adapter ===

In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.

==== Option 1: Raspberry Pi Pico ====

First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:

$ mkdir -p ~/ox64/pico
$ cd ~/ox64/pico
$ wget https://github.com/Kris-Sekula/Pine64_Ox64_SBC/raw/main/uart/picoprobe.uf2

Put the Raspberry Pi Pico board into programming mode:

* Press the BootSel button
* Apply power by plugging the USB cable to PC
* Release the BootSel button

NOTE: As an alternative to pressing the BootSel button, you can also connect the probe point `TP6` (located on the bottom of the Pico board) to any ground point (e. g. pin 28).

The Pico will now appear as a USB mass storage device. Copy the `UF2` file to program it:

$ cp ~/ox64/pico/picoprobe.uf2 /media/<user>/RPI-RP2

Next, connect the Ox64 board to the Pico according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | PI PICO | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_pin17
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_pin16
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_pin6
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_pin7
| ACM0 for serial console

| gnd_pin38
| gnd_pin38/3
|

| vbus5v_pin40
| vbus5v_pin40
|
|===

With the Pico flashed and wired as per the instructions above, we have access to two of the Ox64's UART ports at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Reconnect the Pico to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)

==== Option 2: STM32 Bluepill ====

The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.

[NOTE]

The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does **not** have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).

If you own an SWD-capable debugger (ST-Link, J-link, etc.) you can use that for programming the Bluepill as well, although instead of `stm32flash` console command you would be using https://openocd.org/[openocd] or other suitable software.

WARNING: Your serial adapter must use 3.3V logic levels.

Install software to flash Bluepill. For Debian-based systems just install package from repository:

$ sudo apt install stm32flash

For Arch Linux systems, use the AUR repository:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ git clone https://aur.archlinux.org/stm32flash.git
$ cd ~/ox64/bluepill/stm32flash
$ makepkg -si

Download the https://github.com/r2axz/bluepill-serial-monster[Bluepill Serial Monster] firmware:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ wget https://github.com/r2axz/bluepill-serial-monster/releases/download/v2.6.4/bluepill-serial-monster.hex

Put the Bluepill into programming mode:

* Set boot jumpers for booting from rom: Boot0=1, Boot1=0.
* Connect it to a USB-Serial adapter with A9 to Rx, A10 to Tx, GND to GND, 3v3 to Vcc.
* Apply power by plugging the USB cable to PC. Press the Reset button.

Find your USB serial adapter's device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`. Upload the firmware:

$ cd ~/ox64/bluepill
$ sudo stm32flash -w bluepill-serial-monster.hex /dev/tty[DEVICE]

After upload, set boot jumpers for boot from flash: Boot0=0, Boot1=0. Disconnect the USB serial adapter from both the PC and Bluepill board.

Next, connect the Ox64 board to the Bluepill according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | Bluepill | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_A3
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_A2
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_A9
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_A10
| ACM0 for serial console

| gnd_pin38
| GND
|

| vbus5v_pin40
| 5V
|

|===

With the Bluepill flashed and wired as per the instructions above, we have access to two of the Ox64's UART connections at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Connect the Bluepill to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)
* `/dev/ttyACM2` (unused)

==== Option 3: Generic UART adapter ====

image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]

Check that your serial adapter is on the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. You will (most likely) only have one serial interface available to you; unlike the previous options you will be using this same serial interface for both flashing and testing the system.

Find its device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`.

You will also need a way of powering your Ox64. If your serial adapter has a 5V line, you can connect it to VBUS (pin 40). Otherwise, you can connect either the micro-B or the USB-C port on the Ox64 to any 5V power supply.

WARNING: Your serial adapter must use 3.3V logic levels.

Refer to the pinout image below. Connect your UART adapter as follows:

* RX -> UART0_TX / GPIO14 / pin 1
* TX -> UART0_RX / GPIO15 / pin 2
* GND -> any ground (e. g. pin 3)

Proceed with the instructions in the sections that follow, up to and including <<flashing_the_ox64>> and <<flashing_the_microsd_card>>, but replace all occurrences of `/dev/ttyACM1` with `/dev/tty[DEVICE]`.

Next, power off the Ox64 and re-connect your UART adapter as follows:

* RX -> TXD / GPIO16 / pin 32
* TX -> RXD / GPIO17 / pin 31
* GND -> any ground (e. g. pin 33)

Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.

=== Download flashing tools ===

You have a choice of flashing software:

* DevCube: GUI-based closed source flashing tool
* CLI (`bflb-iot-tool`): command line open source flashing tool

==== DevCube installation ====

Download the latest DevCube flashing tool from BouffaloLab's website:

$ mkdir -p ~/ox64/devcube
$ cd ~/ox64/devcube
$ wget https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.9.zip
$ unzip BouffaloLabDevCube-v1.8.9.zip
$ chmod u+x BLDevCube-ubuntu

If you did not create a link:#optional_create_a_combined_soc_image[combined image] you may need an older version of the DevCube. In that case, download v1.8.3 from one of the mirrors below:

* https://openbouffalo.org/static-assets/bldevcube/BouffaloLabDevCube-v1.8.3.zip
* https://hachyderm.io/@mkroman/110787218805897192[] > https://pub.rwx.im/~mk/bouffalolab/BouffaloLabDevCube-v1.8.3.zip
* https://we.tl/t-eJWShQJ4iF
* https://cdn.discordapp.com/attachments/771032441971802142/1145565853962735639/BouffaloLabDevCube-v1.8.3.zip

Verify that your copy of `BouffaloLabDevCube-v1.8.3.zip` matches the hashes below:

* SHA1: `0f2619e87d946f936f63ae97b0efd674357b1166`
* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`

==== CLI packages installation ====

Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:

$ sudo apt install pipenv # for Debian-based systems
# or
$ sudo pacman -S python-pipenv # for Arch Linux systems

$ cd ~/ox64/
$ pipenv install setuptools # install prerequisite of CLI flash tool
$ pipenv install bflb-iot-tool # install CLI flash tool
$ pipenv shell # activate virtual environment
$ # bflb-iot-tool --help # return info about the tool

NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.

=== Flashing the Ox64 ===

Put the Ox64 into programming mode:

* Press the BOOT button
* Apply power or re-plug the USB cable
* Release the BOOT button

==== CLI flashing method ====

Set up some environment variables to save typing them out later:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ PORT=/dev/ttyACM1
$ BAUD=230400 # safe value for macOS, set to 2000000 for faster flashing on Linux

Finally, flash the Ox64. If you created a link:#optional_create_a_combined_soc_image[combined image] then run the command below:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware bl808-combined.bin --single

Otherwise, run the following commands:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware m0_lowload_bl808_m0.bin --single
$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single
$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x800000 --firmware bl808-firmware.bin --single

If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.

==== BLDevCube flashing method ====

Open a new terminal window to run the DevCube flasher:

$ cd ~/ox64/devcube
$ ./BLDevCube-ubuntu

Select chip [BL808], press Finish, and configure BOTH the [MCU] and [IOT] tabs as follows. When you switch between tabs double check that they still match the settings below:

[cols="~,~"]
|===
|Interface
|UART

|Port/SN
|`/dev/ttyACM1`

|UART rate
|230400 (safe value for macOS, set to 2000000 for faster flashing on Linux)
|===

If you created a link:#optional_create_a_combined_soc_image[combined image] then you only need to use the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x0], [PATH to bl808-combined.bin]
* Click 'Create & Download' and wait until it's done
* Close DevCube

Otherwise, start in the [MCU] tab:

* M0 Group[group0], Image Address [0x58000000], [PATH to m0_lowload_bl808_m0.bin]
* D0 Group[group0], Image Address [0x58100000], [PATH to d0_lowload_bl808_d0.bin]
* Click 'Create & Download' and wait until it's done

Then, switch to the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x800000], [PATH to bl808-firmware.bin]
* Click 'Create & Download' again and wait until it's done
* Close DevCube

=== Erasing the microSD card ===

Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.

$ sudo wipefs /dev/[DEVICE]
$ sudo wipefs --all --force /dev/[DEVICE]*
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=1

Optionally you can zeroes the whole device:

$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] | head -1) \/ 32768)

=== Flashing the microSD card ===

Insert the microSD card into your PC, locate its device under `lsblk` and write the image:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync

=== Booting for the first time ===

Power off your Ox64 and insert the microSD card.

Open a terminal window to connect to the D0 core’s (i.e. Linux’s) serial console:

$ minicom -b 2000000 -D /dev/ttyACM0

If you are using a Pico or Bluepill as your serial adapter, open another terminal window to to monitor the M0 core’s serial console (reminder: `/dev/ttyACM1` is the same port we previously used for flashing):

$ minicom -b 2000000 -D /dev/ttyACM1

Re-apply power to the Ox64.

On the main/D0 console (`/dev/ttyACM0`) you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error.

On the M0 console (`/dev/ttyACM1`) you'll see following messages until the sytem is fully loaded:

----
[I][MBOX] Mailbox IRQ Stats:
[I][MBOX] Peripheral SDH (33): 0
[I][MBOX] Peripheral GPIO (60): 0
[I][MBOX] Unhandled Interupts: 0 Unhandled Signals 0
----

Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.

==== Connecting the Ox64 to your WiFi network ====

The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):

$ blctl connect_ap <YourSSID> <YourPassword>

Wait for it to connect (if you're monitoring the M0 console on `/dev/ttyACM1` it should tell you when it's done), then run the following command from the Linux console:

$ udhcpc -i bleth0

Unfortunately the WiFi range leaves something to be desired. When you are performing the procedure above for the first time, move the Ox64 right next to your router. Once you are successfully connected, you can try experimenting with the maximum range.

For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].

=== Appendix ===

==== Adding Nuttx RTOS ====

In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].

First, write the normal Linux image to the SD card if you have not done so already. You can find the correct device under `lsblk`:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=/sdcard.img of=/dev/[DEVICE] bs=1M conv=fsync status=progress

Run the following command to re-read the partition tables. Re-inserting the SD card works too:

$ sudo blockdev --rereadpt /dev/[DEVICE]

Download the NuttX image:

$ mkdir -p ~/ox64/nuttx
$ cd ~/ox64/nuttx
$ wget -O ImageNuttx https://github.com/lupyuen2/wip-pinephone-nuttx/releases/download/bl808d-1/Image

Mount the boot partition and make the required modifications:

$ sudo mount /dev/[DEVICE]2 /mnt
$ sudo cp ImageNuttx /mnt/
$ sudo tee -a /mnt/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Mount the rootfs and make the required modifications:

$ sudo mount /dev/[DEVICE]3 /mnt
$ sudo cp ImageNuttx /mnt/boot/
$ sudo tee -a /mnt/boot/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Enjoy your new Nuttx booting option!

Ox64

2024-06-23T15:51:54Z

Giorez:

[[File:Ox64_board.jpg|thumb|right|The Ox64]]
[[File:Ox64 pinout.png|thumb|Pinout of the production version]]
[[File:RISC-V.png|thumb|right|Powered by RISC-V]]

The '''Ox64''' is a RISC-V based single-board computer based on the Bouffalo Lab BL808 RISC-V SoC with C906 64-bit and E907/E902 32-bit CPU cores supported by 64 MB of embedded PSRAM memory, and with built-in WiFi, Bluetooh and Zigbee radio interfaces. The Ox64 comes in a breadboard-friendly form-factor, has a microSD card slot, a USB 2.0 Type-C port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/openbouffalo/buildroot_bouffalo buildroot] bringing all the work below together with a bootable kernel and updated filesystem images for SD cards
* [https://github.com/smaeul/u-boot/tree/bl808 U-Boot] and [https://github.com/smaeul/opensbi/tree/bl808 OpenSBI] work by Smauel
* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others

Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

* [https://github.com/bouffalolab/bl808_linux Linux for BL808]
* [https://wiki.pine64.org/wiki/File:Linux_BL808.pdf Installation Instructions for Linux on BL808 (Chinese)]
* [https://wiki.pine64.org/wiki/File:Linux_BL808_en.pdf Installation Instructions for Linux on BL808 (machine translated to English)]

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/bouffalolab/bl_mcu_sdk BL808 MCU SDK]
* [https://dev.bouffalolab.com/download BLDevCube Flashing Tool for Windows, macOS and Ubuntu x64]
* [https://wiki.pine64.org/wiki/File:Ox64_BL808UART_connect.pdf Ox64 UART Flashing Guide], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/bl808_demo_event.bin BL808 Demo Firmware: bl808_demo_event.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/whole_flash_data.bin BL808 UART Log Firmware: whole_flash_data.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/BL808.DVK.Quick.Start.pdf BL808 DVK Quick Start]
* [https://github.com/bouffalolab/bl808_linux/tree/main/opensbi-0.6-808 OpenSBI for BL808]
* [https://github.com/bouffalolab/bl-pac/tree/main/bl808 Rust Peripheral Access Crate (PAC) for BL808]
* [https://github.com/bouffalolab/bl-pac/blob/main/bl808/bl808.svd System View Description (SVD) for BL808]

== SoC and Memory Specification ==

[[File:Bouffalo_Lab_icon.png|right]]

Based on the [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]

[[File:BL808_Block_Diagram.jpg|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 480 MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head E907 320 MHz 32-bit RISC-V CPU:

* Supports RISC-V RV32IMAFCP instruction set
* Supports RISC-V 32-bit/16-bit mixed instruction set
* Supports RISC-V machine mode and user mode
* Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
* Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
* Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
* 32K instruction cache, two-way set associative structure
* 16K data cache, two-way set associative structure
* See [https://www.t-head.cn/product/e907?lang=en here]

T-Head E902 150 MHz 32-bit RISC-V CPU:

* See [https://www.t-head.cn/product/e902?lang=en here]

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100 Mbit/s Ethernet (optional, on expansion board)

=== Storage ===
* On-board 16 Mbit (2 MB) or 128 Mbit (16 MB) XSPI NOR flash memory
* MicroSD, supports SDHC and SDXC (only on the 128 Mbit version)

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO pins, including SPI, I2C and UART functionality, possible I2S and GMII expansion
* Dual-lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* Microphone (optional, on the camera module)
* Speaker (optional, on the camera module)

== Board Information, Schematics and Certifications ==
[[File:Ox64 ethphy.png|thumb|Pinout for wiring ethernet PHY to EMAC]]

* Baseboard dimensions: 51 mm x 21 mm x 19 mm x 3.5 mm (breadboard friendly)
* Input power: 5 V, 0.5 A through the microUSB or USB-C ports

Production version schematic:

* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221018.pdf Ox64 Schematic 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221018.pdf Ox64 PCB Component placement(ToP) 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221018.pdf Ox64 PCB Component placement(Bottom) 20221018 v1.1]

Prototype (dispatched to developers) schematic:
* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==

Bouffalo BL808 SoC information:
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf Bouffalo Lab BL808 SoC Datasheet]
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_RM/en/BL808_RM_en_1.3.pdf Bouffalo Lab BL808 SoC Reference Manual]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevice 16Mb XSPI-Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevice 128Mb XSPI-Flash Datasheet]
* [https://wiki.pine64.org/images/5/5d/W25Q128JW_RevB_11042019-1761358.pdf Winbond 128Mb QSPI-Flash Datasheet] (W25Q128JWSQ)

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Compatible UARTs when in bootloader mode ==

When the Ox64 is in bootloader mode, some UARTs are unable to communicate with it. When this is the case, utilities such as BLDevCube are unable to actually program the device. If you see "Shake hand fail" and an empty ack, and your device is in bootloader mode, then it is likely an incompatible UART.

The below devices have been tested and verified as working:
* Raspberry Pi Pico - running the following [https://github.com/sanjay900/ox64-uart/releases/tag/v1.1 UART firmware] (GP4 and GP5 are used for port 0, GP12 and GP13 for port 1)
* Compiled binary for Pi Pico and connectivity diagram is [https://github.com/Kris-Sekula/Pine64_Ox64_SBC/tree/main/uart here]
* ESP32 with CP210x - bridge the EN pin to ground to disable the ESP32 itself, and then connect the TX on the esp32 to 14 on the Ox64 and RX to pin 15. Note that only baud rate 115200 works, and this doesn't seem to work for everyone)
* Stand-alone CP2102 dongle works at 115200 baud. Brand used was HiLetgo.
* STM32F401 BlackPill - running the [https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2 Black Magic Debug] firmware
* STM32F103C8T6 BluePill - running Black Magic Debug.
* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
* Some CH340G based adapters work and some don't.

== Resources and Articles ==
* [https://youtube.com/watch?v=czRtF-UNiEY A short video] on how to connect to the Ox64, flash and boot
* [https://youtu.be/vPAk5sq_Ilc Another video] that covers soldering pins, connecting via Pi Pico and flashing Linux and U-Boot
* [https://wiki.pine64.org/images/5/59/How_to_Run_Ox64.pdf Step-by-step tutorial] for how to build, flash and run Ox64
* [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff First batch of Ox64 won't appear as USB serial port]
* [https://gist.github.com/lupyuen/2087e9b3fb40aab5e0795bb02a265a3b First batch of Ox64 tested OK with CH340C/G]
* [https://www.robertlipe.com/bl808-not-symmetric/ First thoughts on the (a)symmetry of Bouffalo Labs BL808 as in Pine64 Ox64]
* [https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html The $8 linux computer (with picoprobe-rp2040 programming instructions)]
* [https://github.com/p4ddy1/pine_ox64/blob/main/build_toolchain_macos.md Building the Xuantie GNU Toolchain for Ox64 on macOS and Apple Silicon]

Ox64 BL808 RISC-V SBC articles by [https://lupyuen.codeberg.page/ Lup Yuen LEE]:
* [https://lupyuen.codeberg.page/articles/ox64.html Booting Linux and (maybe) Apache NuttX RTOS]
* [https://lupyuen.codeberg.page/articles/ox2.html Starting Apache NuttX real-time operating system]
* [https://lupyuen.codeberg.page/articles/mmu.html Sv39 Memory Management Unit]
* [https://lupyuen.codeberg.page/articles/app.html NuttX Apps and Initial RAM Disk]
* [https://lupyuen.codeberg.page/articles/plic2.html UART Interrupt and Platform-Level Interrupt Controller (PLIC)]
* [https://lupyuen.codeberg.page/articles/plic3.html Fixing the UART Interrupt and Platform-Level Interrupt Controller]
* [https://www.hackster.io/lupyuen/8-risc-v-sbc-on-a-real-time-operating-system-ox64-nuttx-474358 $8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX]
* [https://lupyuen.codeberg.page/articles/nim.html Nim on a Real-Time Operating System: Apache NuttX RTOS + Ox64 BL808 SBC]

Git repositories:
* [https://github.com/sfranzyshen/arduino-bl808 Community made Arduino Core specifically for the Bouffalo Labs BL808 RISC-V MCU] (initial development has been postponed until further notice)

== Development Efforts ==
* [https://twitter.com/gamelaster/status/1583916501400068096 Ox64 boots Linux successfully]
* [https://twitter.com/btashton/status/1586381334439923713?t=w5xRRUR74HGK2O1Zg_aFyw&s=19 Brennan Ashton is porting Apache NuttX RTOS and OpenAMP (Asymmetric Multiprocessing) to BL808]
* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

== Building ==
Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

$ mkdir -p ~/ox64
$ cd ~/ox64
$ git clone https://github.com/buildroot/buildroot
$ git clone https://github.com/openbouffalo/buildroot_bouffalo

Define an environment variable for the Buildroot Bouffalo overlay path:

$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo

Change directory into the cloned Buildroot folder:

$ cd ~/ox64/buildroot

Apply the default configuration for Pine64 Ox64:

$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig

Use the `menuconfig` tool to adjust the build settings:

$ make menuconfig

Within `menuconfig`, configure the following:

* Select `Target Options`
* Enable `Integer Multiplication and Division (M)`
* Enable `Atomic Instructions (A)` using space key
* Enable `Single-precision Floating-point (F)`
* Enable `Double-precision Floating-point (D)`
* Select `Target ABI`, set it to `lp64d` and `press Exit`
* Select `Toolchain`, enable `Fortran support`, enable `OpenMP support`, and Save & Exit

Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.

$ make

Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

== Flashing ==
This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

== Prepare images for flashing ==

Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.

$ mkdir -p ~/ox64/openbouffalo
$ cd ~/ox64/openbouffalo
$ wget https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ tar -xvzf bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ cd ~/ox64/openbouffalo/firmware
$ xz -v -d -k sdcard-pine64_ox64_full_defconfig.img.xz
$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img

=== Optional: create a combined SoC image ===

Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ fallocate -l 0x800000 bl808-combined.bin
$ dd conv=notrunc if=m0_lowload_bl808_m0.bin of=bl808-combined.bin
$ dd conv=notrunc if=d0_lowload_bl808_d0.bin of=bl808-combined.bin seek=$((0x100000))B
$ cat bl808-firmware.bin >> bl808-combined.bin

=== Check that you have the required files for flashing ===

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ ls -1 *808*.bin *.img

Expected files:

* `bl808-combined.bin` -- If you created the combined image.
* `bl808-firmware.bin` -- OpenSBI and UBoot DTB files. Runs on the D0 core.
* `d0_lowload_bl808_d0.bin` -- Startup code for the D0 core.
* `m0_lowload_bl808_m0.bin` -- Startup code for the M0 core.
* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.

== Set up your UART adapter ==

In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.

=== Option 1: Raspberry Pi Pico ===

First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:

$ mkdir -p ~/ox64/pico
$ cd ~/ox64/pico
$ wget https://github.com/Kris-Sekula/Pine64_Ox64_SBC/raw/main/uart/picoprobe.uf2

Put the Raspberry Pi Pico board into programming mode:

* Press the BootSel button
* Apply power by plugging the USB cable to PC
* Release the BootSel button

NOTE: As an alternative to pressing the BootSel button, you can also connect the probe point `TP6` (located on the bottom of the Pico board) to any ground point (e. g. pin 28).

The Pico will now appear as a USB mass storage device. Copy the `UF2` file to program it:

$ cp ~/ox64/pico/picoprobe.uf2 /media/<user>/RPI-RP2

Next, connect the Ox64 board to the Pico according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | PI PICO | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_pin17
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_pin16
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_pin6
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_pin7
| ACM0 for serial console

| gnd_pin38
| gnd_pin38/3
|

| vbus5v_pin40
| vbus5v_pin40
|
|===

With the Pico flashed and wired as per the instructions above, we have access to two of the Ox64's UART ports at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Reconnect the Pico to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)

=== Option 2: STM32 Bluepill ===

The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.

[NOTE]

The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does **not** have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).

If you own an SWD-capable debugger (ST-Link, J-link, etc.) you can use that for programming the Bluepill as well, although instead of `stm32flash` console command you would be using https://openocd.org/[openocd] or other suitable software.

WARNING: Your serial adapter must use 3.3V logic levels.

Install software to flash Bluepill. For Debian-based systems just install package from repository:

$ sudo apt install stm32flash

For Arch Linux systems, use the AUR repository:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ git clone https://aur.archlinux.org/stm32flash.git
$ cd ~/ox64/bluepill/stm32flash
$ makepkg -si

Download the https://github.com/r2axz/bluepill-serial-monster[Bluepill Serial Monster] firmware:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ wget https://github.com/r2axz/bluepill-serial-monster/releases/download/v2.6.4/bluepill-serial-monster.hex

Put the Bluepill into programming mode:

* Set boot jumpers for booting from rom: Boot0=1, Boot1=0.
* Connect it to a USB-Serial adapter with A9 to Rx, A10 to Tx, GND to GND, 3v3 to Vcc.
* Apply power by plugging the USB cable to PC. Press the Reset button.

Find your USB serial adapter's device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`. Upload the firmware:

$ cd ~/ox64/bluepill
$ sudo stm32flash -w bluepill-serial-monster.hex /dev/tty[DEVICE]

After upload, set boot jumpers for boot from flash: Boot0=0, Boot1=0. Disconnect the USB serial adapter from both the PC and Bluepill board.

Next, connect the Ox64 board to the Bluepill according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | Bluepill | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_A3
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_A2
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_A9
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_A10
| ACM0 for serial console

| gnd_pin38
| GND
|

| vbus5v_pin40
| 5V
|

|===

With the Bluepill flashed and wired as per the instructions above, we have access to two of the Ox64's UART connections at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Connect the Bluepill to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)
* `/dev/ttyACM2` (unused)

=== Option 3: Generic UART adapter ===

image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]

Check that your serial adapter is on the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. You will (most likely) only have one serial interface available to you; unlike the previous options you will be using this same serial interface for both flashing and testing the system.

Find its device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`.

You will also need a way of powering your Ox64. If your serial adapter has a 5V line, you can connect it to VBUS (pin 40). Otherwise, you can connect either the micro-B or the USB-C port on the Ox64 to any 5V power supply.

WARNING: Your serial adapter must use 3.3V logic levels.

Refer to the pinout image below. Connect your UART adapter as follows:

* RX -> UART0_TX / GPIO14 / pin 1
* TX -> UART0_RX / GPIO15 / pin 2
* GND -> any ground (e. g. pin 3)

Proceed with the instructions in the sections that follow, up to and including <<flashing_the_ox64>> and <<flashing_the_microsd_card>>, but replace all occurrences of `/dev/ttyACM1` with `/dev/tty[DEVICE]`.

Next, power off the Ox64 and re-connect your UART adapter as follows:

* RX -> TXD / GPIO16 / pin 32
* TX -> RXD / GPIO17 / pin 31
* GND -> any ground (e. g. pin 33)

Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.

== Download flashing tools ==

You have a choice of flashing software:

* DevCube: GUI-based closed source flashing tool
* CLI (`bflb-iot-tool`): command line open source flashing tool

=== DevCube installation ===

Download the latest DevCube flashing tool from BouffaloLab's website:

$ mkdir -p ~/ox64/devcube
$ cd ~/ox64/devcube
$ wget https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.9.zip
$ unzip BouffaloLabDevCube-v1.8.9.zip
$ chmod u+x BLDevCube-ubuntu

If you did not create a link:#optional_create_a_combined_soc_image[combined image] you may need an older version of the DevCube. In that case, download v1.8.3 from one of the mirrors below:

* https://openbouffalo.org/static-assets/bldevcube/BouffaloLabDevCube-v1.8.3.zip
* https://hachyderm.io/@mkroman/110787218805897192[] > https://pub.rwx.im/~mk/bouffalolab/BouffaloLabDevCube-v1.8.3.zip
* https://we.tl/t-eJWShQJ4iF
* https://cdn.discordapp.com/attachments/771032441971802142/1145565853962735639/BouffaloLabDevCube-v1.8.3.zip

Verify that your copy of `BouffaloLabDevCube-v1.8.3.zip` matches the hashes below:

* SHA1: `0f2619e87d946f936f63ae97b0efd674357b1166`
* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`

=== CLI packages installation ===

Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:

$ sudo apt install pipenv # for Debian-based systems
# or
$ sudo pacman -S python-pipenv # for Arch Linux systems

$ cd ~/ox64/
$ pipenv install setuptools # install prerequisite of CLI flash tool
$ pipenv install bflb-iot-tool # install CLI flash tool
$ pipenv shell # activate virtual environment
$ # bflb-iot-tool --help # return info about the tool

NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.

== Flashing the Ox64 ==

Put the Ox64 into programming mode:

* Press the BOOT button
* Apply power or re-plug the USB cable
* Release the BOOT button

=== CLI flashing method ===

Set up some environment variables to save typing them out later:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ PORT=/dev/ttyACM1
$ BAUD=230400 # safe value for macOS, set to 2000000 for faster flashing on Linux

Finally, flash the Ox64. If you created a link:#optional_create_a_combined_soc_image[combined image] then run the command below:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware bl808-combined.bin --single

Otherwise, run the following commands:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware m0_lowload_bl808_m0.bin --single
$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single
$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x800000 --firmware bl808-firmware.bin --single

If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.

=== BLDevCube flashing method

Open a new terminal window to run the DevCube flasher:

$ cd ~/ox64/devcube
$ ./BLDevCube-ubuntu

Select chip [BL808], press Finish, and configure BOTH the [MCU] and [IOT] tabs as follows. When you switch between tabs double check that they still match the settings below:

[cols="~,~"]
|===
|Interface
|UART

|Port/SN
|`/dev/ttyACM1`

|UART rate
|230400 (safe value for macOS, set to 2000000 for faster flashing on Linux)
|===

If you created a link:#optional_create_a_combined_soc_image[combined image] then you only need to use the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x0], [PATH to bl808-combined.bin]
* Click 'Create & Download' and wait until it's done
* Close DevCube

Otherwise, start in the [MCU] tab:

* M0 Group[group0], Image Address [0x58000000], [PATH to m0_lowload_bl808_m0.bin]
* D0 Group[group0], Image Address [0x58100000], [PATH to d0_lowload_bl808_d0.bin]
* Click 'Create & Download' and wait until it's done

Then, switch to the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x800000], [PATH to bl808-firmware.bin]
* Click 'Create & Download' again and wait until it's done
* Close DevCube

== Erasing the microSD card ==

Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.

$ sudo wipefs /dev/[DEVICE]
$ sudo wipefs --all --force /dev/[DEVICE]*
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=1

Optionally you can zeroes the whole device:

$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] | head -1) \/ 32768)

== Flashing the microSD card ==

Insert the microSD card into your PC, locate its device under `lsblk` and write the image:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync

== Booting for the first time ==

Power off your Ox64 and insert the microSD card.

Open a terminal window to connect to the D0 core’s (i.e. Linux’s) serial console:

$ minicom -b 2000000 -D /dev/ttyACM0

If you are using a Pico or Bluepill as your serial adapter, open another terminal window to to monitor the M0 core’s serial console (reminder: `/dev/ttyACM1` is the same port we previously used for flashing):

$ minicom -b 2000000 -D /dev/ttyACM1

Re-apply power to the Ox64.

On the main/D0 console (`/dev/ttyACM0`) you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error.

On the M0 console (`/dev/ttyACM1`) you'll see following messages until the sytem is fully loaded:

----
[I][MBOX] Mailbox IRQ Stats:
[I][MBOX] Peripheral SDH (33): 0
[I][MBOX] Peripheral GPIO (60): 0
[I][MBOX] Unhandled Interupts: 0 Unhandled Signals 0
----

Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.

=== Connecting the Ox64 to your WiFi network ===

The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):

$ blctl connect_ap <YourSSID> <YourPassword>

Wait for it to connect (if you're monitoring the M0 console on `/dev/ttyACM1` it should tell you when it's done), then run the following command from the Linux console:

$ udhcpc -i bleth0

Unfortunately the WiFi range leaves something to be desired. When you are performing the procedure above for the first time, move the Ox64 right next to your router. Once you are successfully connected, you can try experimenting with the maximum range.

For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].

== Appendix ==

=== Adding Nuttx RTOS ===

In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].

First, write the normal Linux image to the SD card if you have not done so already. You can find the correct device under `lsblk`:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=/sdcard.img of=/dev/[DEVICE] bs=1M conv=fsync status=progress

Run the following command to re-read the partition tables. Re-inserting the SD card works too:

$ sudo blockdev --rereadpt /dev/[DEVICE]

Download the NuttX image:

$ mkdir -p ~/ox64/nuttx
$ cd ~/ox64/nuttx
$ wget -O ImageNuttx https://github.com/lupyuen2/wip-pinephone-nuttx/releases/download/bl808d-1/Image

Mount the boot partition and make the required modifications:

$ sudo mount /dev/[DEVICE]2 /mnt
$ sudo cp ImageNuttx /mnt/
$ sudo tee -a /mnt/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Mount the rootfs and make the required modifications:

$ sudo mount /dev/[DEVICE]3 /mnt
$ sudo cp ImageNuttx /mnt/boot/
$ sudo tee -a /mnt/boot/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Enjoy your new Nuttx booting option!

Ox64

2024-06-23T15:46:05Z

Giorez: /* Flashing */

[[File:Ox64_board.jpg|thumb|right|The Ox64]]
[[File:Ox64 pinout.png|thumb|Pinout of the production version]]
[[File:RISC-V.png|thumb|right|Powered by RISC-V]]

The '''Ox64''' is a RISC-V based single-board computer based on the Bouffalo Lab BL808 RISC-V SoC with C906 64-bit and E907/E902 32-bit CPU cores supported by 64 MB of embedded PSRAM memory, and with built-in WiFi, Bluetooh and Zigbee radio interfaces. The Ox64 comes in a breadboard-friendly form-factor, has a microSD card slot, a USB 2.0 Type-C port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/openbouffalo/buildroot_bouffalo buildroot] bringing all the work below together with a bootable kernel and updated filesystem images for SD cards
* [https://github.com/smaeul/u-boot/tree/bl808 U-Boot] and [https://github.com/smaeul/opensbi/tree/bl808 OpenSBI] work by Smauel
* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others

Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

* [https://github.com/bouffalolab/bl808_linux Linux for BL808]
* [https://wiki.pine64.org/wiki/File:Linux_BL808.pdf Installation Instructions for Linux on BL808 (Chinese)]
* [https://wiki.pine64.org/wiki/File:Linux_BL808_en.pdf Installation Instructions for Linux on BL808 (machine translated to English)]

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/bouffalolab/bl_mcu_sdk BL808 MCU SDK]
* [https://dev.bouffalolab.com/download BLDevCube Flashing Tool for Windows, macOS and Ubuntu x64]
* [https://wiki.pine64.org/wiki/File:Ox64_BL808UART_connect.pdf Ox64 UART Flashing Guide], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/bl808_demo_event.bin BL808 Demo Firmware: bl808_demo_event.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/whole_flash_data.bin BL808 UART Log Firmware: whole_flash_data.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/BL808.DVK.Quick.Start.pdf BL808 DVK Quick Start]
* [https://github.com/bouffalolab/bl808_linux/tree/main/opensbi-0.6-808 OpenSBI for BL808]
* [https://github.com/bouffalolab/bl-pac/tree/main/bl808 Rust Peripheral Access Crate (PAC) for BL808]
* [https://github.com/bouffalolab/bl-pac/blob/main/bl808/bl808.svd System View Description (SVD) for BL808]

== SoC and Memory Specification ==

[[File:Bouffalo_Lab_icon.png|right]]

Based on the [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]

[[File:BL808_Block_Diagram.jpg|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 480 MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head E907 320 MHz 32-bit RISC-V CPU:

* Supports RISC-V RV32IMAFCP instruction set
* Supports RISC-V 32-bit/16-bit mixed instruction set
* Supports RISC-V machine mode and user mode
* Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
* Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
* Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
* 32K instruction cache, two-way set associative structure
* 16K data cache, two-way set associative structure
* See [https://www.t-head.cn/product/e907?lang=en here]

T-Head E902 150 MHz 32-bit RISC-V CPU:

* See [https://www.t-head.cn/product/e902?lang=en here]

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100 Mbit/s Ethernet (optional, on expansion board)

=== Storage ===
* On-board 16 Mbit (2 MB) or 128 Mbit (16 MB) XSPI NOR flash memory
* MicroSD, supports SDHC and SDXC (only on the 128 Mbit version)

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO pins, including SPI, I2C and UART functionality, possible I2S and GMII expansion
* Dual-lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* Microphone (optional, on the camera module)
* Speaker (optional, on the camera module)

== Board Information, Schematics and Certifications ==
[[File:Ox64 ethphy.png|thumb|Pinout for wiring ethernet PHY to EMAC]]

* Baseboard dimensions: 51 mm x 21 mm x 19 mm x 3.5 mm (breadboard friendly)
* Input power: 5 V, 0.5 A through the microUSB or USB-C ports

Production version schematic:

* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221018.pdf Ox64 Schematic 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221018.pdf Ox64 PCB Component placement(ToP) 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221018.pdf Ox64 PCB Component placement(Bottom) 20221018 v1.1]

Prototype (dispatched to developers) schematic:
* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==

Bouffalo BL808 SoC information:
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf Bouffalo Lab BL808 SoC Datasheet]
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_RM/en/BL808_RM_en_1.3.pdf Bouffalo Lab BL808 SoC Reference Manual]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevice 16Mb XSPI-Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevice 128Mb XSPI-Flash Datasheet]
* [https://wiki.pine64.org/images/5/5d/W25Q128JW_RevB_11042019-1761358.pdf Winbond 128Mb QSPI-Flash Datasheet] (W25Q128JWSQ)

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Compatible UARTs when in bootloader mode ==

When the Ox64 is in bootloader mode, some UARTs are unable to communicate with it. When this is the case, utilities such as BLDevCube are unable to actually program the device. If you see "Shake hand fail" and an empty ack, and your device is in bootloader mode, then it is likely an incompatible UART.

The below devices have been tested and verified as working:
* Raspberry Pi Pico - running the following [https://github.com/sanjay900/ox64-uart/releases/tag/v1.1 UART firmware] (GP4 and GP5 are used for port 0, GP12 and GP13 for port 1)
* Compiled binary for Pi Pico and connectivity diagram is [https://github.com/Kris-Sekula/Pine64_Ox64_SBC/tree/main/uart here]
* ESP32 with CP210x - bridge the EN pin to ground to disable the ESP32 itself, and then connect the TX on the esp32 to 14 on the Ox64 and RX to pin 15. Note that only baud rate 115200 works, and this doesn't seem to work for everyone)
* Stand-alone CP2102 dongle works at 115200 baud. Brand used was HiLetgo.
* STM32F401 BlackPill - running the [https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2 Black Magic Debug] firmware
* STM32F103C8T6 BluePill - running Black Magic Debug.
* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
* Some CH340G based adapters work and some don't.

== Resources and Articles ==
* [https://youtube.com/watch?v=czRtF-UNiEY A short video] on how to connect to the Ox64, flash and boot
* [https://youtu.be/vPAk5sq_Ilc Another video] that covers soldering pins, connecting via Pi Pico and flashing Linux and U-Boot
* [https://wiki.pine64.org/images/5/59/How_to_Run_Ox64.pdf Step-by-step tutorial] for how to build, flash and run Ox64
* [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff First batch of Ox64 won't appear as USB serial port]
* [https://gist.github.com/lupyuen/2087e9b3fb40aab5e0795bb02a265a3b First batch of Ox64 tested OK with CH340C/G]
* [https://www.robertlipe.com/bl808-not-symmetric/ First thoughts on the (a)symmetry of Bouffalo Labs BL808 as in Pine64 Ox64]
* [https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html The $8 linux computer (with picoprobe-rp2040 programming instructions)]
* [https://github.com/p4ddy1/pine_ox64/blob/main/build_toolchain_macos.md Building the Xuantie GNU Toolchain for Ox64 on macOS and Apple Silicon]

Ox64 BL808 RISC-V SBC articles by [https://lupyuen.codeberg.page/ Lup Yuen LEE]:
* [https://lupyuen.codeberg.page/articles/ox64.html Booting Linux and (maybe) Apache NuttX RTOS]
* [https://lupyuen.codeberg.page/articles/ox2.html Starting Apache NuttX real-time operating system]
* [https://lupyuen.codeberg.page/articles/mmu.html Sv39 Memory Management Unit]
* [https://lupyuen.codeberg.page/articles/app.html NuttX Apps and Initial RAM Disk]
* [https://lupyuen.codeberg.page/articles/plic2.html UART Interrupt and Platform-Level Interrupt Controller (PLIC)]
* [https://lupyuen.codeberg.page/articles/plic3.html Fixing the UART Interrupt and Platform-Level Interrupt Controller]
* [https://www.hackster.io/lupyuen/8-risc-v-sbc-on-a-real-time-operating-system-ox64-nuttx-474358 $8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX]
* [https://lupyuen.codeberg.page/articles/nim.html Nim on a Real-Time Operating System: Apache NuttX RTOS + Ox64 BL808 SBC]

Git repositories:
* [https://github.com/sfranzyshen/arduino-bl808 Community made Arduino Core specifically for the Bouffalo Labs BL808 RISC-V MCU] (initial development has been postponed until further notice)

== Development Efforts ==
* [https://twitter.com/gamelaster/status/1583916501400068096 Ox64 boots Linux successfully]
* [https://twitter.com/btashton/status/1586381334439923713?t=w5xRRUR74HGK2O1Zg_aFyw&s=19 Brennan Ashton is porting Apache NuttX RTOS and OpenAMP (Asymmetric Multiprocessing) to BL808]
* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

== Building ==
Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

$ mkdir -p ~/ox64
$ cd ~/ox64
$ git clone https://github.com/buildroot/buildroot
$ git clone https://github.com/openbouffalo/buildroot_bouffalo

Define an environment variable for the Buildroot Bouffalo overlay path:

$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo

Change directory into the cloned Buildroot folder:

$ cd ~/ox64/buildroot

Apply the default configuration for Pine64 Ox64:

$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig

Use the `menuconfig` tool to adjust the build settings:

$ make menuconfig

Within `menuconfig`, configure the following:

* Select `Target Options`
* Enable `Integer Multiplication and Division (M)`
* Enable `Atomic Instructions (A)` using space key
* Enable `Single-precision Floating-point (F)`
* Enable `Double-precision Floating-point (D)`
* Select `Target ABI`, set it to `lp64d` and `press Exit`
* Select `Toolchain`, enable `Fortran support`, enable `OpenMP support`, and Save & Exit

Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.

$ make

Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

== Flashing ==
This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

== Prepare images for flashing

Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.

$ mkdir -p ~/ox64/openbouffalo
$ cd ~/ox64/openbouffalo
$ wget https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ tar -xvzf bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ cd ~/ox64/openbouffalo/firmware
$ xz -v -d -k sdcard-pine64_ox64_full_defconfig.img.xz
$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img

=== Optional: create a combined SoC image

Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ fallocate -l 0x800000 bl808-combined.bin
$ dd conv=notrunc if=m0_lowload_bl808_m0.bin of=bl808-combined.bin
$ dd conv=notrunc if=d0_lowload_bl808_d0.bin of=bl808-combined.bin seek=$((0x100000))B
$ cat bl808-firmware.bin >> bl808-combined.bin

=== Check that you have the required files for flashing

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ ls -1 *808*.bin *.img

Expected files:

* `bl808-combined.bin` -- If you created the combined image.
* `bl808-firmware.bin` -- OpenSBI and UBoot DTB files. Runs on the D0 core.
* `d0_lowload_bl808_d0.bin` -- Startup code for the D0 core.
* `m0_lowload_bl808_m0.bin` -- Startup code for the M0 core.
* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.

== Set up your UART adapter

In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.

=== Option 1: Raspberry Pi Pico

First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:

$ mkdir -p ~/ox64/pico
$ cd ~/ox64/pico
$ wget https://github.com/Kris-Sekula/Pine64_Ox64_SBC/raw/main/uart/picoprobe.uf2

Put the Raspberry Pi Pico board into programming mode:

* Press the BootSel button
* Apply power by plugging the USB cable to PC
* Release the BootSel button

NOTE: As an alternative to pressing the BootSel button, you can also connect the probe point `TP6` (located on the bottom of the Pico board) to any ground point (e. g. pin 28).

The Pico will now appear as a USB mass storage device. Copy the `UF2` file to program it:

$ cp ~/ox64/pico/picoprobe.uf2 /media/<user>/RPI-RP2

Next, connect the Ox64 board to the Pico according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | PI PICO | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_pin17
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_pin16
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_pin6
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_pin7
| ACM0 for serial console

| gnd_pin38
| gnd_pin38/3
|

| vbus5v_pin40
| vbus5v_pin40
|
|===

With the Pico flashed and wired as per the instructions above, we have access to two of the Ox64's UART ports at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Reconnect the Pico to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)

=== Option 2: STM32 Bluepill

The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.

[NOTE]

====
The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does **not** have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).

If you own an SWD-capable debugger (ST-Link, J-link, etc.) you can use that for programming the Bluepill as well, although instead of `stm32flash` console command you would be using https://openocd.org/[openocd] or other suitable software.
====

WARNING: Your serial adapter must use 3.3V logic levels.

Install software to flash Bluepill. For Debian-based systems just install package from repository:

$ sudo apt install stm32flash

For Arch Linux systems, use the AUR repository:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ git clone https://aur.archlinux.org/stm32flash.git
$ cd ~/ox64/bluepill/stm32flash
$ makepkg -si

Download the https://github.com/r2axz/bluepill-serial-monster[Bluepill Serial Monster] firmware:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ wget https://github.com/r2axz/bluepill-serial-monster/releases/download/v2.6.4/bluepill-serial-monster.hex

Put the Bluepill into programming mode:

* Set boot jumpers for booting from rom: Boot0=1, Boot1=0.
* Connect it to a USB-Serial adapter with A9 to Rx, A10 to Tx, GND to GND, 3v3 to Vcc.
* Apply power by plugging the USB cable to PC. Press the Reset button.

Find your USB serial adapter's device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`. Upload the firmware:

$ cd ~/ox64/bluepill
$ sudo stm32flash -w bluepill-serial-monster.hex /dev/tty[DEVICE]

After upload, set boot jumpers for boot from flash: Boot0=0, Boot1=0. Disconnect the USB serial adapter from both the PC and Bluepill board.

Next, connect the Ox64 board to the Bluepill according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | Bluepill | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_A3
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_A2
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_A9
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_A10
| ACM0 for serial console

| gnd_pin38
| GND
|

| vbus5v_pin40
| 5V
|

|===

With the Bluepill flashed and wired as per the instructions above, we have access to two of the Ox64's UART connections at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Connect the Bluepill to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)
* `/dev/ttyACM2` (unused)

=== Option 3: Generic UART adapter

image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]

Check that your serial adapter is on the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. You will (most likely) only have one serial interface available to you; unlike the previous options you will be using this same serial interface for both flashing and testing the system.

Find its device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`.

You will also need a way of powering your Ox64. If your serial adapter has a 5V line, you can connect it to VBUS (pin 40). Otherwise, you can connect either the micro-B or the USB-C port on the Ox64 to any 5V power supply.

WARNING: Your serial adapter must use 3.3V logic levels.

Refer to the pinout image below. Connect your UART adapter as follows:

* RX -> UART0_TX / GPIO14 / pin 1
* TX -> UART0_RX / GPIO15 / pin 2
* GND -> any ground (e. g. pin 3)

Proceed with the instructions in the sections that follow, up to and including <<flashing_the_ox64>> and <<flashing_the_microsd_card>>, but replace all occurrences of `/dev/ttyACM1` with `/dev/tty[DEVICE]`.

Next, power off the Ox64 and re-connect your UART adapter as follows:

* RX -> TXD / GPIO16 / pin 32
* TX -> RXD / GPIO17 / pin 31
* GND -> any ground (e. g. pin 33)

Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.

== Download flashing tools

You have a choice of flashing software:

* DevCube: GUI-based closed source flashing tool
* CLI (`bflb-iot-tool`): command line open source flashing tool

=== DevCube installation

Download the latest DevCube flashing tool from BouffaloLab's website:

$ mkdir -p ~/ox64/devcube
$ cd ~/ox64/devcube
$ wget https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.9.zip
$ unzip BouffaloLabDevCube-v1.8.9.zip
$ chmod u+x BLDevCube-ubuntu

If you did not create a link:#optional_create_a_combined_soc_image[combined image] you may need an older version of the DevCube. In that case, download v1.8.3 from one of the mirrors below:

* https://openbouffalo.org/static-assets/bldevcube/BouffaloLabDevCube-v1.8.3.zip
* https://hachyderm.io/@mkroman/110787218805897192[] > https://pub.rwx.im/~mk/bouffalolab/BouffaloLabDevCube-v1.8.3.zip
* https://we.tl/t-eJWShQJ4iF
* https://cdn.discordapp.com/attachments/771032441971802142/1145565853962735639/BouffaloLabDevCube-v1.8.3.zip

Verify that your copy of `BouffaloLabDevCube-v1.8.3.zip` matches the hashes below:

* SHA1: `0f2619e87d946f936f63ae97b0efd674357b1166`
* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`

=== CLI packages installation

Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:

$ sudo apt install pipenv # for Debian-based systems
# or
$ sudo pacman -S python-pipenv # for Arch Linux systems

$ cd ~/ox64/
$ pipenv install setuptools # install prerequisite of CLI flash tool
$ pipenv install bflb-iot-tool # install CLI flash tool
$ pipenv shell # activate virtual environment
$ # bflb-iot-tool --help # return info about the tool

NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.

== Flashing the Ox64

Put the Ox64 into programming mode:

* Press the BOOT button
* Apply power or re-plug the USB cable
* Release the BOOT button

=== CLI flashing method

Set up some environment variables to save typing them out later:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ PORT=/dev/ttyACM1
$ BAUD=230400 # safe value for macOS, set to 2000000 for faster flashing on Linux

Finally, flash the Ox64. If you created a link:#optional_create_a_combined_soc_image[combined image] then run the command below:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware bl808-combined.bin --single

Otherwise, run the following commands:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware m0_lowload_bl808_m0.bin --single

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x800000 --firmware bl808-firmware.bin --single

If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.

=== BLDevCube flashing method

Open a new terminal window to run the DevCube flasher:

$ cd ~/ox64/devcube
$ ./BLDevCube-ubuntu

Select chip [BL808], press Finish, and configure BOTH the [MCU] and [IOT] tabs as follows. When you switch between tabs double check that they still match the settings below:

[cols="~,~"]
|===
|Interface
|UART

|Port/SN
|`/dev/ttyACM1`

|UART rate
|230400 (safe value for macOS, set to 2000000 for faster flashing on Linux)
|===

If you created a link:#optional_create_a_combined_soc_image[combined image] then you only need to use the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x0], [PATH to bl808-combined.bin]
* Click 'Create & Download' and wait until it's done
* Close DevCube

Otherwise, start in the [MCU] tab:

* M0 Group[group0], Image Address [0x58000000], [PATH to m0_lowload_bl808_m0.bin]
* D0 Group[group0], Image Address [0x58100000], [PATH to d0_lowload_bl808_d0.bin]
* Click 'Create & Download' and wait until it's done

Then, switch to the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x800000], [PATH to bl808-firmware.bin]
* Click 'Create & Download' again and wait until it's done
* Close DevCube

== Erasing the microSD card

Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.

$ sudo wipefs /dev/[DEVICE]
$ sudo wipefs --all --force /dev/[DEVICE]*
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=1

Optionally you can zeroes the whole device:

$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] | head -1) \/ 32768)

== Flashing the microSD card

Insert the microSD card into your PC, locate its device under `lsblk` and write the image:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync

== Booting for the first time

Power off your Ox64 and insert the microSD card.

Open a terminal window to connect to the D0 core’s (i.e. Linux’s) serial console:

$ minicom -b 2000000 -D /dev/ttyACM0

If you are using a Pico or Bluepill as your serial adapter, open another terminal window to to monitor the M0 core’s serial console (reminder: `/dev/ttyACM1` is the same port we previously used for flashing):

$ minicom -b 2000000 -D /dev/ttyACM1

Re-apply power to the Ox64.

On the main/D0 console (`/dev/ttyACM0`) you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error.

On the M0 console (`/dev/ttyACM1`) you'll see following messages until the sytem is fully loaded:

----
[I][MBOX] Mailbox IRQ Stats:
[I][MBOX] Peripheral SDH (33): 0
[I][MBOX] Peripheral GPIO (60): 0
[I][MBOX] Unhandled Interupts: 0 Unhandled Signals 0
----

Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.

=== Connecting the Ox64 to your WiFi network
The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):

$ blctl connect_ap <YourSSID> <YourPassword>

Wait for it to connect (if you're monitoring the M0 console on `/dev/ttyACM1` it should tell you when it's done), then run the following command from the Linux console:

$ udhcpc -i bleth0

Unfortunately the WiFi range leaves something to be desired. When you are performing the procedure above for the first time, move the Ox64 right next to your router. Once you are successfully connected, you can try experimenting with the maximum range.

For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].

== Appendix

=== Adding Nuttx RTOS

In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].

First, write the normal Linux image to the SD card if you have not done so already. You can find the correct device under `lsblk`:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=/sdcard.img of=/dev/[DEVICE] bs=1M conv=fsync status=progress

Run the following command to re-read the partition tables. Re-inserting the SD card works too:

$ sudo blockdev --rereadpt /dev/[DEVICE]

Download the NuttX image:

$ mkdir -p ~/ox64/nuttx
$ cd ~/ox64/nuttx
$ wget -O ImageNuttx https://github.com/lupyuen2/wip-pinephone-nuttx/releases/download/bl808d-1/Image

Mount the boot partition and make the required modifications:

$ sudo mount /dev/[DEVICE]2 /mnt
$ sudo cp ImageNuttx /mnt/
$ sudo tee -a /mnt/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Mount the rootfs and make the required modifications:

$ sudo mount /dev/[DEVICE]3 /mnt
$ sudo cp ImageNuttx /mnt/boot/
$ sudo tee -a /mnt/boot/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Enjoy your new Nuttx booting option!

Ox64

2024-06-23T15:45:31Z

Giorez: /* Building */

[[File:Ox64_board.jpg|thumb|right|The Ox64]]
[[File:Ox64 pinout.png|thumb|Pinout of the production version]]
[[File:RISC-V.png|thumb|right|Powered by RISC-V]]

The '''Ox64''' is a RISC-V based single-board computer based on the Bouffalo Lab BL808 RISC-V SoC with C906 64-bit and E907/E902 32-bit CPU cores supported by 64 MB of embedded PSRAM memory, and with built-in WiFi, Bluetooh and Zigbee radio interfaces. The Ox64 comes in a breadboard-friendly form-factor, has a microSD card slot, a USB 2.0 Type-C port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/openbouffalo/buildroot_bouffalo buildroot] bringing all the work below together with a bootable kernel and updated filesystem images for SD cards
* [https://github.com/smaeul/u-boot/tree/bl808 U-Boot] and [https://github.com/smaeul/opensbi/tree/bl808 OpenSBI] work by Smauel
* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others

Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

* [https://github.com/bouffalolab/bl808_linux Linux for BL808]
* [https://wiki.pine64.org/wiki/File:Linux_BL808.pdf Installation Instructions for Linux on BL808 (Chinese)]
* [https://wiki.pine64.org/wiki/File:Linux_BL808_en.pdf Installation Instructions for Linux on BL808 (machine translated to English)]

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/bouffalolab/bl_mcu_sdk BL808 MCU SDK]
* [https://dev.bouffalolab.com/download BLDevCube Flashing Tool for Windows, macOS and Ubuntu x64]
* [https://wiki.pine64.org/wiki/File:Ox64_BL808UART_connect.pdf Ox64 UART Flashing Guide], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/bl808_demo_event.bin BL808 Demo Firmware: bl808_demo_event.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/whole_flash_data.bin BL808 UART Log Firmware: whole_flash_data.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/BL808.DVK.Quick.Start.pdf BL808 DVK Quick Start]
* [https://github.com/bouffalolab/bl808_linux/tree/main/opensbi-0.6-808 OpenSBI for BL808]
* [https://github.com/bouffalolab/bl-pac/tree/main/bl808 Rust Peripheral Access Crate (PAC) for BL808]
* [https://github.com/bouffalolab/bl-pac/blob/main/bl808/bl808.svd System View Description (SVD) for BL808]

== SoC and Memory Specification ==

[[File:Bouffalo_Lab_icon.png|right]]

Based on the [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]

[[File:BL808_Block_Diagram.jpg|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 480 MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head E907 320 MHz 32-bit RISC-V CPU:

* Supports RISC-V RV32IMAFCP instruction set
* Supports RISC-V 32-bit/16-bit mixed instruction set
* Supports RISC-V machine mode and user mode
* Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
* Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
* Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
* 32K instruction cache, two-way set associative structure
* 16K data cache, two-way set associative structure
* See [https://www.t-head.cn/product/e907?lang=en here]

T-Head E902 150 MHz 32-bit RISC-V CPU:

* See [https://www.t-head.cn/product/e902?lang=en here]

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100 Mbit/s Ethernet (optional, on expansion board)

=== Storage ===
* On-board 16 Mbit (2 MB) or 128 Mbit (16 MB) XSPI NOR flash memory
* MicroSD, supports SDHC and SDXC (only on the 128 Mbit version)

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO pins, including SPI, I2C and UART functionality, possible I2S and GMII expansion
* Dual-lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* Microphone (optional, on the camera module)
* Speaker (optional, on the camera module)

== Board Information, Schematics and Certifications ==
[[File:Ox64 ethphy.png|thumb|Pinout for wiring ethernet PHY to EMAC]]

* Baseboard dimensions: 51 mm x 21 mm x 19 mm x 3.5 mm (breadboard friendly)
* Input power: 5 V, 0.5 A through the microUSB or USB-C ports

Production version schematic:

* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221018.pdf Ox64 Schematic 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221018.pdf Ox64 PCB Component placement(ToP) 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221018.pdf Ox64 PCB Component placement(Bottom) 20221018 v1.1]

Prototype (dispatched to developers) schematic:
* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==

Bouffalo BL808 SoC information:
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf Bouffalo Lab BL808 SoC Datasheet]
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_RM/en/BL808_RM_en_1.3.pdf Bouffalo Lab BL808 SoC Reference Manual]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevice 16Mb XSPI-Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevice 128Mb XSPI-Flash Datasheet]
* [https://wiki.pine64.org/images/5/5d/W25Q128JW_RevB_11042019-1761358.pdf Winbond 128Mb QSPI-Flash Datasheet] (W25Q128JWSQ)

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Compatible UARTs when in bootloader mode ==

When the Ox64 is in bootloader mode, some UARTs are unable to communicate with it. When this is the case, utilities such as BLDevCube are unable to actually program the device. If you see "Shake hand fail" and an empty ack, and your device is in bootloader mode, then it is likely an incompatible UART.

The below devices have been tested and verified as working:
* Raspberry Pi Pico - running the following [https://github.com/sanjay900/ox64-uart/releases/tag/v1.1 UART firmware] (GP4 and GP5 are used for port 0, GP12 and GP13 for port 1)
* Compiled binary for Pi Pico and connectivity diagram is [https://github.com/Kris-Sekula/Pine64_Ox64_SBC/tree/main/uart here]
* ESP32 with CP210x - bridge the EN pin to ground to disable the ESP32 itself, and then connect the TX on the esp32 to 14 on the Ox64 and RX to pin 15. Note that only baud rate 115200 works, and this doesn't seem to work for everyone)
* Stand-alone CP2102 dongle works at 115200 baud. Brand used was HiLetgo.
* STM32F401 BlackPill - running the [https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2 Black Magic Debug] firmware
* STM32F103C8T6 BluePill - running Black Magic Debug.
* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
* Some CH340G based adapters work and some don't.

== Resources and Articles ==
* [https://youtube.com/watch?v=czRtF-UNiEY A short video] on how to connect to the Ox64, flash and boot
* [https://youtu.be/vPAk5sq_Ilc Another video] that covers soldering pins, connecting via Pi Pico and flashing Linux and U-Boot
* [https://wiki.pine64.org/images/5/59/How_to_Run_Ox64.pdf Step-by-step tutorial] for how to build, flash and run Ox64
* [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff First batch of Ox64 won't appear as USB serial port]
* [https://gist.github.com/lupyuen/2087e9b3fb40aab5e0795bb02a265a3b First batch of Ox64 tested OK with CH340C/G]
* [https://www.robertlipe.com/bl808-not-symmetric/ First thoughts on the (a)symmetry of Bouffalo Labs BL808 as in Pine64 Ox64]
* [https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html The $8 linux computer (with picoprobe-rp2040 programming instructions)]
* [https://github.com/p4ddy1/pine_ox64/blob/main/build_toolchain_macos.md Building the Xuantie GNU Toolchain for Ox64 on macOS and Apple Silicon]

Ox64 BL808 RISC-V SBC articles by [https://lupyuen.codeberg.page/ Lup Yuen LEE]:
* [https://lupyuen.codeberg.page/articles/ox64.html Booting Linux and (maybe) Apache NuttX RTOS]
* [https://lupyuen.codeberg.page/articles/ox2.html Starting Apache NuttX real-time operating system]
* [https://lupyuen.codeberg.page/articles/mmu.html Sv39 Memory Management Unit]
* [https://lupyuen.codeberg.page/articles/app.html NuttX Apps and Initial RAM Disk]
* [https://lupyuen.codeberg.page/articles/plic2.html UART Interrupt and Platform-Level Interrupt Controller (PLIC)]
* [https://lupyuen.codeberg.page/articles/plic3.html Fixing the UART Interrupt and Platform-Level Interrupt Controller]
* [https://www.hackster.io/lupyuen/8-risc-v-sbc-on-a-real-time-operating-system-ox64-nuttx-474358 $8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX]
* [https://lupyuen.codeberg.page/articles/nim.html Nim on a Real-Time Operating System: Apache NuttX RTOS + Ox64 BL808 SBC]

Git repositories:
* [https://github.com/sfranzyshen/arduino-bl808 Community made Arduino Core specifically for the Bouffalo Labs BL808 RISC-V MCU] (initial development has been postponed until further notice)

== Development Efforts ==
* [https://twitter.com/gamelaster/status/1583916501400068096 Ox64 boots Linux successfully]
* [https://twitter.com/btashton/status/1586381334439923713?t=w5xRRUR74HGK2O1Zg_aFyw&s=19 Brennan Ashton is porting Apache NuttX RTOS and OpenAMP (Asymmetric Multiprocessing) to BL808]
* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

== Building ==
Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

$ mkdir -p ~/ox64
$ cd ~/ox64
$ git clone https://github.com/buildroot/buildroot
$ git clone https://github.com/openbouffalo/buildroot_bouffalo

Define an environment variable for the Buildroot Bouffalo overlay path:

$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo

Change directory into the cloned Buildroot folder:

$ cd ~/ox64/buildroot

Apply the default configuration for Pine64 Ox64:

$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig

Use the `menuconfig` tool to adjust the build settings:

$ make menuconfig

Within `menuconfig`, configure the following:

* Select `Target Options`
* Enable `Integer Multiplication and Division (M)`
* Enable `Atomic Instructions (A)` using space key
* Enable `Single-precision Floating-point (F)`
* Enable `Double-precision Floating-point (D)`
* Select `Target ABI`, set it to `lp64d` and `press Exit`
* Select `Toolchain`, enable `Fortran support`, enable `OpenMP support`, and Save & Exit

Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.

$ make

Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

== Flashing Ox64 SBC and microSD Card ==
This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

== Prepare images for flashing

Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.

$ mkdir -p ~/ox64/openbouffalo
$ cd ~/ox64/openbouffalo
$ wget https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ tar -xvzf bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ cd ~/ox64/openbouffalo/firmware
$ xz -v -d -k sdcard-pine64_ox64_full_defconfig.img.xz
$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img

=== Optional: create a combined SoC image

Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ fallocate -l 0x800000 bl808-combined.bin
$ dd conv=notrunc if=m0_lowload_bl808_m0.bin of=bl808-combined.bin
$ dd conv=notrunc if=d0_lowload_bl808_d0.bin of=bl808-combined.bin seek=$((0x100000))B
$ cat bl808-firmware.bin >> bl808-combined.bin

=== Check that you have the required files for flashing

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ ls -1 *808*.bin *.img

Expected files:

* `bl808-combined.bin` -- If you created the combined image.
* `bl808-firmware.bin` -- OpenSBI and UBoot DTB files. Runs on the D0 core.
* `d0_lowload_bl808_d0.bin` -- Startup code for the D0 core.
* `m0_lowload_bl808_m0.bin` -- Startup code for the M0 core.
* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.

== Set up your UART adapter

In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.

=== Option 1: Raspberry Pi Pico

First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:

$ mkdir -p ~/ox64/pico
$ cd ~/ox64/pico
$ wget https://github.com/Kris-Sekula/Pine64_Ox64_SBC/raw/main/uart/picoprobe.uf2

Put the Raspberry Pi Pico board into programming mode:

* Press the BootSel button
* Apply power by plugging the USB cable to PC
* Release the BootSel button

NOTE: As an alternative to pressing the BootSel button, you can also connect the probe point `TP6` (located on the bottom of the Pico board) to any ground point (e. g. pin 28).

The Pico will now appear as a USB mass storage device. Copy the `UF2` file to program it:

$ cp ~/ox64/pico/picoprobe.uf2 /media/<user>/RPI-RP2

Next, connect the Ox64 board to the Pico according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | PI PICO | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_pin17
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_pin16
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_pin6
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_pin7
| ACM0 for serial console

| gnd_pin38
| gnd_pin38/3
|

| vbus5v_pin40
| vbus5v_pin40
|
|===

With the Pico flashed and wired as per the instructions above, we have access to two of the Ox64's UART ports at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Reconnect the Pico to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)

=== Option 2: STM32 Bluepill

The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.

[NOTE]
====
The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does **not** have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).

If you own an SWD-capable debugger (ST-Link, J-link, etc.) you can use that for programming the Bluepill as well, although instead of `stm32flash` console command you would be using https://openocd.org/[openocd] or other suitable software.
====

WARNING: Your serial adapter must use 3.3V logic levels.

Install software to flash Bluepill. For Debian-based systems just install package from repository:

$ sudo apt install stm32flash

For Arch Linux systems, use the AUR repository:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ git clone https://aur.archlinux.org/stm32flash.git
$ cd ~/ox64/bluepill/stm32flash
$ makepkg -si

Download the https://github.com/r2axz/bluepill-serial-monster[Bluepill Serial Monster] firmware:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ wget https://github.com/r2axz/bluepill-serial-monster/releases/download/v2.6.4/bluepill-serial-monster.hex

Put the Bluepill into programming mode:

* Set boot jumpers for booting from rom: Boot0=1, Boot1=0.
* Connect it to a USB-Serial adapter with A9 to Rx, A10 to Tx, GND to GND, 3v3 to Vcc.
* Apply power by plugging the USB cable to PC. Press the Reset button.

Find your USB serial adapter's device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`. Upload the firmware:

$ cd ~/ox64/bluepill
$ sudo stm32flash -w bluepill-serial-monster.hex /dev/tty[DEVICE]

After upload, set boot jumpers for boot from flash: Boot0=0, Boot1=0. Disconnect the USB serial adapter from both the PC and Bluepill board.

Next, connect the Ox64 board to the Bluepill according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | Bluepill | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_A3
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_A2
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_A9
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_A10
| ACM0 for serial console

| gnd_pin38
| GND
|

| vbus5v_pin40
| 5V
|

|===

With the Bluepill flashed and wired as per the instructions above, we have access to two of the Ox64's UART connections at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Connect the Bluepill to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)
* `/dev/ttyACM2` (unused)

=== Option 3: Generic UART adapter

image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]

Check that your serial adapter is on the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. You will (most likely) only have one serial interface available to you; unlike the previous options you will be using this same serial interface for both flashing and testing the system.

Find its device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`.

You will also need a way of powering your Ox64. If your serial adapter has a 5V line, you can connect it to VBUS (pin 40). Otherwise, you can connect either the micro-B or the USB-C port on the Ox64 to any 5V power supply.

WARNING: Your serial adapter must use 3.3V logic levels.

Refer to the pinout image below. Connect your UART adapter as follows:

* RX -> UART0_TX / GPIO14 / pin 1
* TX -> UART0_RX / GPIO15 / pin 2
* GND -> any ground (e. g. pin 3)

Proceed with the instructions in the sections that follow, up to and including <<flashing_the_ox64>> and <<flashing_the_microsd_card>>, but replace all occurrences of `/dev/ttyACM1` with `/dev/tty[DEVICE]`.

Next, power off the Ox64 and re-connect your UART adapter as follows:

* RX -> TXD / GPIO16 / pin 32
* TX -> RXD / GPIO17 / pin 31
* GND -> any ground (e. g. pin 33)

Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.

== Download flashing tools

You have a choice of flashing software:

* DevCube: GUI-based closed source flashing tool
* CLI (`bflb-iot-tool`): command line open source flashing tool

=== DevCube installation

Download the latest DevCube flashing tool from BouffaloLab's website:

$ mkdir -p ~/ox64/devcube
$ cd ~/ox64/devcube
$ wget https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.9.zip
$ unzip BouffaloLabDevCube-v1.8.9.zip
$ chmod u+x BLDevCube-ubuntu

If you did not create a link:#optional_create_a_combined_soc_image[combined image] you may need an older version of the DevCube. In that case, download v1.8.3 from one of the mirrors below:

* https://openbouffalo.org/static-assets/bldevcube/BouffaloLabDevCube-v1.8.3.zip
* https://hachyderm.io/@mkroman/110787218805897192[] > https://pub.rwx.im/~mk/bouffalolab/BouffaloLabDevCube-v1.8.3.zip
* https://we.tl/t-eJWShQJ4iF
* https://cdn.discordapp.com/attachments/771032441971802142/1145565853962735639/BouffaloLabDevCube-v1.8.3.zip

Verify that your copy of `BouffaloLabDevCube-v1.8.3.zip` matches the hashes below:

* SHA1: `0f2619e87d946f936f63ae97b0efd674357b1166`
* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`

=== CLI packages installation

Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:

$ sudo apt install pipenv # for Debian-based systems
# or
$ sudo pacman -S python-pipenv # for Arch Linux systems

$ cd ~/ox64/
$ pipenv install setuptools # install prerequisite of CLI flash tool
$ pipenv install bflb-iot-tool # install CLI flash tool
$ pipenv shell # activate virtual environment
$ # bflb-iot-tool --help # return info about the tool

NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.

== Flashing the Ox64

Put the Ox64 into programming mode:

* Press the BOOT button
* Apply power or re-plug the USB cable
* Release the BOOT button

=== CLI flashing method

Set up some environment variables to save typing them out later:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ PORT=/dev/ttyACM1
$ BAUD=230400 # safe value for macOS, set to 2000000 for faster flashing on Linux

Finally, flash the Ox64. If you created a link:#optional_create_a_combined_soc_image[combined image] then run the command below:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware bl808-combined.bin --single

Otherwise, run the following commands:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware m0_lowload_bl808_m0.bin --single

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x800000 --firmware bl808-firmware.bin --single

If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.

=== BLDevCube flashing method

Open a new terminal window to run the DevCube flasher:

$ cd ~/ox64/devcube
$ ./BLDevCube-ubuntu

Select chip [BL808], press Finish, and configure BOTH the [MCU] and [IOT] tabs as follows. When you switch between tabs double check that they still match the settings below:

[cols="~,~"]
|===
|Interface
|UART

|Port/SN
|`/dev/ttyACM1`

|UART rate
|230400 (safe value for macOS, set to 2000000 for faster flashing on Linux)
|===

If you created a link:#optional_create_a_combined_soc_image[combined image] then you only need to use the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x0], [PATH to bl808-combined.bin]
* Click 'Create & Download' and wait until it's done
* Close DevCube

Otherwise, start in the [MCU] tab:

* M0 Group[group0], Image Address [0x58000000], [PATH to m0_lowload_bl808_m0.bin]
* D0 Group[group0], Image Address [0x58100000], [PATH to d0_lowload_bl808_d0.bin]
* Click 'Create & Download' and wait until it's done

Then, switch to the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x800000], [PATH to bl808-firmware.bin]
* Click 'Create & Download' again and wait until it's done
* Close DevCube

== Erasing the microSD card

Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.

$ sudo wipefs /dev/[DEVICE]
$ sudo wipefs --all --force /dev/[DEVICE]*
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=1

Optionally you can zeroes the whole device:

$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] | head -1) \/ 32768)

== Flashing the microSD card

Insert the microSD card into your PC, locate its device under `lsblk` and write the image:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync

== Booting for the first time

Power off your Ox64 and insert the microSD card.

Open a terminal window to connect to the D0 core’s (i.e. Linux’s) serial console:

$ minicom -b 2000000 -D /dev/ttyACM0

If you are using a Pico or Bluepill as your serial adapter, open another terminal window to to monitor the M0 core’s serial console (reminder: `/dev/ttyACM1` is the same port we previously used for flashing):

$ minicom -b 2000000 -D /dev/ttyACM1

Re-apply power to the Ox64.

On the main/D0 console (`/dev/ttyACM0`) you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error.

On the M0 console (`/dev/ttyACM1`) you'll see following messages until the sytem is fully loaded:

----
[I][MBOX] Mailbox IRQ Stats:
[I][MBOX] Peripheral SDH (33): 0
[I][MBOX] Peripheral GPIO (60): 0
[I][MBOX] Unhandled Interupts: 0 Unhandled Signals 0
----

Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.

=== Connecting the Ox64 to your WiFi network
The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):

$ blctl connect_ap <YourSSID> <YourPassword>

Wait for it to connect (if you're monitoring the M0 console on `/dev/ttyACM1` it should tell you when it's done), then run the following command from the Linux console:

$ udhcpc -i bleth0

Unfortunately the WiFi range leaves something to be desired. When you are performing the procedure above for the first time, move the Ox64 right next to your router. Once you are successfully connected, you can try experimenting with the maximum range.

For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].

== Appendix

=== Adding Nuttx RTOS

In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].

First, write the normal Linux image to the SD card if you have not done so already. You can find the correct device under `lsblk`:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=/sdcard.img of=/dev/[DEVICE] bs=1M conv=fsync status=progress

Run the following command to re-read the partition tables. Re-inserting the SD card works too:

$ sudo blockdev --rereadpt /dev/[DEVICE]

Download the NuttX image:

$ mkdir -p ~/ox64/nuttx
$ cd ~/ox64/nuttx
$ wget -O ImageNuttx https://github.com/lupyuen2/wip-pinephone-nuttx/releases/download/bl808d-1/Image

Mount the boot partition and make the required modifications:

$ sudo mount /dev/[DEVICE]2 /mnt
$ sudo cp ImageNuttx /mnt/
$ sudo tee -a /mnt/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Mount the rootfs and make the required modifications:

$ sudo mount /dev/[DEVICE]3 /mnt
$ sudo cp ImageNuttx /mnt/boot/
$ sudo tee -a /mnt/boot/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Enjoy your new Nuttx booting option!

Ox64

2024-06-23T15:44:23Z

Giorez: /* Flashing Ox64 SBC and microSD Card */

[[File:Ox64_board.jpg|thumb|right|The Ox64]]
[[File:Ox64 pinout.png|thumb|Pinout of the production version]]
[[File:RISC-V.png|thumb|right|Powered by RISC-V]]

The '''Ox64''' is a RISC-V based single-board computer based on the Bouffalo Lab BL808 RISC-V SoC with C906 64-bit and E907/E902 32-bit CPU cores supported by 64 MB of embedded PSRAM memory, and with built-in WiFi, Bluetooh and Zigbee radio interfaces. The Ox64 comes in a breadboard-friendly form-factor, has a microSD card slot, a USB 2.0 Type-C port, and many other peripheral interfaces for makers to integrate with sensors and other devices.

== Software Releases ==

=== Quick Links to the Source of OS Images Build ===

There is a community effort to bring updated kernels, peripherals and buildroot - Lots of communication happening in the #ox64-nutcracker channel.

* [https://github.com/openbouffalo/buildroot_bouffalo buildroot] bringing all the work below together with a bootable kernel and updated filesystem images for SD cards
* [https://github.com/smaeul/u-boot/tree/bl808 U-Boot] and [https://github.com/smaeul/opensbi/tree/bl808 OpenSBI] work by Smauel
* [https://github.com/arm000/linux-bl808/tree/linux-next/mboxic Kernel] IRQChip, SDCard, and (WIP) USB by arm000, Alexander Horner and others
* [https://github.com/openbouffalo/OBLFR OpenBouffalo Firmware] low_load drivers by Fishwaldo and others

Original Linux Images provided by Bouffalo - Very basic '''alpha build''' which are only fit for board bring up and testing purposes.

* [https://github.com/bouffalolab/bl808_linux Linux for BL808]
* [https://wiki.pine64.org/wiki/File:Linux_BL808.pdf Installation Instructions for Linux on BL808 (Chinese)]
* [https://wiki.pine64.org/wiki/File:Linux_BL808_en.pdf Installation Instructions for Linux on BL808 (machine translated to English)]

Toolchain:

* elf_newlib_toolchain/bin/riscv64-unknown-elf-gcc (Xuantie-900 elf newlib gcc Toolchain V2.2.5 B-20220323) 10.2.0
* linux_toolchain/bin/riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.2.4 B-20211227) 10.2.0
* cmake version 3.19.3

=== Software Development Kits ===
* [https://github.com/bouffalolab/bl_mcu_sdk BL808 MCU SDK]
* [https://dev.bouffalolab.com/download BLDevCube Flashing Tool for Windows, macOS and Ubuntu x64]
* [https://wiki.pine64.org/wiki/File:Ox64_BL808UART_connect.pdf Ox64 UART Flashing Guide], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/bl808_demo_event.bin BL808 Demo Firmware: bl808_demo_event.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/whole_flash_data.bin BL808 UART Log Firmware: whole_flash_data.bin], see the [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff notes]
* [https://github.com/lupyuen/lupyuen.github.io/releases/download/ox64/BL808.DVK.Quick.Start.pdf BL808 DVK Quick Start]
* [https://github.com/bouffalolab/bl808_linux/tree/main/opensbi-0.6-808 OpenSBI for BL808]
* [https://github.com/bouffalolab/bl-pac/tree/main/bl808 Rust Peripheral Access Crate (PAC) for BL808]
* [https://github.com/bouffalolab/bl-pac/blob/main/bl808/bl808.svd System View Description (SVD) for BL808]

== SoC and Memory Specification ==

[[File:Bouffalo_Lab_icon.png|right]]

Based on the [https://en.bouffalolab.com/product/ Bouffalo Lab BL808]

[[File:BL808_Block_Diagram.jpg|500px]]

=== CPU Architecture ===

[[File:T-Head.png|right|200px]]

T-Head C906 480 MHz 64-bit RISC-V CPU:

* Supports RISC-V RV64IMAFCV instruction architecture
* Five-stage single-issue sequentially executed pipeline
* Level-1 instruction and data cache of Harvard architecture, with a size of 32 KB and a cache line of 64B
* Sv39 memory management unit, realizing the conversion of virtual and real addresses and memory management
* jTLB that supports 128 entries
* Supports AXI 4.0 128-bit master interface
* Supports core local interrupt (CLINT) and platform-level interrupt controller (PLIC)
* With 80 external interrupt sources, 3 bits for configuring interrupt priority
* Supports BHT (8K) and BTB
* Compatible with RISC-V PMP, 8 configurable areas
* Supports hardware performance monitor (HPM) units
* See [https://www.t-head.cn/product/c906?lang=en here]

T-Head E907 320 MHz 32-bit RISC-V CPU:

* Supports RISC-V RV32IMAFCP instruction set
* Supports RISC-V 32-bit/16-bit mixed instruction set
* Supports RISC-V machine mode and user mode
* Thirty-two 32-bit integer general purpose registers (GPR) and thirty-two 32-bit/64-bit floating-point GPRs
* Integer (5-stage)/floating-point (7-stage), single-issue, sequentially executed pipeline
* Supports AXI 4.0 main device interface and AHB 5.0 peripheral interface
* 32K instruction cache, two-way set associative structure
* 16K data cache, two-way set associative structure
* See [https://www.t-head.cn/product/e907?lang=en here]

T-Head E902 150 MHz 32-bit RISC-V CPU:

* See [https://www.t-head.cn/product/e902?lang=en here]

=== System Memory ===
* Embedded 64MB PSRAM

== Board Features ==

=== Network ===
* 2.4 GHz 1T1R WiFi 802.11 b/g/n
* Bluetooth 5.2
* Zigbee
* 10/100 Mbit/s Ethernet (optional, on expansion board)

=== Storage ===
* On-board 16 Mbit (2 MB) or 128 Mbit (16 MB) XSPI NOR flash memory
* MicroSD, supports SDHC and SDXC (only on the 128 Mbit version)

=== Expansion Ports ===
* USB 2.0 OTG port
* 26 GPIO pins, including SPI, I2C and UART functionality, possible I2S and GMII expansion
* Dual-lane MiPi CSI port, located at USB-C port, for camera module

=== Audio ===
* Microphone (optional, on the camera module)
* Speaker (optional, on the camera module)

== Board Information, Schematics and Certifications ==
[[File:Ox64 ethphy.png|thumb|Pinout for wiring ethernet PHY to EMAC]]

* Baseboard dimensions: 51 mm x 21 mm x 19 mm x 3.5 mm (breadboard friendly)
* Input power: 5 V, 0.5 A through the microUSB or USB-C ports

Production version schematic:

* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221018.pdf Ox64 Schematic 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221018.pdf Ox64 PCB Component placement(ToP) 20221018 v1.1]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221018.pdf Ox64 PCB Component placement(Bottom) 20221018 v1.1]

Prototype (dispatched to developers) schematic:
* [https://files.pine64.org/doc/ox64/PINE64_Ox64-Schematic-202221007.pdf Ox64 Schematic 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Top-20221007.pdf Ox64 PCB Component placement(ToP) 20221007 v1.0]
* [https://files.pine64.org/doc/ox64/PINE64_Ox64_PCB_Placement-Bottom-20221007.pdf Ox64 PCB Component placement(Bottom) 20221007 v1.0]

Certifications:
* Disclaimer: Please note that PINE64 SBC is not a "final" product and in general certification is not necessary.
* Not yet available

== Datasheets for Components and Peripherals ==

Bouffalo BL808 SoC information:
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf Bouffalo Lab BL808 SoC Datasheet]
* [https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_RM/en/BL808_RM_en_1.3.pdf Bouffalo Lab BL808 SoC Reference Manual]

SPI NOR Flash information:
* [https://files.pine64.org/doc/datasheet/ox64/gd25lq16e_rev1.2_20210108.pdf GigaDevice 16Mb XSPI-Flash Datasheet]
* [https://files.pine64.org/doc/datasheet/star64/gd25lq128e_rev1.0_20210513.pdf GigaDevice 128Mb XSPI-Flash Datasheet]
* [https://wiki.pine64.org/images/5/5d/W25Q128JW_RevB_11042019-1761358.pdf Winbond 128Mb QSPI-Flash Datasheet] (W25Q128JWSQ)

Power Regulator information:
* [https://files.pine64.org/doc/datasheet/ox64/IA2014-03.pdf Innovation Analog Tech IA2014 Step_down Converter Datasheet]

MicroSD socket information:
* [https://files.pine64.org/doc/datasheet/ox64/TF%20PUSH%20type%20socket%20specification.pdf Push type microSD socket specification]

== Compatible UARTs when in bootloader mode ==

When the Ox64 is in bootloader mode, some UARTs are unable to communicate with it. When this is the case, utilities such as BLDevCube are unable to actually program the device. If you see "Shake hand fail" and an empty ack, and your device is in bootloader mode, then it is likely an incompatible UART.

The below devices have been tested and verified as working:
* Raspberry Pi Pico - running the following [https://github.com/sanjay900/ox64-uart/releases/tag/v1.1 UART firmware] (GP4 and GP5 are used for port 0, GP12 and GP13 for port 1)
* Compiled binary for Pi Pico and connectivity diagram is [https://github.com/Kris-Sekula/Pine64_Ox64_SBC/tree/main/uart here]
* ESP32 with CP210x - bridge the EN pin to ground to disable the ESP32 itself, and then connect the TX on the esp32 to 14 on the Ox64 and RX to pin 15. Note that only baud rate 115200 works, and this doesn't seem to work for everyone)
* Stand-alone CP2102 dongle works at 115200 baud. Brand used was HiLetgo.
* STM32F401 BlackPill - running the [https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2 Black Magic Debug] firmware
* STM32F103C8T6 BluePill - running Black Magic Debug.
* Some UART adapters based on the FT232H (note that the FT232RL does not work, and neither does the Pine 64 JTAG)
* Some CH340G based adapters work and some don't.

== Resources and Articles ==
* [https://youtube.com/watch?v=czRtF-UNiEY A short video] on how to connect to the Ox64, flash and boot
* [https://youtu.be/vPAk5sq_Ilc Another video] that covers soldering pins, connecting via Pi Pico and flashing Linux and U-Boot
* [https://wiki.pine64.org/images/5/59/How_to_Run_Ox64.pdf Step-by-step tutorial] for how to build, flash and run Ox64
* [https://gist.github.com/lupyuen/7a0c697b89abccda8e38b33dfe5ebaff First batch of Ox64 won't appear as USB serial port]
* [https://gist.github.com/lupyuen/2087e9b3fb40aab5e0795bb02a265a3b First batch of Ox64 tested OK with CH340C/G]
* [https://www.robertlipe.com/bl808-not-symmetric/ First thoughts on the (a)symmetry of Bouffalo Labs BL808 as in Pine64 Ox64]
* [https://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer-part-2.html The $8 linux computer (with picoprobe-rp2040 programming instructions)]
* [https://github.com/p4ddy1/pine_ox64/blob/main/build_toolchain_macos.md Building the Xuantie GNU Toolchain for Ox64 on macOS and Apple Silicon]

Ox64 BL808 RISC-V SBC articles by [https://lupyuen.codeberg.page/ Lup Yuen LEE]:
* [https://lupyuen.codeberg.page/articles/ox64.html Booting Linux and (maybe) Apache NuttX RTOS]
* [https://lupyuen.codeberg.page/articles/ox2.html Starting Apache NuttX real-time operating system]
* [https://lupyuen.codeberg.page/articles/mmu.html Sv39 Memory Management Unit]
* [https://lupyuen.codeberg.page/articles/app.html NuttX Apps and Initial RAM Disk]
* [https://lupyuen.codeberg.page/articles/plic2.html UART Interrupt and Platform-Level Interrupt Controller (PLIC)]
* [https://lupyuen.codeberg.page/articles/plic3.html Fixing the UART Interrupt and Platform-Level Interrupt Controller]
* [https://www.hackster.io/lupyuen/8-risc-v-sbc-on-a-real-time-operating-system-ox64-nuttx-474358 $8 RISC-V SBC on a Real-Time Operating System: Ox64 + NuttX]
* [https://lupyuen.codeberg.page/articles/nim.html Nim on a Real-Time Operating System: Apache NuttX RTOS + Ox64 BL808 SBC]

Git repositories:
* [https://github.com/sfranzyshen/arduino-bl808 Community made Arduino Core specifically for the Bouffalo Labs BL808 RISC-V MCU] (initial development has been postponed until further notice)

== Development Efforts ==
* [https://twitter.com/gamelaster/status/1583916501400068096 Ox64 boots Linux successfully]
* [https://twitter.com/btashton/status/1586381334439923713?t=w5xRRUR74HGK2O1Zg_aFyw&s=19 Brennan Ashton is porting Apache NuttX RTOS and OpenAMP (Asymmetric Multiprocessing) to BL808]
* [https://twitter.com/thanos_engine/status/1585153938092761093 Phone Concept for BL808]

== Build==
Start the building process cloning both the upstream Buildroot repository and the Buildroot Bouffalo overlay repository:

$ mkdir -p ~/ox64
$ cd ~/ox64
$ git clone https://github.com/buildroot/buildroot
$ git clone https://github.com/openbouffalo/buildroot_bouffalo

Define an environment variable for the Buildroot Bouffalo overlay path:

$ export BR_BOUFFALO_OVERLAY_PATH=$(pwd)/buildroot_bouffalo

Change directory into the cloned Buildroot folder:

$ cd ~/ox64/buildroot

Apply the default configuration for Pine64 Ox64:

$ make BR2_EXTERNAL=$BR_BOUFFALO_OVERLAY_PATH pine64_ox64_defconfig

Use the `menuconfig` tool to adjust the build settings:

$ make menuconfig

Within `menuconfig`, configure the following:

* Select `Target Options`
* Enable `Integer Multiplication and Division (M)`
* Enable `Atomic Instructions (A)` using space key
* Enable `Single-precision Floating-point (F)`
* Enable `Double-precision Floating-point (D)`
* Select `Target ABI`, set it to `lp64d` and `press Exit`
* Select `Toolchain`, enable `Fortran support`, enable `OpenMP support`, and Save & Exit

Initiate the build process, but first make sure that your `PATH` variable contains no spaces. For Arch Linux distrubution you may also need to install extra-packages with `sudo pacman -S cpio rsync bc`.

$ make

Buildroot will output the needed files to the `~/ox64/buildroot/output/images` directory in about 1 hour, according to your computer processing resources and internet connection speed.

== Flashing Ox64 SBC and microSD Card ==
This page explains how to flash an Ox64 board and a microSD card to boot the system. You will need a Linux computer, a serial UART adapter, the Ox64 board, and a microSD card.

== Prepare images for flashing

Download the Ox64 images from the latest OpenBouffalo release. You may skip this step if you built your own images as per the instructions in the link:/documentation/Ox64/Software/Building/[Building] page.

$ mkdir -p ~/ox64/openbouffalo
$ cd ~/ox64/openbouffalo
$ wget https://github.com/openbouffalo/buildroot_bouffalo/releases/download/v1.0.1/bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ tar -xvzf bl808-linux-pine64_ox64_full_defconfig.tar.gz
$ cd ~/ox64/openbouffalo/firmware
$ xz -v -d -k sdcard-pine64_ox64_full_defconfig.img.xz
$ mv sdcard-pine64_ox64_full_defconfig.img sdcard.img

=== Optional: create a combined SoC image

Use the following commands to combine _m0_lowload_bl808_m0.bin_, _d0_lowload_bl808_d0.bin_, and _bl808-firmware.bin_ into a single image. This is mainly useful for troubleshooting (e. g. when using DevCube v1.8.4 or later).

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ fallocate -l 0x800000 bl808-combined.bin
$ dd conv=notrunc if=m0_lowload_bl808_m0.bin of=bl808-combined.bin
$ dd conv=notrunc if=d0_lowload_bl808_d0.bin of=bl808-combined.bin seek=$((0x100000))B
$ cat bl808-firmware.bin >> bl808-combined.bin

=== Check that you have the required files for flashing

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ ls -1 *808*.bin *.img

Expected files:

* `bl808-combined.bin` -- If you created the combined image.
* `bl808-firmware.bin` -- OpenSBI and UBoot DTB files. Runs on the D0 core.
* `d0_lowload_bl808_d0.bin` -- Startup code for the D0 core.
* `m0_lowload_bl808_m0.bin` -- Startup code for the M0 core.
* `sdcard.img` -- Kernel and root filesystem. Runs on the D0 core.

== Set up your UART adapter

In this section we will configure and wire up a UART adapter in order to flash the Ox64. Choose one of the options below based on the hardware available to you; the first two are the most convenient since they minimise the number of times you will need to swap electrical connections.

=== Option 1: Raspberry Pi Pico

First, download the Raspberry Pi Pico firmware that allows it to act as a serial UART adapter:

$ mkdir -p ~/ox64/pico
$ cd ~/ox64/pico
$ wget https://github.com/Kris-Sekula/Pine64_Ox64_SBC/raw/main/uart/picoprobe.uf2

Put the Raspberry Pi Pico board into programming mode:

* Press the BootSel button
* Apply power by plugging the USB cable to PC
* Release the BootSel button

NOTE: As an alternative to pressing the BootSel button, you can also connect the probe point `TP6` (located on the bottom of the Pico board) to any ground point (e. g. pin 28).

The Pico will now appear as a USB mass storage device. Copy the `UF2` file to program it:

$ cp ~/ox64/pico/picoprobe.uf2 /media/<user>/RPI-RP2

Next, connect the Ox64 board to the Pico according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | PI PICO | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_pin17
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_pin16
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_pin6
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_pin7
| ACM0 for serial console

| gnd_pin38
| gnd_pin38/3
|

| vbus5v_pin40
| vbus5v_pin40
|
|===

With the Pico flashed and wired as per the instructions above, we have access to two of the Ox64's UART ports at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Reconnect the Pico to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)

=== Option 2: STM32 Bluepill

The Bluepill is an affordable STM32 development board, based on the STM32F103C8T6 chip. We can program it to act as a USB serial adapter, just like we did with the Raspberry Pi Pico.

[NOTE]
====
The one catch is that you already need a serial adapter in order to program your Bluepill board. The good news is that you serial adapter does **not** have to be one from from the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. These programming instructions have been tested with a FT232RL adapter (which, notably, is listed as _not_ supported on that list).

If you own an SWD-capable debugger (ST-Link, J-link, etc.) you can use that for programming the Bluepill as well, although instead of `stm32flash` console command you would be using https://openocd.org/[openocd] or other suitable software.
====

WARNING: Your serial adapter must use 3.3V logic levels.

Install software to flash Bluepill. For Debian-based systems just install package from repository:

$ sudo apt install stm32flash

For Arch Linux systems, use the AUR repository:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ git clone https://aur.archlinux.org/stm32flash.git
$ cd ~/ox64/bluepill/stm32flash
$ makepkg -si

Download the https://github.com/r2axz/bluepill-serial-monster[Bluepill Serial Monster] firmware:

$ mkdir -p ~/ox64/bluepill
$ cd ~/ox64/bluepill
$ wget https://github.com/r2axz/bluepill-serial-monster/releases/download/v2.6.4/bluepill-serial-monster.hex

Put the Bluepill into programming mode:

* Set boot jumpers for booting from rom: Boot0=1, Boot1=0.
* Connect it to a USB-Serial adapter with A9 to Rx, A10 to Tx, GND to GND, 3v3 to Vcc.
* Apply power by plugging the USB cable to PC. Press the Reset button.

Find your USB serial adapter's device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`. Upload the firmware:

$ cd ~/ox64/bluepill
$ sudo stm32flash -w bluepill-serial-monster.hex /dev/tty[DEVICE]

After upload, set boot jumpers for boot from flash: Boot0=0, Boot1=0. Disconnect the USB serial adapter from both the PC and Bluepill board.

Next, connect the Ox64 board to the Bluepill according to the following wiring diagram:

[cols="1,1,1"]
|===
| Ox64 | Bluepill | /dev/tty

| uart0_Tx_GPIO14_pin1
| uart0_Rx_A3
| ACM1 for flashing

| uart0_Rx_GPIO15_pin2
| uart0_Tx_A2
| ACM1 for flashing

| Rxd_GPIO17_pin31
| uart1_Tx_A9
| ACM0 for serial console

| Txd_GPIO16_pin32
| uart1_Rx_A10
| ACM0 for serial console

| gnd_pin38
| GND
|

| vbus5v_pin40
| 5V
|

|===

With the Bluepill flashed and wired as per the instructions above, we have access to two of the Ox64's UART connections at the same time. This configuration eliminates the need to switch the physical connections for flashing or testing the system.

Connect the Bluepill to your computer's USB port and verify that we have access to all the serial ports we need:

$ ls /dev/ttyACM*

Expected result:

* `/dev/ttyACM0` connects to the D0 core's (i.e. Linux's) serial console
* `/dev/ttyACM1` is used for flashing (but also connects to the M0 core's serial console)
* `/dev/ttyACM2` (unused)

=== Option 3: Generic UART adapter

image:/documentation/Ox64/images/ox64_pinout.png[Ox64 pinout,title="Ox64 pinout", 300, float="right"]

Check that your serial adapter is on the link:/documentation/Ox64/Further_information/Compatible_UARTs/[Compatible UARTs] list. You will (most likely) only have one serial interface available to you; unlike the previous options you will be using this same serial interface for both flashing and testing the system.

Find its device path with `ls /dev/ttyUSB* /dev/ttyACM*` (or similar); for the rest of this section we will refer to it as `/dev/tty[DEVICE]`.

You will also need a way of powering your Ox64. If your serial adapter has a 5V line, you can connect it to VBUS (pin 40). Otherwise, you can connect either the micro-B or the USB-C port on the Ox64 to any 5V power supply.

WARNING: Your serial adapter must use 3.3V logic levels.

Refer to the pinout image below. Connect your UART adapter as follows:

* RX -> UART0_TX / GPIO14 / pin 1
* TX -> UART0_RX / GPIO15 / pin 2
* GND -> any ground (e. g. pin 3)

Proceed with the instructions in the sections that follow, up to and including <<flashing_the_ox64>> and <<flashing_the_microsd_card>>, but replace all occurrences of `/dev/ttyACM1` with `/dev/tty[DEVICE]`.

Next, power off the Ox64 and re-connect your UART adapter as follows:

* RX -> TXD / GPIO16 / pin 32
* TX -> RXD / GPIO17 / pin 31
* GND -> any ground (e. g. pin 33)

Then, follow the instructions in <<booting_for_the_first_time>>, but replace all occurrences of `/dev/ttyACM0` with `/dev/tty[DEVICE]`. You should then have a working Linux system.

== Download flashing tools

You have a choice of flashing software:

* DevCube: GUI-based closed source flashing tool
* CLI (`bflb-iot-tool`): command line open source flashing tool

=== DevCube installation

Download the latest DevCube flashing tool from BouffaloLab's website:

$ mkdir -p ~/ox64/devcube
$ cd ~/ox64/devcube
$ wget https://dev.bouffalolab.com/media/upload/download/BouffaloLabDevCube-v1.8.9.zip
$ unzip BouffaloLabDevCube-v1.8.9.zip
$ chmod u+x BLDevCube-ubuntu

If you did not create a link:#optional_create_a_combined_soc_image[combined image] you may need an older version of the DevCube. In that case, download v1.8.3 from one of the mirrors below:

* https://openbouffalo.org/static-assets/bldevcube/BouffaloLabDevCube-v1.8.3.zip
* https://hachyderm.io/@mkroman/110787218805897192[] > https://pub.rwx.im/~mk/bouffalolab/BouffaloLabDevCube-v1.8.3.zip
* https://we.tl/t-eJWShQJ4iF
* https://cdn.discordapp.com/attachments/771032441971802142/1145565853962735639/BouffaloLabDevCube-v1.8.3.zip

Verify that your copy of `BouffaloLabDevCube-v1.8.3.zip` matches the hashes below:

* SHA1: `0f2619e87d946f936f63ae97b0efd674357b1166`
* SHA256: `e6e6db316359da40d29971a1889d41c9e97d5b1ff1a8636e9e6960b6ff960913`

=== CLI packages installation

Install `bflb-iot-tool` using your preferred method of managing PIP packages. One option is to set up a Python virtual environment as follows:

$ sudo apt install pipenv # for Debian-based systems
# or
$ sudo pacman -S python-pipenv # for Arch Linux systems

$ cd ~/ox64/
$ pipenv install setuptools # install prerequisite of CLI flash tool
$ pipenv install bflb-iot-tool # install CLI flash tool
$ pipenv shell # activate virtual environment
$ # bflb-iot-tool --help # return info about the tool

NOTE: Each time you open a new terminal window you will need to `cd ~/ox64/` and re-run `pipenv shell` to reactivate the virtual environment.

== Flashing the Ox64

Put the Ox64 into programming mode:

* Press the BOOT button
* Apply power or re-plug the USB cable
* Release the BOOT button

=== CLI flashing method

Set up some environment variables to save typing them out later:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ PORT=/dev/ttyACM1
$ BAUD=230400 # safe value for macOS, set to 2000000 for faster flashing on Linux

Finally, flash the Ox64. If you created a link:#optional_create_a_combined_soc_image[combined image] then run the command below:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware bl808-combined.bin --single

Otherwise, run the following commands:

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x0 --firmware m0_lowload_bl808_m0.bin --single

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x100000 --firmware d0_lowload_bl808_d0.bin --single

$ bflb-iot-tool --chipname bl808 --interface uart --port $PORT --baudrate $BAUD --addr 0x800000 --firmware bl808-firmware.bin --single

If you get permission errors when running any of the commands above, run `ls -l /dev/tty[DEVICE]`, to find out which group is allowed to talk to serial ports and add your user to that group, with `sudo usermod -a -G [GROUP] $USER` (i.e. `dialout` for Debian or `uucp` for Arch Linux). Make sure you re-login. Running the commands as `root` is not recommended since this will make `bflb-iot-tool` create root-owned files in your home directory. You can now run `exit` from virtual environment.

=== BLDevCube flashing method

Open a new terminal window to run the DevCube flasher:

$ cd ~/ox64/devcube
$ ./BLDevCube-ubuntu

Select chip [BL808], press Finish, and configure BOTH the [MCU] and [IOT] tabs as follows. When you switch between tabs double check that they still match the settings below:

[cols="~,~"]
|===
|Interface
|UART

|Port/SN
|`/dev/ttyACM1`

|UART rate
|230400 (safe value for macOS, set to 2000000 for faster flashing on Linux)
|===

If you created a link:#optional_create_a_combined_soc_image[combined image] then you only need to use the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x0], [PATH to bl808-combined.bin]
* Click 'Create & Download' and wait until it's done
* Close DevCube

Otherwise, start in the [MCU] tab:

* M0 Group[group0], Image Address [0x58000000], [PATH to m0_lowload_bl808_m0.bin]
* D0 Group[group0], Image Address [0x58100000], [PATH to d0_lowload_bl808_d0.bin]
* Click 'Create & Download' and wait until it's done

Then, switch to the [IOT] tab:

* Enable 'Single Download'
* Image Address [0x800000], [PATH to bl808-firmware.bin]
* Click 'Create & Download' again and wait until it's done
* Close DevCube

== Erasing the microSD card

Make sure there are no signatures or partitions left, and overwrite the first sectors with zeroes. You can find the target device under `lsblk` command.

$ sudo wipefs /dev/[DEVICE]
$ sudo wipefs --all --force /dev/[DEVICE]*
$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=1

Optionally you can zeroes the whole device:

$ sudo dd if=/dev/zero of=/dev/[DEVICE] status=progress bs=32768 count=$(expr $(lsblk -bno SIZE /dev/[DEVICE] | head -1) \/ 32768)

== Flashing the microSD card

Insert the microSD card into your PC, locate its device under `lsblk` and write the image:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M status=progress conv=fsync

== Booting for the first time

Power off your Ox64 and insert the microSD card.

Open a terminal window to connect to the D0 core’s (i.e. Linux’s) serial console:

$ minicom -b 2000000 -D /dev/ttyACM0

If you are using a Pico or Bluepill as your serial adapter, open another terminal window to to monitor the M0 core’s serial console (reminder: `/dev/ttyACM1` is the same port we previously used for flashing):

$ minicom -b 2000000 -D /dev/ttyACM1

Re-apply power to the Ox64.

On the main/D0 console (`/dev/ttyACM0`) you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error.

On the M0 console (`/dev/ttyACM1`) you'll see following messages until the sytem is fully loaded:

----
[I][MBOX] Mailbox IRQ Stats:
[I][MBOX] Peripheral SDH (33): 0
[I][MBOX] Peripheral GPIO (60): 0
[I][MBOX] Unhandled Interupts: 0 Unhandled Signals 0
----

Once the system is running, the "MBOX" logs will abruptly disappear and you'll be able to manage the M0 multimedia core, i.e. wifi settings, etc. When prompted, type `help` to see available commands.

=== Connecting the Ox64 to your WiFi network
The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`):

$ blctl connect_ap <YourSSID> <YourPassword>

Wait for it to connect (if you're monitoring the M0 console on `/dev/ttyACM1` it should tell you when it's done), then run the following command from the Linux console:

$ udhcpc -i bleth0

Unfortunately the WiFi range leaves something to be desired. When you are performing the procedure above for the first time, move the Ox64 right next to your router. Once you are successfully connected, you can try experimenting with the maximum range.

For more information on using the `blctl` command, see https://github.com/bouffalolab/blwnet_xram[here].

== Appendix

=== Adding Nuttx RTOS

In this section, we will set up our Ox64 to dual-boot both Linux and the NuttX real-time operating system. For more information see the https://nuttx.apache.org/docs/latest/platforms/risc-v/bl808/boards/ox64/index.html[official documentation].

First, write the normal Linux image to the SD card if you have not done so already. You can find the correct device under `lsblk`:

$ cd ~/ox64/openbouffalo/firmware # if you downloaded pre-built images
# or
$ cd ~/ox64/buildroot/output/images # if you built your own images

$ sudo dd if=/sdcard.img of=/dev/[DEVICE] bs=1M conv=fsync status=progress

Run the following command to re-read the partition tables. Re-inserting the SD card works too:

$ sudo blockdev --rereadpt /dev/[DEVICE]

Download the NuttX image:

$ mkdir -p ~/ox64/nuttx
$ cd ~/ox64/nuttx
$ wget -O ImageNuttx https://github.com/lupyuen2/wip-pinephone-nuttx/releases/download/bl808d-1/Image

Mount the boot partition and make the required modifications:

$ sudo mount /dev/[DEVICE]2 /mnt
$ sudo cp ImageNuttx /mnt/
$ sudo tee -a /mnt/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Mount the rootfs and make the required modifications:

$ sudo mount /dev/[DEVICE]3 /mnt
$ sudo cp ImageNuttx /mnt/boot/
$ sudo tee -a /mnt/boot/extlinux/extlinux.conf <<EOF
LABEL PINE64 OX64 Nuttx
KERNEL ../ImageNuttx
FDT ../bl808-pine64-ox64.dtb
EOF
$ sudo umount /mnt

Enjoy your new Nuttx booting option!

Ox64

2024-06-23T15:37:04Z

Giorez: /* Build */

Ox64

2024-06-23T15:34:45Z

Giorez: /* Build */

Ox64

2024-06-23T15:34:02Z

Giorez: /* Build */

Ox64

2024-01-19T02:17:23Z

Giorez:

Ox64

2024-01-19T01:33:03Z

Giorez:

Ox64

2024-01-19T01:32:24Z

Giorez:

Ox64

2024-01-19T00:52:56Z

Giorez:

Ox64

2024-01-19T00:52:03Z

Giorez:

Ox64

2024-01-19T00:17:48Z

Giorez:

Ox64

2024-01-18T23:18:25Z

Giorez:

Ox64

2024-01-18T22:49:14Z

Giorez:

Ox64

2024-01-18T22:40:34Z

Giorez:

Ox64

2024-01-18T22:29:45Z

Giorez:

Ox64

2024-01-18T22:23:52Z

Giorez:

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-11T02:05:21Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

For PostMarketOS you can use bootstrap to generate distro image or download image as for the other distros. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab
# sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-11T01:52:56Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

For PostMarketOS you can use bootstrap to generate distro image or download image as for the other distros. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-11T00:55:29Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

For PostMarketOS you can use bootstrap to generate distro image or download image as for the other distros. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T23:03:53Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

For PostMarketOS you can use bootstrap to generate distro image or download image as for the other distros. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T22:55:36Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

For PostMarketOS you can use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

If you don't build image via bootatrap (as for other distros), download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T22:53:21Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

For PostMarketOS you can use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

If you don't build image via bootatrap (as for other distros), download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T22:48:04Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
---
For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Download, decompress, mount the image. Copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T22:32:11Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T22:07:36Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos.img
losetup -P /dev/loop0 postmarketos.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T21:27:56Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T19:32:18Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *rchlinux*.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *anjaro*.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *obian*.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *ostmarket*.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *buntu*.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T19:31:35Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *rchlinux*.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *anjaro*.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *obian*.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *ostmarket*.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *buntu*.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo nano /mnt/ubuntusd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>menu label UT
>linux /boot/vmlinuz-6.5.0-okpine-ut
>initrd /boot/initrd.img-6.5.0-okpine-ut
>fdtdir /boot/dtb-6.5.0-okpine-ut//rockchip/

>#append root=UUID=9f3cfee6-e7ed-4d4a-bfeb-e54ef502cec7 console=ttyS2,115200n8 consoleblank=0 loglevel=7 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0
>APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T19:12:11Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *rchlinux*.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *anjaro*.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *obian*.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *ostmarket*.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *buntu*.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T19:07:14Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *rchlinux*.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *anjaro*.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *obian*.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *ostmarket*.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *buntu*.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T18:56:40Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *rchlinux*.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *anjaro*.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *obian*.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *ostmarket*.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *buntu*.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/rockchip/

APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-10T13:08:28Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *rchlinux*.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *anjaro*.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *obian*.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *ostmarket*.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *buntu*.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T20:36:15Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T20:33:37Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
sudo scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot
sudo chmod a=rwx /mnt/ubuntutouchsd/boot/extlinux && sudo chmod a=rwx /mnt/ubuntutouchsd/etc/fstab

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T20:16:38Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketos-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T20:11:59Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.6-rockchip
>initrd /boot/initrd.img-6.6-rockchip
>fdtdir /boot/dtb-6.6-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
># append root=UUID=b282b619-c9b7-4c15-9c3d-2005b35d5999 consoleblank=0 loglevel=7 ro quiet splash plymouth.ignore-serial>

Ctrl+X to save, Yes, Enter.

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T20:07:45Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot
sudo chmod a=rwx /mnt/mobiansd/boot/extlinux && sudo chmod a=rwx /mnt/mobiansd/etc/fstab

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:57:48Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && sudo mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && sudo mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && sudo mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:55:02Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop3 mobian.img
sudo mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
sudo mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

sudo dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
sudo mount /dev/sdb4 /mnt/mobiansd/
sudo scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

sudo cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

sudo nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop4 postmarketos-edge.img
sudo mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
sudo mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

sudo dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
sudo mount /dev/sdb5 /mnt/postmarketossd/
sudo scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
sudo mkdir /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/boot/extlinux && sudo chmod a=rwx /mnt/postmarketossd/etc/fstab

sudo cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

==== Build Ubuntu Touch partition ====

Mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop5 ubuntu.raw
sudo mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
sudo mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

sudo dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
sudo mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

sudo cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

sudo cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Unmount and detach all images ====

sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*
sudo losetup -D

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:33:45Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
sudo rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:32:05Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop2 manjaro.img
sudo mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
sudo mount /dev/loop2p1 /mnt/manjaro/boot/ && sudo mount /dev/loop2p2 /mnt/manjaro/root/

sudo dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
sudo mount /dev/sdb3 /mnt/manjarosd/
sudo scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
sudo mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
sudo mkdir /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/boot/extlinux && sudo chmod a=rwx /mnt/manjarosd/etc/fstab

sudo cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:27:43Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu-touch-pinephone-pro-img-arm64.raw ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop2 manjaro.img
mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/

dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
mount /dev/sdb3 /mnt/manjarosd/
chmod -R a=rwx /mnt/*
scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
mkdir /mnt/manjarosd/boot/extlinux

cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

exit

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:21:43Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop2 manjaro.img
mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/

dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
mount /dev/sdb3 /mnt/manjarosd/
chmod -R a=rwx /mnt/*
scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
mkdir /mnt/manjarosd/boot/extlinux

cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

exit

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /mnt/* && sudo umount /media/*/*
rm -r /mnt/*/* && sudo rm -r /mnt/* && sudo sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:17:09Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/etc/fstab

cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop2 manjaro.img
mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/

dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
mount /dev/sdb3 /mnt/manjarosd/
chmod -R a=rwx /mnt/*
scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
mkdir /mnt/manjarosd/boot/extlinux

cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

exit

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /media/*/*
sudo rm -r /mnt/* && sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:15:09Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux && sudo chmod a=rwx /mnt/archlinuxsd/boot/extlinux

cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop2 manjaro.img
mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/

dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
mount /dev/sdb3 /mnt/manjarosd/
chmod -R a=rwx /mnt/*
scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
mkdir /mnt/manjarosd/boot/extlinux

cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

exit

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /media/*/*
sudo rm -r /mnt/* && sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:11:29Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux

sudo cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

sudo cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop2 manjaro.img
mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/

dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
mount /dev/sdb3 /mnt/manjarosd/
chmod -R a=rwx /mnt/*
scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
mkdir /mnt/manjarosd/boot/extlinux

cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

exit

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /media/*/*
sudo rm -r /mnt/* && sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]

PinePhone Pro/Create a multi-distribution image using rk2aw

2024-01-09T19:10:45Z

Giorez:

This article explains how to create a multi-distribution image on the [[PinePhone Pro]] using ''rk2aw''.

== Multi-distro on microSD Card ==

This article explains how to install megi's [https://xnux.eu/rk2aw/ rk2aw loader], U-Boot to SPI and a multi-distribution image to the microSD card and/or eMMC of the [[PinePhone Pro]]. Further instructions regarding ''rk2aw'' can be found on megi's website under https://xff.cz/kernels/rk2aw/rk2aw-rk3399-pinephone-pro/INSTALL. Please note that loader and userspace utility to flash it are free, but not open-source.

=== Flash rk2Aw loader to SPI ===

Connect PinePhone Pro to a Linux machine, start a ssh connection and download installer to flash pre-loader to the phone's SPI.

ssh <user>@<phoneip>
cd ~/Downloads
curl -O https://xff.cz/kernels/bootloaders/ppp.tar.gz
tar -xvzf ppp.tar.gz -C ~/Downloads
# scp -r ~/Downloads/ppp <user>@<phoneip>:~/Downloads'' # copy to phone, non needed''
cd ppp
sudo ./spinor-flash-initial-setup.sh

=== Build multi-distro on the microSD card ===

If necessary wipe the microSD card

sudo dd if=/dev/zero of=/dev/sdb count=1 bs=32768 status=progress'' # quick way i.e. # 32GB SDcard (30989615104bytes/32768dim=1volta)''
sudo dd if=/dev/zero of=/dev/sdb count=945728 bs=32768 status=progress'' # slow way i.e. # 32GB SDcard (30989615104bytes/32768dim=945728volte)''
sudo dd if=/dev/zero of=/dev/sdb count=15271040 bs=4096 status=progress'' # 63GB SDcard (62550179840bytes/512dim=122168320volte)''
sudo shred -n 5 -vz /dev/sdb # 6 scritture 12h x 64gb

Before removing partitions, if you need to remove also left signatures, use gParted and format each partition "cleared". Than remove all partitions with gParted.

sudo wipefs /dev/sdb # shows current signatures
sudo wipefs --all --force /dev/sdb # erase current signatures

==== Partition the microSD card ====

{{Info|A minimum capacity of 64 GB for the microSD card is recommended for 5 distributions.}}

sudo sfdisk /dev/sdb --wipe always <<EOF
label: gpt
first-lba: 64
table-length: 8
start=64, size=32704, type=D7B1F817-AA75-2F4F-830D-84818A145370, name="loader", attrs=RequiredPartition
size=11G, name="ALARM", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MANJARO", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="MOBIAN", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="PMOS", attrs="RequiredPartition,LegacyBIOSBootable"
size=11G, name="UT", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="extra", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 58.25 GiB, 62550179840 bytes, 122168320 sectors
Disk model: SD Card Reader
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C44BE2FC-34D6-4DD8-99FC-7FFB75602A79
Old situation:
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: F71BFBA6-D2C3-4C20-8079-1401B10C724C).
The maximal number of partitions is 8 (default is 128).
/dev/sdb1: Created a new partition 1 of type 'unknown' and of size 16 MiB.
/dev/sdb2: Created a new partition 2 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb3: Created a new partition 3 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb4: Created a new partition 4 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb5: Created a new partition 5 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb6: Created a new partition 6 of type 'Linux filesystem' and of size 11 GiB.
/dev/sdb7: Created a new partition 7 of type 'Linux filesystem' and of size 3.2 GiB.
/dev/sdb8: Done.
New situation:
Disklabel type: gpt
Disk identifier: F71BFBA6-D2C3-4C20-8079-1401B10C724C
Device Start End Sectors Size Type
/dev/sdb1 64 32767 32704 16M unknown
/dev/sdb2 32768 23101439 23068672 11G Linux filesystem
/dev/sdb3 23101440 46170111 23068672 11G Linux filesystem
/dev/sdb4 46170112 69238783 23068672 11G Linux filesystem
/dev/sdb5 69238784 92307455 23068672 11G Linux filesystem
/dev/sdb6 92307456 115376127 23068672 11G Linux filesystem
/dev/sdb7 115376128 122167295 6791168 3.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

==== Get image files of the distributions ====
Get the compressed distribution images from [[PinePhone Pro Software Releases]], decompress them and mount both partitions "/boot", "/root" from each distro.

Change the directory to the ''Downloads'' folder.
cd ~/Downloads/ppp/distros

Get images.'' Example releases (update the syntax to newer releases).''

wget https://github.com/dreemurrs-embedded/Pine64-Arch/releases/download/20230925/archlinux-pinephone-pro-phosh-20230925.img.xz
wget https://github.com/manjaro-pinephone/phosh/releases/download/beta37/Manjaro-ARM-phosh-pinephonepro-beta37.img.xz
wget https://images.mobian.org/pinephonepro/weekly/mobian-pinephonepro-phosh-20240107.img.xz
wget https://images.postmarketos.org/bpo/v23.12/pine64-pinephonepro/phosh/20240103-1352/20240103-1352-postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz
wget https://ci.ubports.com/job/focal-hybris-rootfs-arm64/job/master/lastSuccessfulBuild/artifact/ubuntu-touch-pinephone-pro-img-arm64.raw.xz

Extract the compressed files:

xz -v -d -k archlinux-pinephone-pro-phosh-20230925.img.xz && rm *.xz && mv archlinux-pinephone-pro-phosh-20230925.img archlinux.img
xz -v -d -k Manjaro-ARM-phosh-pinephonepro-beta37.img.xz && rm *.xz && mv Manjaro-ARM-phosh-pinephonepro-beta37.img manjaro.img
xz -v -d -k mobian-pinephonepro-phosh-20240107.img.xz && rm *.xz && mv mobian-pinephonepro-phosh-20240107.img mobian.img
xz -v -d -k postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img.xz && rm *.xz && mv postmarketOS-v23.12-phosh-22.3-pine64-pinephonepro.img postmarketos.img
xz -v -d -k ubuntu-touch-pinephone-pro-img-arm64.raw.xz && rm *.xz && mv ubuntu.raw

For PostMarketOS you can also use bootstrap to generate distro image. Make sure you install pmbootstrap before building images

git clone --depth=1 https://git.sr.ht/~postmarketos/pmbootstrap
mkdir -p ~/.local/bin
ln -s "$PWD/pmbootstrap/pmbootstrap.py" ~/.local/bin/pmbootstrap
source ~/.profile ''# remember to update your environment''
pmbootstrap --version ''# If this returns error, put ~/.local/bin in your PATH, adding the following to your ~/.profile (zsh: ~/.zprofile).''
''# PATH="$HOME/.local/bin:$PATH" # optional''

Create 2GB empty image file, format and mount it.

sudo su
dd if=/dev/zero of=postmarketos-edge.img bs=1 count=0 seek=2G status=progress && sync
mkfs.ext4 postmarketOS-edge.img
losetup -P /dev/loop0 postmarketos-edge.img
exit

Build PMOS image via pmbootstrap
pmbootstrap init ''# follow all the setup directions''
pmbootstrap status
pmbootstrap pull
pmbootstrap install --sdcard=/dev/loop0
pmbootstrap shutdown ''# remember to deactivare chroot after the image creation''

==== Build Arch Linux partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo losetup -P /dev/loop1 archlinux.img
sudo mkdir /mnt/archlinux /mnt/archlinux/boot /mnt/archlinux/root /mnt/archlinuxsd
sudo mount /dev/loop1p1 /mnt/archlinux/boot/ && sudo mount /dev/loop1p2 /mnt/archlinux/root/

sudo dd if=/dev/loop1p2 of=/dev/sdb2 bs=1M status=progress conv=fsync
sudo mount /dev/sdb2 /mnt/archlinuxsd/
sudo scp -r /mnt/archlinux/boot/* /mnt/archlinuxsd/boot
sudo mv /mnt/archlinuxsd/boot/boot.scr /mnt/archlinuxsd/boot/boot.scrORIG
sudo mkdir /mnt/archlinuxsd/boot/extlinux

cat << EOF > /mnt/archlinuxsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL ALARM
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image.gz
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=ALARM console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/archlinuxsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=ALARM / ext4 rw,relatime 0 1
EOF

==== Build Manjaro partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop2 manjaro.img
mkdir /mnt/manjaro /mnt/manjaro/boot /mnt/manjaro/root /mnt/manjarosd
mount /dev/loop2p1 /mnt/manjaro/boot/ && mount /dev/loop2p2 /mnt/manjaro/root/

dd if=/dev/loop2p2 of=/dev/sdb3 bs=1M status=progress conv=fsync
mount /dev/sdb3 /mnt/manjarosd/
chmod -R a=rwx /mnt/*
scp -r /mnt/manjaro/boot/* /mnt/manjarosd/boot
mv /mnt/manjarosd/boot/boot.scr /mnt/manjarosd/boot/boot.scrORIG
mkdir /mnt/manjarosd/boot/extlinux

cat << EOF > /mnt/manjarosd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL MANJARO
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=MANJARO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/manjarosd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MANJARO / ext4 defaults 0 1
EOF

exit

==== Build Mobian partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop3 mobian.img
mkdir /mnt/mobian /mnt/mobian/boot /mnt/mobian/root /mnt/mobiansd
mount /dev/loop3p1 /mnt/mobian/boot/ && mount /dev/loop3p2 /mnt/mobian/root/

dd if=/dev/loop3p2 of=/dev/sdb4 bs=1M status=progress conv=fsync
mount /dev/sdb4 /mnt/mobiansd/
scp -r /mnt/mobian/boot/* /mnt/mobiansd/boot

cat << EOF > /mnt/mobiansd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=MOBIAN / ext4 defaults,x-systemd.growfs 0 1
EOF

nano /mnt/mobiansd/boot/extlinux/extlinux.conf
>adjust ## /boot/extlinux/extlinux.conf file
>MENU LABEL MOBIAN
>linux /boot/vmlinuz-6.1-rockchip
>initrd /boot/initrd.img-6.1-rockchip
>fdtdir /boot/dtb-6.1-rockchip/
>APPEND root=PARTLABEL=MOBIAN console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait

==== Build PostmarketOS partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop4 postmarketos-edge.img
mkdir /mnt/postmarketos /mnt/postmarketos/boot /mnt/postmarketos/root /mnt/postmarketossd
mount /dev/loop4p1 /mnt/postmarketos/boot/ && mount /dev/loop4p2 /mnt/postmarketos/root/

dd if=/dev/loop4p2 of=/dev/sdb5 bs=1M status=progress conv=fsync
mount /dev/sdb5 /mnt/postmarketossd/
scp -r /mnt/postmarketos/boot/* /mnt/postmarketossd/boot
mkdir /mnt/postmarketossd/boot/extlinux

cat << EOF > /mnt/postmarketossd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 10
label l0
menu label PMOS
linux /boot/vmlinuz
initrd /boot/initramfs-extra
fdtdir /boot/dtbs-pine64-pinephonepro/
APPEND root=PARTLABEL=PMOS console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

cat << EOF > /mnt/postmarketossd/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
PARTLABEL=PMOS / ext4 defaults 0 0
EOF

exit

==== Build Ubuntu Touch partition ====

Login as root, mount the image, copy rootfs and bootfs to the partition. You need also to make some changes on some files.

cd ~/Downloads/ppp/distros
sudo su ''# login with your psw''
losetup -P /dev/loop5 ubuntu.raw
mkdir /mnt/ubuntutouch /mnt/ubuntutouch/boot /mnt/ubuntutouch/root /mnt/ubuntutouchsd
mount /dev/loop5p2 /mnt/ubuntutouch/boot/ && mount /dev/loop5p3 /mnt/ubuntutouch/root/

dd if=/dev/loop5p3 of=/dev/sdb6 bs=1M status=progress conv=fsync
mount /dev/sdb6 /mnt/ubuntutouchsd/
scp -r /mnt/ubuntutouch/boot/* /mnt/ubuntutouchsd/boot

cat << EOF > /mnt/ubuntutouchsd/etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=UT / ext4 defaults 0 1
EOF

cat << EOF > /mnt/ubuntutouchsd/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
default l0
menu title U-Boot menu
prompt 0
timeout 50
label l0
menu label UT
linux /boot/vmlinuz-6.5.0-okpine-ut
initrd /boot/initrd.img-6.5.0-okpine-ut
fdtdir /boot/dtb-6.5.0-okpine-ut/
APPEND root=PARTLABEL=UT console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

exit

==== Unmount and detach all images ====

sudo losetup -D
sudo umount /mnt/*/* && sudo umount /media/*/*
sudo rm -r /mnt/* && sudo rm -r /media/*/*

==== Switching On Device ====

[[File:Rk2awTutorialGioWiki.jpg|thumb|right|200px|Options to boot Arch Linux ARM, Manjaro, Mobian, PostmarketOS and Ubuntu Touch]]

According to [https://xnux.eu/rk2aw/ rk2aw loader] info, to operate your PinePhonePro you can:

Plug in USB power cord. Led blinks: 0.5s on, 0.5s off. Battery is charging.

Press shortly power button. Graphical menu appears, than just press onto the image to boot from.

Press power button longer, led starts to blinks rapidly. Release power button, led blinks N times each second according to the flashed images. 
''In example: ''
''Led blinks once each second and 1st image is selected ;''
''Led blinks twice each second and 2nd image is seleted ;''
''Led blinks triple each second and 3rd image is selected .''
Press shortly to move to next image. 
Press longer to boot the selected image.

In case you hold the power button too long, the device is forced to power off.

==== Troubleshooting ====

If device doesn't start, connect serial cable (https://pine64.com/product/pinebook-pinephone-pinetab-serial-console/) to headphone jack, switch off microswitch 6 and start a serial console:

ls /dev/ttyUSB* # check usb address from linux machine
minicom -b 1500000 -D /dev/ttyUSB0

More info about erasing eMMC on https://wiki.pine64.org/wiki/PinePhone_Pro_Developer_Edition#Method_2:_Via_serial_cable

== Multi-distro on eMMC ==

[[File:P1090461.JPG|thumb|right|200px|Options to boot Phosh or sxmo]]

Make sure you boot from the microSD card in your PinePhone Pro as we are going to overwrite the eMMC. Note that below, Arch is booted from the microSD card and the microSD card is listed as the device '''/dev/mmcblk1'''.

=== Flash rk2Aw loader to SPI ===

Same as above. Note this installs rk2aw and a bootloader to SPI NOR flash. Resulting SPI status is as follow:

# ./rk2aw-spi-flasher
Machine: Pine64 PinePhonePro (pine64,pinephone-pro)
SPI NOR Flash:
- Total size: 16384 KiB
- Erase block size: 4 KiB
- Write size: 1
- Manufacturer: gigadevice
- Part name: gd25lq128e
- JEDEC ID: 257018

Bootable images currently present in SPI NOR flash:
Idx Header Off 1 Size 1 Off 2 Size 2 Notes/content
-------------------------------------------------------------------------------
0 0 2048 6144 0 0 (padded) 0='rk2aw'
5 131072 133120 67584 200704 124928 0='U-Boot TPL' 1='U-Boot SPL'
7 524288 526336 147456 673792 124928 0='ddrbin' 1='U-Boot SPL'

Auto-calculated layout for rk2aw dual bootloader scheme:
Area Offset Size
---------------------------------------------------
rk2aw primary 0 65536
rk2aw backup 65536 65536
spl fallback 131072 393216
spl primary 524288 389120
itb fallback 913408 2097152
itb primary 3010560 2097152

=== Build multi-distro eMMC ===

In this example we are going to build 2 partitions on the eMMC, the first with Arch/Phosh and the second with Arch/sxmo. We have already downloaded the images from [https://github.com/dreemurrs-embedded/Pine64-Arch/releases Danct12] and decompressed them.

==== Mount the images ====

cd ~/Downloads ''# enter to directory''
sudo su ''# login with your psw''
losetup -P /dev/loop0 archlinux-pinephone-pro-phosh-20230203.img
losetup -P /dev/loop1 archlinux-pinephone-pro-sxmo-20230203.img
ls -l /mnt/
mkdir /mnt/phosh
mkdir /mnt/sxmo
mkdir /mnt/phosh/boot
mkdir /mnt/phosh/root
mkdir /mnt/sxmo/boot
mkdir /mnt/sxmo/root
mkdir /mnt/ephosh'' # e for the partition on the eMMC''
mkdir /mnt/esxmo'' # e for the partition on the eMMC''
mount /dev/loop0p1 /mnt/phosh/boot/
mount /dev/loop0p2 /mnt/phosh/root/
mount /dev/loop1p1 /mnt/sxmo/boot/
mount /dev/loop1p2 /mnt/sxmo/root/

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 122M 0 part
└─mmcblk2p2 179:2 0 115.1G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Prepare eMMC ====

dd if=/dev/zero of=/dev/mmcblk2 count=32768 bs=32768 status=progress'' # overwrite the front to clear any bootloaders''

sfdisk /dev/mmcblk2 << EOF
label: gpt
first-lba: 64
table-length: 8
size=32G, name="PHOSH", attrs="RequiredPartition,LegacyBIOSBootable"
size=+, name="SXMO", attrs="RequiredPartition,LegacyBIOSBootable"
EOF

Checking that no-one is using this disk right now ... OK
Disk /dev/mmcblk2: 115.23 GiB, 123731968000 bytes, 241664000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461).
The maximal number of partitions is 8 (default is 128).
/dev/mmcblk2p1: Created a new partition 1 of type 'Linux filesystem' and of size 32 GiB.
/dev/mmcblk2p2: Created a new partition 2 of type 'Linux filesystem' and of size 83.2 GiB.
/dev/mmcblk2p3: Done.

New situation:
Disklabel type: gpt
Disk identifier: 7EB4B1E0-5F49-4F30-9F1E-E9E1F305D461
Device Start End Sectors Size Type
/dev/mmcblk2p1 2048 67110911 67108864 32G Linux filesystem
/dev/mmcblk2p2 67110912 241661951 174551040 83.2G Linux filesystem
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part /mnt/phosh/boot
└─loop0p2 259:1 0 4.9G 0 part /mnt/phosh/root
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

==== Build Phosh partition ====

dd if=/dev/loop0p2 of=/dev/mmcblk2p1 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p1 /mnt/ephosh/
scp -r /mnt/phosh/boot/* /mnt/ephosh/boot
mv /mnt/ephosh/boot/boot.scr /mnt/ephosh/boot/boot.scrORIG

cat << EOF > /mnt/ephosh/etc/fstab
#/boot/extlinux/extlinux.conf
#Static information about the filesystems.
#See fstab(5) for details.
#<file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=PHOSH / ext4 rw,relatime 0 1
# UUID=52CA-6165 /boot vf rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

mkdir /mnt/ephosh/boot/extlinux

cat << EOF > /mnt/ephosh/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL phosh
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=PHOSH console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

==== Build SXMO partition ====

We have unmounted all the Phosh devices, so

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 5G 0 loop
├─loop0p1 259:0 0 122M 0 part
└─loop0p2 259:1 0 4.9G 0 part
loop1 7:1 0 3.5G 0 loop
├─loop1p1 259:2 0 122M 0 part /mnt/sxmo/boot
└─loop1p2 259:3 0 3.4G 0 part /mnt/sxmo/root
mmcblk2 179:0 0 115.2G 0 disk
├─mmcblk2p1 179:1 0 32G 0 part
└─mmcblk2p2 179:2 0 83.2G 0 part
mmcblk2boot0 179:32 0 4M 1 disk
mmcblk2boot1 179:64 0 4M 1 disk
mmcblk1 179:96 0 59.6G 0 disk
├─mmcblk1p1 179:97 0 122M 0 part /boot
└─mmcblk1p2 179:98 0 59.5G 0 part /
zram0 254:0 0 1.5G 0 disk [SWAP]

dd if=/dev/loop1p2 of=/dev/mmcblk2p2 bs=1M status=progress conv=fsync
mount /dev/mmcblk2p2 /mnt/esxmo/
scp -r /mnt/sxmo/boot/* /mnt/esxmo/boot
mv /mnt/esxmo/boot/boot.scr /mnt/esxmo/boot/boot.scrORIG

cat << EOF > /mnt/esxmo/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
PARTLABEL=SXMO / ext4 rw,relatime 0 1
# UUID=841C-F9DD /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
EOF

mkdir /mnt/esxmo/boot/extlinux

cat << EOF > /mnt/esxmo/boot/extlinux/extlinux.conf
#/boot/extlinux/extlinux.conf
MENU TITLE Pinephone Pro Boot Menu
LABEL l0
MENU LABEL sxmo
FDT /boot/dtbs/rockchip/rk3399-pinephone-pro.dtb
KERNEL /boot/Image
INITRD /boot/initramfs-linux.img
APPEND root=PARTLABEL=SXMO console=ttyS2,115200 console=tty0 loglevel=4 rw rootwait
EOF

== Follow-up comments ==

# On first boot neither Phosh nor sxmo resized their partition - ''sudo resize2fs'' sorted that.
# Any time an update rebuilds the initramfs it is necessary to delete /boot/boot.scr again to keep the rk2aw menu clean.
# In case you want to reinstall just a single distribution, the easy way is to delete an recreate partition using gParted GUI.

[[Category:PinePhone Pro]]