Search the Community

Hello, My Orange Pi Zero was working during a few days. However after a few days it stopped working. I tried to install a fresh armbian (and I also tried lot's of different distribution on several SD cards), and all of them are unable to boot. Today, I tried to plug an UART cable (USB <-> Serial) during boot in order to see what happened... And here is what I got : U-Boot SPL 2016.09.01-armbian (Nov 14 2016 - 08:40:41) DRAM: 0 MiB ### ERROR ### Please RESET the board ### (The date of armbian of course depends on the version I'm running). The RESET seems to refer to a power cycle reset (which I obviously do each time I try to restart), so I dont see what I can try to correct this problem. The "DRAM: 0MiB" let me think that it has some troubles to recognize the RAM, but I'm not sure to understand it correctly. Do you confirm that ? Do you have any idea to solve my problem ? Thank you, tobiasBora

I just ordered a couple of Orange Pi Zero systems to use in small IoT projects. Reading the forum I see the wireless for Orange Pi Zero might have issues. But some of the posts wanted to use it as an AP. That's not my case, I'll test them when they get here, but just how bad is it? I will not have a heavy load, but I would like something stable. When push comes to shove should I plan on using an Ethernet cable rather than the wifi?

Hello. Yesterday i tried to switch kernel in debian jessie 5.24 from 3.4.113 to 4.x using this article: To make sure you won’t run into conflicts within newly installed packages, remove them all before upgrade: 1 2 aptitude remove ~nlinux-dtb ~nlinux-u-boot ~nlinux-image ~nlinux-headers aptitude remove ~nlinux-firmware ~narmbian-firmware ~nlinux-$(lsb_release -cs)-root Proceed with install: 1 2 3 4 apt-get install linux-image-dev-sun8i linux-dtb-dev-sun8i linux-headers-dev-sun8i apt-get install linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero apt-get install armbian-firmware sunxi-tools swconfig a10disp reboot https://www.armbian.com/orange-pi-zero/ But there is no linux-u-boot-orangepizero-dev linux-$(lsb_release -cs)-root-dev-orangepizero packages in default repository. I used apt-cache search to find this packages, so I found this dev. packages for other Orange pi models, but not dev. packages for orange pi zero. How to switch kernel on Orange pi zero?

Thanks for your effort on this project. Much appreciated. I was able to follow this tutorial (10 minutes, 24 seconds in) on the Debian image to get the TV out working. I'm building scripts to modify the networking between a number of modes - super helpful to get a console access when I break something and lose all networking access. Is there support for this on the Ubuntu side? The simple "add 'tv' to the bottom of "/etc/modules" doesn't do anything. Please advise. Thanks!

