PINE64 - User contributions [en]

Pinebook Pro Software Releases

2021-02-20T14:41:49Z

Cypherpunks: /* NixOS for Pinebook Pro */ fix link

= Linux OS Image Releases =
For information on how to install these images onto your device, please see the [[NOOB]] Page, which includes information on writing images to the device eMMC or an SD card.

If Manjaro is installed on the eMMC you may experience issues booting different installations from SD card. [https://gitlab.manjaro.org/snippets/490 List of known affected distros and workaround].

== elementary OS ==
[[File:elementaryLogo.png|right|100px]]

=== elementary OS 6 [microSD/eMMC boot] ===

* Full version of elementary OS optimized for Pinebook Pro
* Experimental [https://builds.elementary.io/ “Early Access” build of elementary OS 6] (which has not been released as stable)
** Size: ~1.2 GB (varies since images are built daily)
* Polished first-run setup which helps you create a user before logging in
* Downloading, installation, etc. details at the [https://github.com/elementary/os/wiki/Pinebook-Pro elementary OS Wiki]

==Kali Linux==
[[File:Kali.jpeg|right|100px]]

=== Kali Linux prebuilt OS images for Pinebook Pro [SD/eMMC boot]===
* Official pre-built OS images of Kali Linux for the Pinebook Pro featuring all tools you'd expect from the distribution.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://www.offensive-security.com/kali-linux-arm-images/ Direct download latest images from Offensive Security's website]
** size: 2.0GB
* Login with
** username: kali
** password: kali

== Arch Linux ==
[[File:Archlinux-logo.png|right|100px]]

=== Arch Linux ARM install image [microSD/USB Boot] ===
* archiso image customized for Arch Linux ARM on the Pinebook Pro
* DD image (for 1GB or larger microSD card/USB stick):
** [https://github.com/nadiaholmquist/archiso-pbp/releases Direct download for latest releases from GitHub]
** size: 579MB
* Automatic login as root
* Make sure to thoroughly read the [https://github.com/nadiaholmquist/archiso-pbp/blob/master/README.md readme] and [https://github.com/nadiaholmquist/archiso-pbp/blob/master/FAQ.md FAQ], otherwise follow the normal Arch installation guide.

== Manjaro ARM ==
[[File:Manjaro.png|right|100px]]

* The Manjaro project offers a mainline kernel with patches and modules to support PBPro hardware in two flavors. Both provide DD images and installer images (DD to SD card which will then install to eMMC when booted).
* To learn more about Manjaro please visit [https://forum.manjaro.org/tags/manjaroarm Manjaro Forum]
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=8207)

=== Manjaro ARM with KDE (Plasma) desktop [microSD / eMMC Boot] ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-kde-plasma/ Direct download from Manjaro] (microSD image only)
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/kde-plasma/ Direct download from osdn.net] (both microSD and emmc-installer images)

=== Manjaro ARM with GTK (XFCE) desktop [microSD / eMMC Boot] ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-xfce/ Direct download from Manjaro]
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/xfce/ Direct download from osdn.net]

=== Manjaro ARM with i3 tiling window manager [microSD / eMMC Boot] ===

