gounthar

gounthar,
activate 1wire, edit armbianEnv.txt, connect the sensor (with pull-up resistor) to the pi pins correctly, and it will work everything

I mount this one on Hikey970
I can only recommend!
 

Mine also arrived last week. They are around 40% bigger than stock for Tinkerboard.

They are finally here. Still waiting for the thermal adhesive.

@Ernest Kusa seeing your compile did work so well I was a little bit more "brave" and compiled the dev version
Armbian bullseye with Linux 5.6.5-sunxi   (non-minimal = console only image)
 
Also here no more problems - on my site - with ethernet going down/up.
Audio is working like on your current compiled image
I didnt check emmc, because I want to have there the android inside.
 
Welcome to Armbian bullseye with Linux 5.6.5-sunxi No end-user support: built from trunk & unsupported (bullseye) userspace! package bsp-kernel[20.05.0-trunk.111] u-boot[20.05.0-trunk] dtb [20.05.0-trunk.111] firmware [20.05.0-trunk] config[20.05.0-trunk] branch[dev] System diagnosis information will now be uploaded to http://ix.io/2iOj

@Ernest Kusa Thanks for compiling  Did you use some special options in the armbian-build-system or just stadard?

Analog-Audio and HDMI sound is working on my Sunvell R69 with red pcb (1GB Ram).
Analog-Audio is only set to a very low volume.

Do a 
apt install alsa-utils mpg123
and use
alsamixer
to set Line-Out and DAC to a value around 75 (upper limit of the white range)
 
I could play internetradio just fine
 