This was my second attempt and it finished with exactly the same result. Console log: ~$ ssh admin@zero ___ ____ _ _____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.113-sun8i System load: 0.07 Up time: 3 min Memory usage: 9 % of 494Mb IP: 192.168.8.91 CPU temp: 34°C Usage of /: 18% of 7.2G [ 7 updates to install: apt-get upgrade ] Last login: Sat Feb 4 14:15:58 2017 from 192.168.8.111 ----------------------------------------------------------------------- 16:26:25 admin@zero:~$ sudo apt-get upgrade -y Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-firmware armbian-tools-jessie hostapd linux-headers-sun8i linux-image-sun8i linux-jessie-root-orangepizero linux-u-boot-orangepizero-default 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/20.9 MB of archives. After this operation, 2,142 kB of additional disk space will be used. (Reading database ... 57509 files and directories currently installed.) Preparing to unpack .../armbian-firmware_5.25_armhf.deb ... Unpacking armbian-firmware (5.25) over (5.24) ... Preparing to unpack .../armbian-tools-jessie_5.25_armhf.deb ... Unpacking armbian-tools-jessie (5.25) over (5.24) ... Preparing to unpack .../hostapd_1%3a2.5~armbian5.25+1_armhf.deb ... Unpacking hostapd (1:2.5~armbian5.25+1) over (1:2.5~armbian5.24.161202+1) ... Preparing to unpack .../linux-headers-sun8i_5.25_armhf.deb ... Unpacking linux-headers-sun8i (5.25) over (5.24) ... Preparing to unpack .../linux-image-sun8i_5.25_armhf.deb ... Unpacking linux-image-sun8i (5.25) over (5.24) ... Preparing to unpack .../linux-jessie-root-orangepizero_5.25_armhf.deb ... Leaving 'diversion of /etc/mpv/mpv.conf to /etc/mpv/mpv-dist.conf by linux-jessie-root-orangepizero' Unpacking linux-jessie-root-orangepizero (5.25) over (5.24) ... /var/lib/dpkg/info/linux-jessie-root-orangepizero.postrm: 2: [: missing ] Preparing to unpack .../linux-u-boot-orangepizero-default_5.25_armhf.deb ... Unpacking linux-u-boot-orangepizero-default (5.25) over (5.24) ... Processing triggers for systemd (215-17+deb8u6) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for initramfs-tools (0.120+deb8u2) ... update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i update-initramfs: Converting to u-boot format Setting up armbian-firmware (5.25) ... Setting up armbian-tools-jessie (5.25) ... Setting up hostapd (1:2.5~armbian5.25+1) ... Setting up linux-headers-sun8i (5.25) ... Compiling headers - please wait ... Setting up linux-image-sun8i (5.25) ... update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i update-initramfs: Converting to u-boot format Setting up linux-jessie-root-orangepizero (5.25) ... Setting up linux-u-boot-orangepizero-default (5.25) ... Updating u-boot on device /dev/mmcblk0 Processing triggers for initramfs-tools (0.120+deb8u2) ... update-initramfs: Generating /boot/initrd.img-3.4.113-sun8i update-initramfs: Converting to u-boot format Scanning processes... Scanning candidates... Scanning kernel images... Failed to retrieve available kernel versions. Restarting services using systemd... ----------------------------------------------------------------------- 16:31:19 admin@zero:~$ ls -lh /boot total 14M -rw-r--r-- 1 root root 123 Feb 4 14:20 armbianEnv.txt drwxr-xr-x 2 root root 4.0K Feb 4 16:29 bin drwxr-xr-x 2 root root 4.0K Nov 14 13:13 bin.old -rw-r--r-- 1 root root 6.8K Nov 14 13:14 boot.bmp -rw-r--r-- 1 root root 2.0K Nov 14 13:10 boot.cmd -rw-r--r-- 1 root root 2.1K Nov 14 13:15 boot.scr -rw-r--r-- 1 root root 95K Feb 2 06:01 config-3.4.113-sun8i -rw-r--r-- 1 root root 3.7M Feb 4 16:30 initrd.img-3.4.113-sun8i lrwxrwxrwx 1 root root 20 Nov 14 13:13 script.bin -> bin/orangepizero.bin -rw-r--r-- 1 root root 2.0M Feb 2 06:01 System.map-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Feb 4 16:30 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3.7M Feb 4 16:30 uInitrd-3.4.113-sun8i -rwxr-xr-x 1 root root 4.6M Feb 2 06:01 vmlinuz-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Feb 4 16:30 zImage -> vmlinuz-3.4.113-sun8i ----------------------------------------------------------------------- 16:32:50 admin@zero:~$ sudo cat /etc/network/interfaces # Wired adapter #1 allow-hotplug eth0 #no-auto-down eth0 iface eth0 inet dhcp #address 192.168.0.100 #netmask 255.255.255.0 #gateway 192.168.0.1 #dns-nameservers 8.8.8.8 8.8.4.4 # hwaddress ether # if you want to set MAC manually # pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838 link-speed 10 link-duplex full ethernet-autoneg off # Wireless adapter #1 # Armbian ships with network-manager installed by default. To save you time # and hassles consider using 'sudo nmtui' instead of configuring Wi-Fi settings # manually. The below lines are only meant as an example how configuration could # be done in an anachronistic way: # #allow-hotplug wlan0 #iface wlan0 inet dhcp #address 192.168.0.100 #netmask 255.255.255.0 #gateway 192.168.0.1 #dns-nameservers 8.8.8.8 8.8.4.4 # wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf # Disable power saving on compatible chipsets (prevents SSH/connection dropouts over WiFi) #wireless-mode Managed #wireless-power off # Local loopback auto lo iface lo inet loopback ----------------------------------------------------------------------- 16:33:27 admin@zero:~$ pstree systemd─┬─NetworkManager─┬─{NetworkManager} │ ├─{gdbus} │ └─{gmain} ├─2*[agetty] ├─cron ├─dbus-daemon ├─dhclient ├─haveged ├─lircd ├─ntpd ├─polkitd─┬─{gdbus} │ └─{gmain} ├─rsyslogd─┬─{in:imklog} │ ├─{in:imuxsock} │ └─{rs:main Q:Reg} ├─sshd───sshd───sshd───bash───pstree ├─systemd───(sd-pam) ├─systemd-journal ├─systemd-logind ├─systemd-udevd └─wpa_supplicant ----------------------------------------------------------------------- 16:35:03 admin@zero:~$ sudo reboot Connection to zero closed by remote host. Connection to zero closed. ----------------------------------------------------------------------- 16:35:13 ~$ ssh admin@zero ^C ----------------------------------------------------------------------- 16:40:15 ~$ nmap zero Starting Nmap 7.40 ( https://nmap.org ) at 2017-02-04 16:53 YEKT Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn Nmap done: 1 IP address (0 hosts up) scanned in 3.98 seconds ----------------------------------------------------------------------- 16:53:27 ~$ nmap -Pn zero Starting Nmap 7.40 ( https://nmap.org ) at 2017-02-04 16:53 YEKT Nmap scan report for zero (192.168.8.91) Host is up (0.00013s latency). All 1000 scanned ports on zero (192.168.8.91) are filtered Nmap done: 1 IP address (1 host up) scanned in 14.23 seconds ----------------------------------------------------------------------- 16:53:50 ~$ After previous attempt I just restored SD card from saved image, so I can do it again, sure, but it means that I can't use subsequent releases. Thanks.

