gounthar

Hello
 
Did anyone have success with connecting an ili9486 to an orangepi zero 3 or another SBC?
 
I read that starting with linux 5.4, we need to change the reset pin polarity to 1, as show in https://github.com/swkim01/waveshare-dtoverlays/issues/24
 
I just got this LCD https://www.aliexpress.us/item/3256803856059047.html
 
It is the bigger borther of the ili9341 which I already have working according to: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204672
 
 
The interesting thing is: when I use the ili9341 dtbo with the ili9486, I see a fraction of the X11 desktop, in the left 15% of the LCD screen... so at least I know that the connections and lowest level protocol is working.
 
However, when I try changing the compatible to ilitek,ili9486, with all the settings the same (except for rotation->rotate), I stay with a white screen.
 
actually, some other Aliexpress buyer says that my LCD is ili9488… so everyone needs to check their actual lcd controller. I need to recompile Armbian tomorrow
 
It appears that ili9488 is a clone of st7796s, which has this example DTS https://github.com/Sergey1560/fb_st7796s/blob/master/dts/sun50i-h6-st7796s.dts
 
It also appears that having the correct init bytes is critical. Here's another reference: https://forum.allaboutcircuits.com/threads/configuration-of-lcd-with-linux.145849/

The problem behind their promotion statement is that its a scam. Dietpi is bloated with proprietary scripts and they are removing packages that are dependencies for everything ... so it makes no sense at the end, just first installation of anything takes longer. But they can claim images has few MB less ... which is "better" and most of end users have no ability / interest to understand they have been conned.
https://docs.armbian.com/#comparison
Damages they create to open source, by playing dirty, that is beyond commenting.
 
 
This should also work OOB then
https://www.armbian.com/uefi-riscv64/
and you don't need to remove anything (from minimal Bookworm OS image, which is significantly lighter then Dietpi).
 
If you / anyone can confirm they are working well, we can move this to Supported section.

Hi there,
 
I revived my BananaPi M1 (ARM7 32bit) last week. I installed a fresh armbian and just docker like this:
 
sudo apt-get update sudo apt-get install ca-certificates curl sudo install -m 0755 -d /etc/apt/keyrings sudo curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc sudo chmod a+r /etc/apt/keyrings/docker.asc echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian \ $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin sudo gpasswd -a $USER docker newgrp docker docker run hello-world  
The "Hello world" worked.
 
But when I tried to run anything useful things failed. Seafile installed okay, but calling the UI timed out. Paperless-ngx complained that paperless-webserver cannot find route to redis. Stuff like this. I just want to use the machine in my internal Network at home.
 
To investigate further I installed a simple httpd docker to see if I can reach that one. No luck. Neither from another machine in my LAN, nor via lynx  on BananaPi calling localhost. The request goes out as the port seems to be open, but it never reaches the daemon inside the container or cannot respond. Same commands on my "production box" (a HP t630 with debian bookworm) work fine.
 
So my conclusion is that it must be something in the OS.
 
I compared iptables on BananaPi and t630 and checked the output of 'sudo /usr/sbin/sysctl -a | grep forwarding | grep ipv4' - they are the same.
 
I'm a little bit clueless where to check, what commands to use as I'm quite new to docker. Do you have any suggestions?
 
Thanks, Peter.

I'm happy to see the support for this board is progressing. 🤗

@tiziano000, where did you find an adapter to connect to the GPIO pins?
I have an SPI screen that I can't connect for the time being because of the strange (to me) spacing of the GPIO pins. 🤷‍♂️

I'm using overlay meson-g12a-radxa-zero-i2c-ee-m1-gpiox-10-gpiox-11.dtbo
sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Overlay meson-g12a-radxa-zero-i2c-ee-m3-gpioa-14-gpioa-15.dtbo works for me as well.
 

Hi all.
Has anyone managed to get the gpio pins working? I'm trying to use gps as timesource for my pi.
I tried connecting the GPS to UART5 (pins 3 and 5) and using pin 12 as a PPS input.
However, I saw that the serial ports are deactivated by default; how can I activate uart5?
then I tried with a serial-usb converter to test the functioning of the pps pin, but without success despite it being correctly configured from gpioinfo. 
 
