Christian_

Hello, this was my way to make RTC DS3231 works on rock64.
 
apt-get install i2c-tools
 
- /etc/rc.local
/lib/udev/hwclock-set /dev/rtc1 exit 0 - /lib/udev/hwclock-set
if [ -e /run/systemd/system ] ; then #    exit 0      /bin/enable_dtoverlay i2c0 i2c@ff150000 okay      echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device fi #if [ -e /run/udev/hwclock-set ]; then #    exit 0 #fi HCTOSYS_DEVICE=rtc1  
Copy to /bin/ and make executable
https://raw.githubusercontent.com/ayufan-rock64/linux-package/master/root/usr/local/sbin/enable_dtoverlay
 
systemctl stop systemd-timesyncd.service
systemctl disable systemd-timesyncd.service
systemctl stop fake-hwclock.service
systemctl disable fake-hwclock.service
 
sudo apt-get -y remove fake-hwclock
apt install chrony

ROCK64 is a RK3328 Quad-Core ARM Cortex A53 board with up to 4 GB of RAM. Unfortunately it has a non-functional RTC (/dev/rtc0), which is not battery backed. If your board is not connected to internet 7/24, you can not use the NTP or systemd-timesyncd. Therefore you need to connect a battery-backed external RTC module to the ROCK64 header, and get the time via the i2c protocol. The good news is, the GPIO headers on ROCK64 is compatible with Raspberry Pi headers. Therefore almost any Raspberry Pi RTC module will work on ROCK64. But you need to do some tweaking to communicate with the RTC module. I will explain the required steps which worked for me.
 
1. Buy an external RTC module for Raspberry Pi, preferably with DS1307 chip. Here is an example:
https://www.abelectronics.co.uk/p/70/rtc-pi
 
2. Install i2c-tools package:
sudo apt-get install i2c-tools  
3. Connect the RTC module to the board as in the attached picture.
 
