elsabz
Members-
Posts
17 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
@royk thanks for the answer but this Virtual Desktop is out of the discussion, what I want is to reach the same point that I had experimented with Raspberrypi. With the raspi-config I could set a fixed resolution that was activated even if there was no display connected to the hdmi. Achieving this result would be the goal of this discussion, thanks anyway!
-
On my Orange Pi 5, I have successfully installed the X11VNC server. I followed the guide at the following link X11VNC and everything works as expected. I can connect with Real VNC from another device and see the desktop of the Orange Pi as if I were in front of its display. However, when the Orange Pi 5 is powered on without a display connected to the HDMI port, the access with Real VNC doesn't work as before. I get a black screen and I am unable to interact with the Orange Pi. I had a similar issue with Raspberry Pi, where I could resolve it by setting a default screen resolution. How can I achieve this with Armbian? How can I configure an alternative resolution when the HDMI port is not connected?
-
WiringOP-Next Oops: Unable to determine board revision...
elsabz replied to elsabz's topic in Orange Pi 5
I managed to solve the problem by myself! I found that I had a number of libwiringPi files inside the /usr folder, they are probably left over from previous attempts to install the wiringpi library. I removed these files manually and then proceeded to install the correct library After this gpio readall started working again -
I don't know why, I think after doing "sudo apt update/upgrade" (but I'm not sure), the wiringOP library on "orange pi 5" with Armbian 23.02.2 doesn't work anymore. If I run the command "sudo gpio readall" I get the following output: Oops: Unable to determine board revision from /proc/device-tree/system/linux,revision or from /proc/cpuinfo -> No "Hardware" line -> You'd best google the error to find out why. Can anyone help me solve this problem?
-
Orange PI5 - WiringOP - Interrupt NOT WORKING, How can it be activated ?
elsabz replied to elsabz's topic in Orange Pi 5
@royk Unfortunately it doesn't work for me, but I have to do a test by grounding the input, I'm doing it this weekend, thanks -
Orange PI5 - WiringOP - Interrupt NOT WORKING, How can it be activated ?
elsabz replied to elsabz's topic in Orange Pi 5
@royk With the command you suggested, when I run the code it no longer gives an error, but sadly the interrupt doesn't work! Is it possible that the orange PI 5 interrupt is not implemented at the hardware level? -
Orange PI5 - WiringOP - Interrupt NOT WORKING, How can it be activated ?
elsabz replied to elsabz's topic in Orange Pi 5
Hi @royk i check with the next branch is the same problem... -
Orange PI5 - WiringOP - Interrupt NOT WORKING, How can it be activated ?
elsabz replied to elsabz's topic in Orange Pi 5
Hi @royk thanks for the answer, I had already looked in the library but I can't find anything different from the code I use, if you look at the isr.c example the call is the same as the one I use, except for the number of PINs that goes from 0 to 7, I tried to put PIN 0 but nothing changes, always the same error. -
Hello Armbian forum, I need to have a GPIO interrupt on Orange PI5. I have successfully installed WiringOP and I am using it with C code. The problem is that the interrupt is not working, and I am receiving the following error. How can I proceed? Does anyone know how to enable the WiringOP interrupt on the GPIO PIN? Code C : #define AUX 13 wiringPiISR(AUX, INT_EDGE_FALLING, &MyFunction); Error: wiringPiISR: unable to open /sys/class/gpio/gpio92/value: No such file or directory PS. I have just successfully installed this version: Armbian 23.02 Jammy Gnome
-
Thanks @usual user for the reply, ok I also saw this way of describing the hardware in the post I linked at the beginning. Unfortunately I'm new in armbian (I apologize but I'm ignorant), so please I ask you to follow me in the next description. The following structure is located in the /boot folder: /boot -> dtb -> amlogic -> overlay -> dtb-6.1.11-meson64 -> amlogic -> overlay In the amlogic folders (both in one path and in the other) there are several .dtb files. Files named odroid-n2-plus are as follows: meson-g12b-odroid-n2-plus.dtb meson-g12b-odroid-n2-plus-spi.dtb Where is it determined which file is to be used? These files I can easily convert to dts and then compile dtb. Which files should I edit? In which path should I change them?
-
Hi @Igor thanks for the answer, the first thing I did is armbian-config: System -> Hardware -> uartA and uartB enabled, then reboot. Unfortunately it doesn't work! With "ls /dev/tty*" I see all ports tty0-50, ttyS0-7, ttyAML0, any port gives me input/output error when I access it. How can I edit device tree and enable this UART ? Where can I find the information?
-
Hello, i need to activate the serial port on the odroid N2-plus, the serial port is on pins (J2 - 2x20 PINS) 8/10. Usually this uart with ubuntu is at /dev/ttyS1. If I try to use it on armbian I get an input/output error. I read the following post, I understand that it is not implemented yet. Can anyone point me in the direction of trying to do this?
-
Hi thank you all now the audio works!
-
Hi all, after installing the latest version of Armbian (Jammy 6.1.11 desktop) I found that HDMI monitor audio is not working. With the Ubuntu MATE version of odroid the audio worked. Armbian seems more powerful and its look is much better than MATE, I hope I can solve all the problems because I don't want to go back to MATE anymore, How can I make HDMI audio work? Thanks in advance... PS. I have already updated the firmware to full with the WiFi USB stick problem which has since been resolved
-
Odroid N2+ USB Wifi RTL8811 How to install driver?
elsabz replied to elsabz's topic in Odroid N2/N2+
Stop everyone, problem solved!!! I did a fresh install of the armbian image to start fresh. Then I ran "sudo apt-get update", then ran "sudo apt-get install armbian-firmware-full". At the end of this update I noticed that with "lsusb" the Realtek device had a strange "CD rom mode". Reading on the net I installed "sudo apt-get install usb-modeswitch" then executed at least twice the command "sudo usb_modeswitch -KW -v 0bda -p 1a2b". Then I found the wlan interface. With "sudo armbian-config" I configured the WiFi and now everything works fine! 💪 The only thing I don't like so much is that the WiFi interface is not called wlan0 but wlxa0d768106782 which is not very simple! Thanks Werner for the tip, I hope it can be useful to someone else 😀