gpiochip3 - 32 lines: line 21: unnamed "pps-gpio0" input active-high [used]
any suggestions?

Thanks in advance

Raspberry Pi OS started to secretly (!?) adding Microsoft proprietary package base, access to their servers, by default. 
 
Security consequences? tl;dr; ... Microsoft gained root access to millions of Rpi users without their consent or awareness. From the outside. This is bad, but it is actually much worse since from the inside they already have full control of your Raspberry Pi regardless of operating system of your choice. Linux/BSD/* can't boot without proprietary Microsoft owned real time OS.
 
Most of the RPi users probably just don't care, others are naively assuming they are running FOSS software. Well, a part of it is, a part not. Not as bad as Android, but still. You can peek into the code, but at the end, Google, or lets say corpo world, is/are fully in charge of our mobile devices. Mainly with services.
 
After recent Chromium improvements, this is yet another loss for (Linux) community and FOSS in general.
 
http://techrights.org/2021/02/02/microsoft-pi/
https://en.wikipedia.org/wiki/ThreadX
https://www.infoworld.com/article/3536569/inside-microsofts-latest-os-azure-rtos.html
https://www.zdnet.com/article/linux-distributors-frustrated-by-googles-new-chromium-web-browser-restrictions/

Hello, for those still interested in hardware video decoding, I made a new thread introducing an APT repository to make installation easier for Armbian Debian Bookworm and Ubuntu Jammy distros:
 
 

https://github.com/150balbes/build/tree/risc-v

Wow! Thanks ALIGMSTEN! This solve the issue completely. The last docker version is now working on Armbian bullseye kernel 4.9 on Orange pi zero2.
Thanks for your help and for what you are doing!
Here is the detailed procedure for the people that may experience the same issue.
 
-Fresh install of Armbian_23.02.3_Orangepizero2_bullseye_legacy_4.9.318.img.xz
http://xogium.performanceservers.nl/archive/orangepizero2/archive/Armbian_23.02.3_Orangepizero2_bullseye_legacy_4.9.318.img.xz
 
sudo apt-get update
sudo apt-get upgrade
 
-add the following to /boot/armbianEnv.txt
extraargs=systemd.unified_cgroup_hierarchy=0
 
-return to prompt
sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
 
-reboot
 
-install docker according to https://docs.docker.com/engine/install/debian/ (below)
sudo apt-get update
sudo apt-get install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
 
-Then
echo \
  "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
  "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
 
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo reboot
 
-Test docker with
sudo docker run hello-world
 

The only solution for legacy images is to downgrade to cgroups v1 with kernel parameter 
 
You add this in armbianEnv.txt
 
extraargs=systemd.unified_cgroup_hierarchy=0  
 
To use cgroup v2, you need to have kernel 4.15 or later https://github.com/opencontainers/runc/blob/v1.0.0-rc95/docs/cgroup-v2.md#host-requirements.
 
Other requirements you might need to set iptables debian os
 
The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables. sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy  
 
As for non booting zero2 images please check latest, builds are working fine for me at this point, although I will check, (limited time atm, also 'not sure about mirrors synching').

kernel 6.5-rc1
info
 
https://forum.mangopi.org/t/armbiantv-and-altlinux-for-allwinner-d1-risc-v/2171/2?u=balbes-150

Docker needs some kernel stuff that has been introduced after 4.9.y was released. So the only way is to run a more recent kernel which probably does not support all hw features the board has to offer.

Hello everyone，
 
     You can run linux(armbian...) on am40 now！ 
 
https://gitee.com/xiayang0521/rk3399
 
镜像下载：http://files.kos.org.cn/rockchip/am40/
ophub Armbian下载：https://github.com/ophub/amlogic-s9xxx-armbian/releases
ophub openwrt下载：https://github.com/ophub/amlogic-s9xxx-openwrt/releases
本人移植或者收集群友的镜像分享: https://lajilao.top/thread-63-1-1.html

Clone my GIT and build the kernel (you can additionally change the configuration as you wish) - get a DEB package for manual installation\updating of the kernel on any system. The assembly can be done on the rock 5b itself, the assembly time is small.

You are using an old version of the kernel. Use the latest version of the images, there is already the necessary module there.
 
https://github.com/150balbes/build/blob/ed6c18895b1ed1429ea1a22210a826039d177d58/config/kernel/linux-station-m3-current.config#L2939

Hi,
 
Got same issue, looks like allwinner subdir is expected but not there. From a linux laptop, mounting the SD, I create a symlink dir named allwinner linked to /boot/dtb  :
 
root@nanopiduo2:/boot/dtb# ls -l allwinner lrwxrwxrwx 1 root root 1 Apr 16 15:15 allwinner -> .  

Unknown. Plus I managed to fry the board. It was sent to repair, got repaired, it is coming back ... but sadly anyway don't have time to do anything. 
 

When they boots, images would be at the download pages with at least WIP / community support status.
 

This might be helpful.
https://github.com/Kwiboo/arm-trusted-firmware

PD has advantages when you use the cables at 2A for a long time. But that is typically for charging a phone or a laptop in a short time.
 
With a PD-adapter the power consumption is pretty bad for the Rock5.
With a constant Voltage power supply it is only bad in combination with NVMe and good in combination with eMMC.
When powered of, without removing the power cable, the Rock5B still uses about 0,5W (slightly worse than a RPI4, which is already bad).
 
When using eMMC the Rock5B uses about 1.8-2W in idle. When you are using a general 30-65W PD adapter make it 2.4-3W in idle (the DC-DC conversion from  20V to 5V is very inefficient, if you have a small and cheap PD adapter this adds to the  inefficiency).
 
When using an NVMe you could get the power consumption as low as 4W in idle, with a 12V constant voltage adapter.
CPU 0-3: 1200 ( 600 Mhz - 1800 MHz / conservative) CPU 4-5: 816 ( 408 Mhz - 2400 MHz / conservative) CPU 6-7: 600 ( 408 Mhz - 2400 MHz / conservative) GPU : 300 ( 300 Mhz - 1000 MHz / simple_ondemand) DMC : 1560 ( 528 Mhz - 1560 MHz / dmc_ondemand) Here the pcie_aspm (NVMe connection) is set to powersupersave.
 
With the pcie_aspm set to performance and all the cpu and gpu settings to max you get 6W in idle.
CPU 0-3: 1800 (1800 Mhz - 1800 MHz / performance) CPU 4-5: 2400 (1000 Mhz - 2400 MHz / performance) CPU 6-7: 2400 (1000 Mhz - 2400 MHz / performance) GPU : 1000 ( 300 Mhz - 1000 MHz / performance) DMC : 2112 ( 528 Mhz - 2112 MHz / performance) The Kingston A2000 might not be the most energie-efficient NVMe, but other brands generally also focus on performance instead of efficiency.
 
The above summary is made by parsing the settings from:
  /sys/devices/system/cpu/cpufreq/policyX/
  /sys/devices/platform/fb000000.gpu/devfreq/fb000000.gpu/
  /sys/devices/platform/dmc/devfreq/dmc/
  /sys/module/pcie_aspm/parameters/
(You can also use the sys-tree to quickly change the settings with a script).
 
Ondemand and conservative are generally similar for power consumption in idle mode.
 
Earlier experiences that low power consumption and NVMe are a bad combination is true for the Rock5 as well. PowerSuperSave can not be considered a stable option for all NVMe drives. But still with lowpower solutions NVMe might be preferable to eMMC since it is slightly better protected against data loss.
 
In performance mode, during a compilation, the consumption easily reaches 13W (with NVMe, without large USB users, without much GPU use).
(I use a cheap power supply with monitoring to get the general idea of power consumption, not a calibrated solution).
 
Finally you could use a constant power supply of 5V to lower the power consumption in idle. I would not recommend that , I think optimizing for 1.5A at peak performance is better, resulting in 9V or 12V for most cases. (Instead of PD, QC is probably cheaper and more power efficient).

Yesterday, I was able to build the unpatched source of ffmpeg (the snapshot available in this date), and it ran fine, with CPU H264 decoding.
 
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
 
Then, I downloaded this libreelec patch.
https://github.com/LibreELEC/LibreELEC.tv/blob/master/packages/multimedia/ffmpeg/patches/v4l2-request/ffmpeg-001-v4l2-request.patch
with:
cd ffmpeg_sources/ffmpeg
patch -p1 < ffmpeg-001-v4l2-request.patch
 
There was only 1 hunk error.
patching file libavcodec/h264_slice.c
Hunk #1 FAILED at 808.
Hunk #2 succeeded at 861 (offset 7 lines).
1 out of 2 hunks FAILED -- saving rejects to file libavcodec/h264_slice.c.rej
 
I am working on fixing this patch correctly.

USB-LAN

The Luma library allows you to display text, graphics, animation, etc. on multiple display types. Here I will describe the easiest one to configure which is Luma.OLED and the I2C version of the SSD1306. You can find these displays on EBay and Amazon for less than $10 US each (you can get them for less than $3 US if you order from China, but it might not show up). I've configured Luma on many SBCs and it's my go to library if I need a small display for projects.
 

 
Requirements
NanoPi Duo (I used V1.0 board with 512 MB RAM) flashed with Armbian image. This will work with or without the mini shield. Small nylon nuts, bolts and standoffs if you want to mount display I2C OLED display (check http://luma-oled.readthedocs.io/en/latest/hardware.html) 4 female to female jumper wires If you want to configure wifi the easy way just edit the following file on the SD sudo nano /media/username/43296f0d-fc9e-4cec-b3bf-f335fc72f371/etc/network/interfaces and add:
allow-hotplug wlan0 iface wlan0 inet static address 192.168.1.69 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.1 wpa-ssid your_ssid wpa-psk your_password Comment out the eth0 stuff. You can do it the hard way with the debug serial interface though if you want When I ordered my Duos I forgot to order the USB dongle, so I would have been out of luck otherwise. Boot up and configure the Duo the way you like, power off and wire up the display as follows:
VCC to either 5Vin or 3V3 GND to GND SCL to SCL SDA to SDA Power up Duo and configure I2C:
sudo nano /boot/armbianEnv.txt and add i2c0 to overlays= sudo apt-get install i2c-tools sudo usermod -a -G i2c username (non-root user you created) sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- If you see the 3c on i2c0 then you are in business. Let's install Luma.OLED:
sudo apt-get install python-dev python-pip libfreetype6-dev libjpeg-dev sudo -H pip install --upgrade pip sudo apt-get purge python-pip sudo -H pip install --upgrade pip setuptools sudo -H pip install --upgrade luma.oled sudo -H pip uninstall RPi.GPIO (this will not work on Duo and is not needed for I2C) OK, let's create a simple demo program to make sure things are working nano i2chello.py:
import time from luma.core.interface.serial import i2c from luma.core.render import canvas from luma.oled.device import ssd1306 serial = i2c(port=0, address=0x3C) device = ssd1306(serial) with canvas(device) as draw: draw.rectangle(device.bounding_box, outline="white") draw.text((3, 3), "Hello", fill="white") time.sleep(10) And you should see (screen shot from the Luma emulator):
 

 
Now we can install the Luma examples:
sudo apt-get install git-core libsdl-dev libportmidi-dev libsdl-ttf2.0-dev libsdl-mixer1.2-dev libsdl-image1.2-dev
git clone https://github.com/rm-hull/luma.examples.git
cd luma.examples
sudo -H pip install -e .
Let's run an example: sudo python examples/invaders.py -d ssd1306 --i2c-port 0 --i2c-address 0x3c

You are using u-boot shit in MTD\SPI. replace with the normal version and get a full launch from any media (USB\SD\NVMe) in any NVMe state.
 
https://forum.armbian.com/topic/24931-armbian-efigrub-nvme/

Here is the result of my test: http://ix.io/4sgx .
 

If we would have time / resources we would do this months ago. In case you want to help others:
https://docs.armbian.com/Developer-Guide_Adding-Board-Family/