4. Right now, you can not probe the RTC module, because most of the GPIO headers on ROCK64 board is disabled by default. (See https://github.com/ayufan-rock64/linux-build/blob/master/recipes/additional-devices.md for details.)
Therefore if you try to probe i2c-0, you will get the error below:
root@rock64:~# sudo i2cdetect -y 0 Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory Ayufan wrote a nice script named "enable_dtoverlay" to enable the GPIO headers on-the-fly. Here is the link: https://raw.githubusercontent.com/ayufan-rock64/linux-package/master/root/usr/local/sbin/enable_dtoverlay
Download this script and copy it under /bin and make it executable. We will enable "i2c-0" with this script, which we need for the RTC module. The command to enable i2c-0 is as follows:
/bin/enable_dtoverlay i2c0 i2c@ff150000 okay After you run this command, /dev/i2c-0 becomes available, and we can probe it via the command below:
 
root@rock64:~# sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- If you see the number 68, you are on the right track.
 
5. Now we need the kernel driver for DS1307. Unfortunately DS1307 driver is not available with armbian kernel (see below).
root@rock64:~# cat /boot/config-4.4.162-rockchip64 | grep DS1307 # CONFIG_RTC_DRV_DS1307 is not set So we need to recompile the Armbian kernel with this option enabled. I will not cover the steps to compile the kernel, you can find it here: https://docs.armbian.com/Developer-Guide_Build-Preparation/
Let's hope @Igor or any other Armbian developer will enable this module by default, and save us from this burden.
 
After we compile the kernel with DS1307 driver, we are almost done. We need to tell the kernel that a DS1307 chip is using the i2c-0. Here is the way to do that:
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device After we execute this command, /dev/rtc1 becomes available, and points to our external RTC module. Please note that /dev/rtc0 is the onboard RTC, which does not work, and should be avoided.
 
We need to update the date/time information from the system for the first time. Here is the command to do that:
hwclock --rtc /dev/rtc1 --systohc Now our external RTC clock is set, and ready to take over NTP.
 
6. Edit /lib/udev/hwclock-set. Find the lines below, and update as shown:
if [ -e /run/systemd/system ] ; then # exit 0 /bin/enable_dtoverlay i2c0 i2c@ff150000 okay echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device fi  
7. Edit /etc/rc.local, add the following lines to set the system clock for every boot:
 
/lib/udev/hwclock-set /dev/rtc1  
8. Disable the below services, as we don't need them anymore:
systemctl stop systemd-timesyncd.service systemctl disable systemd-timesyncd.service systemctl stop fake-hwclock.service systemctl disable fake-hwclock.service  
9. Reboot and enjoy your RTC module.

Of course, I've shown the source located in kernel tree, not a decompiled version ...
 
I've also said something wrong : I've a local patch not included in Armbian tree :

You can use that patch if you are doing you own build ...
... or you can tweak your decompile DT to make sure that USB nodes are matching that, or use my own DTB attached, of course after backing up yours first ...
 
sun8i-h3-orangepi-lite.dtb

Hi,
 
thanks for wonderful collection of prepared packages. Works great.
 
I just found some improvements. I wanted to let know, so:
 
Kodi 18.4 with Acceleration
I found newer kodi version - 18.4 with acceleration enabled.
You can download it here:
https://www.areascout.at/kodi/kodi-bin_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_armhf.deb https://www.areascout.at/kodi/kodi_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_all.deb https://www.areascout.at/kodi/kodi-eventclients-common_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_all.deb https://www.areascout.at/kodi/kodi-eventclients-dev_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_all.deb https://www.areascout.at/kodi/kodi-eventclients-kodi-send_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_all.deb https://www.areascout.at/kodi/kodi-eventclients-ps3_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_all.deb https://www.areascout.at/kodi/kodi-eventclients-wiiremote_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_armhf.deb https://www.areascout.at/kodi/kodi-tools-texturepacker_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_armhf.deb https://www.areascout.at/kodi/kodi-addon-dev_18.4~git20190902.1505-3ade758ceb-dirty-1~bionic_all.deb Only thing is you must manually install ffmpeg package (it's not in dependecies...)
Source: https://forum.odroid.com/viewtopic.php?t=34149
 
Widevine and Flash with Chromium 76 from armbian repository
 
I also found nice way how to get widevine library for latest Chromium browser. It can be extracted from ChromeOS images.
I found how to do it here: https://gist.github.com/ruario/19a28d98d29d34ec9b184c42e5f8bf29
(Actually I am not sure if script works, I just read from script how to do that and did that manually)
This way you can have latest Chromium with widevine working. Do you do not have to use some very old release which can be problematic.
 
You can use this prepared archive which I made for myself:
https://mega.nz/#!D0dCGAoJ!k8MEiY0jdu0uyqQI4u4wrS5dEcbJ5G1cTJRY6PeIq5I  
Just a tip
 
I also noticed that many people are getting into trouble with apt update/upgrade, when their packages get overwritten.
But there is nice feature in apt how to solve this. apt-mark hold/unhold is your friend here.
 
You can freeze updates of kodi, chromium and xorg for example with:
apt-mark hold kodi kodi-bin chromium-browser xserver-common-rockchip xserver-xorg-core-rockchip But use with caution! This will disable updates for mentioned packages until you will update them manually or do not mark them as upgradable (unhold).
 

Hi all.
I'm trying to figure out how to use gstreamer to encode h264 video on Rock64 (Rockchip RK3328). I'm using Armbian Bionic 5.60 (stable Ubuntu 18.04.1 LTS 4.4.156-rockchip64).
I compiled mpp and gstreamer-rockchip from https://github.com/rockchip-linux  and installed both, but I'm still missing mpph264enc, how do I get that?
gst-inspect-1.0 mpph264enc says: No such element or plugin 'mpph264enc'
Many thanks for reading, any help would be greatly appreciated.
 
Regards.
Christian
 

It is in the default U-Boot environment, the default fdtfile is declared in board defconfig...

sed -i "s/MAX_SPEED=.*/MAX_SPEED=1512000/" /etc/default/cpufrequtils
 
"1512000" instead.

or... you SSH into a working SBC and use it's spare UART pins to ttl into the non-working SBC... 
Likely to be one of the most silly things I've ever did with an SBC.. But hey, it works...  (at least @martinayotte will like it.   )
 

 

 
 
do we have UART2 and UART3? at least on mine (4.14) we use UART3...  @TonyMac32? Or was it back then when we used UART2? Can't remember anymore..  

The problem was the wifi region setting unset, this prevented to tune the radio to channel 1.

Orange Pi Mini 2 was never directly supported and yes, you probably can just use the image from Orange Pi 2. Disappeared boards appear here: https://www.armbian.com/deprecated/

Yesterday I came across the following - for me - fine project (Demo-Page):
ESPTERM Release 2.3.0 Cricket
https://espterm.github.io/term.html
 
GitHub-Page:
https://github.com/espterm/espterm-firmware
 
Downloads:
https://github.com/espterm/espterm-firmware/releases
 
Its a VT100-Webpage-Terminal on a ESP8266-Microcontroller which opens a Accesspoint.
You could connect via this VT100-Webpage-Terminal to the TTL-Port of the ESP8266.
 
TTL-Connection is done (like allways in TTL-Connections) with RX,TX and GND
 
I connected my Orange Pi R1 via TTL and 115200 Baud and could "work" at a (max.) Terminal-Size of 80x25
(80x25 is max. in the downloadable binary - if you do compile by yourself mor is possible.... 132x50 would be fine )
 
So if you have a misconfigured Network-Connection (missed the /24 in the IP of the server in nmtui) and you dont want to use a USB-serial-Dongle because every Dongle wats its own driver  - here a second solution