After receiving several Orange Pi Zeros and a Pi+2E, I have been experiment on different ways to connect them using the g_ether and usbnet modules, and configuring the Zero OTG port as slave (mode 2). My last attempt was to use the Pi+2E as a data concentrator, connecting three different OPIZ on the independent USB channels, creating ethernet over USB links ... this have been my week's nightmare. By now these are my findings (could change with more information at hand). 1) The Pi+2E enables 4 different usb ports. The usb0 is the OTG microUSB port, and the usb1, usb2 and usb3 are the other exposed type A USB ports. 2) The usb0 has a particular MAC Address and all the other usb ports (1,2 and 3) share the same MAC Address. 3) Was impossible to have a reliable connection (with more than one OPIZ connected) when configuring the USB ports on different networks. 4) Was necessary to define a bridge on the three usb ports (1,2 and 3) to enable all the three OPIZ to see the Pi+2E (before that, "sometimes" one worked other times another one ... I was never capable to figure why or how). 5) When the bridge is on, everything works as a charm. 6) If one of the usb0 ports (in the OPIZ side) is disabled and re-enabled, the corresponding usbX port in the Pi+2E is separated from the bridge (disappear). And continue without working until the usbX por is re-added to the bridge manually on the Pi+2E side (brctl addif br0 usb0, when adding the usb0 to the bridge br0). 7) Oh yes ... I added hard disks on two of the OPIZ. When using PiDrives, have been necessary to provide external power with the WD special cable. With a SanDisk Z400s SSD this was not necessary. By now I have not been successful on enabling a dhcp server for the bridge on the Pi+2E side, although with static addresses everything work. The other thing I have no idea how to do is to automatically re-add some usb port that have been enabled by connecting something on the other side ... I have been thinking on creating a small daemon that pools on the bridge, but by now it is only an idea. I expect this to be of help for others, and any additional information will be welcomed. P.S. By the way, when connecting one Zero with another Zero from an OTG in one machine to the Type A in the other machine, everything is perfect. It is possible to add a PiDrive if the machine receiving electricity is the one with the drive. The other one will work well with the electricity offered by the OTG connector.

