gounthar

Thanks. I don't know yet what this output means, but I'll find out. Anyway, I tried to install RPi-Monitor, but it looks like something failed along the path: sudo armbianmonitor -r Installing RPi-Monitor. This can take up to 5 minutes. Be patient pleaseE: Unable to locate package rpimonitor /usr/bin/armbianmonitor: line 697: /usr/share/rpimonitor/scripts/updatePackagesStatus.pl: No such file or directory Now patching RPi-Monitor to deal correctly with H3 Now you're able to enjoy RPi-Monitor at http://192.168.0.21:8888 poddingue@orangepizero-ups:/sys/bus/w1/devices$ wget http://192.168.0.21:8888 --2020-04-21 21:55:21-- http://192.168.0.21:8888/ Connecting to 192.168.0.21:8888... failed: Connection refused.

[ 11.862342] Driver for 1-wire Dallas network protocol. [ 11.881792] gpio-10 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 11.914947] w1_master_driver w1_bus_master1: Attaching one wire slave 28.3c01a8160ce7 crc a8 It looks like it has been detected. I now have to find where the information is stored. I may have found it: cat /sys/devices/w1_bus_master1/28-3c01a8160ce7/hwmon/hwmon0/temp1_input 23437 Thanks a lot!

Thanks a lot, folks, that will help me for sure!

I'm about to start tinkering with a DS18B20 clone on an Orange Pi Zero running Armbian buster with Linux 5.4.31-sunxi. I will re-read the whole thread to avoid any obvious mistake.

I now have to get the I2C screen working and at the same time handle some PWM output to control this board. I tried user space io, and it worked out of the box (with a LED for the time being). Next step: get a DS18B20 to work...

Thanks @martinayotte, that made the trick. The board still has lots of connectivity problems, as I lose the Wifi connection a few tens of seconds after the boot (I am able to do a sudo apt update, and then, it's gone).

I got it, thanks a lot.

Hi, I now have the habit to use the status LEDs on my Orange Pi Zero(s), and would like to do the same on my RK3399. The files indicated in this thread don't exist for the version of Armbian I'm using (very recent build by @martinayotte). Is there anything I can add to have some kind of hearbeat or mmc use with the LEDs? The heatsink is way too small, and I'm getting lots of brutal shutdown... Thanks.

I now have a working OrangePi RK3399, thanks a lot. I haven't seen on the download page that the wifi was non fonctional, so do we have to use a Wifi USB stick?

Ok, I think I managed to get the pads to work ONE time... And I managed to boot Armbian, thanks a lot for your help and patience... Now, I'm using it through one USB2UART thingie on an OrangePi Zero, but I don't have all the characters... So... Quick quick quick add Wifi via command line, and let's go to work. Thanks a ton for your help!

Almost, except if the pads are really worn out... The "almost" is because I'm still afraid of the chair-to-keyboard interface problem...

Ok, the image does not change the message... I guess my RK3399 boards (1*2GB 1*4GB) can't use the TP50265 anymore... Or is it a chair-to-keyboard interface problem?

Thanks a bunch, I will give it a try.

Would you mind sharing your image @martinayotte?

I now can remember why I had put this board aside for a few months... Whenever I think I managed to get it to start on the SDCard, I get DDR Version 1.08 20170320 In hannel 0: DDR3, 800MHz BMB 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 pmoot1: 2017-04-07, version: 1.06 CPUId = 0x0 ChipType = 0x10, 1838 2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=15193MB FwPartOffset=2000 , 0 StorageInit ok = 195484 LoadTrustBL No find bl30.bin o find bl32.bin unBL31 0x40000 NOTI 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 INFO: BL31: Initializing BL32 and nothing else. Never. Ever.

Thanks. I think this card has the eMMC kind of broken. By jumper, do you mean the test pads shorcut, because I can't see any jumper on the board...

And another... Armbian_20.02.1_Orangepi-rk3399_bionic_legacy_4.4.213_desktop 940 bytes read in 22 ms (129.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 17 ms (5.9 KiB/s) 36013 bytes read in 583 ms (14.1 MiB/s) 0492296 bytes read in 1341 ms (14.6 MiB/s) ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! * File not found /boot/dtb/rockchip/overlay/rockchip-fixup.scr ** Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... => CTRL-A Z for help | 1500000 8N1 | I suppose that the board is the problem, and not each and every Armbian image.

Same with image Armbian_20.02.1_Orangepi-rk3399_buster_legacy_4.4.213 canning mmc 1:1... ound U-Boot script /boot/boot.scr 40 bytes read in 22 ms (129.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 17 ms (5.9 KiB/s) 674569 bytes read in 520 ms (14.1 MiB/s) 0492296 bytes read in 1338 ms (14.6 MiB/s) * File not found /boot/dtb/ ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ile not found /boot/dtb/rockchip/overlay/rockchip-fixup.scr ** # Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7674505 Bytes = 7.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... =>

Hi, I tried today the latest image Armbian_20.02.1_Orangepi-rk3399_buster_current_5.4.20_desktop.img for the Orange Pi RK3399, and got ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 17 ms (5.9 KiB/s) 34210 bytes read in 487 ms (14 MiB/s) 0722176 bytes read in 1353 ms (14.6 MiB/s) * File not found /boot/dtb/ ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 698 bytes read in 32 ms (82 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7134146 Bytes = 6.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... K ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... I know my board is nit-picky, and I will try another image, but does the log says anything that could be helpful? Thanks.

Thanks. There are a few pointers there. I should maybe put the Zero to sleep and not shut it down... so that I can wake it up via GPIO?

The UPS is working as expected, but I still have a problem. If I do a clean shutdown, the board never starts again by itself, because it still has 5V on the micro USB. I guess that if there is no main power source for a while, the charger board will cut the 5V, but it will also take some time before it gives power back to the OrangePi Zero once we plug it in the main power source. Would it be possible to trigger the boot of the OrangePi once we get the main power source back?

Thanks!

If there is one better suited library for the Zero, I will gladly use it. Thanks.

I see...

Hi team, I am trying to get a voltage drop (3.3V to about 0V) detected on a GPIO pin on my OrangePi Zero running Armbian buster 20.02.1 with Linux 5.4.31-sunxi. I have another OrangePi Zero on which I have already managed to install I2C OLED screen, and the i2cdetect was working, and so on... For this one, I got a problem with the gpio group not existing. As I tried to install OPi.GPIO, I got usermod: group 'gpio' does not exist It's an Armbian version that I downloaded yesterday, and upgraded today with armbian-config. So... What did I do the wrong way? Thanks.