nanopct3plus
By Igor Pečovnik / Desktop • General purpose / 0 Comments

Nanopc T3+

  • You need to hold boot key and power/reset the device to force boot from SD card,
  • Shutdown doesn’t work properly. It reboots the board.
  • Devices, which memory number begins with SEC710 K4B4G16, need to do.:
  • https://forum.armbian.com/topic/7274-nanopc-t3-boot-troubles/page/3/?tab=comments#comment-83688
Pinebook A64
By Test Test / Desktop / 0 Comments

Pinebook A64

  • Supported 720 and 1080p model,
  • DVFS, battery and brightness control,
  • MALI with opensource Lima drivers,
  • Chromium web-dl enabled,
  • not enabled or not tested: suspend/resume
TinkerBoard
By jock jock / General purpose • Desktop / 0 Comments

Tinkerboard / S

  • Severe powering troubles due to Micro USB power connector. It’s recommended to power through GPIO pins to prevent under-voltage issues (instabilities, boot/crash cycles). Powering situation is a little improved/masked on model S.
  • serial console is enabled on UART2 (pin 32, 33, 34=gnd)
  • eMMC flashing (model Tinkerboard S with eMMC) can be done the same way as burning an SD card. Connect your board with USB cable to your computer (Linux or Windows) and eMMC will be seen as a new hard drive. Burn an image to this drive. Wait until it's done, detach from computer and power with your normal PSU.
  • booting from SD card on S model is possible in Maskrom mode.

Debian Bookworm 24.8.1 minimal testing:

  • Boot ok, from sdcard and eMMC
  • HDMI is ok
  • USB2 ports are ok
  • Gigabit Etherner is ok, troughput ~940Mbit/s
  • Wireless ok, (stable but slow, ~5Mbps/s but router is far away as well)
  • Analog audio codec does not work
  • Reboot and shutdown work as intended

Ubuntu Noble 24.8.1 XFCE testing:

  • Boot ok from sdcard and eMMC
  • HDMI is ok
  • USB2 ports are ok
  • Gigabit ethernet ok
  • Wireless ok, inglorius performances as Debian
  • Bluetooth works
  • Analog audio codec work
  • Reboot and shutdown work as intended
odroidxu4
By Joe Khoobyar / Desktop • General purpose / 0 Comments

Odroid XU4 / HCx

For HC1 and HC2 we provide specially optimized config which has to be applied manually. This results in shorter boot time and lower consumption. Edit /boot/armbianEnv.txt and add:

board_name=xu4 # or xu3, xu3, hc1

Overlay management via armbian-config is not supported. You need to edit /boot/boot.ini and add overlays manually. Look for a line:
setenv overlays "i2c0 i2c1 hktft-cs-ogst"

Here you add what you need. More you can find in /boot/dtb/ or /boot/dtb/overlays

Make sure to adjust path in

ext4load mmc 0:1 0x60000000 /boot/dtb/overlays/${overlay}.dtbo

accordingly.