Search the Community

Armbian 24.2 is broken on Orange PI PC2 (Debian Bookworm CLI) Latest stable community release: https://github.com/armbian/community/releases/download/24.5.0-trunk.123/Armbian_community_24.5.0-trunk.123_Orangepipc2_bookworm_current_6.6.20_minimal.img.xz With update 23.11 -> 24.2 the orange pi pc2 no longer starts. I tried a new sd installation and it too does not appear on the network. Right now I don't have a serial cable to check but it is possible that the network driver is missing or not working. SD, SBC and PSU are 100% working: a revert to 23.11.2 makes it work perfectly.

I will use a orangepi PC2 as openhab server. Arbian 25.2 kernel 6.6.62 minimal.img is installed. The orangepi is connected with an ethernet cable to the router, but is not visible in the list of connected devices. So I suppose he does not make connection. I want to access the orangepi by putty on my PC but as long he is not online, connection is not possible. Led's on the ethernet connector ar flashing. What do I wrong ?

Hi, I am a Grade 12 STEM Student, and right now I need someone's help on our Investigatory Project. Can someone help me on how to connect screen saver (turns off automatically when snoozing) and turns on when PIR Sensor detected something so that It saves power when not used. And I also need to know how do I connect it to the Smart TV because our project is basically an Interactive Board (The thing that you can find around malls which you can use to know specific locations around the mall.) What I have: 1. Orange Pi 2. PIR Sensor 3. Smart TV What I need: 1. A step-by-step procedure on how to do it. 2. What commands/codes to input (Right now, we are using Python language but you can suggest other languages that we can use.)

I am creating a script that can backup sd-cards running on the system, resizing it with desired value or via resize2fs calculated. I learn a lot but there are a few things I don't fully understand. When I create a backup I dd what I understand is the bootsector, ie I grab the "start" position of the partition I am backing up with fidisk and use that value and a blocksize of 512. I then add another 10mb (in bytes) just to be sure. Usually the bootsector is 8192 big, but not always (IIRC nanopi neo3;s is WAY bigger). dd bs=512 count=$DDBOOTSECTOR if=/dev/mmcblk0 of=$IMG_FILE conv=noerror,sync status=progress I then truncate the file, calculated either by resize2fs minimum calculation or via an input + file usage in df (depending of what flag I start the script with) + bootsector + yadayadayda. (if someone want me to post the script I will, but the script and calculations work, although I "force" some commands) I then loop the created img file and delete the partition on the /dev/loop0 and recreates it to cover 100%. Then format it with mkfs.ext4 copying the name and uuid from wherever I backup from. I mount the loop and rsync / rsync -ahvD --exclude={/lost+found,/proc/*,/sys/*,/dev/*,/tmp,/run/*,/mnt/*,/media/*,/var/log.hdd,/var/swap,/etc/udev/rules.d/70-persistent-net.rules,/var/lib/asterisk/astdb.sqlite3-journal} --info=progress2 --stats --delete --force --partial / $tmp_dir This seems to work, but there are probably some things that are just "accepted" not really "perfect". So questions: 1. Should I only dd the EXACT bootsector and not add the extra 10mb? The reason I ask is because if I try to delete the partition with parted, I have to do a hack in the scrip where I simulate button presses, it warns me that "the partition cant be outside of the disk" when I try to REMOVE it. Solution, I use sfdisk to remove the partition, but it prompts me to think there is something wrong going on here. If the size I create is ABOVE the resize2fs reported minimum i don't get this warning. sfdisk was the solution in this case, but still curious on this behavior. If I try to only dd the small part, it sometimes works, sometimes doesn't so I come here asking. (I might be able to do some further research but since I have other questions, why not ask) 2. Does armbian ever update the u-boot via apt? I do my next update with rscync by looping the file and mounting it. But that wont EVER cover the bootsector. 2b. If yes, do I solve this by again dd:ing ONLY the bootsector? 3. I have noticed that sudo apt update on armbian includes armhf even though running arm64. This makes the update process VERY long. dpkg --print-foreign-architectures shows armhf so i remove it with dpkg --remove-architecture armhf and then find /var/lib/apt/lists/ -type f -exec rm {} -v \; Seems to fix this but is this a bad idea? Why is the armhf even being fetched to begin with? To my memory I have not added arhmf architecture... Thanks in advance!

Hi I'm auto-login using nodm with orange pi. I run my udp.py file by creating a file named udp.desktop under the .etc/xdg/autostart folder at startup. but I need to play the wav file using pygame in the .py file, but I get a warning that the audio device could not be initialized. If I trigger my .py file manually, I can play the wav file without any problems. probably unable to load sound drivers during autostart. Can you help with this.

