robertoj

From the Amazon and page, it looks like the lcd panel have a digitizer chip (instead of bare connection to the panel’s analog XY outputs, like others). Can you see the model of that chip U2? definitely needs a second SPI interface in the orange pi, or bitbanging.

Instead of replacing with your kernel deb, try modifying the linux config to have what you want. Sometime ago, I made instructions just for this, but for the orange pi zero https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md (warning, these instructions refer to a old kernel version) Look for the part that explains the "Change kernel configuration"

Darriy, thank you I tried it but it didn't work... did you install more packages related to WPA or encryption?

Here's a discussion about how sysfs is deprecated and you should be using gpiod (libgpiod)

Plug in another usb-serial device, see what happens in that case

Probably no dtbo will be needed. Find the 5 pins in your orange pi, that would be contacted by the hat, and try to control them with the Python code here: https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/?do=findComment&comment=181191 if that lorahat software is open source, then change that source code to point to the correct pin addresses

Please, can you share your hostapd.conf (minus the ssid and keys of course) I am running into other problems, but I am glad that others are getting hostapd working 👍

After the usb4-1 lines, you should have seen cdc_acm something You can check that you have the acm driver with: zcat /proc/config.gz|grep ACM you should see config_usb_acm=m Have you tried: ls /dev/ttyUSB* ? When you see the ttyACM*, you should get the by-serial files appear automatically (devrules function)

OrangePi has this analog audio figured out: http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_Zero_2W#Headphone_interface_audio_playback_test http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_Zero_3#Headphone_jack_playback_audio_test

Go and see the LibreElec project... find the image for Orange Pi PC. That's the OS that works with Orange Pi Zero. I think Cedrus for video codec is for the H2/H3 specifically... I dont know about H616/8. Wiki says that the codec hardware is not available in Linux http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_Zero_3

Is there something specially difficult about SPI versus I2C? Luckily, my servo controller I plan to use with my opiz3 is I2C, but I was hoping to use an SPI LCD too in the future. Is there an spi-overlay option in armbian-config? https://forum.armbian.com/topic/12571-opi-win-how-to-steering-rgb-led-apa106/

I returned to checking on my opiz3, and saw that there's a kernel update available... with related updated dtb's I will hold off from updating, and test it first in my non-production opiz3

https://www.armbian.com/orange-pi-zero-3/ Now it links to an OS image made on February 22. Try the non GUI image, and see if it makes a difference. See if the difference is with 802.11b, g or n Current and older releases: https://github.com/armbian/community/releases/tag/24.5.0-trunk.58 https://github.com/armbian/community/releases

I am using the armbian bookworm for Opiz3 from February 15 with zero problems. Are you using this image?

This is an artificial limitation on the linux uvc driver, which handles webcams Try connecting the 2nd webcam in a port in a different USB root inside your orange pi. Or try following this guide https://www.thegoodpenguin.co.uk/blog/multiple-uvc-cameras-on-linux/

Instead of connecting to /dev/ttyUSB0,1,2,3.. or /dev/ttyACM0,1,2,3... there are links in the /dev/serial/by-id/ and /dev/serial/by-path/ folders with links that are constant, relative to the USB adapters inside the 3D printers.

Thank you... I will continue to use fdtoverlay 👍

usual user, I compiled the "con1" dtso you provided, but I didn't integrate it in the whole SBC dtb. I left it as a dtbo and copied it to the user overlays... it worked and I have the opiz3 gpio pins named 😄 As a reminder, here's how to do it: {start with a fresh armbian OS, or make sure that the orangepizero3 dtb is the original} # cat /sys/kernel/debug/gpio {check that the GPIO pins are not named} {copy the dtso to /boot/user-overlays} # dtc --in-format dts sun50i-h618-orangepi-zero3-con1.dtso --out sun50i-h618-orangepi-zero3-con1.dtbo # ls -l total 8 -rw-r--r-- 1 root root 591 Feb 18 01:35 sun50i-h618-orangepi-zero3-con1.dtbo -rw-r--r-- 1 root root 1374 Feb 17 22:36 sun50i-h618-orangepi-zero3-con1.dtso # nano /boot/armbianEnv.txt {add line: user_overlays=sun50i-h618-orangepi-zero3-con1} # reboot # cat /sys/kernel/debug/gpio {the gpio pins are named} I was expecting it that the user overlays appear in the armbian-config utility... but my dtbo didnt show in the system>hardware selection options... is this normal? To any newbie trying this: be careful of conflicts in activating a kernel-provided overlay and a user overlay at the same time: https://docs.armbian.com/User-Guide_Allwinner_overlays/ I just noticed that there's a February 15 linux image... I will try that Update... the compiled dtso did not work for the new linux OS image... uboot could not overlay the dtbo and I noticed that it uses a different dtb... what should I do to update the dtso and make it work? sun50i-h618-orangepi-zero3.dtb HOWEVER: the DTSO works when applying it in the DTB, as you suggested. It is only when trying to apply the DTBO with uboot, it fails. Unfortuately, the linux os freezes after 10 minutes or so nevermind... it maybe another cause...

