Edit page

STAR64 full documentation


The STAR64

The Star64 is a RISC-V based Single Board Computer powered by StarFive JH7110 Quad-Core SiFive U74 64-Bit CPU, Imagination Technology BX-4-32 GPU and supports up to 8GB 1866MHz LPDDR4 memory. It provides an eMMC module socket, MicroSD Card slot, PCI-e, Pi-2 Bus, USB 3.0, and many other peripheral interfaces for makers to integrate with sensors and other devices.


Software

The releases are still in alpha state and are only fit for testing purposes.

Apache NuttX RTOS

Apache NuttX RTOS

Armbian

STAR64 on armbian.com. Read the Armbian forum thread on forum.pine64.org.

DietPi

Star64 image on dietpi.com, with Linux 6.1 based on StarFive VisionFive 2 kernel sources, rebased on latest mainline kernel, with Star64 support from Fishwaldo’s kernel sources and own configuration. The kernel sources can be found on the DietPi Star64 repository on GitHub.com.

Download:

Fishwaldo images

A Set of Images built with Yocto for commandline, weston and plasma, see the project on GitHub.com.

Notes:

  • Where possible, GPU/VPU acceleration is enabled.

NixOS

NixOS, based on the the nixos-hardware configuration


Board features

Video

  • Digital Video output up to 4K@30Hz
  • 4K HDR @ 60fps
  • H.264/AVC Base/Main/High/High10 profile @ level 5.1; up to 4K×2K @ 60fps
  • H.265/HEVC Main/Main10 profile @ level 5.1 High-tier; up to 4K×2K @ 60fps

Audio

  • 3.5mm audio Jack

Network

  • Single or Dual 10/100/1000Mbps Ethernet
  • 2.4GHz/5Ghz MIMO WiFi 802.11 b/g/n/ac with Bluetooth 5.2

Storage

  • on-board 128Mbit (16MByte) XSPI NOR flash memory - bootable
  • microSD - bootable, supports SDHC and SDXC and storage up to 256GB
  • eMMC - bootable (optional eMMC Module)
  • 1× USB3.0 Dedicated Host port
  • 3× USB2.0 Host port

Expansion Ports

  • PCIe 2.0 ×1 lane
  • 2×20 pins “Pi2” GPIO Header
    • The JH7110 SoC supports full multiplexing of its GPIO pins. This means any non-power/ground pin can be configured to any function outlined in Table 4-2 of the SoC datasheet.
  • 4 lane MiPi DSI port for LCD panel
  • 4 lane MiPi CSI port for camera module

Development

Bringup notes

  • The USB over-current protection is not wired up correctly to the USB ports on Star64. The default Starfive Kernel will disable USB on boot as it belives the ports are overcurrent. This ugly hack works around it: https://github.com/Fishwaldo/Star64_linux/commit/2634a13ecfa1fa5c232ec2b9f6a6b6b0d9d66898
  • The Wifi Chip (RTL8852BU) is not supported in the kernel. There is a Vendor Driver that is imported in the kernel at https://github.com/Fishwaldo/Star64_linux/tree/Star64_devel/drivers/staging/rtl8852bu but it really needs a cleanup. It does BUG_ON at boot, but wifi is confirmed working.
  • HDMI can be finicky. 4K Monitors are known to have a issue. This is also relevant for VisionFive2
  • Some kernels/distributions do not detect the total memory correctly. This is due to the way u-boot is configured. Currently, u-boot reads the memory from the eeprom on the Star64, and updates the dtb file before booting the kernel. Distributions that boot differently may not get the updated dtb file with the correct memory entry. You can work around this by recompiling the DTB with the correct memory for your board
  • VisionFive2 Kernels will only offer limited functionality on the Star64 - Mainly USB, Wifi and PCI will not work.
  • The 4-pin 12 volt JST-XH-4A connector found on the Star64 is incompatible with the dual SATA power adapter intended for the ROCKPro64. The connector on the Star64 is rotated 180 degrees to the one on the ROCKPro64, resulting in the cable receiving +12V where GND is expected and vice versa. The cable’s internal circuitry ends up shorting in this configuration.
  • Booting from uSD: Component S1804 is adjacent to the 40pin GPIO Bus; ignore the printed text on S1804 that says “ON” or “ONKE”. Do pay attention to the ‘1’ and ‘2’ printed on S1804. Also pay attention to the ‘L’ and ‘H’ text on the board next to S1804. The ‘L’ stand for ‘0’ and the ‘H’ stands for ‘1’. You will need to flip switch ‘1’ (GPIO_1) on S1804 to the ‘L’ position and switch ‘2’ (GPIO_0) on S1804 to the ‘H’ position. S1804 maps to the table next to S1804 that has text [ [GPIO_1 | GPIO_0], [0|0] Flash, [0|1] SD, [1|0] EMMC, [1|1] UART ]; Helpful links: https://mrrcode979.github.io/blog/post/star64-guide/, https://www.bortzmeyer.org/star64-first-boot.html
  • TTL use notes: Ground is on pin 6, RXD is on pin 8, and TXD is on pin 10.

