Search the Community

Hi, Is there any way to set all gpio to low in OPI Zero during de boot? becouse my OPI Zero is turning on some devices when is turning on. i've been searching about this problem but i couldn't find any solution. ty!

hi, I had a few Orange Pi Zero's lying around for a while and thought of putting them to some use. I was trying to find an image for Orange Pi Zero H2+ over here ( at Armbian Orange Pi downloads section ). I couldn't find the image for Orange Pi Zero H2+. There are images for H3 and H5 on that page. Can someone please point to the appropriate image for this board? Thanks a lot.

Hi, is it possible to run xfce4 on mainline on a Orange Pi Zero? I'm doing it with jessie legacy (I need to have a mumble client running, accessing it with X11vnc) but I wanted to upgrade. I've tried the same setup but without any luck. apt-get install --no-install-recommends xserver-xorg apt-get install --no-install-recommends xinit apt-get install xfce4 xfce4-terminal tango-icon-theme gnome-icon-theme lightdm lightdm fails to start on boot and startx tells me: Fatal server error: (EE) no screens found(EE) Have somebody done it and can it be done easily?

dear friends i used 20 Opi zero with armbian 5.38 for communicating over ttyS1 to Megatec UPS devices boards should send string on baud rate 2400 to UPS with RS232-To-TTL and get answer and work normally for the first time bur after a while serial stop transmitting data at all restart , stop-start ,... not fix problems the only way to fix the problem is connecting ttl to rs232 to pc and connect to serial with putty after that serial started send and receiving data and can use to communicate to ups devices i faced this problems on 9 of 20 boards programming language in python Thank you in advance!

In the context of this topic, after removing network-manager and configuring the network "the old way", via /etc/network/interfaces, what is the proper way to make sure that the WiFi radio is not emitting? I plan to place my OPi Zero next to the router (wired connection) and I want to make sure there's no unneeded radio interference. My /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp

I've been using an OrangePi Zero hw rev. 1.5 for a few months with no issues, using the Stretch mainline image (4.x kernel). Suddenly the filesystem became read-only. I thought it was a SD card issue so I burned a fresh armbian to a new card. But the device does not show up in the DHCP pool with an allocated IP. Being withought a HDMI connector, an OPi Zero must be accessed via SSH. I've tried all versions, mainline and legacy. Only with Jessie legacy image, it gets an IP from the DHCP pool just on the very first boot. After that, it does not show up. I've tried the images provided by OrangePI and their Ubuntu and Raspbian images work. They have Ubuntu 14.x and Raspbian Jessie. Another strange behavior: the device has different MACs, depending an the distribution used. I think maybe it's something related to this, being one of those el-cheapo adapters with no proper MAC?

4.14.65-sunxi on an Orange Pi Zero. Trying to set the i2c bus speed to 400kHz using the following dts: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&i2c0>; __overlay__ { clock-frequency = <400000>; }; }; }; Which produces: Error: dtc does not support compiling overlays Please try to install matching kernel headers Installed linux-headers-next-sunxi and still getting the same thing. Device tree compiler version: DTC 1.4.2. What am I doing wrong?

How often do nightly builds get added. I had a kernel support committed for meshpoint to the Orange Pi H5 repo but there is still no new download and its been over a month.

Hello fellas, I would like to borrow your experience to compete with my task which counts (and measures) pulses on GPIO with Orange Pi zero. Currently, my simple solution is to register a callback to a specific edge and increment a global variable. I would like to catch a few hundreds of pulses in one burst which have in a 5-100 us length. However, even the number of counted pulses is not okay. Some of them are missed sometimes, which leads to an unreliable solution. I used different libs and all of them fall into the same issue. I tried the following libs: * ArmbianIO (C) * ArmbianIO (Python: original API) * ArmbianIO (Python: RPi compatibility API) * OPi I have missed the pyH3 forks intentionally as they do not offer callback functionality. I see on an oscilloscope that all the pulses arrive in the GPIO pin. The signal has a nice square shape and has the good level. I tried the ArmbianIO RPi compatibility API version to run on real Raspberry, and it is reliable works there. I noticed, that when it misses some pulses, the htop shows CPU usage peek. What was visible is the network manager, so I blacklisted Wifi modul and killed the wpa agent. I only use cable. The problem still appears. I also tried to raise the nice level, but it did not help, so I am out of ideas. Could it really be CPU load problem? Or does anybody has any idea what can go wrong and how it can be fixed? Thank you in advance! My actual implementation is here: from __future__ import print_function import time from armbianio.armbianio import * import atexit DETECT_GPIO_CH = 3 active = True started = False tick_count = 0 def catch_code(): print("Waiting for code...") global started global active while not started: time.sleep(10.0e-3) time.sleep(550.0e-3) started = False active = False print("Code: {}".format(tick_count)) def edge_detected(channel): if active: global started global tick_count if not started: tick_count = 0 started = True else: tick_count += 1 def cleanup(): AIORemoveGPIOCallback(DETECT_GPIO_CH) AIOWriteGPIOEdge(DETECT_GPIO_CH, EDGE_NONE) AIOShutdown() def main(): AIOInit() AIOAddGPIO(DETECT_GPIO_CH, GPIO_IN) AIOWriteGPIOEdge(DETECT_GPIO_CH, EDGE_FALLING) time.sleep(1) AIOAddGPIOCallback(DETECT_GPIO_CH, AIOCALLBACK(edge_detected)) atexit.register(cleanup) catch_code() if __name__ == "__main__": main()