https://www.amazon.com/Expansion-Connector-Interface-Development-Computer/dp/B0CHMTT4XP/ http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/2W-expansion-board.html http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_Zero_2W#24Pin_expansion_board_interface_pin_description In the tiny 24 pin expansion connector Pin 22=left audio Pin 23=right audio Pin 24=ground In armbian, orangepizero 3 audio support is missing, as of 2024-Feb-15... so you should try it and see if it works or not in opiz 2w (probably not). Then, use the OFFICIAL OrangePi Zero 3 Debian with Linux 6.1. The audio should work. Then tell us in the OrangePi Zero 2W thread. Raspberry Pi has a whole different ARM CPU... don't expect that hardware is going to work exact the same way.

Audio on the opiz2w is through the "expansion interface". Have you seen other boards using the PWM for audio? There's a thread about the opiz2w... use that

"usual user" has posted instructions to incorporate your dtbo inside the dtb... but I personally like having a separate dtbo that is applied by uboot. https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/?do=findComment&comment=181688 dtb and dtbos are the correct way to assign pins and tell the kernel where everything is. I don't think there's anything wrong with the boot process, if it only needs a dtbo to start working correctly. Everything depends on having good dtb and dtbos.

Thank you! I will try it later... but I can see how the dtso is structured

With armbian's DTB. cat /sys/kernel/debug/gpio root@orangepizero3:~# cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/300b000.pinctrl, 300b000.pinctrl: gpio-76 ( |red:status ) out lo gpio-77 ( |green:power ) out hi gpio-80 ( |regulator-usb1-vbus ) out hi gpio-166 ( |cd ) in lo ACTIVE LOW gpio-210 ( |reset ) out hi ACTIVE LOW gpiochip1: GPIOs 352-383, parent: platform/7022000.pinctrl, 7022000.pinctrl: root@orangepizero3:~# With the DTB you created yesterday root@orangepizero3:~# cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-287, parent: platform/300b000.pinctrl, 300b000.pinctrl: gpio-69 (con1-13 ) gpio-70 (con1-11 ) gpio-71 (con1-22 ) gpio-72 (con1-15 ) gpio-73 (con1-07 ) gpio-74 (con1-26 ) gpio-75 (con1-12 ) gpio-76 ( |red:status ) out lo gpio-77 ( |green:power ) out hi gpio-78 (con1-18 ) gpio-79 (con1-16 ) gpio-80 ( |regulator-usb1-vbus ) out hi gpio-166 ( |cd ) in lo ACTIVE LOW gpio-210 ( |reset ) out hi ACTIVE LOW gpio-226 (con1-08 ) gpio-227 (con1-10 ) gpio-228 (con1-05 ) gpio-229 (con1-03 ) gpio-230 (con1-23 ) gpio-231 (con1-19 ) gpio-232 (con1-21 ) gpio-233 (con1-24 ) gpiochip1: GPIOs 352-383, parent: platform/7022000.pinctrl, 7022000.pinctrl: root@orangepizero3:~# And, the result of gpioinfo is: And the contents of pinmux-pins

THANK YOU. I will try this tonight

Thank you... I already got the help that I personally needed to get my work project rolling again I want to learn how to make a DTS, compile it into a DTBO and make a Pull Request I agree that GPIOD is less capable than MRAA. I may have the time to learn how to make it work.