Search the Community

Hi guys! I am making a separated network to connect my OPi3 to my old notebook to run some codes of my research. So, the problems is with ethernet connector in Orange Pi 3 that when I connect the cable from OPi3 to my switch LEDs just flash slow and in big intervals. When I try to ping from OPi3 to computer the ping just happens after big time later. I verify the cable and the switch with other devices (my personal notebook and my notebook from work). Everything is ok and running well. One thing blow my mind: when I connect cable from OPi3 directly to my notebook the LEDs of ethernet of OPi3 works normally but in the armbian the networks not always being up and even LEDs flash normal in the software it comes down being necessary to activate again. So, I am new on networks and connections. I saw the topic: But nothing could be used in my case. I hope you can help me! Below I out the videos before I connect OPi3 to my notebook and in the second video after, remembering I just connect OPi3 to notebook to "activate" the ethernet connector, after this both, OPi3 and notebook were connected to switch. VID_20200707_162920_284.mp4 VID_20200707_171510_950.mp4

I have move system to emmc, and want to use sdcard to storage videos from camera. So I want to sdcard can automount/umount after hotplug. I have try to use udev to fulfill it. But it seems not work. I add a rules for udev at /etc/udev/rules.d: ACTION=="add",KERNEL=="mmcblk2p1",RUN+="/etc/udev/sdcard_hotplug.sh add /home/opi/Videos/sdcard %k" ACTION=="remove",KERNEL=="mmcblk2p1",RUN+="/etc/udev/sdcard_hotplug.sh remove /home/opi/Videos/sdcard %k" And add a shell file at /etc/udev/sdcard_hotplug.sh #!/bin/bash case $1 in add) mkdir -p $2 mount -t exfat -o iocharset=utf8,rw,sync,umask=0000,dmask=0000,fmask=0000 /dev/$3 $2 ;; remove) umount $2 rm -rf $2 ;; esac Add chmod a+x for it. Test it ok. But udev seems not work! I have use udev monitor to test if remove and insert sdcard can generate event. It works. And use udevadm test, and it also ok. Anybody can help me?