Hello all, The board has a 2MB NOR FLASH chip what would be enough for storing u-boot and booting the system over network. Unfortunately u-boot says there is no ethernet. Is there anybody who knows how to enable ethernet on this or similar board like OPi PC2 or Nanopi NEO2? Is it just a matter of configuration or is RTL8211E as PHY generally not supported on H5 chips? Thank you very much for your help. --DieHackbeere

I'm trying to set up one of my Orange PI Zero to be a MPD Player and in parallel to play streams from other devices over network. The streams are provided by a Ubuntu desktop PC and and a Librelec PC. The Orange Pi Zero is running Armbian 5.38 with Kernel 4.14.18. I tried the last days two solutions: ALSA dmix plugin playing everything except network streams and Pulseaudio for nework streams Playing everything through Pulseaudio in system mode The first solution failed as the dmix plugin in ALSA has poor performance and causes regularly high CPU load resulting in broken audio playback with MPD The second solution seemed to be better suitable, but Pulseaudio crashes because of an underrun when using MPD as playback device. Network streams from other Linux PCs work properly. From the Pulseaudio debug messages I cannot see what may be the issue.(see below) Normally I would think this is a Pulseaudio or MPD issue, but then I switched to a Banana PI having the A20 equipped and everything worked well. Same Armbian and kernel version, same configurations for ALSA and Pulseaudio. To be sure it is not a codec issue I tried an USB sound card. This worked well on the Banana Pi with ALSA and Pulseaudio+MPD, but not on the Orange Pi Zero. There Pulseadudio stopps also with underrun error. So I think this seems to be an issue related to the Orange PI Zero. Hopefully someone can give me a workaround to solve this issue because I have 3 devices working with ALSA only which I want to upgrade with network stream support. D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: Latency set to 24,99ms D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: hwbuf_unused=348396 D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: setting avail_min=87542 D: [alsa-sink-CDC PCM Codec-0] protocol-native.c: Requesting rewind due to end of underrun. D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: Requested to rewind 352800 bytes. D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: Limited to 3764 bytes. D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: before: 941 D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: after: 941 D: [alsa-sink-CDC PCM Codec-0] alsa-sink.c: Rewound 3764 bytes. D: [alsa-sink-CDC PCM Codec-0] sink.c: Processing rewind... D: [alsa-sink-CDC PCM Codec-0] sink-input.c: Have to rewind 3764 bytes on render memblockq. D: [alsa-sink-CDC PCM Codec-0] sink-input.c: Have to rewind 3764 bytes on render memblockq. D: [alsa-sink-CDC PCM Codec-0] sink-input.c: Have to rewind 3764 bytes on render memblockq. D: [alsa-sink-CDC PCM Codec-0] source.c: Processing rewind... Killed

