gounthar

Do you think we could get the patch

Hi there, I don't know yet much about the USB gadget framework, but was wondering it I could use it to make an Orange Pi Zero or One seen as a video sink by the host computer. I know the framework should allow the board to be seen as an audio source, a video source, a Midi device and other things, but could it be seen as a video consumer of some sort ? My goal would be to grab the host's webcam content, encode and stream it on the SBC so that the host's CPU still has resource for other tasks. Does it make sense ? Thanks.

Thanks a lot @sfx2000, I will give it a try. ;-)

Well, I have a big heatsink AND a fan running. Without the fan, the temperature goes quickly around 83/84°C. It does not hang up though. These days, it runs around 53°C in the afternoon with a full Rosetta load.

I have updated my 4B with armbian-config today, and I think that now the temperature readings are wrong. It's cold in here, the board is working for Rosetta, but before the update, it was running at full throttle at 42°C, and now it's written 83°C. The big heatsink is cold, the fan is on. There's something fishy.... ___ ____ _ _ _ / _ \ _ __ __ _ _ __ __ _ ___| _ \(_) | || | | | | | '__/ _` | '_ \ / _` |/ _ \ |_) | | | || |_ | |_| | | | (_| | | | | (_| | __/ __/| | |__ _| \___/|_| \__,_|_| |_|\__, |\___|_| |_| |_| |___/ Welcome to Armbian buster with Linux 5.4.43-rockchip64 System load: 5.30 4.19 4.05 Up time: 3:21 Local users: 3 Memory usage: 67 % of 3868MB Zram usage: 16 % of 1023Mb IP: 192.168.0.46 192.168.0.43 CPU temp: 83°C Usage of /: 45% of 15G Last login: Fri Jun 5 19:51:59 2020 On another subject, has anyone attempted to install and use libraries/SDK for the NPU? Thanks.

I had a lot of stability issues with the original Orange Pi image, and it's running like a charm with Armbian. Thanks, folks!

Reading further in the tutorial mentioned earlier, I changed the content of /etc/systemd/system/parprouted.service [Unit] Description=proxy arp routing service Documentation=https://raspberrypi.stackexchange.com/q/88954/79866 [Service] Type=forking # Restart until wlan0 gained carrier Restart=on-failure RestartSec=5 TimeoutStartSec=30 ExecStartPre=/usr/bin/perl -e 'sleep 1 until -e "/sys/class/net/wlan0"' ExecStartPre=/bin/echo 'parprouted: wlan0 is online' # clone the dhcp-allocated IP to eth0 so dhcp-helper will relay for the correct subnet ExecStartPre=/bin/bash -c '/sbin/ip addr add $(/sbin/ip -4 addr show wlan0 | /bin/grep -Po "\\d+\\.\\d+\\.\\d+\\.\\d+\/")32 dev eth0' ExecStartPre=/sbin/ip link set dev eth0 up ExecStartPre=/sbin/ip link set wlan0 promisc on # v minus sign ExecStart=-/usr/sbin/parprouted eth0 wlan0 ExecStopPost=/sbin/ip link set wlan0 promisc off ExecStopPost=/sbin/ip link set dev eth0 down ExecStopPost=/bin/bash -c '/sbin/ip addr del $(/sbin/ip -4 addr show eth0 | /bin/grep -c1 -Po "\\d+\\.\\d+\\.\\d+\\.\\d+")/32 dev eth0' [Install] WantedBy=multi-user.target And the error is gone. My PC still can't see the network, but we're progressing.

I tried another way with arp proxy, following this tutorial, but at the end, I only get Apr 24 00:04:54 localhost systemd[1]: parprouted.service: Scheduled restart job, restart counter is at 249. Apr 24 00:04:54 localhost systemd[1]: Stopped proxy arp routing service. Apr 24 00:04:54 localhost systemd[1]: Starting proxy arp routing service... Apr 24 00:05:00 localhost systemd-networkd-wait-online[3263]: Event loop failed: Connection timed out Apr 24 00:05:00 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:00 localhost bash[3286]: Error: any valid prefix is expected rather than "/32". Apr 24 00:05:00 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:00 localhost systemd[1]: parprouted.service: Failed with result 'exit-code'. Apr 24 00:05:00 localhost systemd[1]: Failed to start proxy arp routing service. Apr 24 00:05:05 localhost systemd[1]: parprouted.service: Service RestartSec=5s expired, scheduling restart. Apr 24 00:05:05 localhost systemd[1]: parprouted.service: Scheduled restart job, restart counter is at 250. Apr 24 00:05:05 localhost systemd[1]: Stopped proxy arp routing service. Apr 24 00:05:05 localhost systemd[1]: Starting proxy arp routing service... Apr 24 00:05:12 localhost systemd-networkd-wait-online[3295]: Event loop failed: Connection timed out Apr 24 00:05:12 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:12 localhost bash[3298]: Error: any valid prefix is expected rather than "/32". Apr 24 00:05:12 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:12 localhost systemd[1]: parprouted.service: Failed with result 'exit-code'. Apr 24 00:05:12 localhost systemd[1]: Failed to start proxy arp routing service. Apr 24 00:05:17 localhost systemd[1]: parprouted.service: Service RestartSec=5s expired, scheduling restart. Apr 24 00:05:17 localhost systemd[1]: parprouted.service: Scheduled restart job, restart counter is at 251. Apr 24 00:05:17 localhost systemd[1]: Stopped proxy arp routing service. Apr 24 00:05:17 localhost systemd[1]: Starting proxy arp routing service... I will investigate.

Super cool, ubobrov! I unfortunately have to address other issues, but I sure will come back one of these days to try H264 encoding on Orange Pi Zero running mainline.

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).