Matthai

Oh, thanks. Stupid me.

Hi, I am running Armbian 23.02.2 Bookworm with Linux 5.15.93-sunxi on OrangePi PC Plus. When I say sudo apt update, I get this output: Nap:6 http://imola.armbian.com/apt bokworm Release 404 Not Found [IP: 93.103.15.56 80] Branje seznama paketov ... Narejeno E: The repository 'http://apt.armbian.com bokworm Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware' N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/armhf/release-notes/ch-information.html#non-free-split Can anyone help?

I had the same issue after upgrade and I just removed noscan=1 option from hostapd.conf. BTW, here is the listing from armbianmonitor, if anyone finds it useful: http://ix.io/3xDv

I am looking for a device that has good support for being WiFi access point and being in client (managed) mode at the same time. Which can you recommend?

Hi, I am looking for a device that has good support for being WiFi access point and being in client (managed) mode at the same time. Which can you recommend?

I have a similar problem. i2c detect detects OLED, I was using Codelectron library, but it seems it stopped working. However, I tried to install Luma library, but I am getting some error: sudo -H pip3 install -e . Obtaining file:///home/matej/luma.examples Collecting argcomplete (from luma.examples==0.0.0) Downloading https://files.pythonhosted.org/packages/b7/9e/9dc74d330c07866d72f62d553fe8bdbe32786ff247a14e68b5659963e6bd/argcomplete-1.12.3-py2.py3-none-any.whl Collecting luma.core>=1.17.1 (from luma.examples==0.0.0) Using cached https://files.pythonhosted.org/packages/e9/c8/878165a9413bcf4745a396809646f16a2eb00eba5589bf5aac1817bf3ce3/luma.core-2.3.1-py2.py3-none-any.whl Collecting luma.emulator>=1.3.0 (from luma.examples==0.0.0) Downloading https://files.pythonhosted.org/packages/53/2c/d00bcb9bb02a7a6b36bc984a577181d2ce08709d630cf80739465ef05f43/luma.emulator-1.4.0-py2.py3-none-any.whl Collecting luma.lcd>=2.5.0 (from luma.examples==0.0.0) Downloading https://files.pythonhosted.org/packages/4f/a9/b84d13a24e2393ffe989d0fb19c4ba3f8e83abf71fbe487528b7105e2ce7/luma.lcd-2.9.0-py2.py3-none-any.whl Collecting luma.led_matrix>=1.5.0 (from luma.examples==0.0.0) Downloading https://files.pythonhosted.org/packages/c9/2d/ffe0f4c610b2740f5ed16dd3d7179cd28d935f1ea851812871ee739da738/luma.led_matrix-1.5.0-py2.py3-none-any.whl Collecting luma.oled>=3.6.0 (from luma.examples==0.0.0) Using cached https://files.pythonhosted.org/packages/d5/3c/2a464be33c7a29633506b75c579cb50356a1e788609db809bf7999c74511/luma.oled-3.8.1-py2.py3-none-any.whl Collecting importlib-metadata<5,>=0.23; python_version == "3.7" (from argcomplete->luma.examples==0.0.0) Downloading https://files.pythonhosted.org/packages/8e/e2/49966924c93909d47612bb47d911448140a2f6c1390aec2f4c1afbe3748f/importlib_metadata-4.0.1-py3-none-any.whl Requirement already satisfied: pillow>=4.0.0 in /usr/lib/python3/dist-packages (from luma.core>=1.17.1->luma.examples==0.0.0) (5.4.1) Requirement already satisfied: pyftdi in /usr/local/lib/python3.7/dist-packages (from luma.core>=1.17.1->luma.examples==0.0.0) (0.52.9) Collecting RPI.GPIO; platform_system == "Linux" (from luma.core>=1.17.1->luma.examples==0.0.0) Using cached https://files.pythonhosted.org/packages/cb/88/d3817eb11fc77a8d9a63abeab8fe303266b1e3b85e2952238f0da43fed4e/RPi.GPIO-0.7.0.tar.gz Requirement already satisfied: deprecated in /usr/local/lib/python3.7/dist-packages (from luma.core>=1.17.1->luma.examples==0.0.0) (1.2.12) Requirement already satisfied: smbus2 in /usr/local/lib/python3.7/dist-packages (from luma.core>=1.17.1->luma.examples==0.0.0) (0.4.1) Requirement already satisfied: cbor2 in /usr/local/lib/python3.7/dist-packages (from luma.core>=1.17.1->luma.examples==0.0.0) (5.2.0) Collecting spidev; platform_system == "Linux" (from luma.core>=1.17.1->luma.examples==0.0.0) Using cached https://files.pythonhosted.org/packages/62/56/de649e7d95f9fcfaf965a6eb937b4a46bc77ef21487c99cde1a7a0546040/spidev-3.5.tar.gz Collecting pygame (from luma.emulator>=1.3.0->luma.examples==0.0.0) Downloading https://files.pythonhosted.org/packages/c7/b8/06e02c7cca7aec915839927a9aa19f749ac17a3d2bb2610b945d2de0aa96/pygame-2.0.1.tar.gz (5.5MB) 100% |████████████████████████████████| 5.5MB 47kB/s Complete output from command python setup.py egg_info: WARNING, No "Setup" File Exists, Running "buildconfig/config.py" Using UNIX configuration... /bin/sh: 1: sdl2-config: not found /bin/sh: 1: sdl2-config: not found /bin/sh: 1: sdl2-config: not found /tmp/pip-install-psoj4g37/pygame/setup.py:44: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5 distro = platform.linux_distribution() Traceback (most recent call last): File "<string>", line 1, in <module> File "/tmp/pip-install-psoj4g37/pygame/setup.py", line 318, in <module> buildconfig.config.main(AUTO_CONFIG) File "/tmp/pip-install-psoj4g37/pygame/buildconfig/config.py", line 221, in main deps = CFG.main(**kwds) File "/tmp/pip-install-psoj4g37/pygame/buildconfig/config_unix.py", line 194, in main DependencyProg('SDL', 'SDL_CONFIG', 'sdl2-config', '2.0', ['sdl']), File "/tmp/pip-install-psoj4g37/pygame/buildconfig/config_unix.py", line 39, in __init__ self.ver = config[0].strip() IndexError: list index out of range Hunting dependencies... --- For help with compilation see: https://www.pygame.org/wiki/CompileDebian To contribute to pygame development see: https://www.pygame.org/contribute.html --- ---------------------------------------- Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-psoj4g37/pygame/ Any idea how to solve this?