Analog-Audio: mpg123 -v -b 1024 -a hw:0,0 -@ ./MP3_FFH80s HDMI: mpg123 -v -b 1024 -a hw:1,0 -@ ./MP3_FFH80s aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: allwinnerhdmi [allwinner-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Welcome to Armbian buster with Linux 5.4.33-sunxi No end-user support: built from trunk package bsp-kernel[20.05.0-trunk] u-boot[20.05.0-trunk] dtb [20.05.0-trunk] firmware [20.05.0-trunk] config[] branch[current]  
MP3_FFH80s

If I interpret the schematics correctly, all LEDs are hardwired to power rails or SATA controller.
So there is no way to change the functionality via software.
The only way to get your desired functionality is to add an additional LED via GPIO pin and apply proper DT configuration.

Slightly improved and simplified script (still room for improvement, I guess).
 
#!/bin/bash if [ ! -d /sys/class/pwm/pwmchip1/pwm0 ]; then echo 0 > /sys/class/pwm/pwmchip1/export fi sleep 1 while [ ! -d /sys/class/pwm/pwmchip1/pwm0 ]; do sleep 1 done ISENABLE=`cat /sys/class/pwm/pwmchip1/pwm0/enable` if [ $ISENABLE -eq 1 ]; then echo 0 > /sys/class/pwm/pwmchip1/pwm0/enable fi echo 50000 > /sys/class/pwm/pwmchip1/pwm0/period echo 1 > /sys/class/pwm/pwmchip1/pwm0/enable # max speed run 5s echo 0 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle sleep 5 echo 49994 > /sys/class/pwm/pwmchip1/pwm0/duty_cycle declare -a CpuTemps=(75000 63000 58000 52000 48000 0) declare -a PwmDutyCycles=(25000 37000 48300 49250 49300 49994) while true do temp=$(cat /sys/class/thermal/thermal_zone0/temp) for i in 0 1 2 3 4 5; do if [ $temp -gt ${CpuTemps[$i]} ]; then DUTY=${PwmDutyCycles[$i]} echo $DUTY > "/sys/class/pwm/pwmchip1/pwm0/duty_cycle"; #echo "temp: $temp, target: ${CpuTemps[$i]}, duty: $DUTY" break fi done sleep 2s; done  

Hi all,
 
So if a lot of you maybe know is a heatsink and fan  a must for the OrangePi 4. With my temporarly installed fan makes a lot of noise i maked yesterday the step to order a Noctua NF-A4x20 5V PWM. The price was arround €17,- not the cheapest but te reviews are amazing.
 
Even on full speed its a lot more silence then the 20x20 mini fan but with a good air flow. But as you could read did i choose for a PWM variant so i could control the rpm´s with a PWM GPIO pin. And amazingly it did work! I have the PWM pin connected to pin 7 of the OrangePi 4.
 
Commands to start pwm for the first time:
 
cd /sys/class/pwm/pwmchip1/ echo 0 > export echo 1000000 > pwmchip1/pwm0/period echo 500000 > pwm0/duty_cycle #and with this step the fan goes on a lower speed echo 1 > pwm0/enable #and back on full speed without PWM echo 0 > pwm0/enable  
So it´s really nice. And i found a nice script for the Nanopi M4 with also a RK3399 chip from @mar0ni in this topic
 
To make it complete i paste also here the script from @mar0n

After transferring Armbian from SDCard to eMMC, next time you wish to boot SDCard, it will be less painful, no more needs of TP50265 ...
Simply stop U-Boot with spacebar, then you can select SD with "setenv devnum 1" followed by "run mmc_boot".
 
You need to switch firmware to another version :
mv /lib/firmware/brcm/brcmfmac4356-sdio.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin-ORIG mv /lib/firmware/brcm/brcmfmac4356-sdio.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt-ORIG cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.bin /lib/firmware/brcm/brcmfmac4356-sdio.bin cp /lib/firmware/brcm/brcmfmac4356-sdio-nanopi-m4v2.txt /lib/firmware/brcm/brcmfmac4356-sdio.txt  

You should change the "verbosity=1" to "verbosity=7" in /boot/armbianEnv.txt

Here it is : https://mega.nz/file/fS5XhTQI#_7bZ_jw4XdqFWc_9x6wAI1s07sEnKoamqOBqhMf_hc8
 

Updated to 4.14.176
https://github.com/armbian/upload/pull/23

This U-Boot seems to be pretty old ...
 
The one I built recently is booting fine 5.6.2 from eMMC :
DDR Version 1.24 20191016 In soft reset SRX Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 307 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67497 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xa5d94 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.01-armbian (Apr 06 2020 - 16:14:46 -0400) Model: Orange Pi RK3399 Board DRAM: 2 GiB PMIC: RK808 MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Orange Pi RK3399 Board rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 19 ms (150.4 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 209 bytes read in 16 ms (12.7 KiB/s) 7746799 bytes read in 755 ms (9.8 MiB/s) 22217216 bytes read in 2122 ms (10 MiB/s) 74021 bytes read in 38 ms (1.9 MiB/s) 1266 bytes read in 33 ms (37.1 KiB/s) Applying kernel provided DT overlay rockchip-spi-spidev.dtbo 2698 bytes read in 33 ms (79.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7746735 Bytes = 7.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 7d7be000, end 7df214af ... OK Loading Device Tree to 000000007d743000, end 000000007d7bdfff ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.6.2-rockchip64 (root@giroles-hpel8300) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #trunk SMP PREEMPT Mon Apr 6 16:26:34 EDT 2020 [ 0.000000] Machine model: Orange Pi RK3399 Board ...  

Small update.
 
We are able to create one cycle of a full sbc-bench, io and network testing in around 1h on all devices at once. Tests are still distant from perfection, but slowly we are getting some overview which will tell where to look closely https://dl.armbian.com/_test-reports/2020-04-14_09.06.24.html
 
 
 
 

It seems to be clear that DTB is missing ...

Maybe a small timer relay triggere by mains voltage that opens the 5v to the sbc for a second?

There is also this one, although not a fork of the previous : https://github.com/Jeremie-C/OrangePi.GPIO
 

Why don't you use well known lib like :
 
https://github.com/duxingkei33/orangepi_PC_gpio_pyH3
 
I think there is also a fork of it for specific OPiZero, which will avoid tweaking the mapping.h for the pins.

Two new boards have been tested.
This one did not work for me, partially because I did not understand what it is supposed to do... It's written in Chinese, and I have not been able to get 5V out of it... yet, only 4.2V.
This second one worked for me despite my very crude soldering job and the salvaged 18650.
So, after a few dozens of minutes charging the battery, I just unplugged the power on the charging board, and did not get any error on the OrangePi Zero...
Now, I would like to get some information on the voltage and other relevant information on the board to see if that's working properly, or if it's just luck...
And... I have to plug the 3.3V step down converter to one GPIO pin (linked to the main power), and see what's going on.

Here is what I did with one of mine - added $7.5 neo core as standalone terminal with back to back ethernet and serial connections :-)
 
 

Took some time to resume working on it...
 
At the moment, i'm only able to get Kodi working fine with hw decoding.
MPV and VLC are a no-go.
 
MPV log
 
 

Hi, what about h616? is there something compatible yet?

New Armbian CI autotest facility:

Switch: https://amzn.to/2w91QIZ
USB PSU: https://amzn.to/2R2mzW8
HUB: https://amzn.to/343ysQS
 

 

I will answer my own question. After adding voltage debug to statistics I have concluded that regulator 10 is for the four ARM A53 and regulator 23 is for the two ARM A72.

if anyone interested files here https://github.com/Freddan-67/rpimonitor-armbian.git