balbes150

mac=

No, I don't add binaries. I only accept DTS with the correct structure (not converted by the DTC utility).

The new version of images 20200427. Everyone who has the opportunity to test the wired network for s805\s812\s802. This is important for the developer of this direction, Martin. It needs feedback on how the wired network will work in the latest version of the core. To check it, you need to run a simple test and post the results here. start iperf3 on your computer with: "iperf3 -s" on the device: "iperf3 -c <computer IP>" after that on the device: "iperf3 -c -R <computer IP>"

This information is very outdated and does not relate to modern images. You need to configure DTB only by editing the file (uEnv.txt). Change the name of the file used in it. For this reason, nothing works for you.

1. The LEGACY version is not intended to be built by regular users (it can only be used by specialists who know its purpose well). 2. According to the log, you have a problem accessing network repositories (problems with the Internet, a large load on servers, and so on). This error does not apply to the build system.

Version 20.05.3 (20200425). Analog audio (Jack 3.5) for NanoPC T4

Hmm. Now I checked for N2 (ArmbianTV) , the temperature and the rest shows correctly with the core 5.7-rc2. root@arm-64:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time big.LITTLE load %cpu %sys %usr %nice %io %irq CPU C.St. 12:52:01: 1908/1992MHz 6.13 73% 10% 62% 0% 0% 0% 56.5°C 0/11 12:52:06: 1908/1992MHz 6.12 99% 10% 88% 0% 0% 0% 56.5°C 0/11 12:52:11: 1908/1992MHz 6.11 99% 15% 83% 0% 0% 0% 56.0°C 0/11 12:52:17: 1908/1992MHz 6.10 98% 19% 78% 0% 0% 1% 56.6°C 0/11 12:52:22: 1908/1992MHz 6.10 99% 15% 82% 0% 0% 0% 56.0°C 0/11^C

Script for automatically enabling audio on all known ARM models (in my images, it runs automatically when the system is first started and includes all known audio devices for the model being used). By the way, today, T4 has almost full support for all hardware (WiFi BT NVMe sound etc) and copes well with any tasks. It remains only to solve the issue with 4K resolution. sound.sh

patch for kernel 5.4 (current) z-add-sound-codec-nanopc-t4.patch

I figured out that the sound really works. Now you need to issue ready-made patches for Armbian.

?

There is a strange result. When using sources and patches from the Armbian build system (core 5.4) and adding changes from the T4 patch, the 5651 device does not appear. But if comment on a line &i2s0{ assigned-clocks = <&cru SCLK_I2SOUT_SRC>; // assigned-clock-parents = <&cru SCLK_I2S0_8CH>; rockchip,i2s-broken-burst-len; rockchip,playback-channels = <2>; rockchip,capture-channels = <2>; #sound-dai-cells = <0>; status = "okay"; }; the device appears and there are clicks in the speakers when switching on and off. @Merblud What alsa settings do you use to enable audio ?

Most likely, this is the reason. You have changed the default u-boot and the system will not be able to activate universal multi-boot. Restore the factory firmware using the USB Burn Tool and then taste it.

What kernel sources do you use ?

patch use SCLK_I2S_8CH kernel SCLK_I2SOUT_SRC https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-current/rk3399-add-sclk-i2sout-src-clock.patch Maybe I'm doing something wrong. I tried to use the patch (taking into account another parameter), but the device did not appear.

No If have test sample, it will take 2-3 hours to release the finished image (this is taking into account the complete build and testing / debugging of the launch).

No, I haven't tried putting it in SPI yet (I don't have exact instructions on how to do this).

You don't need these steps for s905x.

I added everything you used to DTS a long time ago, but the sound didn't work for me (due to the lack of settings for alsa), I thought my DTS settings weren't correct. I'm wondering how you found (defined) these parameters ?

Compiled in the Armbian build system ( with patches added).

No SPI - is very bad. Use an SD card (speed 50) or eMMC (speed 125) , if you have USB 3 (speed 340), to work - you need to be an idiot. At the same time, u-boot placement is possible only on SD\eMMC\SPI and therefore for the system to work with USB, you will have to have either an SD card (all SD cards are complete crap in speed and reliability and I generally consider them only as temporary media , such as CD\DVD on a PC), or buy an expensive branded EMMC module (almost 15$ for 8Gb), just for the sake of starting the system from USB. HK needs to be added before mass release SPI (only 4Mb is enough) and make it the main carrier for u-boot placement.

Added in the latest version 20200423 installation of the system in eMMC for Renegade Elite (rk3399) and now perezalivayu images on the site. I checked with myself, everything works. Now I have Armbian installed on EMMC in Renegade and a new feature has appeared-direct launch of other systems immediately from USB media (the connectors on the front line work).

If you haven't previously run any pirated stuff on this device (which blocks the execution of scripts), try the "toothpick"method.

Copy the file to the /boot directory and configure (uEnv.txt) to the new file. However, note that this file may not work with the current kernel and the system may not start, or it may not work with the new kernel when the kernel is updated. You will need to start the system from an external media and return the settings back.

These models need a different DTB. You need to edit this line and specify a different DTB. This string must either not exist, or it must start with the character # How have you tried using other DTB ? What systems were previously launched on these TV boxes ?