balbes150

Ethernet works: http://ix.io/2pla
 

I did a quick hack (stupid value replacement
TEXT_OFFSET 
0x0 -> 0x01080000
 

Ver 20200616-dev
"clean" kernel (no patch) 5.8-rc1

1. I don't owe anything.
2. if you Want to get detailed documentation and dedicated resources for posting materials for download, pay 5000 to donate Armbian.
3. I have a very negative attitude to those who use someone else's development for free (in which a lot of work\money\time of different people is invested), absolutely do not help this project in any way and at the same time make claims.

1. I don't owe anything.
2. if you Want to get detailed documentation and dedicated resources for posting materials for download, pay 5000 to donate Armbian.
3. I have a very negative attitude to those who use someone else's development for free (in which a lot of work\money\time of different people is invested), absolutely do not help this project in any way and at the same time make claims.

Version 20200612.
Kernel 5.7.2.
updated the build system, supported build on aarch64 Focal.

Version 20200612.
Kernel 5.7.2.
updated the build system, supported build on aarch64 Focal.

Checked the transition from Bionic to Focal with the command (do-release-upgrade). The system was updated from the beginning to Eoan and then upgraded to Focal. Please note that this is a potentially dangerous procedure and you must first save all your valuable data.

The start system in Coreelec is not compatible with LibreELECE  Armbian  etc. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.
 
Questions that do not specify exact details (the exact image version, TV box model, detailed steps that were performed for DTB settings, and so on) will be ignored and deleted.
 
For all. I don't support s905x3. I don't have this equipment. All messages about this platform deleted. What works or doesn't work from this equipment - I don't know. I do not give any answers or comments on the s905x3 chip.
 
The build and publication of unified test images with a common core for the Rockchip Amlogic Allwinner platform begins.
 
Y-disk
https://yadi.sk/d/_rQgn_FosYuW0g
 
MEGA
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link. 
https://users.armbian.com/balbes150/
 
 
*********************************************************************************************************************************
Pay attention. Starting from version 20.08 (20200814), the configuration order for the used DTB changes.
 
Please note that the algorithm for initial configuration of the system for startup has changed. Instead of a file "uEnv.txt", the file "/extlinux/extlinux.conf " is now used. The rules for editing a file remain the same.
All Amlogic models now need the "u-boot.ext" file.
Before launching on Amlogic, you must copy or rename one of the existing files "u-boot-*" to "u-boot.ext".
 
For s905 (not X) - used u-boot-s905
For s905x and s912 - used u-boot-s905x-s912
For s905x2 and s922 - used u-boot-s905x2-s922
 
For g12a\g12b models, a single file is now used (files u-boot.sd and u-boot.usb now replaces one u-boot-s922 file).
For the Allwinner platform, you no longer need to rename the scripts "boot.scr".
All "boot.scr" scripts have been canceled and are not used.
 
*************************************************************************************************************************************
 
How to run these images on the Amlogic platform .
Now all images Armbian and LE has all the files for activate the multi-boot. Anything addition to download and copy to media is not required.
 
1. Download the image for your device
2. Unpack
3. Burn the image on the medium
4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
 
If universal multi-upload has not yet been activated on this device, you need to activate it once. There are several options for activating multi-loading.
 
option A
- Connect the prepared media to the device and turn on the power, boot into Android
- Open the app "Update&Backup"
- Click on "Select" local update and chose the file on the removable media aml_autoscript.zip
- Start "Update"
- System will reboot twice and start running the system from external media.
 
option B
-  try using the "toothpick method"
 
 
How to run these images on the Rockchip and Allwinner platform .
1. Download the image for your device
2. Unpack
3. Burn the image on the medium
4. Configure in the file (uEnv.txt) launch parameters for the desired platform and model (uncomment the desired lines and comment out or delete unused ones)
5. If your device does not support USB startup , you can only use SD cards and you need to add the correct u-boot to the SD card (for details on how to add it, see the text of this message)
6. Connect the prepared media to the device and turn on the power
 
Please note that the DTB configuration order has changed.
Now a single configuration method is used for all Rockchip Allwinner Amlogic platforms. The file (uEnv.txt) is used for configuration DTB all platforms. 
Now a single configuration method is used for all platforms, using the file (uEnv.txt). You need to edit this file to configure it. You need to uncomment the two lines that are responsible for your platform and specify the correct DTB for your model. If you use this image to run on the one platform, you can delete it from the settings file (uEnv.txt) strings from other platforms.
 
Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.
 
Pay attention.
The installation algorithm in eMMC has changed. My recommend that you perform a clean installation in eMMC. Be sure to make a full backup of eMMC before installing it in eMMC.
The system installation scripts in eMMC have changed accordingly. If you have a system with eMMC core 5 installed on RK33xx, it is advisable to perform a clean installation in eMMC to upgrade to the new version. 
 
For the aw H6 platform, all scripts are already in the image (which have the ending aw). You need to rename the files with the replacement (remove the ".aw" ending).
 
Fix for correct color to G12 (Amlogic S905X2 S922X)
For models based on g12 (s905x2 s922), which have a problem not the correct color , 
If you are starting the system from an SD card, you need to copy file  u-boot.sd to u-boot.ext,
If you are starting the system from an USB, you need to copy file  u-boot.usb to u-boot.ext
When installing in eMMC, you do not need to do anything with your hands, the installation script itself will perform the necessary system configuration and when running from eMMC, the system will work with the correct color.
 
Please note, this version for the transition to the release of a single image for the platform Rockchip + Amlogic + Allwinner. The new image after writing to external media and after configuring the used dtb (and if necessary adding the desired u-boot option to run from the SD card on the Rockchip and Allwinner) can be used simultaneously on AML (s9xxx), RK (rk3399 and rk3328) and AW (H6). If the TV boxes RK (rk3328 and rk3399) and AW (H6) in eMMC installed a new version of u-boot  with support for starting the system with USB, adding u-boot to SD card is not required, the system will automatically start on with USB.
 
Important change. With this version (>= 20200218), you can easily add the desired u-boot on any PC (including Windows) .
 
To do this, new versions of u-boot are downloaded on the site.
 
https://yadi.sk/d/lTbXkrmZN5Hf6g
 
Rules for using the new u-boot option. Download, Armbian image, unpack. Write image Armbian to the SD card. Download and write the desired version of the u-boot file to SD card. Configure the DTB and the launch string (APPEND) in (uEnv.txt) for the desired model\platform.
 
Pay attention. Now you don't need to write u-boot with complex commands, you write the u-boot image with the same program as you usually write an Armbian image. This allows you to configure the system to run (including writing a u-boot image) on any PC (including Windows).
 
Pay attention. The new version changed the size of the partitions that are obtained when writing an image (all images have a fixed size of 5GB).  This u-boot entry option only applies to the new version 20200218 and subsequent versions. Don't try this for old images. This will not work on older images.
 
OLD add u-boot
 
 
 
For RK33xx
if you have windows and can't use the add u-boot commands to the SD card, use the SD+USB combination , write only the new u-boot to the SD card, and write the Armbian image to a USB storage device. And connect them together to the TV box.
 
To turn on the sound on models AML
where it is not present after the initial start. To enable audio , run the script (sound.sh).  You need to run the script
 
sudo sound.sh
 
 
 
Odroid N2
When starting from an SD card on Odroid N2, you must, after recording the image, write uboot to the SD card, configure uEnv.txt, additionally rename the script (boot.scr.aw) in (boot.scr). To be able to start any system from any media (USB SD eMMC), i'm recommend using the updated version of u-boot-SPI. Details about u-boot-SPI for Odroid N2 can be found here.
 
 
 
 

OK.  Boots, gets to desktop, plays the test video, sound via HDMI works, my RTL8821CU wifi was properly recognized. 
 
Only thing I see is no fan control, and the LED is just blinking at 1 Hz for no known reason.
 
LibreELEC: same, boots, audio, etc.  [edit]  it did not recognize the wifi adapter.
 
Now to dig up my Ugoos and stuff this on it. 
 
 

@TonyMac32  Did I remember correctly that you have a MIQI Board (rk3288) ?

The new version 20200609. In it, I switched to using the u-boot version 2020.04 (source shared with universal images for aarch64). This version has long implemented the function of starting the system from USB media. Now rk3288 also has the option to start the system from USB media. Minimal Bionic and Buster images have also been added to the site.
 
Starting from USB is available on both systems (Libreelec and Armbian). For example. You can write to an Armbian SD card, and write to a Libreelec USB flash drive. When you connect both media, LE will work, and when you disable the USB flash drive, Armbian starts.
 
 
p.s. The correct installation of these systems in eMMC is currently being tested.

https://github.com/Pyrestone/jetson-fan-ctl  works good.
 
I wrote a little script which monitors the pwm fan speed:  show_fan_pwm.sh
 
#!/bin/bash
# script show_fan_pwm.sh
main () {
  while [ 1 ]; do
  echo -n "fan pwn speed is : "
    cat /sys/devices/pwm-fan/target_pwm
  sleep 1
  done
}
main $@
exit 0
 

The difference between armbian and nvidia ubuntu 18.04 is:
nvidia ubuntu shows in /sys/class/devfreq/ 2 links:
lrwxrwxrwx  1 root root 0 Jan 28  2018 54340000.vic -> ../../devices/50000000.host1x/54340000.vic/devfreq/54340000.vic
lrwxrwxrwx  1 root root 0 Jun  5 18:40 57000000.gpu -> ../../devices/57000000.gpu/devfreq/57000000.gpu

armbian 20.05.5_Jetson-nano_buster_legacy_4.9.140_20200528 shows in /sys/class/devfreq/ only 1 link:
lrwxrwxrwx  1 root root 0 Jun  5 20:46 54340000.vic -> ../../devices/50000000.host1x/54340000.vic/devfreq/54340000.vic
 
Here is a link https://www.jetsonhacks.com/2018/10/07/nvpmodel-nvidia-jetson-agx-xavier-developer-kit/
 
which decribes nvpmodel and jetson_clocks.sh (which was renamed to jetson_clocks, meanwhile)
Interesting of the link above is, that the performance model can be set nvpmodel.
If you take the nvpmodel program, the jetson_clocks script from nvidia ubuntu 18.04 and if you uncomment line 391 of jetson_clocks
    do_hotplug
    do_clusterswitch
    do_cpu
    #do_gpu <--- commented out at line 391
    do_emc
    do_fan
    do_nvpmodel
then the script seems to work.
Additionally  https://github.com/Pyrestone/jetson-fan-ctl should work then too.
 
I will try it and i report it to you.

Version 20200605.
Added WiFi support for Allwinner Tanix TX6 (H6).

Version 20200605.
Added WiFi support for Allwinner Tanix TX6 (H6).

Version 20200605.
Added WiFi support for Allwinner Tanix TX6 (H6).

Update ver 20200604 kernel 5.4

My fan is really quiet with 255. I think it depends on the fan if it is too loud or not.

The temperature of my jetson nano is under 40 degrees too.
 
In tried https://github.com/Pyrestone/jetson-fan-ctl, but it works with ubuntu from nvidia only.
I tried nvidia ubuntu and the fan works really quiet and it sets the fan speed dynamically.
It uses /usr/bin/jetson_clocks which produces an error on armbian but the fan starts working. Maybe, on nvidia ubuntu are some defines set which are not available on armbian.
 
/usr/bin/jetson_clocks is used by https://github.com/Pyrestone/jetson-fan-ctl, too.
 
The do_gpu() function of /usr/bin/jetson_clocks produces an error:
Maybe, there are some environment variables about GPU not set in this section: /usr/bin/jetson_clocks line 242...
 
    for devfreq in /sys/class/devfreq/*; do
        name=$(tr -d '\0' <${devfreq}/device/of_node/name)
        if [[ "${name}" == "gv11b" || "${name}" == "gp10b" || "${name}" == "gpu" ]]; then
            GPU_MIN_FREQ="${devfreq}/min_freq"
            GPU_MAX_FREQ="${devfreq}/max_freq"
            GPU_CUR_FREQ="${devfreq}/cur_freq"
            GPU_RAIL_GATE="${devfreq}/device/railgate_enable"
            break
        fi
    done
    if [[ "${name}" == "" ]]; then
        echo "Error! Unknown GPU!"   <------------------- this error is shown on armbian
        exit 1
    fi

First test with ugoos ut3s with default dtb (firefly-reload): http://ix.io/2o7o
For information, I have jock uboot and an old Q8 image installed on emmc.
Wifi works, but ethernet seems buggy like on recent arm64 images (kernel 5.X pb with current dtbs ?). I didn't test it, but the connection was activated whereas no cable... System halts instead of reboot.
Bluetooth seems not working well (xfce applet disappear when I try to use it to activate)
With Q8 dtb the experience seems similar from a user perspective: http://ix.io/2o7q
With popmetal and tinker dtb, the system does not boot: waiting root file system... running /scripts/local-block
With miqi dtb, it boots, but without wifi and I was not able to connect a cable to test the wired network, but eth0 still shows as connected.
 
Edit: As I noticed on Jock images, the Q8 dtb is not able to detect emmc on contrary to firefly-reload.

And there are a number of important differences between ArmbianTV and the official versions. For example, there are two sections. The first boot partition is necessarily made available for any PC (Windows Linux MAC etc), in particular it uses FAT. This is crucial. This allows any user, on any device, to easily configure system startup for their device. In case of problems with startup, it can connect the media to any PC and easily edit startup parameters, enable new options, change settings, add/delete files, etc. With official versions, this is not possible on a Windows PC, which greatly narrows the circle of users who want to start using Linux (Armbian). The official versions also use oters technologies. Installation in eMMC using direct bitwise copying of the source system (via DD).  use of the UUID, etc.
Please note that I do not impose anything on anyone or criticize the official version. I'm just stating the differences. Developers of the official version decide what to do and what to use.

Images with two kernel versions are available for testing.
Legacy.
Uses the 5.4 core built using source code and patches (with minor fixes) that are used to build the rockchip.
 
DEV.
The core 5.7-rc7 is used (the sources are shared with the version I use to build aarhc64 images).
 
There are no patches in this version yet. The legacy version has almost all the working hardware on UM3. On the DEV version, not everything works, but there is access to eMMC. how it is used (the setting for running is the same as the aarch64 version of images). To configure dtb, use the file (uEnv.txt). At this stage, I used settings and patches from MIQI to build the u-boot. I tried the u-boot version from Q8, it works the same way, but I haven't decided which version is better to use yet (I haven't fully figured out what the pros and cons of these u-boot versions are).
 
The link to the images and the launch order will be placed in the first message.

I opened this theme to support running ArmbianTV on 32-bit ARM models. To date, there are first results on launching ArmbianTV on the Rockchip rk3288 and AML s8xx platform (in the future, by analogy with aarch64, I plan to switch to a common image for all 32-bit models of TV boxes).
 
 
 
The link to the images
https://yadi.sk/d/85ZvBuXyyenf_A
 
 
MEGA (name -rk3288)
https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ
 
Now you can download the latest versions of images and DEB packages from the official Armbian resource via the link. 
https://users.armbian.com/balbes150/
 
 
Recommended startup procedure on UM3.
 
1. Install the Linux firmware version in eMMC (either a dual boot or a single Linux).
2. follow these instructions to download and run the Linux version from linuxium
 
https://forum.freaktab.com/forum/tv-player-support/rk3288-devices/21091-use-windows-to-create-an-sd-card-so-you-can-run-linux-on-a-rk3288-device
 
(do not forget to immediately expand the system partition to the entire media after writing the image). After launch, make a full backup eMMC with the DD command (or copy the ddbr utility to the system and use it).
3. Erase the first 4Mb on eMMC (using a simple DD command).
4. Download, unpack and burn the ArmbianTV image to your SD card.
5. Connect to the TV box and turn on the power. The system will start automatically.
 
For those who are not afraid to lose their regular firmware and be able to easily restore it later, you can use the "accelerated" launch option (erase eMMC use the tools for Rockchip TV boxes). 
 

To upgrade from the old core, you need to restore the original firmware and go through all the steps for a clean installation. Or perform all the steps manually (do not wait for a detailed step-by-step guide for the manual option, you will have to solve everything yourself on the spot).
 
 

Version 20200529.
Added 4K support for rk3399 and rk3328.