Jump to content

Search the Community

Showing results for tags 'orangepipcplus'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Armbian Bionic not sound output 3.5mm jack root@orangepipcplus:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0
  2. Hello, when I connect R307 fingerprint reader to USB port, Linux identifies it as mass storage device. If the device is connected to the Orange Pi board before turning on, the system resets itself on early startup with "Resetting CPU..." message. What can be the reason and how to avoid it? I know about alternate serial connection, but would prefer to use USB. I use Armbian recent version with console image. Thanks in advance.
  3. Hello Folks! Already successfully running an RTL-SDR device (for Flight Tracking) and U-Blox NEO-6M GPS (for GPS/NTP) on my Orange Pi PC Plus, and now wanted to try a BME280 weather chip, but ran into problems talking to it. The 'i2cdetect' seems to be working fine: darren@frodo10:~$ sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- 76 -- However, after many Googles with both C and Python code, I can't seem to successfully talk to this device In my last attempt (using bme280_sample.py and modifying the reference to 0x76, installing 'smbus2', etc.): darren@frodo10:~/Downloads$ sudo python bme280_sample.py Traceback (most recent call last): File "bme280_sample.py", line 138, in <module> setup() File "bme280_sample.py", line 133, in setup writeReg(0xF2,ctrl_hum_reg) File "bme280_sample.py", line 19, in writeReg bus.write_byte_data(i2c_address,reg_address,data) File "/usr/local/lib/python2.7/dist-packages/smbus2/smbus2.py", line 391, in write_byte_data ioctl(self.fd, I2C_SMBUS, msg) IOError: [Errno 6] No such device or address Does the 'ic2detect' output mean that I have everything wired up properly? Am I close to success?
  4. I'm powering a small PCB via the OTG port on my OPI PC Plus, however sometimes I need to be able to reboot the device. It is possible to cut power to the OTG port momentarily to force a reboot? I've seen mention of PL2 GPIO, but it is unclear to me how this should be setup. I've also looked at uhubctl, but that didn't work. Thoughts?
  5. Hello, i'M having this issue with the latest Armbian 5.75 stretch image with updated firmware. When booting with a huwei E303 modem is in the usb port the board fall in a eternal reboot. if i let the board boot as normal an then insert the modem everything is o.k. I tried with 4 others OPI PC+ and others E303 sticks, same thing. also tried with 5.65, same problem. BUT, with an earlier version 5.35 and it boots as normal.
  6. Hello, I'm buliding a music player for my old car using Orange Pi PC Plus. I would like to use external incoming logic levels (3.3V / 0V) to wake up the OPi from suspend state. Could you help me how to do that? Waking up using the HW button SW4 is working perfectly. I need to do this using external logic signal connected to PA11 / GPIO pin #5. I tried the following setting in fex editor: [gpio_power_key] key_used = 1 key_io = port:PA11<6><default><default><0> It doesn't work. I keep the pin on HIGH (3.3V) normally, and when I bring it to LOW state, OPi won't wake up. I tried also changing the second parameter 6 to 0, as input function. No success. Of course I have disabled the TWI0 interface in the fex editor, so pins PA12 and PA11 are available. I tried to read pin PA11 state as input using a Python code and it reads properly ON and OFF states. But the wake up function doesn't work. Could anyone give me any suggestion what shall I try to make it work?
  7. I have a Orange PI PC Plus that isn't booting either from sd or emmc. I had really messed up some configuration, so I erased emmc. After I erased EMMC, I started to get this boot screen. https://photos.app.goo.gl/EbJX43eSATyqTEau8 If I insert a sd card in with the latest Armbian, I get no boot screen, or activity at all. In fact, even if I format the card, and insert it into the OP+ it gets no boot activity. It is only after that I remove the card that it can then boot from usb flash. I ended up writing the latest orangepiplus image to a usb flash drive, and am able to get it to boot via a flash drive. I did backup my microsd install a few months ago with clonezilla. When I boot via USB, and run armbian-config there are no options for EMMC now. Basically, I need a little instruction of how to to get the OP+ to boot from micro sd again. https://photos.app.goo.gl/1WZDoYZLuPMnYhLC9 root@orangepipcplus:~# blkid /dev/mmcblk1p1: LABEL="emmc" UUID="19962a0d-5650-4f65-849d-8ecbafdfe67c" TYPE="ext4" PARTUUID="34dc0819-01" /dev/zram0: LABEL="log2ram" UUID="eec54a38-cb53-4031-b1b4-f606ca2bd7a8" TYPE="ext4" /dev/mmcblk1: PTUUID="34dc0819" PTTYPE="dos" /dev/sda1: UUID="d8699223-136d-4b8c-a25f-94e77a5b6ab3" TYPE="ext4" PARTUUID="a139e8b2-01" /dev/zram1: UUID="54a87408-738f-4f75-820a-1f51f87a3202" TYPE="swap" /dev/zram2: UUID="df462624-f671-4951-a0cd-ab0a9eafb089" TYPE="swap" /dev/zram3: UUID="0940ee89-bc6e-47ca-a587-67e2144ce3e5" TYPE="swap" /dev/zram4: UUID="7dc622a1-55af-4efb-a77b-9f81358ebbb7" TYPE="swap"
  8. Hello, I would like to ask your help with the following problem. I'm able to put my Orange Pi PC Plus to suspend state using this command: echo -n mem>/sys/power/state When I wake it up using the SW4 pushbutton it resumes operation properly. I would like to automatically execute my script every time the system resumes from suspend state. I found two different methods, I've spent several hours trying them and non of them seems to be working with Orange Pi PC Plus. First method: using /lib/systemd/system-sleep Second method: using /etc/pm/sleep.d It seems my system does not execute the scripts configured in none of the above folders after resume. Is there a special solution to do this? Could you give me any suggestion what else shall I try? Linux orangepipcplus 3.4.113-sun8i
  9. hi how can i enable the tv out in orange pi PC+, I need to do a kiosk mode thanks
  10. Hi there, after a recent apt upgrade I have problem with WiFi. I CAN connect to one WiFi, WPA2, static IP. However I CAN'T connect to another one, WPA2, tried with static and dynamic IP. I am using NetworkManager. Searched forum, deleted /etc/networks/interfaces. Information in /etc/NetworkManager/"network name" seems to be correct. Almost the same as for working net. (except uuid & IP info) CAN also connect from laptop. wpa_supplicant line from ps: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant What should I check else?
  11. Hello, I installed last Bionic on a Orange Pi PC+. It's on EMMC. (it used to have an old Armbian Ubuntu with 3.x kernel before) Common settings (background image, GTK theme, icons, panel) are there on logout but are not saved on reboot. I saved a text file in the home user folder, it's OK. With another common user I face the same problem, with the root account settings are saved. My Linux knowledge is average, I really don't know what's wrong. Thank you Mathieu
  12. Orange Pi PC+ installed Armbian Bionic mainline kernel 4.19.y, Armbian Stretch mainline kernel 4.19.y not working sound via HDMI, on an older version Armbian Xenial desktop legacy kernel 3.4.y sound via HDMI works. What to do to make the sound work in the new version
  13. Hello, I am new to Orange PI and Armbian. I try to configure orange pi to run chineese LCD 5 inch screen via HDMI. I managed to do that using lubuntu downloaded from orangepi server. I changed fex file to what I found on the internet: [clock] pll_video = 321 [disp_init] disp_init_enable = 1 disp_mode = 0 screen0_output_type = 3 screen0_output_mode = 2 screen1_output_type = 3 screen1_output_mode = 2 fb0_width = 720 fb0_height = 480 fb0_scaler_mode_enable = 1 fb0_pixel_sequence = 2 fb0_format = 4 fb0_framebuffer_num = 2 fb1_width = 720 fb1_height = 480 fb1_scaler_mode_enable = 1 fb1_pixel_sequence = 2 fb1_format = 4 fb1_framebuffer_num = 2 [hdmi_para] hdmi_used = 1 hdmi_x = 720 hdmi_y = 480 hdmi_power = "vcc-hdmi-18" hdmi_cts_compatibility = 1 After positve tests I wstiched to Armbian 5.72 kernel 4.18.17-sunxi. Generaly I could not find on the inter / googled/ searched thru armbian formu waht should I do to recofigure sam as in fex files. What I understad new kernels does not support fex files any more. Is there any way to change HDMI cofig simillar way as in fex files? Currently I try to recompile kernel (never did that before) I also changed orangepipcplus.fex file which i found in armbian git repository. I would appreciate any help or links. Thanks!
  14. Hi there, I am using Workstation edition on OPi PC+, system quite up to date. Problem: wired ethernet looks hardwired to DHCP (client) and I want to use static address(es). There is Network Monitor but I can't edit / delete "ifupdown(eth0)" connection. I can create another connection for wired eth in NM, static address, but it does not go active on system startup. I can switch off "eth0" and activate another connection from NM desktop, but I want system to start automatically with static IP (w/o user action).
  15. Hello everyone. I have installed the Armbian Xenial Multimedia and desktop usage scenarios on my orange pi pc plus. Setup user and new password successfully. By using the command armbian-config I have solved my keyboard issue and language. Also network Lan0 is ok By typing sudo apt-get update and upgrade my orange is now updated succefully. But how to start the desktop ? I can only see the black screen with prompt command. If I reboot it , after all [ok] ...... I read Ubuntu 16.04.5 LTS orangepipcplus tty1 login ...... Did I do some mistakes?
  16. with great joy we saw the new version of Armbian_5.69_Orangepipcplus_Ubuntu_bionic_next_4.19.13 for orange pi pc plus (date 9-1-2019) We were waiting for a WIFI fix, on the WPA. Wifi at the very beginning, it works properly with a WPA connection. Then, you do not want to make another WPA connection and work. Will this problem be corrected in some new version of Armbian? Thanks
  17. Good day! I connect the real time clock, made according to the instructions: RTC time is set I set the wrong time in the RTC, reboot. I look at the time in the system clock - at first not the right one, from the RTC, then they are synchronized and it becomes the right one. But in RTC, the new correct time is not recorded. What am I doing wrong? Or what else needs to be done?
  18. Hi, I use orange pi pc plus with armbian bionic, firstly I use it with a SD card and the temperature its around 30 centigrade degrees, its ok. Then I use EMMC without SD card and the temperature increases to 51 degrees (I think it´s very high), they are some way to use EMMC without the board increases the temperature?? Best regards, Nelson
  19. The translation was done by Google Hello friends, my hardware: Orangepi pc plus dac-pcm5102mk-i2s. 3.5 "touch display So far I have the system in eMMC (ARMBIAN 5.60 stable Ubuntu 16.04.5 LTS 3.4.113-sun8i) and optionally on 16GB uSD card (ARMBIAN Debian GNU / Linux 8 (jessie) 3.4.113-sun8i). In both cases, an xfce desktop is installed. The setup of the DAC I have after the tutorial I2S on Orange Pi H3 by Da Alchemist, February 29, 2016 in both Debian 8 and Ubuntu 16.04. Works well. I installed the display after the hints from How to use Touchscreen + LCD on H3 devices by kutysam, July 31, 2017. It claps with the display of the desktop, but the touch and mouse do not match. With a USB mouse it works, but not permanently. The ad hangs after a few mouse clicks. Now I have tested times times Armbian_5.65_Orangepipcplus_Ubuntu_bionic_next_4.14.78 or Armbian_5.65_Orangepipcplus_Debian_stretch_next_4.14.78.img ever written on a 16GB uSD and tried the device. Unfortunately I did not find the script.bin anymore. The same applies to Debian 9 too. Therefore, I get no sound from the DAC. In addition, I have also connected the display according to the above instructions. However, the display shows the console after booting. What can I do to at least get the same functionality as the older systems? Even better would be a working touch function. Yours sincerely hajupiko49
  20. hi how can i enable the tv out in orange pi PC+, I need to do a kiosk mode thanks
  21. I have an Orange Pi PC Plus running the mainline Debian Stretch desktop version of Armbian, but lately I've been using it headless. When I'm logged in over ssh and shutdown it down using "sudo shutdown -h now", the ssh connection drops and the board's LED flashes then shuts off, giving every indication the board is off. However, power consumption doubles (increasing from ~1.2W to ~2.4 W)! The problem persists as long as the board is powered, so I presume the board is hung and never fully shutdown. Any thoughts as to what could be causing the board to hang when shutting down?
  22. I just noticed there isn't a i2s/i2s0 overlay for the mainline kernel series: Linux orangepipcplus 4.14.78-sunxi #412 SMP Fri Oct 26 11:37:04 CEST 2018 armv7l GNU/Linux https://github.com/armbian/sunxi-DT-overlays/tree/master/sun8i-h3 Is it a simple matter of just adding some text files for DT? Or was i2s intentionally left out because or some conflict for example? (I had good luck with legacy on Banana Pi Pro a long time ago with fex, so I'm guessing it's a unintended omission?)
  23. Hello i found it on both my Opi PC+ and Opi Plus 2E , Both ARMBIAN 5.59.180918 nightly Debian GNU/Linux 9 (stretch) 4.14.70-sunxi. As i get some stability issues with Jeedom i'm playing with frequencies and governors and found that strange thing : root@orangepipcplus:~# cat /etc/default/cpufrequtils && cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=408000 MAX_SPEED=1296000 GOVERNOR=ondemand 240000 480000 648000 816000 912000 960000 1008000 1104000 1200000 1296000 root@orangepipcplus:~# it seems there is a mismatch between MIN_SPEED=408000 in cpufrequtils and the one returned by scaling_available_frequencies 480000 is it normal or there is an error somewhere. can it be an instability cause ? best regards
  24. EDIT: This seems to be a problem with the OS running on the Mikrotik router. See this thread for a work-around that "shouldn't make a difference". Hi! I've got some trouble with u-boot on an Orange Pi PC+ connecting to a Mikrotik router RB922UAGS-5HPacD, and I'm not sure where I should start digging. Here is what I have so far: Orange Pi PC+ with u-boot 2017.11-armbian installed on eMMC by running nand-sata-install. But instead of booting from eMMC, I'd like to fetch the kernel via tftp, so I modified the bootcmd accordingly. The relevant configuration / commands are: setenv ipaddr 192.168.3.74 setenv serverip 192.168.3.73 tftpboot 0x44000000 some_file.scr The Mikrotik RB922UAGS-5HPacD shall be the tftp server. The relevant configuration is: /ip address add address=192.168.3.73/24 interface=ether1 /interface ethernet set [ find default-name=ether1 ] disabled=no /ip tftp add ip-addresses=192.168.3.0/24 allow-rollover=yes req-filename=some_file.scr real-filename=some_file.scr read-only=yes If I connect Orange Pi and RB922 with a straight ethernet cable, I can see the link coming up on the RB922 (100M-half), but u-boot can't ping the RB922 and tftp times out. If I put a switch between the Orange Pi and the RB922, everything works fine. If I use a different Mikrotik device (CRS125-24G-1S, a 24-port gbit-switch/router) and connect the Orange Pi directly to it, everything works fine, too. Note that in this case the configuration of the CRS125 is not exactly the same as on the RB922, because the CRS125 has more than one port and the ports are configured as a bridge: /interface bridge add admin-mac=XX:XX:XX:XX:XX:XX auto-mac=no fast-forward=no name=bridge-lan /interface bridge port add bridge=bridge-lan interface=ether2 /interface bridge port add bridge=bridge-lan interface=ether3 /interface bridge port add bridge=bridge-lan interface=ether4 etc. /ip address add address=192.168.3.1/24 interface=bridge-lan network=192.168.3.0 /ip tftp add ip-addresses=192.168.3.0/24 allow-rollover=yes req-filename=some_file.scr real-filename=some_file.scr read-only=yes # (yes, I changed "serverip" in u-boot for this test) Once the Linux kernel is up and running, the straight connection between Orange Pi and RB922 works fine (100M-full). It's just u-boot, and only with a direct connection to the RB922. Any clues what I should have a closer look at? Thanks a lot, Hendrik
  25. I've try use the emmc storage on my Orange Pi (which was working on previous kernel). Copy seems to work with latest armbian-config but the boot loop on : Begin: Running /scripts/local-block ... done. Here is the full log : U-Boot 2018.05-armbian (Sep 19 2018 - 12:58:14 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi PC Plus DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... MMC: no card present ** Bad device mmc 0 ** Failed (-5) In: serial Out: serial Err: serial Net: phy interface0 eth0: ethernet@1c30000 MMC: no card present ** Bad device mmc 0 ** MMC: no card present ** Bad device mmc 0 ** starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 8 ms (452.1 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 249 bytes read in 2 ms (121.1 KiB/s) MMC: no card present ** Bad device mmc 0 ** 5099960 bytes read in 250 ms (19.5 MiB/s) 6979808 bytes read in 342 ms (19.5 MiB/s) Found mainline kernel configuration 32641 bytes read in 28 ms (1.1 MiB/s) ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5099896 Bytes = 4.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49b22000, end 49fff178 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49ab1000, end 49b21fff ... OK Starting kernel ... Loading, please wait... starting version 232 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 46.790736] reboot: Restarting system
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines