Search the Community

Thought this might be useful: FROM: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=2236 01 3.3V 02 5V 03 TWI0-SDA PA12 04 5V 05 TWI0-SCK PA11 06 GND 07 PWM1 PA06 08 UART1_TX PG06 09 GND 10 UART1_RX PG07 11 UART2_RX PA01 12 SIM_CLK/PA_EINT7 PA07 13 UART2_TX PA00 14 GND 15 UART2_CTS PA03 16 TWI1-SDA PA19 17 3.3V 18 TWI1-SCK PA18 19 SPI1_MOSI PA15 20 GND 21 SPI1_MISO PA16 22 UART2_RTS PA02 23 SPI1_CLK PA14 24 SPI1_CS PA13 25 GND 26 SIM_DET/PA_EINT10 PA10 FROM OFFICIAL USER MANUAL: https://drive.google.com/drive/folders/1lrtE6lbpXqxXTMmq7IxROOaZbOQ0U8uP P01 VCC-3V3 P02 VCC-5V P03 TWI0-SDA PA12 P04 VCC-5V P05 TWI0-SCK PA11 P06 GND P07 PWM1 PA6 P08 UART2_TX PA0 P09 GND P10 UART2_RX PA1 P11 S-TWI-SCK PL0 P12 PD11 P13 S-TWI-SDA PL1 P14 GND P15 UART2_CTS PA3 P16 TWI1-SDA PA19 P17 VCC3V3-EXT P18 TWI1-SCK PA18 P19 SPI1_MOSI PA15 P20 GND P21 SPI1_MISO PA16 P22 UART2_RTS PA2 P23 SPI1_CLK PA14 P24 SPI1_CS PA13 P25 GND P26 PD14 So you can make ~/bin/pinout-orange-pi-zero, and ~/bin/pinout containing: #!/bin/bash cat ~/bin/pinout-orange-pi-zero ... or just "~/bin/pinout": #!/bin/bash echo "text text text" ...so you'll have a pinout command like a Raspberry Pi. I have confirmed that pin 10 should be PG07, pin 12 should be PA07 and pin 26 should be PA10 for a DS18B20 temperature sensor with armbianEnv.txt like: $ cat /boot/armbianEnv.txt --- param_w1_pin=PA07 So it looks like the picture from Orange Pi forums is more accurate. Can anyone comment on the differences between the two pinouts eg pin 10, 12, 26, and others? Thanks, and thanks for making Armbian, and firstpost. Also warning, for other noobs (could have saved me several hours): "Armbian 23.5 Jammy" is broken! Click "Archived versions for reference and troubleshooting" on the download page and download "Armbian_23.02.2_Orangepizero_jammy_current_5.15.93.img.xz" instead

ls /sys/class/udc > UDC ls:write error: Device or resource busy I'm trying to get an armbian device (banana pi m2 zero and/or the orange pi zero LTS) to function as a USB client, but I can't seem to get the above step working. Any suggestions? lsof UDC returns nothing. On the RaspberryPI 4 this worked without issue

