balbes150

Good news for RockPI 4B owners. This is an image with Armbian Bionic that includes support for running from USB. I checked this image with eMMC and SD card, running direct system startup from USB. RockPI 4B does not have a very convenient placement of eMMC and SD connectors (if the NVMe module is connected on top, the loop from it overlaps the SD connector) so it is very difficult to test different systems. This image solves this problem. You can write any system to SD or eMMC and add a u-boot version that supports USB startup to the media (second link). Install the eMMC module or SD card and start the main system from them. When you need to quickly check or just start another system with USB, you simply connect the USB drive with the new system and it starts automatically when you turn on the power, turn off the USB and return to the normal system. If Radxa added one small patch to the source code for SPI, you can get a unique u-boot that supports direct launch from USB. I recorded an Armbian image on eMMC and installed it on the Board, and now it is very convenient for me to quickly launch Libreelec from USB, I can use a universal image that does not depend on the availability of the necessary u-boot for the SD card, just configure the DTB correctly and voila, the system works completely with USB, without any additional steps. I connected the USB-I have LE, disabled USB and can immediately start Armbian. Armbian Biomic https://yadi.sk/d/M1hzFvNq7SpfmA u-boot https://yadi.sk/d/Se637oJkw54tfA

For some reason that I don't understand yet, on the Allwinner H6 (Tanix TX6) model, I have the SD card and eMMC numbers on the opposite side than on the other RK and AML models. If you have problems running on H6, try replacing these files with these options. https://yadi.sk/d/3crtWoQvvosh1w

The topic is detached, since the main system is now shared and discussed in the corresponding topic.

See the topic in the section TV boxes RK+AML+AW

By the way, I published new images 20200117 19.11.5, there are several different DTB there. You can take this image, add your u-boot to it, and play with the different DTB that are there (you can try other ready-made DTB for kernel 5 from other sources). Setting up the DTB used there is very simple - change the name in the file " uEnv.txt". For all. These images added a test version of the system installation in eMMC for H6.

You have u-boot already doing the minimum necessary work-loading the kernel and running it. Will try different DTB that are available for H6. Perhaps some of them will have the minimum necessary configuration for starting the kernel.

I'm tired of telling you that USB support will never come out of thin air. Until someone makes the correct dtb, nothing will change.

The new version 20200117 19.11.5. 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. 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. Added installation in eMMC for the g12 platform with color correction. For this purpose, the universal multiload for AML has been updated. For the system to work correctly on AML, you need to update the multiload. Added a test version of the system installation in eMMC for Allwinner H6 (please note, this is the first version that may contain errors). For anyone who uses an eMMC installation , it is mandatory to perform a full eMMC backup before installation.

Judging by the Armbian startup log, you are missing a working DTB for the kernel itself.

I don't know. Usually there are about 150-300 guests. And such a sharp spike, maybe it's a bot attack .....

Now I paid attention to the numbers of visitors I have never seen such an influx of guests .... 14 Members, 0 Anonymous, 1208 Guests (See full list)

New versions 19.11.5 20200113 with 5.5 kernel. HDMI doesn't work. Management only via UART or SSH.

If there is a u-boot in eMMC, the idbloader from eMMC is used to start from the SD card, then the u-boot control is transferred to the SD card.

You don't need to write a u-boot from H6 to RK. It is enough to write your u-boot for rk3318

Part of the equipment I get from manufacturers or interested in support persons for free. There are some models that I buy myself (which are of personal interest to me).

Is this a question or a statement of fact ?

For a universal image, the installation is performed only through the direct launch of the desired script , for each platform it is different. All long logs need to be removed in the spoiler, they make it very difficult to read the topic. Or put them in a text file and make an attachment to the message. Wiredguard is included in the working (non-DEV) versions. To All DEV versions are intended for experienced users to test new core functionality.

I didn't quite understand what was talking about. There is a special page for donations on Armbian.

To provide support, must have this equipment. If I buy all the models at my own expense, I'll have to cut back on my family expenses. If manufacturers provide test samples, I can add support for them. This model already has the necessary support in the main kernel.

I have now launched the latest version of LE with dtb from RockPi4 on N6. Surprisingly, everything works including WiFi. I hope that when I switch to the next version of the kernel , the same thing will work in Armbian.

Checked the ability to install and normal operation of the Linux system in eMMC on TV boxes with H6. The next step is to add the installation script to the eMMC for the armbian generic image. Details can be seen in this topic. https://forum.freaktab.com/forum/tv-player-support/allwinner-tv-players/793034-libreelec-and-armbian-for-allwinner-tv-box?p=794681#post794681

You must use DTB strictly from the image composition. Use u-boot from a system where PCIe is running. You violated the instructions, installation in eMMC only when using a regular Android and exact execution of the remaining steps.

Carefully read the info on the forum, the work of the x96 mini has been discussed many times and many times given recommendations on what to do and how to do it. You do not have 3 GB, this is a fraud of the seller. Contact the manufacturer or seller from whom you bought it.

I'm trying to add support for running from USB. Changed the polling order and added commands to the config for working with USB. Assembled u-boot. When checking, I see an attempt to initialize USB in the UART console, but the system shows that there are no USB controllers. As far as I understand, they should be described in the DTS used ? Or do I need to add something else to the u-boot source code ?

If you like problems, you can try ....