Hi, I have a OLED display on OrangePi Zero H5. OLED is SSD1306 (128 x 64 pixel) and is detected with i2c scan. I used this library: https://github.com/codelectron/ssd1306 and it was working just fine. However, after some time (it is possible that it was after some update) OLED display stopped working - it is showing just random pixels. I checked soldering (it is OK), even replaced OLED with another one, but no luck. I am running fully updated Armbian (10.9), uname -a says: Linux myopi 5.10.21-sunxi64 #21.02.3 SMP Mon Mar 8 00:45:13 UTC 2021 aarch64 GNU/Linux Is there any tutorial how to set up OLED display with OrangePi Zero H5 and H3 version and any hint what could be wrong in my case? Because as I said, display was already working, and I did not change anything in hardware...

No?

If I say sudo apt update, I got this error: Hit:2 http://ports.ubuntu.com bionic InRelease Hit:3 http://ports.ubuntu.com bionic-security InRelease Hit:4 http://ports.ubuntu.com bionic-updates InRelease Hit:5 http://ports.ubuntu.com bionic-backports InRelease Ign:1 https://apt.armbian.com bionic InRelease Err:6 https://apt.armbian.com bionic Release Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 193.40.103.96 443] Reading package lists... Error! W: http://apt.armbian.com/dists/bionic/InRelease: No system certificates available. Try installing ca-certificates. W: http://apt.armbian.com/dists/bionic/Release: No system certificates available. Try installing ca-certificates. E: The repository 'http://apt.armbian.com bionic Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Encountered a section with no Package: header E: Problem with MergeList /var/lib/apt/lists/ports.ubuntu.com_dists_bionic_main_binary-armhf_Packages.lz4 E: The package lists or status file could not be parsed or opened. However, if I open https://apt.armbian.com on my computer, TLS connection is just fine. But on a Armbian (Ubuntu 18.04.2 LTS), I got this: curl https://apt.armbian.com curl: (77) error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs Any idea why this happened?