Well it took me longer than i hoped but i have managed to forward port icenowys code for TVE on the H2+/H3 to mainline armbian. It seems to work totally fine, with a few caveats. First: Sample images of it in action -> https://imgur.com/a/vXQEM Second: the patch itself -> https://github.com/stevenj/h3-tve/tree/v0.0.11 Third a prebuilt image for Orange Pi Zero: -> https://github.com/stevenj/h3-tve/releases/tag/v0.0.11 Howto: just put the patch into userpatches for the sunxi-next kernel, and build. it should apply cleanly. Its for H2+/H3. I have only tried it on a orange pi zero, but it should work on all H2+/H3 boards. You then need to edit /boot/armbianEnv.txt add tve to overlays to enable it. the driver will only run and enable tv out when the tv out devices are specifically enabled, so i created an overlay which does this. If you want to turn TV out off, just remove tve from the overlays line. My armbianEnv.txt overlays looks like this: overlays=usbhost2 usbhost3 tve If you want copious amounts of DRM debug info in your logs, add this as well: extraargs=drm.debug=0xF Its not needed, unless you really want the debug info. Notes: 1. The default mode is PAL, with 720x576 resolution. Thats outside of normal PAL displayable area, and so the screen overscans. I dont know how to correct this, although its mostly just annoying with terminals. I also don't know how to change the video mode to NTSC. 2. The standard font is a bit thin for composite video, and causes slight strobing and color impurity. Its because PAL needs pixels to be a certain MINIMUM width or color information can not be properly encoded. A way to resolve this is use : # apt-get install fbterm ... $ fbterm -s 20 This will run a terminal which is easy to change the font, and pick a bigger one. its much easier to read. Look at the help for fbterm to work out everything it can do. 3. I used the program "fim" to display the test images. there are others for doing stuff on the terminal. 4. I haven't tried X. I am not interested in running an X terminal on a TV, but it should probably work fine. Other than that it all seems good. I originally tested my hardware with the legacy kernel, and the image quality from this patch seems superior to what the legacy kernel produces. (legacy was noisy) The only other thing you need to know is Orange Pi Zero is missing filter circuity from its Composite Output, the most important thing you need to do is put a 50 ohm resistor between the signal and GND. i soldered one inside my RCA connector, it fits fine and isn't too difficult. IF you don't do this the image will bloom and look like total crap, so you have been warned. As this patch allows TVE to be enabled/disabled through use of the Device Tree overlays, i think it should be fine if the Armbian devs want to include it. I am happy to clean out some of the debug messages i added if they are interested in making a standard part of the build. If not, its easy enough to build your own image, just follow the guides on how to rebuild armbian. EDIT: I need to mention, all props go to Icenowy Zheng who wrote the original driver. I just tweaked the device tree stuff and got it in a state where it can apply cleanly to the armbian mainline kernel and build system. Original code is here: https://github.com/Icenowy/linux/tree/tve-v2

My third Orange Pi Zero came last week, yesterday I plugged it and had heating issues... So I started reading, learning and testing.... Setup: OPiZ-1: 256 MB, no SPI flash - Has extension board plugged - for comparison OPiZ-2: 512 MB, with SPI flash OPiZ-3: 256 MB, with SPI flash (new one with problem) Test conditions: All with (newish) Sandisk Ultra 16 GB Class 10 All new formatted (SD Formatter) and burned/validated (Etcher v1.0.0) with Armbian_5.25_Orangepizero_Debian_jessie_default_3.4.113.img All on my desk - side by side, ambient temperature 25.0-25.1 C (20 cm from boards, no air flow) No case, no passive/active cooling Power supply 7 port 5V 36W total, 2.4A per port (wait, wait, I tried others, separated etc - I'm testing them with USB V/A/W tester - 5.2-5.3V / 0.260-0.350 A) First install done, rebooted, apt-get update && apt-get upgrade'd, rebooted, tested The results are given below... I switched (i.e. reformatted/reinstalled) the SD Card of OPiZ-3, no change... I plugged OPiZ-3 alone, no change... I used 3 other power sources, no change... Is the new OPiZ-3 a faultly board? What else can I test/check? Thanks... OPiZ-1: h3consumption -p armbianmonitor -m OPiZ-2: h3consumption -p armbianmonitor -m OPiZ-3: h3consumption -p armbianmonitor -m

on orange pizero ,i installed pm-utils and with the pm-suspend command i put it in suspend . If I try to wake it up , with etherwake or other WOL programs (which send magic packets in LAN to the pizero's macadress) the pizero will not wake up . Do you know any tricks?

Hello, I'm trying to enable I2C access in U-Boot, for orange PI zero. I've downloaded the Armbian build, and tried to compile with CREATE_PATCHES, exactly like the tutorial here: https://zuckerbude.org/armbian-using-create-patches/ However, the build never stops and waits for me to make changes. I've attached the build log. I *think* I just need to add the following lines to orangepi_zero_defconfig: CONFIG_I2C0_ENABLE=y CONFIG_I2C1_ENABLE=y I guess that would be my next question- is this the proper way to change this config is via CREATE_PATCHES? I tried just changing the defconfig file and re-running compile.sh, but that didn't seem to help. Thanks in advance! build.log