Prototype Bringup Notes

note

This section is relevant to the original prototype (v1.0) that a few developers received.

  • The schematic has several discrepancies with actual board labels.

  • The serial console can be found with TXD on pin 8 and RXD on pin 10; a convention common to Pi-style boards. Use the 40pin header pinouts in color on page one and not the schematic prose.

  • If you have only a single core running and no PCI card present, it appears to power up via the +5V/GND lines from the USB serial adapter pins.

  • It will not boot from a VisionFive R1 uSD card.

  • The boot device switch labels and the silk screen are inverted. “0” means “On”.

  • 2021.10-00001-gdbdaad919b will attempt to boot from SPI, but it appears blank. If you let it for many minutes, the device will eventually time out and boot OpenSBI v1.0 from (SPI?). This will fail, but only after self-identifying as a VisionFive R2, complete with five cores and 4 GB of RAM, before failing. A “press any key” timeout is offered, but I’ve been unable to make it stop. It will eventually crash with:

    Loading Environment from SPIFlash... SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

Not a StarFive EEPROM data format - magic error

Potential issues

If you get the following error in U-Boot (or your 8 GB board is only detected as 4 GB) the possible cause is an empty or corrupted EEPROM:

Not a StarFive EEPROM data format - magic error
EEPROM dump: (0x100 bytes)
00: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

To address this, execute the following commands from within U-Boot:

mac initialize
mac product_id <PRODUCTID>
mac write_eeprom

Set ProductID to either:

  • For 8 GB Models: STAR64V1-2310-D008E000-01234567
  • for 4 GB Models: STAR64V1-2310-D004E000-01234567

You can replace the last 8 digits with a random number if you wish.

If these commands fail, please join the #star64 channel in the Pine64 community for more assistance.


LEDs

The LEDs can be configured to stop blinking. Under Linux this can be done using the following command (as root):

echo “default-on” > /sys/devices/platform/leds/leds/blue-led/trigger

To list possible other triggers for the blue LED:

cat /sys/devices/platform/leds/leds/blue-led/trigger

An example for a trigger is activity, where the the blue LED reflects the CPU activity.


Further information

Datasheets

Star64 JH7110 SoC information:

X-Power PMU information:

LPDDR4 (200 Balls) SDRAM:

eMMC information:

SPI NOR Flash information:

Ethernet related info:

  • TBA

WiFi/BT module info:

Schematics and certifications

Model “A” Baseboard Dimensions: 133mm×80mm×19mm

Input Power: DC 12V @ 3A 5.5mmOD/2.1mm ID center-positive Barrel DC Jack connector

Schematic:

Certifications:

  • Disclaimer: Please note that PINE64 SBC is not a “final” product and in general certification is not necessary. However, PINE64 still submits the SBC for FCC, CE, and ROHS certifications and obtain the certificates to prove that the SBC board can pass the testing. Please note, a final commercial product needs to perform its own testing and obtain its own certificate.
  • Not yet available

Specification

CPU Architecture

  • Quad-core U74 up to 1.5GHz CPU
  • Fully compliant with the RISC-V ISA specification
  • 64-bit RISC-V Application Core
  • 32KB L1 I-cache with ECC
  • 32KB L1 D-cache with ECC
  • 8 Region Physical Memory Protection
  • Virtual Memory support with up to 47 Physical Address bits
  • Integrated up to 2MB L2 Cache with ECC
  • includes RV64IMAC S7 monitor core, 16 KB L1 I-Cache with ECC, 8 KB DTIM with ECC
  • 32-bit RISC-V CPU core (E24) for real time control, support RV32IMFC RISC-V ISA

GPU Architecture

  • Imagination Technology BXE-4-32 up to 600Mhz GPU
  • Support OpenCL 3.0
  • Support OpenGL ES 3.2
  • Support Vulkan 1.2
  • Tile-based deferred rendering architecture for 3D graphics workloads, with concurrent processing of multiple tiles
  • Support for GPU visualization, up to 8 virtual GPUs
  • On fly frame buffer compression and decompression (TFBC) algorithm
  • Performance: 128 FP32 FLOPs/Clock, 256 FP16 FLOPs/Clock

System Memory

  • LPDDR4 RAM Memory Variants: 2GB, 4GB and 8GB.