Hello there, i have one orange pi pc 2 and i need to put this work with 2-Channel Isolated CAN Expansion HAT from Waveshare (2-Channel Isolated CAN Bus Expansion HAT for Raspberry Pi, MCP2515 + SN65HVD230 Dual Chips Solution, Multi Onboard Protection Circuits (waveshare.com) But im stuck with .dts and overlays. This HAT was design to work with raspberry pi but i know we can put it to work with orange pi. My problem is with "chipselect" cause our GPIO pin configuration are diferent then Raspberry Pi Could you please give me an example how should it be my .dts?

Before I file a bug for this, I want to make sure I'm not doing something wrong. I am trying to enable PPS on GPIO pin PD14 of an Orange Pi PC2. I've enabled the pps-gpio and uart overlays in my /boot/armbianEnv.txt file and rebooted. root@ntp0:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-h5 rootdev=UUID=20dbbd2a-5783-4f98-b467-62fa62990ac8 rootfstype=ext4 overlays=pps-gpio uart1 param_pps_pin=PD14 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@ntp0:~# On reboot I see the following problem in dmesg: [ 5.542593] pps-gpio pps@0: failed to map GPIO to IRQ: -22 [ 5.542626] pps-gpio: probe of pps@0 failed with error -22 If I 'rmmod/modprobe' the pps-gpio/pps-ldisc modules I see pps0 created: [ 54.983158] pps pps0: new PPS source serial1 [ 54.983284] pps pps0: source "/dev/ttyS1" added Yet I am not getting PPS data on pps0 even with the gps locked as measured by cgps/gpsmon. root@ntp0:~# ppstest /dev/pps0 trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... time_pps_fetch() error -1 (Connection timed out) time_pps_fetch() error -1 (Connection timed out) time_pps_fetch() error -1 (Connection timed out) ^C root@ntp0:~# lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqklqqqqqqqqqqqqqqqqqqSeen 12/Used 9k x Time: 2022-04-17T18:35:49.000Z (0) xxGNSS PRN Elev Azim SNR Usex x Latitude: xx.xxxxxxxx N xxGP 1 1 26.0 49.0 15.0 Y x x Longitude: yy.yyyyyyyy W xxGP 6 6 23.0 169.0 18.0 Y x x Alt (HAE, MSL): 6353.675, 6407.480 ft xxGP 13 13 28.0 235.0 18.0 Y x x Speed: 0.11 mph xxGP 14 14 54.0 72.0 21.0 Y x x Track (true, var): 332.6, 11.0 deg xxGP 15 15 18.0 270.0 23.0 Y x x Climb: 0.00 ft/min xxGP 17 17 84.0 23.0 22.0 Y x x Status: 3D FIX (9 secs) xxGP 19 19 70.0 231.0 21.0 Y x x Long Err (XDOP, EPX): 0.61, +/- 30.1 ft xxGP 24 24 21.0 314.0 28.0 Y x x Lat Err (YDOP, EPY): 0.64, +/- 31.6 ft xxGP 30 30 26.0 151.0 16.0 Y x x Alt Err (VDOP, EPV): 0.81, +/- 61.1 ft xxGP 7 7 2.0 146.0 0.0 N x x 2D Err (HDOP, CEP): 0.87, +/- 54.2 ft xxGP 21 21 3.0 32.0 0.0 N x x 3D Err (PDOP, SEP): 1.19, +/- 74.2 ft xxSB134 47 0.0 0.0 0.0 N x x Time Err (TDOP): 0.88 xx x x Geo Err (GDOP): 1.87 xx x x ECEF X, VX: n/a n/a xx x x ECEF Y, VY: n/a n/a xx x x ECEF Z, VZ: n/a n/a xx x x Speed Err (EPS): +/- 43.0 mph xx x x Track Err (EPD): n/a xx x x Time offset: 0.551504007 s xx x x Grid Square: AABBCCDD xx x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqjmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj (location/grid square redacted) Looking at what the kernel thinks it has for gpio pins enabled I see this: root@ntp0:~# cat /sys/kernel/debug/gpio gpiochip1: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-20 ( |orangepi:red:status ) out lo gpio-102 ( |gmac-3v3 ) out hi gpio-166 ( |cd ) in lo IRQ ACTIVE LOW gpio-204 ( |usb0_id_det ) in hi IRQ gpiochip0: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl: gpio-354 ( |usb0-vbus ) out lo gpio-355 ( |sw4 ) in hi IRQ ACTIVE LOW gpio-362 ( |orangepi:green:pwr ) out hi root@ntp0:~# Is this indeed a case of the pin not being assigned an interrupt or is the pps-gpio IRQ mapping message unrelated to the problem? Thanks