OK, just an information for others, how I solved this: 1. Install Armbian (on OrangePi Zero H2+) 2. Install Python: sudo apt install python python-pip python-setuptools python-dev 3. Install pyA20: sudo pip install pyA20 4. Install GPIO: git clone https://github.com/nvl1109/orangepi_zero_gpio cd orangepi_zero_gpio/ sudo python setup.py install cd .. 5. Create new Python app: nano reed.py With the content: #!/usr/bin/env python import os import sys if not os.getegid() == 0: sys.exit('Script must be run as root') from time import sleep from pyA20.gpio import gpio from pyA20.gpio import port button = port.PA10 gpio.init() gpio.setcfg(button, gpio.INPUT) """Enable pullup resistor""" gpio.pullup(button, gpio.PULLUP) #gpio.pullup(button, gpio.PULLDOWN) # Optionally you can use pull-down resistor try: print ("Press CTRL+C to exit") while True: state = gpio.input(button) # Read button state if (state == 1): print ("The door is OPENED.") else: print ("The door is CLOSED.") sleep(0.5) except KeyboardInterrupt: print ("Goodbye.") 6. Connect reed switch: - one wire to GND - the other wire to GPIO 26 (PA10) 7. Run the app: sudo python reed.py The output: The door is OPENED. The door is OPENED. The door is OPENED. The door is OPENED. The door is OPENED. The door is CLOSED. The door is CLOSED. The door is CLOSED. The door is CLOSED. The door is OPENED. The door is OPENED. Now... the web app. But this is another story.

OK, I see. So I connect reed switch to GND and GPIO pin and enable internal resistor: gpio.setcfg(button, gpio.INPUT) gpio.pullup(button, gpio.PULLUP) # enable internal pullup resistor I am confident, but what is happening when device is booting? Is it possible, that device goes to some weird state and GPIO pin set to output during device init? By low value you mean 1k, more, less?

OK, I see. I just got confused by gpio1p40 notation. Thanks for clarification. I assume I can connect switch to 3.3V or GND, it will just read the different state (once open, the other closed). But what about resistor? 4.7 kOhm together with internal pullup resistor seems OK? I mean, it is not necessary, but if GPIO pin is accidentally set to output, then I assume it will protect the board from frying? Or I am wrong?

Sorry, I do not understand. As I understand, this: button = connector.gpio1p40 #CHOW This means, that button is connected to gpio1p40. In your link, I cannot find which pin that would be. I mean physically, where to connect reed switch, on which pins exactly?

I would like to connect reed switch to OrangePi Zero with H2 processor. Can I use this? https://github.com/duxingkei33/orangepi_PC_gpio_pyH3 Under examples, there are two examples I think I could use: - read_button.py - read_key_PG7.py I have two questions. 1. Where is the pinout? read_button.py has this code: led = connector.gpio0p0 # This is the same as port.PH2 button = connector.gpio3p40 read_key_PG7.py has this code: led = connector.gpio1p38 # This is the same as port.PH2 button = connector.gpio1p40 #CHOW Which pins are which, where to get the picture of GPIO pins? (And why LED's connector ID's are different in the above examples)? Here is one example of pinouts, but the names are different: http://codelectron.com/blink-leds-using-orange-pi-zero-gpio-and-python/ 2. Where to connect reed switch? One is one of the GPIO pins, and other? GND, 5V, 3.3V? And - I assume I do not to use a resistor? Or I am wrong?

Thanks for advices. BTW, is there any search engine among these devices? I mean among development boards. That you are able to select how many USB's does it have, does it have HDMI, eMMC,...