balbes150

Good news. The latest versions of Armbian and LE work well on Ugoos AM6. By the way, LE is running the sound through HDMI on Odroid N2 and Ugoos AM6. https://yadi.sk/d/OKl5cdXZGEOwpQ

I'll check to see if it can be turned on (so it can automatically assemble with the kernel).

A General comparison S922 and rk3399 you can see the topics Odroid N2. I am only preparing Armbian and Libreelec images for AM6, when they are ready, I will be able to perform a check. Write specifically what tests you want to learn. But I warn you right away, I have little time for tests, all the free time I spend on developing systems and performing work for customers.

Image recording should be done by a special program, when using "dd" there are often problems. This is a special theme in the first sections of this forum.

Update image ver 5.88 I received an Ugoos AM6 sample yesterday. My goal is full launch and support for Armbian and LibreELEC. First impressions are very positive. This TV box has a really great metal case (by the way, the price of a good metal case can reach 30-40$). For 90% of use cases, this completely solves the issue with cooling, i.e. the user does not need to modify anything himself. At the same time it solves the problem of protection of components from external radio interference and so solves the problem of radio interference from the component for regular WiFi\BT.

In order to be able to use direct launch from USB , you need to make changes to ENV for SPI. This can be done through the UART console (this method is described TV this topic), or if release a new version of Piteboot for N2 with these additions. I've suggested to HK representatives to do this through an official update Piteboot SPI, but no response has been received yet. I can collect own version of this upgrade Piteboot, but I think that this way should be collected, verified and submitted officially from HK. If HK will release such update, I am ready to send to GIT HK for u-boot SPI the necessary patch.

Update image for s9xxx 5.87_20190529

Replace all mentions of mmcblk1 with mmcblk2 in the script. You don't have to create partitions, the system has to do it itself.

Write down in detail what steps you are taking. And show the contents of your file "boot.ini"

Continue development. New version 0.4 of the multi-boot. The new version now uses a single startup scheme for all media (USB SD eMMC) using standard files, the basic "boot.ini" and rezervna "boot.scr." For proper operation of the " boot.ini" with USB media they should be adjusted (added new options to run from USB). New activation files "n2_autoscript.ini" and new option "boot.ini" with USB startup support are in the new 0.4 directory. Pay attention, now changed the order of activation of multi-boot. To activate using the new file "n2_autoscript.ini". A new set of commands to activate. I downloaded the scripts to activate the system startup from USB. The order of use https://yadi.sk/d/WrgbX_4ZSlnOXg . 1. Burn image to USB. 2. Download the files and add to the image. 3. Switch to start u-boot with SPI. 4. In the UART console, stop startup. (CTRL+C) 5. Execute the command. usb start fatload usb 0 3000000 n2_autoscript.ini source 3000000 At the same time the updated images with the new version of multi-boot 5.87_20190529.

To change in the script "install.sh" the number of the device mmcblk1 to mmcblk2

Checked the patch , pointed out by @Brad (thanks for the tip). With him eMMC with kernel 5.1 works flawlessly (work install to eMMC). Uploaded new images 20190528 with kernel 5.1 to the site.

Does anyone have a chance to download this container ? I want to try to bring the image to update the SPI enable multi-boot, to be able to activate multiboot on any N2 without the use of conosle UART. https://wiki.odroid.com/odroid-n2/software/using_docker

The new version of activate the multi-boot 0.3. It fixes bugs and adds the ability to easily configure the order of polling devices to run. This is the default order. setenv mmc_list "1 0" setenv boot_order "boot_usb boot_mmc boot_mmc_distro boot_rawimage boot_pxe boot_spi" You can easily change it without using the UART console. It is enough to edit the file "set_boot_order.ini" (this is a plain text file), specify the desired order of the survey (you can remove unnecessary items or add your own). Write the edited file to the SD card named "boot.ini" to connect to N2 and to turn the power on. Automatically starts the script and writes a new SPI parameters of the survey and launch systems. Please note that changing the order will work only after the initial activation of multiloading from SPI. By the way, for those who have already completed the activation of the previous version n2_autoscript to upgrade to a new version does not require the console UART. Record to USB flash drive new file (n2_autoscript) filename "boot.scr", connect to N2 and power on. The script will update the multiload to the new version. Similar changes I added to my version of u-boot , which is recorded in the images Armbian (to run from the SD\mmc). If HK representatives are interested, I can send PR to their GIT u-boot and they will be able to build a new version of u-boot for SPI, so that any user could easily add to their N2 the ability to run any systems from any media immediately from SPI, using the official HK site, without using the UART console.

With new DTB files and "install.sh", I was able to install and run Armbian Server with kernel 5.1 in eMMC. https://yadi.sk/d/WrgbX_4ZSlnOXg

On S905x2 (it's a close platform with S922) eMMC works with this kernel. Perhaps the reason for the settings or is it the result of using a removable connector for the eMMC on the N2. I noticed that if you copy the data in manual parts no more than 500MB, with an intermediate "sync" , everything is copied correctly.

This still works on kernel 4.9. The 5.1 kernel needs patches.

Uploaded a new version of multi-start activation to the site (n2_autoscript).

I forgot to write in the first message about eMMC that I always create partitions with an offset of 4M. New test results. Added files to the images to install the system in eMMC. Checked the Armbian installation with kernel 4.9. Everything was installed and when you restart properly run system from eMMC. Further an interesting outcome. The system startup from USB stopped working. Running from SD card works. When installed on eMMC, only system files were copied, u-boot did not copy. When clean the first 4M for eMMC, start with USB again earned. Now I have collected new images with the addition of the installation script in eMMC and a new option to activate multi-boot (changed the order of polling MMC), now the order of polling boot such 1. USB 2. SD card 3. eMMC. This ensures that the external system starts from USB\SD if there is a breakage with the start-up from eMMC.

Hooked module eMMC (blank) to N2. Switch to SPI. Starting Armbian from USB works without problems. Created a partition table and two partitions (FAT and EXT4) on eMMC . Reboot N2. Everything normally starts from USB and SD card. I haven't checked the system for eMMC yet (I don't have enough time).

New image 5.87_20190523 Update kernel and add new dtb

Try removing the u-boot loader from the eMMC and remove the startup scripts (boot.ini).

The website has added images of the Server Disco By the way, all the latest images for N2 now have support for direct launch from USB.

I have an eMMC module from HK (was bundled with N2). I haven't tried it yet. I'll try to test it with the image Armbian in the course of the week.

Yes, see u-boot documentation.