Dear mainline developers, I'm writing a (mainline) SPI driver for de ads131 from TI which I would like to make use of DMA, on the orangePIzero H2, zero+ H3/H5 and nanopi NEO2+. On the 4.13.3-sunxi kernel (armbian 5.33), this works fine, the driver is automatically loaded when the associated devicetree overlay is loaded, and the DMA can be allocated. However, when I compile the same driver for newer kernels (4.14.17-sunxi, 4.14.39-sunxi, 4.14.67-sunxi armbian 5.59), the dma allocation no longer appears to work, while the SPI part of the devicetree is identical except for the phandle (checked with dtc -I fs /sys/firmware/devicetree/base on newest 4.14.67-sunxi kernel, since 4.14.65 headers were not available in newest 5.59 stretch mainline H3 image) and does specify the DMA addresses for the SPI controller: spi@01c69000 { compatible = "allwinner,sun8i-h3-spi"; clocks = <0x6 0x1f 0x6 0x53>; resets = <0x6 0x10>; clock-names = "ahb", "mod"; status = "okay"; #address-cells = <0x1>; interrupts = <0x0 0x42 0x4>; #size-cells = <0x0>; dma-names = "rx", "tx"; phandle = <0x5e>; reg = <0x1c69000 0x1000>; pinctrl-0 = <0x21>; dmas = <0x1f 0x18 0x1f 0x18>; linux,phandle = <0x5e>; pinctrl-names = "default"; ads131a04@0 { compatible = "ti,ads131a04"; status = "okay"; reg = <0x0>; spi-max-frequency = <0x1e84800>; }; }; I use the following DMA calls that appear to fail in newer kernels, and the driver reverts to non-DMA spi transfers: static int ads131_probe(struct spi_device *spi) { const struct spi_device_id *id = spi_get_device_id(spi); int ret; ret=spi_setup(spi); if (ret!=0) { printk("ads131: Problem setting up spi-device, ret=%d",ret); return ret; } printk("ads131: spi->controller->can_dma=0x%lx",(unsigned long)spi->controller->can_dma); ... if (!dma_set_mask_and_coherent(&spi->dev, DMA_BIT_MASK(64))) { printk("ads131: dma 64 bit"); } else if (!dma_set_mask_and_coherent(&spi->dev, DMA_BIT_MASK(32))) { printk("ads131: dma 32 bit"); } else if (dma_set_mask_and_coherent(&spi->dev, DMA_BIT_MASK(24))) { dev_warn(&spi->dev, "ads131: No suitable DMA available\n"); goto dma_ignore; } else { printk("ads131: dma 24 bit"); } ... I get the following output from my driver in kernel 4.14.67-sunxi: dennis@orangepizeroplus2:~$ dmesg |grep -i dma [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.091893] DMA: preallocated 2048 KiB pool for atomic coherent allocations [ 5.254126] ads131: spi->controller->can_dma=0x0 [ 5.255134] ads131a04 spi0.0: ads131: No suitable DMA available I get the following with the older 4.13.3-sunxi kernel (armbian 5.33): [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 19.848567] ads131: spi->controller->can_dma=0x0 [ 19.849538] ads131: dma 64 bit [ 19.849544] ads131: dma_mask=18446744073709551615 [ 19.849564] xfer dma memory allocated with 16 buffers Do I need to specify additional information in the devicetree for DMA to work in SPI drivers with newer kernels, or do I need to add something to my driver before trying to use DMA with newer kernels? Kind regards, Dennis

Hello! I want to connect to the I2S the DAC PT8211. But it has an another coding format - left justified (Sony) 16 bit. I have already put a 16-bit frame in script.fex, but I can not do the LJ. On the test sine signal, the tip of the sine is turned upside down. Tell me how to change the output format of the stream from I2S to the Japaneese Left Justify? This part of my fex: [pcm0] daudio_used = 1 daudio_master = 1 daudio_select = 1 audio_format = 0 signal_inversion = 1 mclk_fs = 64 sample_resolution = 16 slot_width_select = 16 pcm_lrck_period = 16 pcm_lrckr_period = 1 msb_lsb_first = 0 sign_extend = 0 slot_index = 0 slot_width = 16 frame_width = 0 rx_data_mode = 0 i2s_mclk = port:PA18<2><1><default><default> i2s_bclk = port:PA19<2><1><default><default> i2s_dout0 = port:PA20<2><1><default><default> i2s_din = port:PA21<2><1><default><default> Armbian 3.14 sun8i

Hi all, I am using Orange Pi 0, I am trying to show some initial booting message on LCD. I am interfacing JHD204A which is a 20x4 charecter display.Which uses HD44780 controller. Is there a way to access Pi 0 GPIOs from Uboot? So that I want to show some initial message on L CD while Linux gets loaded. I appreciate any inputs, thanks in advance.

Hi , I have an orange pi zero . I installed armbian_5.38_Orangepizero_ubuntu_xenial_next_4.14.4 my orangepi zero. when ı use 'sudo nmtui' , it does not see wifi networks. I read many questions and answers about this issue but ı dont solve. I am waiting for your answers.

I there im using orange pi zero for homeassisatnt and google assisatant since my card died i install this new version configured every thing but audio isn´t working! I fallowed this guide like before but no audio coming for my orange pi zer no recording either! I have activated analog audio I already have everything configured with homeassistant i don´t wanna configure all again! Can you please help me make audio work in this kernel or is impossible to do?