Hi I need to set static IP in eth0 and wlan0 in my OPi Zero using ARMBIAN Jessie. Googling around, I read a lot of controversial options, like edit /etc/network/interfaces and use nmtui, but, I couldn't set BOTH eth0 and wlan0 to a static IP. If I do it for eth0, wlan0 doesn't work and vice-versa. One guy said that after Debian Jessie version (https://nebulousthinking.wordpress.com/2016/02/25/setting-a-static-ip-for-raspbian-jessie-in-2016/), some things changed to set up static IP. Now, from Jessie, we need to edit /etc/ dhcpcd.conf, but, where is it ( dhcpcd.conf )? Can someone instruct me about how to set static IP, please? Sergio

Hi folks, I'm trying to figure out what the current status of USB OTG support is, as applies to the Orange Pi Zero. I'm trying to use the HID gadget features, but I'm triggering a segfault and stack dump when I try to set it up. I'm using the hidonly.sh script found here (https://github.com/crmulliner/hidemulation), with a tiny modification to make it more generic: - echo ci_hdrc.0 > UDC + ls /sys/class/udc > UDC On running the script, I get the following (using the serial console): I found this report, which appears to be identical, but I'm not sure what it means, or what I should do to get working OTG support on the OPi Zero. Is there a kernel which has working OTG gadget support for the OPi Zero? i.e. a non-dev one? This and WiFi are literally the only features I need, so I'm happy to sacrifice other drivers if it means getting this working. Thanks!

Can somebody help me, how to install teamviewer on Orange PI Zero? I want to do it via SSH. How to get ID and password of teamviewer after installing? (which one image https://www.armbian.com/orange-pi-zero/ is best for me? I need to view desktop...)

Orange Pi Zero - SPI1 - SPI_MOSI - Seems "weak" SPI_SCLK is Peak-to-Peak 3.3v (no problem) SPI_MOSI is Peak-to-Peak 165mv (whoa strange! hooked up to the o-scope) I suspect that MOSI is "dead" in my config since the waveform matches SPI_SCLK almost exactly, so perhaps it's crosstalk or something of that sort. I think my FEX is good. Anybody else with experience? Does anyone else experience this problem? root@orangepizero:/dev# ls -al spi* crw------- 1 root root 153, 0 Jan 28 12:17 spidev0.0 crw------- 1 root root 153, 1 Jan 28 12:17 spidev1.0 [spi0] spi_used = 1 spi_cs_bitmap = 1 spi_mosi = port:PC00<3><default><default><default> spi_miso = port:PC01<3><default><default><default> spi_sclk = port:PC02<3><default><default><default> spi_cs0 = port:PC03<3><1><default><default> [spi1] spi_used = 1 spi_cs_bitmap = 1 spi_cs0 = port:PA13<2><default><default><default> spi_sclk = port:PA14<2><default><default><default> spi_mosi = port:PA15<2><default><default><default> spi_miso = port:PA16<2><default><default><default> [spi_devices] spi_dev_num = 2 [spi_board0] modalias = "spidev" max_speed_hz = 33000000 bus_num = 0 chip_select = 0 mode = 0 full_duplex = 1 manual_cs = 0 [spi_board1] modalias = "spidev" max_speed_hz = 33000000 bus_num = 1 chip_select = 0 mode = 0 full_duplex = 1 manual_cs = 0

Has anyone successfully configured OPI0 AP working in the mainline kernel? I have tried to use the same configuration file with the 3.4 kernel, the hostapd started successfully, dnsmasq also running, but when client device trying to connect to the AP, the client is not able to obtain the IP address from the dnsmasq-dhcp server. the dnsmasq log: journalctl -f -- Logs begin at Sun 2017-01-22 13:30:20 UTC. -- Jan 22 14:47:52 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Jan 22 14:48:00 orangepizero dnsmasq-dhcp[1676]: DHCPDISCOVER(wlan0) cc:08:8d:d5:92:84 Jan 22 14:48:00 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Jan 22 14:48:07 orangepizero sshd[3727]: userauth_pubkey: key type ssh-dss not in PubkeyAcceptedKeyTypes [preauth] Jan 22 14:48:09 orangepizero dnsmasq-dhcp[1676]: DHCPDISCOVER(wlan0) cc:08:8d:d5:92:84 Jan 22 14:48:09 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Jan 22 14:48:10 orangepizero sshd[3727]: Accepted password for root from 192.168.2.101 port 62956 ssh2 Jan 22 14:48:10 orangepizero sshd[3727]: pam_unix(sshd:session): session opened for user root by (uid=0) Jan 22 14:48:10 orangepizero systemd-logind[555]: New session c5 of user root. Jan 22 14:48:10 orangepizero systemd[1]: Started Session c5 of user root. Jan 22 14:48:20 orangepizero dnsmasq-dhcp[1676]: DHCPDISCOVER(wlan0) cc:08:8d:d5:92:84 Jan 22 14:48:20 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Jan 22 14:48:26 orangepizero dnsmasq-dhcp[1676]: DHCPDISCOVER(wlan0) cc:08:8d:d5:92:84 Jan 22 14:48:26 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Jan 22 14:48:34 orangepizero dnsmasq-dhcp[1676]: DHCPDISCOVER(wlan0) cc:08:8d:d5:92:84 Jan 22 14:48:34 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Jan 22 14:48:42 orangepizero dnsmasq-dhcp[1676]: DHCPDISCOVER(wlan0) cc:08:8d:d5:92:84 Jan 22 14:48:42 orangepizero dnsmasq-dhcp[1676]: DHCPOFFER(wlan0) 192.168.43.125 cc:08:8d:d5:92:84 Here you can see DHCPOFFER, but the client didn't get the IP address. Any suggestions or working configuration file examples are appreciated.

Hi I am trying to compile a program test for my new OPi Zero that is running ARMBIAN. From a Hello World program test, I am trying to create a thread that will blink the led at PA17 gpio pin, but GCC's linker complains saying that can't locate pthread_create() function. I am using pthread.h. Somebody found similar issue? Sergio

Please, help! How i can set resolution - 800x480??

Ive just gotten a orange pi zero, fairly inexperienced with linux too. Ive been trying to get a distributed.net client running on it. Does anyone know if this is even possible? I tried a few differnt versions (ARMEL, ARM/eabi and ARM/ELF) always get a no such file or directory when trying to run them using ./dnetc Cheers

Hello Guys, I want to use airodump-ng (Aircrack-ng Suite) or Kismet to get all WiFi Clients in the area. For that, I would like to use the internal WiFi Chipset (so I don't have to use an external WiFi Dongle). My problem is, after I enable the monitor mode (with iwconfig and/or airmon-ng), which gives me no error and it says, the monitor mode is enabled, I am getting no results with Airodump-ng nor Kismet. Are there any solutions for this problem? Is is the driver not capeable of using monitor mode? Thanks in advance, KittFanNr1

I can't seem to get the Orange Pi Zero working as a USB gadget (libcomposite) to emulate a keyboard. Here's the script I'm using to test: #!/bin/bash cd /sys/kernel/config/usb_gadget mkdir g1 cd g1 echo "0x1d6b" > idVendor echo "0x0104" > idProduct mkdir strings/0x409 echo "1234567890" > strings/0x409/serialnumber echo "0x1d6b" > strings/0x409/manufacturer echo "0x0104" > strings/0x409/product mkdir functions/hid.usb0 echo 1 > functions/hid.usb0/protocol echo 1 > functions/hid.usb0/subclass echo 8 > functions/hid.usb0/report_length /bin/echo -ne \\x05\\x01\\x09\\x06\\xa1\\x01\\x05\\x07\\x19\\xe0\\x29\\xe7\\x15\\x00\\x25\\x01\\x75\\x01\\x95\\x08\\x81\\x02\\x95\\x01\\x75\\x08\\x81\\x03\\x95\\x05\\x75\\x01\\x05\\x08\\x19\\x01\\x29\\x05\\x91\\x02\\x95\\x01\\x75\\x03\\x91\\x03\\x95\\x06\\x75\\x08\\x15\\ x00\\x25\\x65\\x05\\x07\\x19\\x00\\x29\\x65\\x81\\x00\\xc0 > functions/hid.usb0/report_desc mkdir configs/c.1 mkdir configs/c.1/strings/0x409 echo Conf 1 > configs/c.1/strings/0x409/configuration echo 120 > configs/c.1/MaxPower ln -s functions/hid.usb0 configs/c.1 echo musb-hdrc.1.auto > UDC When trying to execute the script I get this crash: root@orangepizero:/usr/local/bin# bash -x hid_testing.sh + modprobe libcomposite + cd /sys/kernel/config/usb_gadget/ + mkdir -p g1 + cd g1 + echo 0x1d6b + echo 0x0104 + echo 0x0100 + echo 0x0200 + mkdir -p strings/0x409 + echo fedcba9876543210 + echo girst + echo Hardpass + N=usb0 + mkdir -p functions/hid.usb0 + echo 1 + echo 1 + echo 8 + echo -ne '\x05\x01\x09\x06\xa1\x01\x05\x07\x19\xe0\x29\xe7\x15\x00\x25\x01\x75\x01\x95\x08\x81\x02\x95\x01\x75\x08\x81\x03\x95\x05\x75\x01\x05\x08\x19\x01\x29\x05\x91\x02\x95\x01\x[ 84.870357] Unable to handle kernel NULL pointer dereference at virtual address 000000 02 75\x03\x91\x03\x95\x06\x75\x08\x15\x00\x25\x65\x05\x07\x19\x00\x[ 84.879054] pgd = ce2b8000 29\x65\x81\x00\xc0' + C=1 + mkdir -p configs/c.1/strings/0x409[ 84.887248] [00000002] *pgd=4e2c9835 + echo 'Config 1: ECM network' + echo 250 + ln -s functions/, *pte=00000000hid.usb0 configs/c.1/ + ls /sys/class/udc , *ppte=00000000 [ 84.908434] Internal error: Oops: 17 [#1] SMP THUMB2 [ 84.913394] Modules linked in: usb_f_hid libcomposite evdev sun8i_ths gpio_keys cpufreq_dt uio_pdrv_genirq uio thermal_sys [ 84.924552] CPU: 3 PID: 1208 Comm: ls Not tainted 4.9.0-sun8i #14 [ 84.930639] Hardware name: Allwinner sun8i Family [ 84.935339] task: ce1bb900 task.stack: ce26e000 [ 84.939914] PC is at alloc_ep_req+0x15/0x50 [libcomposite] [ 84.945396] LR is at kmem_cache_alloc+0xe3/0xf0 [ 84.949923] pc : [<bf84ad76>] lr : [<c01c1cb7>] psr: 200e0033 [ 84.949923] sp : ce26fde8 ip : 00000000 fp : c9d8e1ec [ 84.961388] r10: c9c61e94 r9 : cd402ac4 r8 : cd402b1c [ 84.966608] r7 : cd402aa8 r6 : ce0a2418 r5 : ce178480 r4 : 00000008 [ 84.973128] r3 : 00000000 r2 : ffffffff r1 : 00000000 r0 : ce178480 [ 84.979651] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA Thumb Segment none [ 84.986953] Control: 50c5387d Table: 4e2b806a DAC: 00000051 [ 84.992693] Process ls (pid: 1208, stack limit = 0xce26e210) [ 84.998347] Stack: (0xce26fde8 to 0xce270000) [ 85.002703] fde0: bf8570a4 00000000 c9c61e94 bf856461 c0b48ba8 cdbd9000 [ 85.010874] fe00: c9d8e1ec bf847923 c9c61e94 cd402aa8 cd402aa8 00000000 cd402b1c bf84778b [ 85.019046] fe20: cd402b1c c9c61eec 00000200 cd402aa8 00000100 bf84a4b9 00000055 c9d8e000 [ 85.027235] fe40: c9d8e260 ce0a3148 bf84c100 c9d8e298 00000000 cd220200 00000000 c9d8e1ec [ 85.035419] fe60: cd1b06c0 c9d8e1ec c0b48ba8 cdbd9000 00000051 c05429c3 cd220200 00000000 [ 85.043603] fe80: c0b48bc0 c0542ca1 00000000 cd1b06c0 fffffff0 c9d8e000 c9d8e190 00000011 [ 85.051792] fea0: cdadc180 bf84ab99 00037e98 00000000 00000011 cd4278c0 00000011 cd4278d8 [ 85.059982] fec0: ce26ff80 c021de13 ce26ff80 cdadc180 c021dd81 c0712138 ce26ff80 00037e98 [ 85.068172] fee0: 00000011 00000000 00000000 c01cf3f7 50c5387d ce26ffb0 c0b08f2c 000001ff [ 85.076361] ff00: b6f2f120 c010121b 00000000 00000000 585423be 2aedab11 585423be 2aedab11 [ 85.084551] ff20: 585423be 2aedab11 00003077 00000000 bec70370 b6f4bd58 cdadc180 00000011 [ 85.092740] ff40: 00037e98 ce26ff80 00037e98 00000000 00000000 c01cfe5f 0000000e 000081a4 [ 85.100929] ff60: 00000001 cdadc180 cdadc180 00000000 00000000 00037e98 00000011 c01d09df [ 85.109118] ff80: 00000000 00000000 585423be 00000011 00037e98 b6f4bd58 00000004 c0105fe4 [ 85.117307] ffa0: ce26e000 c0105e21 00000011 00037e98 00000001 00037e98 00000011 00000000 [ 85.125496] ffc0: 00000011 00037e98 b6f4bd58 00000004 b6f4c0ac 00000001 b6f9c000 00000000 [ 85.133686] ffe0: 00000000 bec72ae4 b6eaf79b b6eeaf96 000e0030 00000001 4eff6861 4eff6c61 [ 85.141926] [<bf84ad76>] (alloc_ep_req [libcomposite]) from [<bf856461>] (hidg_bind+0x64/0x1d0 [usb_f_hid]) [ 85.151699] [<bf856461>] (hidg_bind [usb_f_hid]) from [<bf84778b>] (usb_add_function+0x3a/0xc4 [libcomposite]) [ 85.161740] [<bf84778b>] (usb_add_function [libcomposite]) from [<bf84a4b9>] (configfs_composite_bind+0x1cc/0x2d8 [libcomposite]) [ 85.173421] [<bf84a4b9>] (configfs_composite_bind [libcomposite]) from [<c05429c3>] (udc_bind_to_driver+0x1b/0x74) [ 85.183785] [<c05429c3>] (udc_bind_to_driver) from [<c0542ca1>] (usb_gadget_probe_driver+0xa1/0xe4) [ 85.192859] [<c0542ca1>] (usb_gadget_probe_driver) from [<bf84ab99>] (gadget_dev_desc_UDC_store+0x80/0x94 [libcomposite]) [ 85.203845] [<bf84ab99>] (gadget_dev_desc_UDC_store [libcomposite]) from [<c021de13>] (configfs_write_file+0x93/0xec) [ 85.214469] [<c021de13>] (configfs_write_file) from [<c01cf3f7>] (__vfs_write+0xf/0xb4) [ 85.222487] [<c01cf3f7>] (__vfs_write) from [<c01cfe5f>] (vfs_write+0x6f/0x13c) [ 85.229811] [<c01cfe5f>] (vfs_write) from [<c01d09df>] (SyS_write+0x2b/0x64) [ 85.236871] [<c01d09df>] (SyS_write) from [<c0105e21>] (ret_fast_syscall+0x1/0x4c) [ 85.244456] Code: d0d8 4605 b190 6a73 (f993) 2002 [ 85.249310] ---[ end trace 5a400d152710de10 ]--- hid_testing.sh: line 27: 1208 Segmentation fault ls /sys/class/udc > UDC Apparently this line is what kicks it off: ls /sys/class/udc > UDC Running this command you can see that it should simply output "musb-hdrc.1.auto" to the "UDC" file: root@orangepizero:/usr/local/bin# ls /sys/class/udc musb-hdrc.1.auto Sending that to the UDC file is basically the final step in initializing a USB gadget. So something in the USB gadget driver is failing to work properly and I haven't the foggiest idea of how to troubleshoot this further. It *seems* like it's a bug but I could be doing something wrong. Any assistance is appreciated.

Here's a small entry about tracking airplanes using the Orange Pi Zero. I was looking recently to get quick and easy plus cheap way to build such base station. Hope you like it, I've set it up all for newbies (ENG/POL): https://blog.jokielowie.com/en/2017/01/sledzimy-samoloty-cz-2-ads-b-i-mlat-najtanszy-odbiornik-dla-flightaware-oraz-flightradar-24/

Hello, I'd like to disable the yellowish and green ethernet port LEDs on Orange Pi Zero. At night, it becomes quite shiny and is really disturbing. Any methods to do this on the software end? If not, I'm planning to apply some nail polish :-/ Thanks in advance,

Hello, I've been trying to use DNSCrypt on ARMBian Debian on OrangePi Zero. I'm following this guide (exact revision link for future reference), and it was working great on Raspbian in Raspberry Pi, When I try the same guide, it compiles, installs successfully, runs the daemon, however it doesn't actually work, saying "connection timed out; no servers could be reached". When I'm not using daemon, and run manually, this time it says "Unable to bind (TCP)". But when I compile and use in Ubuntu, it works nicely. This is my GitHub issue on DNSCrypt repository, including all my tests and inputs: https://github.com/jedisct1/dnscrypt-proxy/issues/561 I'd appreciate your input, why it's working in Ubuntu and why not in Debian ? Images are downloaded from official link, and are version 5.2.4. Any idea would be appreciated. Thanks in advance,

A quick one... is there an estimated date on when a stable version (next version) will be released for OPI Zero...? I am looking for to have the following included: > Full H2+ support / would be great with the goal to to force the power consumption to the lower side > SPI boot from USB > Working serial gadget / Serial through OTG

I got OPi with the 2xUSB official HAT and noticed that it is running very hot: 52 when starting and going to 62 after a while - just idling: Time CPU load %cpu %sys %usr %nice %io %irq CPU 18:56:12: 912MHz 0.20 2% 1% 0% 0% 0% 0% 55°C 18:56:17: 240MHz 0.18 2% 1% 0% 0% 0% 0% 54°C 18:56:23: 240MHz 0.25 2% 1% 0% 0% 0% 0% 56°C System is: # cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepizero BOARD_NAME="Orange Pi Zero" VERSION=5.24 LINUXFAMILY=sun8i BRANCH=default ARCH=arm Linux orangepizero 3.4.113-sun8i #50 SMP PREEMPT Mon Nov 14 08:41:55 CET 2016 armv7l GNU/Linux (no SPI flash, 256M version) This is AFTER two heatsinks applied. System has single DVB-T stick with tvheadend idling. WiFi is not connected but not turned off as it kills the eth interface communication (link is OK) but that as different issue The only other not standard thing is the original chassis from the store (yeah it just looks sweet, no intention on using it really). Question: Is the default armbian configured to feed to high voltage as mentioned in the "Orange Pi Zero went to market" thread? Or is this just the chassis/case?

Anyway, so here is another i can't log in my Orange Pi Zero, tried both images with Etcher, So where am i? It's a bit weird, i try various USB wall chargers and sd cards, but it always get to the same point: Permission denied, please try again. root@192.168.1.19's password: So let me ask you guys something, am i doing something Stupid, if i plug this into my modem, i can ssh to it yeah? there nothing i need to do? So i Nmaped it and sore that the vnc port is open, so password for that is 1234 as well? Like i went through the source, and i can see that the password is 1234, so the only thing that i can put it to is the setup of the sdcard but Etcher verifies the image right? So really i must have some bad powered usb ports? How correct would you say my analysis is?

Hi Everyone I have a small problem, I recently purchased a OrangePi Zero and wanted to run Armbian on it, I downloaded the last stable release 3.4 (Debian Jesse) and prepped my Adata 32gb with Etcher same way I did my Opi Lite, and placed it in the Opi, and nothing happened , it doesnt boot up at all if I apply power (I can see both ethernet leds but not the power LED) I disconnected it and connect my Uart cable to the Zero and confirmed there is no output when you power it on, I then tried the Xenial build and still nothing, I downloaded the latest nightly 4.9 and Boom ,works like a dream I get output via Uart and can use the terminal to configure it. My Problem is I need 3.4 as I want to use composite video out and AFAIK (according to another post here) composite doesn't work on 4.9. Its probably a N00b problem , but I really would like to get it working, the images from orange pis official site works fine ,but they are pretty bad (terrible). PS I am sorry if this has been asked before but I checked several pages back on the forum and couldnt find anything. Kind Regards

Hi, I receive 16 bytes every 0.5 seconds. This should be saved as text or as MySQL table data. Need to compare with all existing records , process and display it on 3.5 inch TFT LCD on SPI ( Notro fbtft ) and also save to SD Card . It should be broadcasted to a fixed Ip using TCPIP. Can I use Orange Pi Zero with 512MB Ram ? Can I partition Ram as RAMFS OR TMPFS to do all read only tasks thus save time for slow SD CARD writes ? Can I first copy boot files and my app,tables to Ram and start from Ram ? Any suggestions ? Thanks

Hi Just got my first Orange Pi Zero today. Everything looking good, with the exception, if I run iperf tests between this and a linux host, the Orange Pi Zero will reboot without any error messages. I changed my power supply to a wall plug which can support 2.4amp easily, also tried to tune down the frequency to 900Mhz max, 4 cores, turned off HDMI/GPU, USB. DRAM is at minimum, 408 I think. Temperature remains at 55 to 58C Still once a while during heavy network, the board will reboot. The image i used is the legacy image posted on orange pi zero, Armbian_5.24_Orangepizero_Debian_jessie_3.4.113 Thanks Jerry