Jordan1x

I’m working on an Armbian box for a project, and getting the DT (device tree) right at boot has been a real pain. This guide cleared up some confusing bits, especially with my microcontroller. Thanks!

Hi everyone, I recently got an ESP-WROOM-32 Development Board to use as a companion board for my Armbian SBC setup. My goal is to have the ESP32 collect sensor data and send it to the Armbian host over serial or WiFi. It works okay at first, but after a while running a Python script, the ESP32 crashes or stops sending data. Setup Details: Armbian running on a Banana Pi (or similar SBC) ESP-WROOM-32 connected over serial (USB-to-TTL) and also configured via WiFi Python script (on the Armbian side) reads from the serial port / receives via a simple socket over WiFi Power supply is stable; using 3.3 V TTL logic on ESP and stable USB power Now here are my issues: Script runs fine for some minutes (5–10), then suddenly no data from ESP3. ESP32 sometimes reboots (observed via onboard LED), sometimes appears alive but unresponsive. Logs show no obvious error messages; serial just quiet or times out I've tried lowering the serial baud rate. Added delays / sleeps in code to reduce data flood. Ensured the USB-power to ESP32 is stable / using good cable. Tried Py serial and different socket listener scripts Could USB-TTL or serial USB drivers under Armbian be causing issues (overheating, buffer overflows)? Would switching fully to WiFi (TCP/UDP) instead of serial help stability? Any tools or logging tips on Armbian to catch the crash (kernel logs, serial trace, etc.)? Thanks in advance for any advice. Jordan

Hi all, I’m running Armbian 24.5 (Ubuntu Jammy CLI) on an Orange Pi 3 LTS with kernel 6.6.y, trying to use a CH341A Mini Programmer to flash an SPI EEPROM chip. But I’m stuck, the programmer isn’t detecting the chip at all. Connected the module to the chip using the correct pins (CS, MOSI, MISO, CLK). Powered the chip at 3.3V to match Armbian’s logic level. Used flashrom on Armbian (via terminal) to detect the chip, but it returns “no device” or similar errors. Tried different USB ports, different cables , same result. Do I need to match some specific SPI mode or speed for Armbian or for specific EEPROMs? Is there an issue with voltage levels or pull-up / pull-down resistors that often catches beginners? Any recommended OS commands/logs to check so I can see what’s going wrong (e.g. permissions, USB detection, lsusb output)? Thanks in advance for your help!

Hi all, I'm trying to use a DHT11 temperature and humidity sensor with my Armbian-based Orange Pi. I grabbed this DHT11 module. It’s cheap and seemed ideal for simple readings. The wiring matches the usual 3.3 V setup (VCC, data, GND), and I'm using the Adafruit_DHT Python library with the right pin number. Here’s my problem: Readings work perfectly right after reboot. tempo is consistent and logical. After a few minutes, the humidity values hang (stuck at 0 %), and temperature readings start to spike randomly or freeze. Resetting the board or restarting the Python script often fixes it temporarily. I've double-checked wiring (no loose connections), shielded against shorts, and even tried using a 10 k pull-up resistor on the data line. but the issue persists. Questions: Could this be a timing issue with how the Armbian kernel handles the GPIO? Any known quirks with DHT11 + Armbian or Orange Pi boards? Would using a level shifter or adding a small capacitor help stabilize the data line? Would love to hear from anyone who’s successfully run DHT11 sensors on Armbian or suggestions on how to dig into what's causing the freeze-up. Thanks for any help! —Jordan