* [https://manjaro.org/downloads/arm/pinebook-pro/arm8-pinebook-pro-i3/ Direct download from Manjaro]
* [https://osdn.net/projects/manjaro-arm/storage/pbpro/i3/ Direct download from osdn.net]

=== Manjaro ARM with Sway tiling window manager [microSD / eMMC Boot] ===

* [https://osdn.net/projects/manjaro-arm/storage/pbpro/sway/ Direct download from osdn.net]

=== Manjaro ARM installer ===

The [https://gitlab.manjaro.org/manjaro-arm/applications/manjaro-arm-installer manjaro-arm-installer] script is intended to install Manjaro ARM directly to SD/eMMC cards without the need for images (including LXQT, Mate & CuboCore editions, as well as full disk encryption). Running on a Linux x86 computer, it can install Manjaro ARM directly to an empty eMMC using an eMMC to USB adapter. The script can also be run from SD to install an image to the eMMC.

== OpenSUSE ==
[[File:Opensuse1.png|right|100px]]

=== OpenSUSE XFCE OS Image [microSD / eMMC Boot] ===
* This image contains an install of openSUSE tumbleweed with XFCE desktop environment.
* To learn more about OpenSUSE please visit the [https://www.opensuse.org/ official website].
* Pinebook Pro build instructions can be found [https://github.com/smithmcgriff/opensuse-on-pinebookpro-gnome here]
* DD image (for 16GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/opensuse-on-pinebookpro/files/Rel_1/ Direct download latest release build from SourceForge]
* login with:
** username: root
** password: linux

=== OpenSUSE GNOME 3 OS Image [microSD / eMMC Boot] ===
* This image contains an install of openSUSE tumbleweed with GNOME 3 desktop environment.
* To learn more about OpenSUSE please visit the [https://www.opensuse.org/ official website].
* Pinebook Pro build instructions can be found [https://github.com/smithmcgriff/opensuse-on-pinebookpro-gnome here]
* DD image (for 16GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/opensuse-on-pinebookpro/files/Rel_1/ Direct download latest release build from SourceForge]
* login with:
** username: tux
** password: susepassword

== Fedora ==
[[File:fedora1.png|right|100px]]

=== Fedora 32 Cinnamon Desktop OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with [https://cinnamon-spices.linuxmint.com/ Cinnamon] desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Cinnamon-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

=== Fedora 32 KDE Desktop OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with [https://kde.org/ KDE aka Plasma] desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-KDE-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

=== Fedora 32 Xfce Desktop OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with [https://xfce.org/ xfce] desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Xfce-Desktop-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

=== Fedora 32 Workstation OS Image [microSD / eMMC Boot] ===
* This image contains an install of Fedora with [https://www.gnome.org/gnome-3/ GNOME 3] desktop environment.
* To learn more about Fedora please visit the [https://getfedora.org/ official website].
* DD image (for 12GB microSD card / eMMC module and above)
** [https://builds.armdevelopers.com/pinebook-pro/releases/dev/Fedora32-Workstation-202009.0.pinebook-pro.img.xz Fedora 32 Pinebook Pro Image]
* login with:
** username: root
** password: fedora

== Armbian ==
[[File:armbian.png|right|100px]]

* To find out more about Armbian and available options please visit their [https://www.armbian.com/pinebook-pro/ site]
* DD image to microSD card or eMMC module and boot. Highly recommend using [https://etcher.io/ Etcher]

=== Armbian Ubuntu Focal XFCE Desktop mainline kernel [microSD / eMMC Boot] ===
* Armbian provides a mainline kernel build images for Ubuntu Focal with XFCE Desktop
* DD image (for 8GB micoSD card or eMMC Module and above)
** [https://dl.armbian.com/pinebook-pro/Focal_current_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]

=== Armbian Ubuntu Focal XFCE Desktop legacy kernel [microSD / eMMC Boot] ===
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Focal with XFCE Desktop
* DD image (for 8GB microSD card or eMMC Module and above)
** [https://dl.armbian.com/pinebook-pro/Focal_legacy_desktop Armbian's Pinebook Pro Ubuntu Focal XFCE Desktop download site]

=== Armbian Debian Buster XFCE Desktop legacy kernel [microSD / eMMC Boot] ===
* Armbian provides a legacy kernel 4.4 build images for Debian Buster with XFCE Desktop
* DD image (for 8GB micoSD card or eMMC Module and above)
** [https://dl.armbian.com/pinebook-pro/Buster_legacy_desktop Armbian's Pinebook Pro Debian Buster XFCE Desktop download site]

=== Armbian Ubuntu Bionic XFCE Desktop legacy kernel [microSD / eMMC Boot] ===
* Armbian provides a legacy kernel 4.4 build images for Ubuntu Bionic with XFCE Desktop
* DD image (for 8GB micoSD card or eMMC Module and above)
** [https://dl.armbian.com/pinebook-pro/Bionic_legacy_desktop Armbian's Pinebook Pro Ubuntu Bionic XFCE Desktop download site]

== AOSC ==
[[File:aosc.png|right|100px]]

* To learn more about AOSC, please visit the official [https://aosc.io/ AOSC website]
* AOSC using LZ4 compression algorithm, please visit the [https://github.com/lz4/lz4 LZ4 github site] for utility
* 8GB microSD card or eMMC module and above
* Login with
** username: aosc
** password: anthon
=== AOSC KDE Community Build Image [microSD and eMMC Boot] ===
* [https://releases.aosc.io/os-arm64/rockchip64/kde/pinebook-pro/ Direct download from AOSC]

=== AOSC GNOME Community Build Image [microSD and eMMC Boot] ===
* [https://releases.aosc.io/os-arm64/rockchip64/gnome/pinebook-pro/ Direct download from AOSC]

=== AOSC MATE Community Build Image [microSD and eMMC Boot] ===
* [https://releases.aosc.io/os-arm64/rockchip64/mate/pinebook-pro/ Direct download from AOSC]

=== AOSC Cinnamon Community Build Image [microSD and eMMC Boot] ===
* [https://releases.aosc.io/os-arm64/rockchip64/cinnamon/pinebook-pro/ Direct download from AOSC]

=== AOSC XFCE Community Build Image [microSD and eMMC Boot] ===
* [https://releases.aosc.io/os-arm64/rockchip64/xfce/pinebook-pro/ Direct download from AOSC]

=== AOSC LXDE Community Build Image [microSD and eMMC Boot] ===
* [https://releases.aosc.io/os-arm64/rockchip64/lxde/pinebook-pro/ Direct download from AOSC]

== Twister OS ==
[[File:Twister_OS.png|right|100px]]

=== Twister OS Armbian-Reforged XFCE Dsktop beta images [SD boot]===
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.
* DD image (for 16GB microSD card /16GB eMMC module and above):
** [https://twisteros.com/twisterarmbian.html Direct download latest images from Twister OS's website]
** size: 2.8GB
* Login with
** password: asdasd

=== Twister OS Monka-Manjaro XFCE Dsktop beta images [SD boot]===
* For more infomation on Twister OS, please visit this {https://twisteros.com/ official site]
* You can follow the ongoing discussion about Twister OS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12192)
* After flashing image with Etcher, edit /boot/armbianEnv.txt, replace the dtb name with rk3399-pinebook-pro.dtb.
* DD image (for 16GB microSD card /16GB eMMC module and above):
** [https://drive.google.com/file/d/1I0yHIDfezqnz1jdphJ4gooWbGtNw0ArW/view?usp=sharing Direct download latest images from Google Drive]
** size: 8.9GB
* Login with
** username: pi
** password: root

== Debian Desktop ==
[[File:debian.png|right|100px]]

=== Debian Desktop Community Build Image [microSD to eMMC] by mrfixit2001 ===
* This was previously the default operating system for the Pinebook Pro
* Includes desktop, Firefox browser, and LibreOffice
* DD image (for 8GB microSD card / 16GB eMMC module and above):
** [https://github.com/mrfixit2001/debian_desktop/releases/download/191226/pinebookpro-debian-desktop-mrfixit191226.img.xz Direct download release build 191226 from mrfixit2001's github]
*** MD5 (img file): 59838c1518b8b6da86a00d38b31ae904
*** File Size: 1.19GB
* Login with
** username: rock
** password: rock

== Ubuntu 20.04 Focal Fossa MATE / GNOME ==
[[File:UbuntuLogo.png|right|100px]]

=== Ubuntu 20.04 Focal Fossa MATE and GNOME Community Builds [microSD/ eMMC Boot] by ayufan ===
* Desktop Images featurng a standard Ubuntu suite of software to get you started.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://github.com/ayufan-rock64/linux-build/releases Direct download for latests releases and pre-releases on ayufan's github]
** size: 1.06GB
* Login with
** username: rock64
** password: rock64 (must be changed on initial boot)

== Ubuntu 18.04 Bionic Beaver LXDE ==
[[File:lxde.png|right|100px]]

=== Ubuntu 18.04 Bionic Beaver LXDE Community Build Image by ayufan [microSD and eMMC Boot] ===
* Included LXDE Desktop, Firefox Browser, and LibreOffice Suite
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.9.14/bionic-lxde-pinebookpro-0.9.14-1159-armhf.img.xz Direct download release build 0.9.14 from ayufan's github]
** MD5 (XZ file): B74E8366615DAE89AEB5CC878F2B316B
** size: 763MB
* Login with
** username: rock64
** password: rock64

== Bionic Mate ==
[[File:mate.png|right|100px]]

=== Bionic Mate Community Build Image [microSD Boot] by ayufan ===
* Included Mate Desktop, Firefox Browser, and LibreOffice Suite
* DD image (for 8GB microSD card / 16GB eMMC module and above):
** [https://github.com/ayufan-rock64/linux-build/releases/download/0.9.14/bionic-mate-pinebookpro-0.9.14-1159-armhf.img.xz Direct download release build 0.9.14 from ayufan's github]
** MD5 (XZ file): 5F60494B9248570FAF5853860A26B489
** size: 1.06GB
* Login with
** username: rock64
** password: rock64

== postmarketOS ==
[[File:PostmarketOS logo.png|right|100px]]

===Official postmarketOS build [microSD/ eMMC Boot] ===
* Official postmarketOS build with the GNOME desktop for the Pinebook Pro.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [http://images.postmarketos.org/pinebookpro/ Direct download latest images from postmarketOS]
** size: 400MB
* Login with
** username: demo
** password: demo OR 147147

== Q4OS ==
[[File:q4os.png|right|100px]]

=== Q4OS Test Build Image [microSD / eMMC Boot] ===
* Q4OS is advertised as a 'fast and powerful operating system based on the latest technologies while offering highly productive desktop environment'
* To learn more please visit the [https://forum.pine64.org/showthread.php?tid=8385 PINE64 forum] or official [https://q4os.org/index.html Q4OS website]
* DD image (for 8GB microSD card / eMMC module and above)
** [https://sourceforge.net/projects/q4os/files/testing/ Direct download latest release build from SourceForge]
* User account and password are created on first run

==Recalbox==
[[File:RB.png|right|100px]]

=== Recalbox for Pinebook Pro [SD/eMMC boot]===
* Recalbox is a retrogaming Linux distribution allowing for emulation of all classic videogame systems.
* DD image (for 8GB microSD card /16GB eMMC module and above):
** [https://github.com/mrfixit2001/recalbox-rockchip/releases Direct download latest images from MrFixit's gitbub]
** size: 450MB
* SSH Login
** username: root
** password: recalboxroot

= BSD OS Image Release =

==NetBSD==
[[File:netbsd.png|right|100px]]

=== NetBSD [microSD /eMMC Boot] ===
* To learn more about NetBSD please visit [https://www.netbsd.org/ NetBSD main page]
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [http://www.armbsd.org/arm/ Direct download from NetBSD]
* Console and SSH default login:
** username: root
** password: [none]
* Instructions concerning enabling SSH can be found [https://www.netbsd.org/docs/guide/en/chap-boot.html#chap-boot-ssh here]

==OpenBSD==
[[File:Puffy_mascot_openbsd.png|right|100px]]

=== OpenBSD ===
* To learn more about OpenBSD, please visit [https://www.openbsd.org/ OpenBSD main page]
* ARM64 images, (including support for Pinebook Pro), can be found here [https://www.openbsd.org/arm64.html OpenBSD arm64]

= Chromium OS Image Release =

== FydeOS ==
[[File:FydeOS.png|right|100px]]

To learn more about FydeOS please visit [https://releases.fydeos.io/11.2/pinebook-pro]

* You can follow the ongoing discussion about FydeOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=12201)
* DD image to microSD card or eMMC module. Highly recommend using [https://etcher.io/ Etcher]
** [https://fydeos.com/download/ Direct download latest release build from FydeOS by select "FydeOS for You Pinebook Pro"]

== ChromiumOS Community Build Image by ayufan [microSD and eMMC Boot] ==
[[File:chromium.jpg|right|100px]]

* DD image (for 8GB microSD card/16GB eMMC module and above)
** [https://github.com/ayufan-rock64/chromiumos-build/releases/download/R77-12371.7.104.g78f88d6/chromiumos-rockpro64-R77-12371.7.104.g78f88d6.img.xz Direct download R77 build from ayufan's github]
** MD5 (XZ file): 7B747B6D2B041C5C0C6434DDB524DB66
** size: 387MB

= Android Image Releases =

== Android 7.1 microSD ==
[[File:android_7.png|right|100px]]

=== Stock Android for DD method [micro SD Boot] [20190918] ===
* Production floor testing image
* Use 'dd' to write the image to the microSD card and boot. Using [https://www.balena.io/etcher/ Etcher] or another specialized SD writing tool is preferred.
* Please allow 3-5 minutes boot up time on first time for initialization
* DD image for 8GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-8GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 207BCBFFF59C1AB29F8ADC63D426EACB
*** File Size: 562MB
* DD image for 16GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-16GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): B1FC25A2F896F5C6B4B85EA6D1E75CDA
*** File Size: 571MB
* DD image for 32GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-32GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): A07E2C2A2798A77375268E423A30048A
*** File Size: 589MB
* DD image for 64GB microSD card
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190918_stock_android_7.1_sdboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): D7626BD50443A88AEB9254C88C575284
*** File Size: 627MB

=== Stock for RK Flash tool [SD Boot] [20190427] ===
* Please unzip first and then using [http://files.pine64.org/os/ROCK64/android/SDDiskTool_v1.57.zip Rockchip SD Firmware Tool ver 1.57] to flash in, please remember to select "SD boot" option.
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_20190918_stock_android_7.1_sdboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): DBA2109C393F514132EC8D5FB6E8EBE2
** File Size: 555MB

== Android 7.1 eMMC ==
=== Stock Android for DD method [eMMC Boot] [20190807] ===
* Production floor testing image
* Please allows some time (around 5 minutes) for the initialization process on 1st boot
* DD image for 64GB eMMC Module
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190807_stock_android_7.1_emmcboot-64GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 314583B550AFF0F424D9997D237D7046
*** File Size: 634MB
* DD image for 128GB eMMC Module
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_dd_20190807_stock_android_7.1_emmcboot-128GB.img.gz Direct download from pine64.org]
*** MD5 (GZip file): 16942B8F9EEE79B81FADDB09AF7E2E80
*** File Size: 700MB

=== Stock for RK Flash tool [eMMC Boot] [20190807] ===
* Please unzip first and then using [http://files.pine64.org/os/ROCK64/android/AndroidTool_Release_v2.63.zip Rockchip Android tool ver 2.63] to flash in
* The OTG port located at USB type-C connector, needs USB type A to type C cable.
* [http://wiki.pine64.org/index.php/NOOB#Flashing_to_eMMC_using_Rockchip_Tools_.28Rock64_Only.29 Guide to flashing eMMC using Rockchip Tools]
* Please allow 3-5 minutes boot up time on first time for initialization
** [http://files.pine64.org/os/PinebookPro/Android/PinebookPro_20190807_stock_android_7.1_emmcboot.img.gz Direct download from pine64.org]
** MD5 (GZip file): DC4C330787E57FC05F9D7D740F741620
** File Size: 555MB

= Linux Installer Releases =
== Debian Installer ==
[[File:debian.png|right|100px]]

=== Daniel Thompson's Debian Installer for the Pinebook Pro ===
* This is an image creator and Debian installer that runs from an existing Linux OS and installs Debian Bullseye
** Installer can configure an encrypted rootfs and provides a choice of desktops, including the default Debian desktop based on Gnome 3
** Strict adoption of upstream Debian packages (with exception of kernel and bootloaders) in order to provide a clean upgrade path as Bullseye matures
* Download at: https://github.com/daniel-thompson/pinebook-pro-debian-installer/
* Pull requests welcome but for discussion and support please use [https://forum.pine64.org/showthread.php?tid=8487 the forum topic].

For more information, see the [[Pinebook_Pro_Debian_Installer]] wiki page

=== Official Debian Installer Images ===
* Uses only the upstream kernel and firmware without special patches
* No graphical display yet, works only through serial console
* Requires adding the non-free component to your /etc/apt/sources.list file and installing the "firmware-linux" package for Wi-Fi and Bluetooth support
* Installer is loaded into RAM, can install onto the same media from which it’s booted
* Supports automatic partitioning and full disk encryption through LVM
* Installer currently doesn't install the bootloader, leaving the installed system in an unbootable state until it's manually added

[https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ The relevant files are built daily here] and may sometimes be unavailable if the build system is having issues. The "README.concatenateable_images" file provides instructions on how to combine the partition.img.gz file with the firmware.pinebook-pro.rk3399.img.gz file in order to create a DD-able image.

The official images are '''not''' recommended yet until the display begins working and the installer properly installs the bootloader. Most users will want to see [[Pinebook Pro Debian Installer|Daniel Thompson's Debian Installer]] instead.

== Gentoo Script ==
[[File:GentooLogo.png|right|100px]]

=== Gentoo Script for Pinebook Pro ===
* This is a script that prepares a Gentoo arm64 stage 3 tarball for the Pinebook Pro
** The script takes care of device specifics like an optimized make.conf, an overlay that provides kernel and firmware amongst others, and other miscellaneous fixes
* The usual tarball setup as per [https://wiki.gentoo.org/wiki/Handbook:AMD64 Gentoo Handbook] is left to the user.
* Forum thread with instructions at https://forum.pine64.org/showthread.php?tid=8765

==Kali Script==
[[File:Kali.jpeg|right|100px]]

=== Kali Linux for Pinebook Pro ===
* This is a script to create official Kali Linux OS images for the Pinebook Pro
** The script carries out the build process in entirety and is Pinebook Pro specific
* Please pull the latest [https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/pinebook-pro.sh Kali Linux install script] from the project's GitLab.
* For more information regarding building the OS image please read the README instruction at https://gitlab.com/kalilinux/build-scripts/kali-arm/blob/master/README.md

==K1ss OS Script==
[[File:K1ss.png|right|100px]]

=== K1ss Linux for Pinebook Pro ===
* This is a repository containing an unofficial port of KISS Linux to aarch64. The tarball is built for generic aarch64, currently being tested on the Pinebook Pro.
* Please pull the latest [https://github.com/jedavies-dev/kiss-aarch64 K1ss Linux install script] from the project's GitHub.
* * You can follow the ongoing discussion about K1ss Linux on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=9304)

==NixOS Script==
[[File:nixos.png|right|100px]]

=== NixOS for Pinebook Pro ===
* This is instructions to install NixOS on the Pinebook Pro: https://nixos.wiki/wiki/NixOS_on_ARM/PINE64_Pinebook_Pro
* Please pull the latest [https://github.com/samueldr/wip-pinebook-pro samueldr's repository ] from the project's GitHub.
* * You can follow the ongoing discussion about NixOS on the PINE64 forum (https://forum.pine64.org/showthread.php?tid=10524)

==SkiffOS for Pinebook Pro ==
[[File:SkiffOS-Icon-1.png|right|100px]]

=== SkiffOS Boot Image for Pinebook Pro ===
* Instructions to build/install on the Pinebook Pro: https://github.com/skiffos/SkiffOS/tree/master/configs/pine64/book
* Please pull the latest version from the project's GitHub.
* Compiling the boot image takes approximately 30 minutes.
* Easily configure the kernel, compiler, etc with Buildroot.
* Pre-built ISOs will be available with the upcoming 2021.02
release.

=== Skiff Core ===
* Supports multiple distros running simultaneously.
* Optionally build from scratch on device on first boot.
* Pre-built multi-arch core container images are available.

=== GentooLTO with KDE Apps ===

* GentooLTO with O3 optimized KDE Desktop configuration.
* Use <tt>SKIFF_CONFIG=pine64/book,core/pinebook_gentoo</tt>
* Default sign-in is username "core" w/ empty password.

[[Category:PineBook Pro]]

PineCube

2021-01-03T19:36:45Z

Cypherpunks: /* Streaming the camera to the network */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motion [microSD Boot] [20201222] ====
* Armbian Ubuntu Focal build for the Pinecube with the motion (detection) package preinstalled.
* There are 2 ways to interact with the OS:
** Scan for the the device IP (with hostname pinecube)
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER to login to the serial console, then check for assigned IP
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

[https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 GitHub gist] for the userpatch which pre-installs and configures the motion (detection) package.

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although [https://www.armbian.com/download/?device_support=No+official+support+(CSC) not officially supported] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian (login: root, password: 1234).

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10). See [https://github.com/ioerror/pinecube this small project for the pinecube] for easy to use programs tuned for the PineCube.

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.

It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

Note that the sender must specify the recipient's IP address in place of <code>$client_ip</code>; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see <code>gst-inspect-1.0 udpsrc</code> and <code>gst-inspect-1.0 udpsink</code> for details.)

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). Compared to HLS, it has the disadvantages that MJPEG requires more bandwidth than h264 for similar quality, pause and seek are not possible, stalled connections cannot jump ahead when they are unstalled, and, in the case of this primitive implementation, it only supports one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T03:12:33Z

Cypherpunks: /* gstreamer and socat: MJPEG HTTP server */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.

It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

Note that the sender must specify the recipient's IP address in place of <code>$client_ip</code>; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see <code>gst-inspect-1.0 udpsrc</code> and <code>gst-inspect-1.0 udpsink</code> for details.)

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). Compared to HLS, it has the disadvantages that MJPEG requires more bandwidth than h264 for similar quality, pause and seek are not possible, stalled connections cannot jump ahead when they are unstalled, and, in the case of this primitive implementation, it only supports one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:59:55Z

Cypherpunks: /* gstreamer: JPEG RTP TCP */ oops

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.

It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

Note that the sender must specify the recipient's IP address in place of <code>$client_ip</code>; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see <code>gst-inspect-1.0 udpsrc</code> and <code>gst-inspect-1.0 udpsink</code> for details.)

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:59:30Z

Cypherpunks: /* gstreamer: JPEG RTP UDP */ oops

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.

It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

Note that the sender must specify the recipient's IP address in place of <code>$client_ip</code>; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see <code>gst-inspect-1.0 udpsrc</code> and <code>gst-inspect-1.0 udpsink</code> for details.)

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:51:23Z

Cypherpunks: /* gstreamer: JPEG RTP UDP */ multicast hint

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.

It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

Note that the sender must specify the recipient's IP address in place of <code>$client_ip</code>; this can actually be a multicast address allowing for many receivers! (You'll need to specify a valid multicast address in the receivers' pipeline also; see <code>gst-inspect-1.0 udpsrc</code> and <code>gst-inspect-1.0 udpsink</code> for details.)

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:41:28Z

Cypherpunks: /* gstreamer: h264 HLS */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

To find out about other options you can configure in the <code>hlssink</code> gstreamer element, you can run <code>gst-inspect-1.0 hlssink</code>.

It is worth noting here that the <code>hlssink</code> element in GStreamer is not widely used in production environments. It is handy for testing, but for real-world free-software HLS live streaming deployments the standard tool today (January 2021) is nginx's RTMP module which can be used with ffmpeg to produce "adaptive streams" which are reencoded at varying quality levels. You can send data to an nginx-rtmp server from a gstreamer pipeline using the <code>rtmpsink</code> element. It is also worth noting that gstreamer has a new <code>hlssink2</code> element which we have not tested; perhaps in the future it will even have a webserver!

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:10:19Z

Cypherpunks: /* gstreamer: h264 RTSP */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h264 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:07:02Z

Cypherpunks: /* gstreamer: h264 HLS */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 encoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h24 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T02:05:03Z

Cypherpunks: /* gstreamer and socat: MJPEG HTTP server */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 decoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h24 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method uses bash, socat, and gstreamer to implement an HTTP-ish server which will serve your video as an MJPEG stream which is playable in browsers.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself, as it has a multipartmux element which produces the headers which precede each frame. But sadly, despite various forum posts lamenting the lack of one over the last 12+ years, as of the end of the 50th year of the UNIX era (aka 2020), somehow nobody has yet gotten a webserver element merged in to gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-03T01:59:27Z

Cypherpunks: ways of seeing video on the network

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

== Streaming the camera to the network ==

In this section we document a variety of ways to stream video to the network from the PineCube. Unless specified otherwise, all of these examples have been tested on Ubuntu groovy (20.10).

In the examples which use h264, we are currently encoding using the x264 library which is not very fast on this CPU. The SoC in the PineCube does have a hardware h264 encoder, which the authors of these examples have so far not tried to use. It appears that https://github.com/gtalusan/gst-plugin-cedar might provide easy access to it, however. Please update this wiki if you find out how to use the hardware encoder!

=== gstreamer: h264 HLS ===

HLS (HTTP Live Streaming) has the advantage that it is easy to play in any modern web browser, including Android and iPhone devices, and that it is easy to put an HTTP caching proxy in front of it to scale to many viewers. It has the disadvantages of adding (at minimum) several seconds of latency, and of requiring an h264 decoder (which we have in hardware, but haven't figured out how to use yet, so, we're stuck with the slow software one).

HLS segments a video stream into small chunks which are stored as .ts (MPEG Transport Stream) files, and (re)writes a playlist.m3u8 file which clients constantly refresh to discover which .ts files they should download. We use a tmpfs file system to avoid needing to write these files to the sdcard in the PineCube. Besides the program which writes the .ts and .m3u8 files (gst-launch-1.0, in our case), we'll also need a very basic web page in tmpfs and a webserver to serve the files.

Create an hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js]. We recommend downloading the hls.js file and editing the example index.html to serve your local copy of it instead of fetching it from a CDN. This file provides HLS playback capabilities in browsers which don't natively support it (which is most browsers aside from the iPhone).

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternately, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

You can also view the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>

Or with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code> (or with mpv, ffplay, etc)

=== v4l2rtspserver: h264 RTSP ===

Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== gstreamer: JPEG RTSP ===

GStreamer's RTSP server isn't an element you can use with gst-launch, but rather a library. We failed to build its example program, so instead used this very small 3rd party tool which is based on it: https://github.com/sfalexrog/gst-rtsp-launch/

After building gst-rtsp-launch (which is relatively simple on Ubuntu groovy; just <code>apt install libgstreamer1.0-dev libgstrtspserver-1.0-dev</code> first), you can read JPEG data directly from the camera and stream it via RTSP: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1280x720]' && gst-rtsp-launch 'v4l2src ! image/jpeg,width=1280,height=720 ! rtpjpegpay name=pay0'</code>

This stream can be played using <code>vlc rtsp://pinecube.local:8554/video</code> or mpv, ffmpeg, gst-play-1.0, etc. If you increase the resolution to 1920x1080, mpv and gst-play can still play it, but VLC will complain <code>The total received frame size exceeds the client's buffer size (2000000). 73602 bytes of trailing data will be dropped!</code> if you don't tell it to increase its buffer size with <code>--rtsp-frame-buffer-size=300000</code>.

=== gstreamer: h24 RTSP ===

Left as an exercise to the reader (please update the wiki). Hint: involves bits from the HLS and the JPEG RTSP examples above, but needs a <code>rtph264pay name=pay0</code> element.

=== gstreamer: JPEG RTP UDP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! udpsink host=$client_ip port=8000</code>

Receive with: <code>gst-launch-1.0 udpsrc port=8000 ! application/x-rtp, encoding-name=JPEG,payload=26 ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer: JPEG RTP TCP ===

Configure camera: <code>media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'</code>

Transmit with: <code>gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! rtpjpegpay name=pay0 pt=96 ! rtpstreampay ! tcpserversink host=0.0.0.0 port=1234</code>

Receive with: <code>gst-launch-1.0 tcpclientsrc host=pinecube.local port=1234 ! application/x-rtp-stream,encoding-name=JPEG ! rtpstreamdepay ! application/x-rtp, media=video, encoding-name=JPEG ! rtpjpegdepay ! jpegdec ! autovideosink</code>

=== gstreamer and socat: MJPEG HTTP server ===

This rather ridiculous method produces a small HTTP-ish server with socat and bash which will serve your video as an MJPEG stream which is playable in browsers. This means it is a multipart HTTP request which keeps on returning more parts, which with another JPEG in it.

This approach has the advantage of being relatively low latency (under a second), browser-compatible, and not needing to reencode anything on the CPU (it gets JPEG data from the camera itself). It has the disadvantage of only supporting one viewer at a time. (Though, really, the RTSP examples on this page perform very poorly with multiple viewers, so...)

Gstreamer can almost do this by itself; it has a multipartmux element which produces the headers which precede each frame. But, despite various forum posts lamenting the lack of one over the last 12+ years, somehow nobody has yet gotten the webserver part merged in gstreamer (which is necessary to produce the HTTP response, which is required for browsers other than firefox to play it). So, here is an absolutely minimal "webserver" which will get MJPEG displaying in a (single) browser.

Create a file called <code>mjpeg-response.sh</code>:
#!/bin/bash
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:JPEG_1X8/1920x1080]'
b="--duct_tape_boundary"
echo -en "HTTP/1.1 200 OK\r\nContent-type: multipart/x-mixed-replace;boundary=$b\r\n\r\n"
gst-launch-1.0 v4l2src ! image/jpeg,width=1920,height=1080 ! multipartmux boundary=$b ! fdsink fd=2 2>&1 >/dev/null

Make it executable: <code>chmod +x mjpeg-response.sh</code>

Run the server: <code>socat TCP-LISTEN:8080,reuseaddr,fork EXEC:./mjpeg-response.sh</code>

And browse to http://pinecube.local:8080/ in your browser.

== Debugging camera issues with the gstreamer pipeline ==

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-01T17:04:02Z

Cypherpunks: /* A simple RTSP server with HLS */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

==== Streaming the camera to the network ====

To stream to web browsers with HLS and x264 encoding, we'll use a tmpfs file system to not write any data to the sdcard in the PineCube. We'll also need a very basic web page in tmpfs, a program to write HLS data to the tmpfs, and finally a webserver to serve the files.

Create the hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js].

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternatively, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

View the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>
View the HLS stream with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code>

===== Debugging camera issues with the gstreamer pipeline =====

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

===== A simple RTSP server with HLS =====
Install dependencies and build required v4l2 software:

apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;

Running the camera:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== Stock Linux ===

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-01T17:02:10Z

Cypherpunks: /* A simple RTSP server with HLS */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

==== Streaming the camera to the network ====

To stream to web browsers with HLS and x264 encoding, we'll use a tmpfs file system to not write any data to the sdcard in the PineCube. We'll also need a very basic web page in tmpfs, a program to write HLS data to the tmpfs, and finally a webserver to serve the files.

Create the hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js].

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternatively, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

View the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>
View the HLS stream with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code>

===== Debugging camera issues with the gstreamer pipeline =====

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

===== A simple RTSP server with HLS =====
Install dependencies and build required v4l2 software:
<code>
apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;
git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;
</code>

Running the camera:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10
</code>

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== Stock Linux ===

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-01T17:01:21Z

Cypherpunks: /* A simple RTSP server with HLS */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

==== Streaming the camera to the network ====

To stream to web browsers with HLS and x264 encoding, we'll use a tmpfs file system to not write any data to the sdcard in the PineCube. We'll also need a very basic web page in tmpfs, a program to write HLS data to the tmpfs, and finally a webserver to serve the files.

Create the hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js].

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternatively, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

View the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>
View the HLS stream with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code>

===== Debugging camera issues with the gstreamer pipeline =====

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

===== A simple RTSP server with HLS =====
Install dependencies and build required v4l2 software:
<code>
apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev;
git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install;
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install;
</code>

Running the camera:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]';
modprobe v4l2loopback video_nr=10 debug=2;
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10 &
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10
</code>

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== Stock Linux ===

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-01T17:00:24Z

Cypherpunks: /* A simple RTSP server with HLS */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

==== Streaming the camera to the network ====

To stream to web browsers with HLS and x264 encoding, we'll use a tmpfs file system to not write any data to the sdcard in the PineCube. We'll also need a very basic web page in tmpfs, a program to write HLS data to the tmpfs, and finally a webserver to serve the files.

Create the hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js].

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternatively, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

View the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>
View the HLS stream with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code>

===== Debugging camera issues with the gstreamer pipeline =====

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

===== A simple RTSP server with HLS =====
Install dependencies and build required v4l2 software:
<code>
apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install
</code>

Running the camera:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]'
modprobe v4l2loopback video_nr=10 debug=2
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10
</code>

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== Stock Linux ===

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2021-01-01T17:00:00Z

Cypherpunks: /* Streaming the camera to the network */

{{note|1=PAGE UNDER CONSTRUCTION, INFO SUBJECT TO CHANGE}}

== Specifications ==
* '''Dimensions:''' 55mm x 51mm x 51.5mm
* '''Weight:''' 55g
* '''Storage:'''
** MicroSD slot, bootable
** 128Mb SPI Nor Flash, bootable
* '''Cameras:''' OV5640, 5Mpx
* '''CPU:''' Allwinner(Sochip) ARM Cortex-A7 MPCore, 800MHz
* '''RAM:''' 128MB DDR3
* '''I/O:'''
** 10/100Mbps Ethernet with passive PoE
** USB 2.0 A host
** 26 pins GPIO port
*** 2x 3.3V Ouptut
*** 2x 5V Output
*** 1x I2C
*** 2x UART
*** 2x PWM
*** 1x SPI
*** 1x eMMC/SDIO/SD (8-bit)
*** 6x Interrupts
*** '''Note: Interfaces are multiplexed, so they can't be all used at same time'''
** Internal microphone
* '''Network:'''
** WiFi
* '''Screen:''' optional 4.5" RGB LCD screen
* '''Misc. features:'''
** Volume and home buttons
** Speakers and Microphone
* '''Power DC in:'''
** 5V 1A from MicroUSB Port or GPIO port
** 4V-18V from Ethernet passive PoE
* '''Battery:''' optional 950-1600mAh model: 903048 Lithium Polymer Ion Battery Pack, can be purchase at [https://www.amazon.com/AKZYTUE-1200mAh-Battery-Rechargeable-Connector/dp/B07TWHHCNK/ Amazon.com]

== PineCube board information, schematics and certifications ==
* PineCube mainboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20MainBoard%20Schematic%20ver%201.0-20200727.pdf PineCube mainboard Released Schematic ver 1.0]
* PineCube faceboard schematic:
** [https://files.pine64.org/doc/PineCube/PineCube%20FaceBoard%20Schematic%20ver%201.0-20200727.pdf PineCube faceboard Released Schematic ver 1.0]
* PineCube certifications:
** [https://files.pine64.org/doc/cert/PineCube-FCC-SDOC%20certification%20S20072502302001.pdf PineCube FCC Certificate]
** [https://files.pine64.org/doc/cert/PineCube-CE-EMC%20certification%20S20072502301001.pdf PineCube CE RED Certificate]
** [https://files.pine64.org/doc/cert/PineCube-ROHS%20Test%20Report.pdf PineCube ROHS Test Report]

== Datasheets for components and peripherals ==
* Allwinner (Sochip) S3 SoC information:
** [https://files.pine64.org/doc/datasheet/pinecube/S3_Datasheet_V1.1-20180123.pdf Sochip S3 SoC Data Sheet V1.1]

* X-Powers AXP209 PMU (Power Management Unit) information:
** [https://files.pine64.org/doc/datasheet/pinecube/AXP209_Datasheet_v1.0en.pdf AXP209 PMIC datasheet]

* CMOS camera module information:
** [https://files.pine64.org/doc/datasheet/pinecube/CH-5A-DV-V2.0%20Specification.pdf PineCube Camera Module Specification]
** [https://files.pine64.org/doc/datasheet/pinephone/OV5640_datasheet.pdf OV5640 5MP CMOS Image Sensor SoC datasheet]

* LCD touch screen panel information:

* Lithium battery information:

* WiFi/BT module information:
** [https://files.pine64.org/doc/datasheet/pinecube/rtl8189es.pdf RTL8189ES specification]

* GPIO Header Pinout: ([[:File:PineCube_GPIO.pdf|PDF]], [https://pine64.gami.ee/pinecube/gpio-pinout.html HTML])
[[File:PineCube_GPIO_Pinout.png|700px]]

* Case information:
** [https://files.pine64.org/doc/PineCube/PineCube%20Case%203D.zip PinePhone 3D file]

[[File:PineCube_Case-1.jpg|400px]] [[File:PineCube_Case-2.jpg|400px]]

== Operating Systems ==

=== Mainlining Efforts ===

Please note:

* this list is most likely not complete
* no review of functionality is done here, it only serves as a collection of efforts

{| class="wikitable"
!colspan="3"|Linux kernel
|-
| Type
| Link
| Available in version
|-
| Devicetree Entry Pinecube
| https://lkml.org/lkml/2020/9/22/1241
| 5.10
|-
| Correction for AXP209 driver
| https://lkml.org/lkml/2020/9/22/1243
| 5.9
|-
| Additional Fixes for AXP209 driver
| https://lore.kernel.org/lkml/20201031182137.1879521-8-contact@paulk.fr/
| tdb (5.11?)
|-
| Device Tree Fixes
| https://lore.kernel.org/lkml/20201003234842.1121077-1-icenowy@aosc.io/
| 5.10
|-
!colspan="3"|U-boot
|-
| Type
| Link
| Available in version
|-
| PineCube Board Support
| https://patchwork.ozlabs.org/project/uboot/list/?series=210044
| expected in v2021.01
|-
!colspan="3"|Buildroot
|-
| No known mainlining efforts yet
|
|
|}

=== NixOS ===

* [https://github.com/danielfullmer/pinecube-nixos danielfullmer's Github]

=== Buildroot ===
[https://elimo.io Elimo Engineering] integrated support for the PineCube into Buildroot.

This has not been merged into upstream Buildroot yet, but you can find the repo on [https://github.com/elimo-engineering/buildroot Elimo's GitHub account] and build instructions in the [https://github.com/elimo-engineering/buildroot/tree/pine64/pinecube/board/pine64/pinecube board support directory] readme.
The most important thing that this provides is support for the S3's DDR3 in u-boot. Unfortunately mainline u-boot does not have that yet, but the u-boot patches from [https://github.com/danielfullmer/pinecube-nixos Daniel Fullmer's NixOS repo] were easy enough to use on buildroot.
This should get you a functional system that boots to a console on UART0. It's pretty fast too, getting there in 1.5 seconds from u-boot to login prompt.

=== Armbian ===

The only Armbian release with support for Ethernet and the camera module is the Ubuntu Groovy release. The Ubuntu Groovy release is an experimental, automatically generated release and it appears to support additional hardware from the other Armbian releases.

==== Armbian Build Image with motionEye [microSD Boot] [20201222] ====
* motionEyeOS is a Linux distribution that turns a single-board computer into a video surveillance system. The OS is based on BuildRoot and uses motion as a backend and motionEye for the frontend
* There are 2 ways to interact with the OS:
** Scan for its IP with hostname pinecube
** Use the PINE64 USB SERIAL CONSOLE/PROGRAMMER and login, then check for assigned IP
** [https://gist.github.com/Icenowy/ff68f6e4ba8231380d3a295226e63fb3 Github link]
* DD image (for 8GB micoSD card and above)
** [https://files.pine64.org//os/PineCube/armbian/Armbian_21.02.0-trunk_Pinecube_focal_dev_5.10.0.img.xz Direct download from pine64.org]
*** MD5 (XZip file): 61e5a6d3ab0f74ce8367c97b7f8cbb7b
*** File Size: 328MGB

Armbian Builds for PineCube are [https://www.armbian.com/pinecube/ available for download], once again thanks to [https://github.com/armbian/build/pull/2364/files the work] of Icenowy Zheng.
Although not officially supported ([https://www.armbian.com/download/?device_support=No+official+support+(CSC) CSC Status] it enables the usage of Debian and Ubuntu.

A serial console can be established with 152008N1 (no hardware flow control). Login credentials are as usual in Armbian login: root password: 1234.

==== Example with screen and the woodpecker USB serial device ====

First connect the woodpecker USB serial device to the PineCube. Pin 1 on the PineCube has a small white dot on the PCB - this should be directly next to the microusb power connection. Attach the GND pin on the woodpecker to pin 6 (GND) on the PineCube, TXD from the woodpecker to pin 10 (UART_RXD) on the PineCube, and RXD from the woodpecker to pin 8 (UART_TXD) on the PineCube.

On the host system which has the woodpecker USB serial device attached, it is possible to run screen and to communicate directly with the PineCube:

<code>screen /dev/ttyUSB0 115200</code>

==== Basic bandwidth tests with iperf3 ====

Install armbian-config:
<code>apt install armbian-config</code>

Enable iperf3 through the menu in armbian-config:
<code>armbian-config</code>

On a test computer on the same network segment run iperf3 as a client:
<code>iperf3 -c pinecube -t 60</code>

The same test computer, run iperf3 in the reverse direction:
<code>iperf3 -c pinecube -t 60 -R</code>

===== Performance results =====
The Ethernet network does not work in the current Ubuntu Focal armbian image. The Ethernet network does work in the Ubuntu Groovy armbian image.

====== Wireless network performance ======
The performance results reflect using the wireless network. The link speed was 72.2Mb/s using 2.462Ghz wireless. Running sixty second iperf3 tests: the observed throughput varies between 28-50Mb/s to a host on the same network segment. The testing host is connected to an Ethernet switch which is also connected to a wireless bridge. The wireless network uses WPA2 and the PineCube is connected to this wireless network bridge.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 293 MBytes 41.0 Mbits/sec 1 sender
[ 5] 0.00-60.01 sec 291 MBytes 40.7 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.85 sec 263 MBytes 36.2 Mbits/sec 3 sender
[ 5] 0.00-60.00 sec 259 MBytes 36.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 230 MBytes 32.1 Mbits/sec 0 sender
[ 5] 0.00-60.09 sec 229 MBytes 32.0 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.14 sec 246 MBytes 34.3 Mbits/sec 7 sender
[ 5] 0.00-60.00 sec 245 MBytes 34.2 Mbits/sec receiver

====== Wired network performance ======

The performance results reflect using the Ethernet network. The link speed was 100Mb/s using a 1000Mb/s prosumer switch. Running sixty second iperf3 tests: the observed throughput varies between 92-102Mb/s to a host on the same network segment. The testing host is connected to the same Ethernet switch which is also connected to the PineCube.

Client rate for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 675 MBytes 94.4 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 673 MBytes 94.0 Mbits/sec receiver

Client rate with -R for sixty seconds:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 673 MBytes 94.1 Mbits/sec receiver

Using WireGuard to protect the traffic between the PineCube and the test system, the performance characteristics change only slightly.

Client rate for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.00 sec 510 MBytes 71.2 Mbits/sec 0 sender
[ 5] 0.00-60.01 sec 509 MBytes 71.1 Mbits/sec receiver

Client rate with -R for sixty seconds with WireGuard:

[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-60.01 sec 642 MBytes 89.8 Mbits/sec 0 sender
[ 5] 0.00-60.00 sec 641 MBytes 89.7 Mbits/sec receiver

==== Streaming the camera to the network ====

To stream to web browsers with HLS and x264 encoding, we'll use a tmpfs file system to not write any data to the sdcard in the PineCube. We'll also need a very basic web page in tmpfs, a program to write HLS data to the tmpfs, and finally a webserver to serve the files.

Create the hls directory to be shared in the existing tmpfs file system that is mounted at /dev/shm:

<code>mkdir /dev/shm/hls/</code>

Create an index.html and optionally a favicon.ico or even a set of icons, and then put the files into the /dev/shm/hls directory. An example index.html that works is available in the Getting Started section of the [https://github.com/video-dev/hls.js/#getting-started README] for [https://github.com/video-dev/hls.js/ hls.js].

In one terminal, run the camera capture pipeline:
<code>
cd /dev/shm/hls/ &&
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/240x320@1/15]' &&
gst-launch-1.0 v4l2src ! video/x-raw,width=320,height=240,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

Alternatively it is possible to capture at a higher resolution:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080@1/15]'
cd /dev/shm/hls/ && gst-launch-1.0 v4l2src ! video/x-raw,width=1920,height=1080,format=UYVY,framerate=15/1 ! decodebin ! videoconvert ! video/x-raw,format=I420 ! clockoverlay ! timeoverlay valignment=bottom ! x264enc speed-preset=ultrafast tune=zerolatency ! mpegtsmux ! hlssink target-duration=1 playlist-length=2 max-files=3
</code>

In another, run a simple single threaded webserver which will serve html, javascript, and HLS to web clients:
<code>
cd /dev/shm/hls/ && python3 -m http.server
</code>

Alternatively, install a more efficient web server (<code>apt install nginx</code>) and set the server root for the default configuration to be /dev/shm/hls. This will run on port 80 rather than the python3 server which defaults to port 8000.

It should be possible to view the HLS stream directly in a web browser by visiting [http://pinecube:8000/ http://pinecube:8000/] if pinecube is the correct hostname and the name correctly resolves.

View the HLS stream with VLC: <code>vlc http://pinecube:8000/playlist.m3u8</code>
View the HLS stream with gst-play-1.0: <code>gst-play-1.0 http://pinecube:8000/playlist.m3u8</code>

===== Debugging camera issues with the gstreamer pipeline =====

If the camera does not appear to work, it is possible to change the <code>v4l2src</code> to <code>videotestsrc</code> and the gstreamer pipeline will produce a synthetic test image without using the camera hardware.

If the camera is only sensor noise lines over a black or white image, the camera may be in a broken state. When in that state, the following kernel messages were observed:
<pre>
[ 1703.577304] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.578570] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.596924] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.598060] alloc_contig_range: [46400, 467f5) PFNs busy
[ 1703.600480] alloc_contig_range: [46400, 468f5) PFNs busy
[ 1703.601654] alloc_contig_range: [46600, 469f5) PFNs busy
[ 1703.619165] alloc_contig_range: [46100, 464f5) PFNs busy
[ 1703.619528] alloc_contig_range: [46200, 465f5) PFNs busy
[ 1703.619857] alloc_contig_range: [46300, 466f5) PFNs busy
[ 1703.641156] alloc_contig_range: [46100, 464f5) PFNs busy
</pre>

===== A simple RTSP server with HLS =====
Install dependencies and build required v4l2 software:
<code>
apt install -y gstreamer1.0-plugins-bad gstreamer1.0-tools \
gstreamer1.0-plugins-good v4l-utils gstreamer1.0-alsa alsa-utils libpango1.0-0 \
libpango1.0-dev gstreamer1.0-plugins-base gstreamer1.0-x x264 \
gstreamer1.0-plugins-{good,bad,ugly} liblivemedia-dev liblog4cpp5-dev \
libasound2-dev vlc libssl-dev iotop libasound2-dev liblog4cpp5-dev \
liblivemedia-dev autoconf automake libtool v4l2loopback-dkms liblog4cpp5-dev \
libvpx-dev libx264-dev libjpeg-dev libx265-dev

git clone --recursive https://github.com/mpromonet/v4l2tools && cd v4l2tools && make && make install
git clone --recursive https://github.com/mpromonet/v4l2rtspserver && cd v4l2rtspserver && cmake -D LIVE555URL=https://download.videolan.org/pub/contrib/live555/live.2020.08.19.tar.gz . && make && make install
</code>

Running the camera:
<code>
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]'
modprobe v4l2loopback video_nr=10 debug=2
v4l2compress -fH264 -w -vv /dev/video0 /dev/video10
v4l2rtspserver -v -S -W 640 -H 480 -F 10 -b /usr/local/share/v4l2rtspserver/ /dev/video10
</code>

The v4l2compress/v4l2rtspserver method of streaming the camera uses around ~45-50% of the CPU for compression of the stream into H264 (640x480@7fps) and around 1-2% of the CPU for serving the HLS stream. Total system RAM used is roughly 64MB and the load average is ~0.4-~0.5 when idle, and ~0.51-~0.60 with one HLS client streaming the camera.

=== Stock Linux ===

== SDK ==

==== Stock Linux ====
* [https://files.pine64.org/SDK/PineCube/PineCube%20Stock%20BSP-SDK%20ver1.0.7z Direct Download from pine64.org]
** MD5 (7zip file): efac108dc98efa0a1f5e77660ba375f8
** File Size: 3.50GB
===== How to compile =====

You can either setup a machine for the build environment, or use a Vagrant virtual machine provided by [https://elimo.io Elimo Engineering]

====== On a dedicated machine ======

Recommended system requirements:
* OS: (L)Ubuntu 16.04
* CPU: 64-bit based
* Memory: 8 GB or higher
* Disk: 15 GB free hard disk space

'''Install required packages'''
<pre>
sudo apt-get install p7zip-full git make u-boot-tools libxml2-utils bison build-essential gcc-arm-linux-gnueabi g++-arm-linux-gnueabi zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32z1-dev
</pre>
'''Install older Make 3.82 and Java JDK 6'''
<pre>
pushd /tmp
wget https://ftp.gnu.org/gnu/make/make-3.82.tar.gz
tar xfv make-3.82.tar.gz
cd make-3.82
./configure
make
sudo apt purge -y make
sudo ./make install
cd ..
# Please, download jdk-6u45-linux-x64.bin from https://www.oracle.com/java/technologies/javase-java-archive-javase6-downloads.html (requires free login)
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
sudo mkdir /opt/java/
sudo mv jdk1.6.0_45/ /opt/java/
sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_45/bin/java 1
sudo update-alternatives --install /usr/bin/javaws javaws /opt/java/jdk1.6.0_45/bin/javaws 1
sudo update-alternatives --config javac
sudo update-alternatives --config java
sudo update-alternatives --config javaws
popd
</pre>
'''Unpack SDK and then compile and pack the image'''
<pre>
7z x 'PineCube Stock BSP-SDK ver1.0.7z'
mv 'PineCube Stock BSP-SDK ver1.0' pinecube-sdk
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

====== Using Vagrant ======

You can avoid setting up your machine and just use Vagrant to spin up a development environment in a VM.

Just clone the [https://github.com/elimo-engineering/pinecube-sdk-vagrant Elimo Engineering repo] and follow the instructions in the [https://github.com/elimo-engineering/pinecube-sdk-vagrant/blob/main/README.md readme file]

After spinning up the VM, you just need to run the build:
<pre>
cd pinecube-sdk/camdroid
source build/envsetup.sh
lunch
mklichee
make -j3
pack
</pre>

== Community Projects ==

Share your project with a PineCube here!

[[Category:PineCube]] [[Category:Allwinner(Sochip) S3]]

PineCube

2020-12-30T19:06:31Z

Cypherpunks: /* Wired network performance */

PineCube

2020-12-30T18:58:52Z

Cypherpunks: /* Wired network performance */

PineCube

2020-12-30T17:58:01Z

Cypherpunks: /* Performance results */

PineCube

2020-12-30T17:44:39Z

Cypherpunks: /* Armbian */

PineCube

2020-12-20T17:43:30Z

Cypherpunks: /* Streaming the camera to the network */ add nginx note

PineCube

2020-12-20T17:25:25Z

Cypherpunks: /* Streaming the camera to the network */ add 1920x1080 example

PineCube

2020-12-20T17:15:10Z

Cypherpunks: /* Streaming the camera to the network */

PineCube

2020-12-20T17:11:06Z

Cypherpunks: /* Streaming the camera to the network */ add note about using gst-play

PineCube

2020-12-20T17:00:12Z

Cypherpunks: /* Armbian */ Add example gstreamer pipeline and simple http web server with python3 to stream HLS

PineCube

2020-12-20T16:10:12Z

Cypherpunks: /* Armbian */ add iperf3 tests: with and without WireGuard

PineCube

2020-12-20T15:14:15Z

Cypherpunks: Add instructions for using screen to communicate with the PineCube with the woodpecker usb serial device