Hi, After running the default image with legacy kernel for a few weeks, I am now trying the run a fresh SD card with the latest build of the mainline image. However, the MAC address of my device appears to be changing after each reboot - and I am running about of ideas to fix this issue. What I've tried so far: - Edit script.bin & add MAC address in the [dynamic] section - Edit armbianEnv.txt - Define an address in /etc/network/interfaces So far, I have not been able to solve the problem. Your help is much appreciated. Any suggestions on possible fixes for the issue?

My Pi Zero with H2+ and latest Armbian 5.35 Xenial works well, but on trying to increase the screen size I get: dk@desktop:~$ ssh dk@zero dk@zero:~$ sudo h3disp -m 1080p60 Unsupported board/kernel combination: Orange Pi Zero running 3.4.113-sun8i dk@zero:~$ Is this going to be fixed? nomachine.com's remote desktop for ARM works brilliantly Ubuntu + citadel-suite gets a mail server/chat server/+other into 337 MB - amazing!

Hello, i'm trying to make a mesh network with some Orange PI Zero devices, but ibss (adhoc) and 80211s (mesh) seem not working...with an usb wifi work fine... I have read that this device's support isn't the best, but i don't kwnow if my case is a release specific bug or these modes aren't really supported. Installed release "Armbian_5.38_Orangepizero_Debian_stretch_next_4.14.14", i have also trying dev kernel but this don't load the device... What are the really working modes and valid interface combinations? Reported info by iw list command seem not correct. Thanks for the help

Does anyone know if the Zero's on board WiFi chip XR819 can be disabled? The RJ45 is disabled by default, so there must be a way to disable the XR819 - right? Any thought appreciated.

Just bumped this one: Orange Pi Zero, stable version, legacy kernel Trying to insert Realtek WiFi dongle (8188eu in my case). Module cannot load - with this error: Peeked solution on 4pda - http://4pda.ru/forum/lofiversion/index.php?t750921-1740.html - decompiled script bin and set wifi_usbc_id = 1 - before it was set to none. Original solution has value "2", but it was just a guess, so I used "1". Module worked in parallel with original xradio. According to original poster on 4pda, this issue was seen on Orange Pi PC. Not sure, is it correct solution, but, well - it may help. Issues seen - when I try to unload realtek module, then modprobe back with some other parameters for powersaving or mac changing wia rtw_xxx options - original xradio gets also resetted. Issue with wifi_usbc_id does not show up, if i use ralink 2800 dongle for example. Hope it is not a duplicate topic and may help others somehow.

Hi, I'm tring to solve an issue on my Orange Pi Zero: at boot time the pins PA18 and PA19 are stucked to Vcc. I tried a lot of solution, now the best result is to add at the beginning of the file boot.cmd the command to clear the gpio configuration: gpio clear PA18 gpio clear PA19 and recompile the boot.scr. Despite this the pins goes HIGH for some seconds until the bootloader reach this line. What is the boot scheme? Why i get this pin HIGH? Is it because the I2C1 is configured? Is it possible to disable it? Thanks Simone

Hi all! I have Orange Pi Zero with armbian kernel 4.14. i'm not sure about the topic name, but to me seems like that. I've managed to make spi tft work flawlessly on my zero. But after i've continued with touchscreen module, i've got problems. After X is started, i can confirm touch is working, because when i touch the display, mouse pointer moves. But in the strange way, very laggy (more than a second to respond), but is works only for ~10 secs, then display stops to redraw. And it is not because of bad contacts! Because i've soldered everything together. And it also freezes if i don't touch it. The system is still working tho, because i can still connect to it. And there is all fine in dmesg log. I've also tried lowering SPI clocks from 16M to 500K, but of no good. I'm not very good at linux, so i don't even know where to look for errors. For those, who is not familiar with Orange Pi Zero SPI - tft is connected directly to spi bus, touch is connected to same bus, but CE1 is not there, so it is muxed to generic gpio10.

Hello everybody and sorry to be sooo stupid. I used to play with Orange Pi Zero H2+ and there was RJ45: it allowed me to connect it via the LAN. Now, with the H5 version, there is no RJ45 connector. And there is no USB port. So how to gain access to this card to start configuration etc... ? Thanks in advance.

Hi, I have 3 Orange Pi Zero running with the same sd image. It's all working fine, but yesterday I added a fourth device, which for some reason took a MAC address that is the same of another device, causing issues on the connection for both of them. I'm using the mainline kernel ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi. Searching on the internet, I found someone saying that mac addresses for Orange Pis are randomly generated every time the device reboots, but in my case the taken MAC address is always the same for every device. I saw to that people suggested to check the content of the /etc/modprobe.d/8189fs.conf file, but I don't have it. Do you encountered the same problem? How is the mac address generated on the Orange Pi Zero? Thank you in advance for your cooperation.