Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cyryl Sochacki

Members
  • Joined

  • Last visited

Everything posted by Cyryl Sochacki

  1. @robertoj only boards with A20. I know they work with Banana Pi , Banana PRO (From lemaker) and Banana M1 and M1+ (from SINOVOIP).
  2. Update: touch works now! The LeMaker 7" panel works completely on the Banana Pi Pro with a current kernel (Armbian Debian 13 trixie, kernel 6.18): display, backlight and touch. The 5" panel works too (display confirmed, touch uses exactly the same controller and wiring as the 7"), and the same image also runs on the original Banana Pi. Getting touch to work needed two fixes. First, the pin called ctp_wakeup in the old fex files (PH7) is actually the RESET line of the FT5x06 controller. Described as a "wake" pin, the edt-ft5x06 driver only waits 5 ms after power-up, and the controller doesn't answer yet. Described as reset-gpios, the driver waits 300 ms and the controller responds. Second, at boot the driver's first probe always fails with an I2C bus error (mv64xxx Ctlr Error, status 0x0, error -11), while the same probe a moment later succeeds. For now a small systemd service retries binding the driver after boot, so touch works right away. If anyone has an idea what causes that first I2C error on the A20, I'd be happy to hear it. There's now a single image for all panels with the XFCE desktop. The 7" panel is enabled by default, and you can switch panels with sudo lemaker-lcd 5 (or 35, 7, off) followed by a reboot, or by uncommenting one line in /boot/armbianEnv.txt. Image, overlays and build scripts: https://github.com/cyryllo/fex_configuration/releases https://photos.app.goo.gl/pM8WR9rU6tHn9ESh9
  3. Quick update: the LeMaker panels work on current kernels! I've tested the 5" and 7" panels on real hardware, and both work on the Banana Pi Pro as well as on the original Banana Pi (non-Pro), using the same image (Armbian Debian 13 trixie, kernel 6.18). The picture appears as soon as the kernel starts, the backlight works too. The 3.5" panel is still untested since I don't have it, but it shares almost everything with the 5" one, so it will most likely work as well. The minimal image has no desktop, so I couldn't check touch yet. I'm now preparing an image with the XFCE desktop, which also includes a simple script to switch panels after boot (sudo lemaker-lcd 5 / 7 / 35 / off), so a single image will work with every panel. I'll post soon whether touch works too. Overlays, build scripts and images: https://github.com/cyryllo/fex_configuration
  4. Hi everyone, After a long break I'm coming back to this topic. Since the old fex/script.bin files only work with the sunxi-3.4 kernel, I've prepared a new configuration for current mainline kernels: device tree overlays for all LeMaker LCD panels for the Banana Pi Pro (LeMaker Banana Pro): - 3.5" RGB 320x240 (BL035-RGB-002) - 5" RGB 800x480 - 7" LVDS 1024x600 - FT5x06 capacitive touch for all of them (edt-ft5x06 driver) All timings, pins, power, backlight and touch settings were taken 1:1 from the original LeMaker fex files. Looking back at my posts from 2023, the missing piece was partly what I suspected: the panel has to be connected to tcon0_out in the device tree, and on A20 the display controller only switches to LVDS mode when the panel is described as "panel-lvds". The overlays handle both. The current Armbian sunxi kernel also includes the fix for the inverted LVDS polarity (the "red screen / backlight but no picture" problem some of you reported). What I have ready: - .dts overlays for each panel (install with armbian-add-overlay) - ready-to-flash images: Armbian Debian 13 (trixie) minimal, kernel 6.18.58, built with the Armbian build framework, one image per panel (3.5", 5", 7"), with the touch driver already enabled and the selected panel turned on in armbianEnv.txt Repository (overlays + build scripts): https://github.com/cyryllo/fex_configuration Important: so far I've only verified that the overlays compile and apply correctly to the Banana Pro device tree. I'll test them on real hardware tomorrow (I have the 5" and 7" panels, I don't have the 3.5"). If anyone still has one of these displays and would like to help with testing, let me know and I'll share the image for your panel. A short report of what you see on the screen (black / backlight only / picture OK) plus the output of this command would help a lot, especially for the 3.5" panel: dmesg | grep -iE "sun4i|lvds|panel|edt|pwm" I'll post the results of my own tests here. Test img: https://github.com/cyryllo/fex_configuration/releases
  5. Hi, I'm working on bringing back support for the original LeMaker LCD panels on the Banana Pi Pro (LeMaker Banana Pro, A20) with current Armbian kernels. The old script.bin / fex files only worked with sunxi-3.4, so I ported the settings to device tree overlays: - 3.5" RGB 320x240 (BL035-RGB-002, already in panel-simple) - 5" RGB 800x480 (panel-dpi) - 7" LVDS 1024x600 (panel-lvds) - FT5x06 touch for all three (edt-ft5x06 driver) Repository: https://github.com/cyryllo/fex_configuration The overlays compile and apply cleanly to sun7i-a20-bananapro.dtb (kernel 6.18). I'm now building a Debian 13 (trixie) minimal image with the Armbian build framework that includes the overlays and the edt-ft5x06 module, and I'll test it on my 5" and 7" panels. I don't have the 3.5" panel, so testers are welcome. Plan once it's tested: - enable CONFIG_TOUCHSCREEN_EDT_FT5X06=m in the sunxi kernel config - submit the overlays, so the panels work on standard images I've also applied to become the maintainer of this board, as it currently has none. Feedback and test reports are very welcome.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.