Hi, Just as my last post. I want to know if it is possible to wakeup opi3 after I switch its state to "mem" or "disk" using gpio on CON12. I have doing some reasch but I don't know if it is right: PL/PM port can be used as wakeup source. PF/G/H/L/M port support interrupt event. PC/D didn't support interrupt. But when I try to write a device tree file, but it just report some error with error code -22. My device three is like this: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h6"; /* * This fragment is needed only for the internal pull-up activation, * external pull-up resistor is highly recommended if using long wires */ fragment@0 { target = <&r_pio>; __overlay__ { gpio_key_wakeup: gpio_key_wakeup { pins = "PL8"; function = "gpio_in"; bias-pull-up; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpio-keys-user { /* * Use "gpio-keys" for EINT capable pins, "gpio-keys-polled" for other pins * add "poll-interval" property if using "gpio-keys-polled" */ compatible = "gpio-keys"; autorepeat; pinctrl-names = "default"; pinctrl-0 = <&gpio_key_wakeup>; key_wakeup{ label = "GPIO KEY_WAKEUP"; linux,code = <143>; /* KEY_WAKEUP, see include/uapi/linux/input-event-codes.h */ gpios = <&r_pio 0 8 1>; /* PL8 GPIO_ACTIVE_LOW */ }; }; }; }; }; I am still a newbie and I don't know enough thing about how to write the right DTS file. Please give me some help. Thanks (I have tested KEY_POWER it seems everything OK. I don't know what is the error part about KEY_WAKEUP) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` Finally， I fulfill it now. dts is like this: one pin for sleep: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h6"; /* * This fragment is needed only for the internal pull-up activation, * external pull-up resistor is highly recommended if using long wires */ fragment@0 { target = <&pio>; __overlay__ { gpio_but_sleep: gpio_but_sleep { pins = "PH3"; function = "gpio_in"; bias-pull-up; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpio-keys-user { /* * Use "gpio-keys" for EINT capable pins, "gpio-keys-polled" for other pins * add "poll-interval" property if using "gpio-keys-polled" */ compatible = "gpio-keys"; autorepeat; pinctrl-names = "default"; pinctrl-0 = <&gpio_but_sleep>; sleep_button { label = "KEY_SLEEP"; linux,code = <142>; /* KEY_SLEEP, see include/uapi/linux/input-event-codes.h */ linux,input-type = <1>; // EV_KEY gpios = <&pio 7 3 1>; /* PD15 GPIO_ACTIVE_LOW */ gpio-key; }; }; }; }; }; one pin for wakeup: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { poweroff_pins:poweroff_pins { allwinner,pins = "PA13"; allwinner,function = "gpio_out"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { poweroff: poweroff { compatible = "gpio-poweroff"; gpios = <&pio 0 13 1>; }; }; }; }; But some weird things happend: after I wakeup again. I can connect to opi3 via debug port(uart0). But can not connect it from ssh again. Even after I setup a new static ip for it. And when I test "who", I find it still connect with the old ssh. But when I try to ping gatway "ping 192.168.1.1": it show: From 192.168.1.108 icmp_seq=1 Destination Host Unreachable It is so wried.

Hi, I want to use a gpio in CON12 to wakeup orange pi 3. But I can not figure it out. I am using armbian 5.4.43. I have done some researh about this question. It seems the basic process shoule be： 1、choose the right pin to wakeup. Cause some pins can not support interrupt and wakeup event. But I can not find which gpio support wakeup event. It seems I should choose pin on PL or PM ports. But according the schmatic, lots of them have been used as other usages: PIN DEFINE CFG PL0 PMU-SCK 3 PL1 PMU-SDA 3 PL2 RECOVERY 2 PL3 LINK-LED 1 PL4 POW-LED 1 PL5 USB0-DRVVBUS 1 PL6 MUTE 1 PL7 STATUS-LED 1 PL8 PL9 IR-RX 2 PL10 BT-WIFI-ON 1 PM0 WL-WAKE-AP 0 PM1 BT-WAKE-AP 0 PM2 AP-WAKE-AP 1 PM3 WL-REG-ON 1 PM4 BT-REG-ON 1 It seems only PL8 isavailable, but PL8 is also used as PWM pin 2、 write a dts file and let it using gpio-keys driver. For examples choose KEY_WAKEUP. But There need more detail about how to write dts files even after I read some examples. I don't know if I should choose "&pio" or "&r_pio". I can not find any file descript this part. (I have found some descriptiion about PL port and others. &pio is used for PA~PK, &r_pio is used for PL port. And Only Pins on PL port can be used as wakeup source.) (I have test PL8 and PL10. All of them return -22 after reboot when i user dmesg | grep to search gpio. I don't know if I have made some mistake) /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h6"; /* * This fragment is needed only for the internal pull-up activation, * external pull-up resistor is highly recommended if using long wires */ fragment@0 { target = <&r_pio>; __overlay__ { gpio_key_wakeup: gpio_key_wakeup { pins = "PL8"; function = "gpio_in"; bias-pull-up; }; }; }; fragment@1 { target-path = "/"; __overlay__ { gpio-keys-user { /* * Use "gpio-keys" for EINT capable pins, "gpio-keys-polled" for other pins * add "poll-interval" property if using "gpio-keys-polled" */ compatible = "gpio-keys"; pinctrl-names = "default"; pinctrl-0 = <&gpio_key_wakeup>; key_wakeup{ label = "GPIO KEY_WAKEUP"; linux,code = <143>; /* KEY_WAKEUP, see include/uapi/linux/input-event-codes.h */ gpios = <&r_pio 0 8 1>; /* PA10 GPIO_ACTIVE_LOW */ }; }; }; }; }; The error message is : opi@orangepi3:~$ dmesg | grep -i gpio [ 2.642632] sun50i-h6-r-pinctrl 7022000.pinctrl: pin PL8 already requested by gpio-keys-user; cannot claim for 7022000.pinctrl:360 [ 2.642646] gpio-keys gpio-keys-user: failed to get gpio: -22 [ 2.642662] gpio-keys: probe of gpio-keys-user failed with error -22 [ 3.343678] sunxi-mmc 4020000.mmc: Got CD GPIO 3、armbian describe we can use "armbian-add-ovelay" to add a custom dts to /boot/user_overlays. But if my dts file have some error if I can delete the relative file directly ? Or I need use other command? （armbian-add-overlay is unavailable for H6 chip. We need to use dtc compile dts file to dtbo and then move it to /boot/overlay-user） 4、add the right ovelay to user-overlays line in /boot/armbianEnv.txt I know it is a old question. But I am so sorry as a newbie can not draw s whole picture about how to use gpio-keys and device tree. Anybody can give me some instructions? Thanks so much!

Hi there, with Armbian Buster "OOB" (+update) I have following problem on Orange Pi 3: - Firefox (with language Polish) does not play network radio: https://www.rmfon.pl/play,25#p , - at the same time: - there are /dev/snd/ files, only for HDMI, but I have read that currently there is no driver for H6 audio, so I may expect at least ALSA is working, - VLC plays MP3 files correctly, (but it can play with pulse and ALSA), - pulseaudio is not started / configured / present. What should I do?

Hi there, just got OPi3 (4x 1.8GHz, 2GB RAM, eMMC), and I have (probably) issue with display settings (resolution / refresh rate?). I have an 1280x1024@60Hz VGA monitor, connected to an KVM switch (VGA+USB), then to HDMI->VGA converter. It worked OK for my 2 OPiPC+. Now what happens when I connect OPi3 instead od one of OPiPC+: - installed "OOB" Armbian Buster for OPi3, (server), - during initial startup there was NO question about monitor resolution (differs from initial startup for PC+), - only login / new user dialog. - now screen "flickers", text mode for few seconds, then blank screen, "power" LED of monitor is lit, like there is signal. Random periods. - can user armbian-config to set up basic parameters, network and install "desktop", - can SSH and do remote X session, - during boot-up to GUI there is NO display at all. - if I log in as root (CLI) and then issue "startx", GUI starts, but shifted 1/4 screen high (part of GUI offscreen), 1/4 screen high black bar on bottom. Questions: - hardware problem, or Armbian config problem? - how do I change screen resolution / refresh rate (CLI or GUI)? For text mode and X.

Hi everyone, I am trying to set the pin 26 (PL08) on orange pi as Input but sometimes it is flashing. I did put a 10K external pull up resistor and it is exported as input pin. I did the same thing with the pin 22 (PD21) and this one is steady, no problems until now. I did not add anything on overlays for these pins. Any idea what I am doing wrong? Thanks

Hi all! I sadly found that I can't watch my videos. Everything's fine with youtube, nevertheless. But video I tested (h264 + avc1, m4v and avi containers) looks like fast slideshow, and sound is VERY ugly! I've tried to install mali-midgard-dkms, I've failed (see below). What should I do to watch the videos? Convert 'em all to some chosen codec? Add to sources.list kind of "unstable" thing and upgrade? Install another armbian image? Find proper mali drivers and compile it carefully? Please, help! armbianmonitor -u http://ix.io/2mXg __@opi3 ~ # apt-get install mali-midgard-dkms 9:14:29 Reading package lists... Done Building dependency tree Reading state information... Done mali-midgard-dkms is already the newest version (16.0+pristine-4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up mali-midgard-dkms (16.0+pristine-4) ... Building for 5.4.28-sunxi64 Building for architecture arm64 This package appears to be a binaries-only package you will not be able to build against kernel 5.4.28-sunxi64 since the package source was not provided Removing old mali-midgard-16.0 DKMS files... ------------------------------ Deleting module version: 16.0 completely from the DKMS tree. ------------------------------ Done. Loading new mali-midgard-16.0 DKMS files... Building for 5.4.28-sunxi64 Building initial module for 5.4.28-sunxi64 Error! Bad return status for module build on kernel: 5.4.28-sunxi64 (aarch64) Consult /var/lib/dkms/mali-midgard/16.0/build/make.log for more information. dpkg: error processing package mali-midgard-dkms (--configure): installed mali-midgard-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: mali-midgard-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) __@opi3 ~ # apt-get install mali-t76x-x11-driver 9:49:35 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mali-t76x-x11-driver:armhf : Depends: mali-midgard-dkms:armhf but it is not installable E: Unable to correct problems, you have held broken packages.

I am trying to access control on Orange PI 3 , H6 some gpio,s using "gpiod" package that I installed from here : apt install gpiod I cannot control gpio's from port L such as 360, 354, 355 , ... +------+-----+----------+------+---+OrangePiH7+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 4.3v | | | 1 || 2 | | | 5v | | | | 123 | 0 | SDA.0 | ALT2 | 0 | 3 || 4 | | | 5V | | | | 122 | 1 | SCL.0 | ALT2 | 0 | 5 || 6 | | | 0v | | | | 119 | 2 | PWM0 | OFF | 0 | 7 || 8 | 0 | OFF | PL02 | 3 | 354 | | | | 1v | | | 9 || 10 | 0 | OFF | PL03 | 4 | 355 | | 121 | 5 | RxD3 | ALT4 | 0 | 11 || 12 | 0 | OFF | PD18 | 6 | 114 | | 120 | 7 | TxD3 | ALT4 | 0 | 13 || 14 | | | 0v | | | | 363 | 8 | PL10 | OFF | 0 | 15 || 16 | 0 | OFF | PD15 | 9 | 111 | | | | 4.3v | | | 17 || 18 | 0 | OFF | PD16 | 10 | 112 | | 230 | 11 | MOSI.1 | ALT2 | 0 | 19 || 20 | | | 0v | | | | 231 | 12 | MISO.1 | ALT2 | 0 | 21 || 22 | 0 | OFF | PD21 | 13 | 117 | | 229 | 14 | SCLK.1 | ALT2 | 0 | 23 || 24 | 0 | ALT2 | CE.1 | 15 | 227 | | | | 1v | | | 25 || 26 | 0 | OFF | PL08 | 16 | 360 | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+OrangePiH7+---+------+----------+-----+------+ as you can see in above table, all 300+ gpio's that cannot be controlled are from PLxx.

I want to control a fan via a script. I found a bunch of tutorials for pwm, but they were either for older version of Armbian, or for another board. I could not find a tutorial for Allwinner H6 boards. Apparently simple overlays=pwm doesn't work anymore. Anyone have any pointers as to how to go about it? my goal is to do something like $ ./setfan.sh 50 Setting Fan Duty Cycle to 50%... Nothing more complicated. I have a 5V fan for the system and I just want to tune how fast it should run - now it's going full 100% and it's louder than I'd like. I planned to do this with a trimmer but because the world situation and distances, the trimmers will arrive only after several weeks. And while I was thinking about it I figure why not just use the GPIO pins for driving the fan with pwm? Should be easily doable, I think. I just don't know how EDIT: I've been trying with WiringOP (now that I found a recent version that had support), but I've bumbed into another weird problem: The PWM pin on the OPi3 board is (physical) pin #7. If I do "gpio readall", it even lists that pin as "PWM.0" (It has WPi number 2), but when I try to put it into pwm mode (via 'gpio -1 mode 7 pwm' or 'gpio mode 2 pwm'), I only get an error that says: the pin you choose doesn't support hardware PWM you can select wiringPi pin 42 for PWM pin or you can use it in softPwm mode There is no WPi pin number 42. If I try to enable pwm on that ('gpio mode 42 pwm') I get an error "[pinMode:L1384] the pin:-1 is invaild,please check it over!" So no dice there either, unfortunately.

Hello! Here's the outputs: $ uname -a Linux opi3 5.4.28-sunxi64 #20.02.7 SMP Sat Mar 28 17:25:10 CET 2020 aarch64 GNU/Linux $ sudo aplay -l **** List of PLAYBACK Hardware Devices **** card 0: allwinnerhdmi [allwinner-hdmi], device 0: 5091000.i2s-i2s-hifi i2s-hifi-0 [5091000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 ...and that's all! There's no second card. I tested HDMI sound with my TV -- works fine, sound plays. But I need to use 3.5mm jack. Is it physically damaged? Or what could I do? Help, please!

Hello, I installed Ubuntu Bionic on sdcard and run Kodi on OrangePI but it seems very hot and hang out to reboot every 5mins. Do you encourter the same problem? And how to install Ubuntu into eMCC?

Hello everybody, the images from armbian for my Orange Pi 3 work very fine and stable. Thank you for that. I came to armbian by links form orangepi.org. When I tried to get an Android image from there I got an Xutuntu image. (https://drive.google.com/drive/folders/1Urh9-yljq9Mrrafp7ZWRVf_s_AdjUoTQ) Do you know where to get an Android for my Orange Pi 3? Thanks if you have information for me about that.

Hi I have an orange pi 3 board ,I want to turn on and use 5v cooler fan that uses GPIO ( pin 2 and pin 4 ) , how can I do that? thank you

I installed Armbian onto a reliable 16GB class 10 SD card, put it into an Orange Pi 3 with a 5v 3000 mA power supply (not a phone charger) and I've bumped into this error.. ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! The armbianmonitor -u command was not found so I had to take a photo of the computer screen. I'm not sure what is going on here and I couldn't find someone who had this error on an Orange Pi 3 before. If anyone has some advice I'd love to hear it.

Hello Everyone, I have an Orange Pi 3 and I want to wipe the default OS and replace it with Armbian. It has some foreign default OS which appears to be Android based and without a word of English. The Armbian documentation wasn't much help because it didn't provide any instructions for this sort of hardware. If any of you could give me some pointers that would be very much appreciated.

Hi, I am facing an i2c problem on orange pi 3. The i2c0 is enabled in armbian-config. The i2cdetect output is correct, as I know my two slave boards connecting to gpio pin3 (SDA) and pin5(SCL) have the addresses 0x20 and 0x23. pi@orangepi3:~$ sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 -- -- 23 -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- pi@orangepi3:~$ However, when I use wiringOP library to access(read and write) slave i2c chip(mcp23008) registers, it always return -1. int main(int argc, char** argv) { int fd_s1 = wiringPiI2CSetup(SLAVE_1_DEVICE_ID); //0x20 if (fd_s1 == -1) { std::cout << "Failed to init I2C Slave 1 communication." << std::endl; return -1; } int fd_s2 = wiringPiI2CSetup(SLAVE_2_DEVICE_ID); //0x23 if (fd_s2 == -1) { std::cout << "Failed to init I2C Slave 2 communication." << std::endl; return -1; } std::cout << "I2C communication successfully setup." << std::endl; int reg_read; reg_read = wiringPiI2CReadReg8(fd_s1, REG_IODIR); //The register address is correct, as this code ran on raspberry Pi correctly std::cout << reg_read << std::endl; } Run output: I2C communication successfully setup. -1 The wiringOP library is from https://github.com/orangepi-xunlong/WiringOP In the wiringPi library (in wiringOP), the code in wiringPiI2C.c shows that all APIs return -1, if the ioctl system call returns fault. Not sure what I should investigate next step to solve this problem. Thanks.

Had a bit of a success with HDMI audio and also video acceleration on OrangePi 3. What was needed was to apply some patches from LibreELEC, namely ones from projects/Allwinner/patches/linux/ . For HDMI audio to work you need 0004-sun4i-i2s-improvements.patch , which contains support for I2S on H6. When done right you should see in dmesg: asoc-simple-card sound: i2s-hifi <-> 5091000.i2s mapping ok Also what helped was an IRC chat that Jernej had with mirko some time ago: https://irclog.whitequark.org/linux-sunxi/2018-03-14 For video acceleration you need 0005-cedrus-improvements.patch and compile Cedrus driver. When done right you should see in dmesg: cedrus 1c0e000.video-codec: Device registered as /dev/video0 For a good measure I applied other patches in that directory as well, some needed modifications to apply to 5.5 kernel (LibreELEC uses 5.4) . Then FFMPEG needs to be compiled with v4l2_request to actually do the acceleration To get Kodi GUI acceleration working you need to compile mesa 20.0.0-devel from Mesa GIT. Kodi then needs to be compiled as GBM version. I also applied patches that LibreELEC has for Kodi into my Kodi tree. @jernej sounds the above about right?

Previously worked, but not now. I am stuck in the login line and cannot login with the keyboard from the putty screen. I cant login with keyboard on USB2. Also HDMI not working. HDMI previously worked too. I am newbie. Thanks in advance. I cant remember which version loaded on the eMMC. U-Boot SPL 2019.04-armbian (Jul 06 2019 - 20:55:41 +0200) DRAM: 2048 MiB Trying to boot from MMC2 NOTICE: BL31: v2.1(debug):bb2d778-dirty NOTICE: BL31: Built : 20:55:33, Jul 6 2019 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc079e78, model: OrangePi 3 INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.04-armbian (Jul 06 2019 - 20:55:41 +0200) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 DRAM: 2 GiB MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from EXT4... Card did not respond to voltage select! In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... No controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3042 bytes read in 1 ms (2.9 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 0 ms Card did not respond to voltage select! 29583 bytes read in 5 ms (5.6 MiB/s) 4161 bytes read in 3 ms (1.3 MiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 44000000 9135838 bytes read in 923 ms (9.4 MiB/s) 15147016 bytes read in 1530 ms (9.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9135774 Bytes = 8.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49749000, end 49fff69e ... OK Loading Device Tree to 00000000496d9000, end 0000000049748fff ... OK Starting kernel ... Ubuntu 18.04.3 LTS orangepi3 ttyS0 orangepi3 login: And This one is Armbian_19.11.4_Orangepi3_bionic_current_5.4.6_desktop with SDCard boot. (2019-12-23) U-Boot SPL 2019.10-armbian (Dec 23 2019 - 09:47:42 +0100) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):aeb3d83-dirty NOTICE: BL31: Built : 09:47:34, Dec 23 2019 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc07f048, model: OrangePi 3 INFO: ARM GICv2 driver initialized INFO: PMIC: Probing AXP805 on I2C INFO: PMIC: aldo1 voltage: 3.300V INFO: PMIC: aldo2 voltage: 3.300V INFO: PMIC: aldo3 voltage: 3.300V INFO: PMIC: bldo1 voltage: 1.800V INFO: PMIC: bldo2 voltage: 1.800V INFO: PMIC: bldo3 voltage: 1.800V INFO: PMIC: cldo1 voltage: 3.300V INFO: PMIC: dcdcd voltage: 0.960V INFO: PMIC: dcdce voltage: 1.200V INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.10-armbian (Dec 23 2019 - 09:47:42 +0100) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 DRAM: 2 GiB MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3033 bytes read in 12 ms (246.1 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 7 ms (22.5 KiB/s) 31388 bytes read in 39 ms (785.2 KiB/s) 4161 bytes read in 40 ms (101.6 KiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 44000000 9549521 bytes read in 1010 ms (9 MiB/s) 15685640 bytes read in 1650 ms (9.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9549457 Bytes = 9.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 496e4000, end 49fff691 ... OK Loading Device Tree to 0000000049673000, end 00000000496e3fff ... OK Starting kernel ... [ 17.213687] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1 [ 17.222692] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 17.386257] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1 [ 17.395289] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 17.428555] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1 [ 17.437574] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 17.466272] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1 [ 17.475285] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) [ 17.504444] dwmac-sun8i 5020000.ethernet eth0: no phy at addr -1 [ 17.513515] dwmac-sun8i 5020000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Armbian 19.11.4 Bionic ttyS0 orangepi3 login:

Hi all. I've been working with the OPi3 and PineH64 model B the last days to try installing MESA and DRM drivers to make Panfrost work. This doesn't seem to work. Every time I install Mesa and reboot. It boots into the desktop normally, but a few seconds later the screen goes into one color. Everything is unresponsive. Can't go to a terminal window. Numlock is stuck... Just tried again with compositor disabled. It does take a bit longer before it blocks. But it still happens about a minute in every time. I can't find a ttl adapter for better debugging. I'll order new ones. Both the OPi3 (bionic 5.4) and PineH64(bionic 5.3) have the same issue. I'm using self built images. You can try it with the script here Don't install all, only install mesa and drm. It seems to install well, but after reboot everything is broken. Any clue would help. Cheers.

Hello there, I tried to use on OPC3 bionic the ttyS1 for communcation with a serial device and didn't get it to work. ttyS3 works fine. Configuration is done for both. But now I need to communicate with a second and possibly a third serial device. So I hoped for updates. But now I can't find a download of the bionic version and i have to make decision how to go further on. Does it make sense to switch to buster or stretch? Is bionic only temporarily or finally offline? Whats the reason? Any idea when there is a chance to get a stable release. Possibly with 6 Months or surely not within 6 months. Which version is more likely to be stable within 6 months. What happend to ttyS2? Does UART1 correlate to ttyS1... etc. I enabled, just for testing, the Overlays for UART1, UART2,UART3, which disables the Ethernet interface. After disabling UART2 Ethernet works fine again. Do they share memory or other resources? Could it be a bug or a feature? Is there a chance to stop kernel messages on ttyS0 completely so this can be used to attach a device? Sorry for the bunch of questions and many thanks in advance.

I do not use wifi at all, so I'd like to disable it completely. It's not configured right now, but I wonder if I could power down whole chip, ex. commenting it out in DT file? Does it save some power or not?

Hi all together, on a Raspberry Pi 3b and 3b+ as well as on a Odroid-C2 I know how to switch off the blinking LEDs s or Power LEDs. Does anybody know how I can switch off or dim that extremely bright red power LED from the OrangePi3? I tried a script snippet like this: echo none > /sys/class/leds/orangepi\:red:\power/trigger But it wont work. Has anybody a helpful hint for an unpatient contemporary? Thanks for help :o)

Hi Everybody, I have the orange pi 3 and I am using Armbian Buster mainline based kernel 5.1.y but sound from hdmi doesn't work. I tried to fix it through /etc/alsa/conf.d/ and put pulse audio as default but nothing happened. I am new using this new version of orange pi and armbian. I hope you can help me. Best regards. Paulo.

I have a headless Orange pi 3 and wanted to be able to test a new install. Is it possible to issue a specific reboot command that will switch to boot from one storage to the other storage? I have armbian bionic installed and running on the EMMC. and A new bionic build installed on a new SD card. So, if i'm tinkering with the new build on the SD card, can i reboot to the EMMC without removing the SD card, and then similarly reboot from the EMMC into the SD card build??