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.

Orima

Members
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Orima reacted to robertoj in Orange Pi Zero 3 ili9486 TFT LCD   
    Yes. Please wait. I was busy with other personal projects, so I haven't been doing armbian stuff for a few weeks.
  2. Like
    Orima got a reaction from Igor in Build armbian kernel config   
    So, here's what I had to do to successfully build the image. First, I corrected my board file in the config/board/orangepizero3.csc directory. The processor value was incorrect, it was 616, so I set it to 618.
    Menuconf suggested selecting a board with a 618 chip, but in the board file it was listed as family 616.
    Later, I copied my board file to the userpatches directory and added the value CONFIG_DRM_PANEL_MIPI_DBI=m. Then I ran the image build script with the menuconf viewer. I was surprised that the CONFIG_DRM_PANEL_MIPI_DBI parameter already had the value "m"; previously, it was empty.
    After all these manipulations, the build went smoothly. Thank you so much for your support.
  3. Like
    Orima got a reaction from laibsch in Build armbian kernel config   
    So, here's what I had to do to successfully build the image. First, I corrected my board file in the config/board/orangepizero3.csc directory. The processor value was incorrect, it was 616, so I set it to 618.
    Menuconf suggested selecting a board with a 618 chip, but in the board file it was listed as family 616.
    Later, I copied my board file to the userpatches directory and added the value CONFIG_DRM_PANEL_MIPI_DBI=m. Then I ran the image build script with the menuconf viewer. I was surprised that the CONFIG_DRM_PANEL_MIPI_DBI parameter already had the value "m"; previously, it was empty.
    After all these manipulations, the build went smoothly. Thank you so much for your support.
  4. Like
    Orima reacted to robertoj in Orange Pi Zero 3 ili9486 TFT LCD   
    No, it wont work.
     
    I have made another thread just for the orange pi zero 3 and ili9488
    https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#comment-208446
    Change the GPIOs to match your wiring and connections.
     
  5. Like
    Orima reacted to robertoj in Orange Pi Zero 3 ili9486 TFT LCD   
    Starting with the DTS that worked for me in the orange pi zero 3, with ili9341:
     
     
    https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/?do=findComment&comment=204672
     
    My DTS is for a customized set of pins that works for me, and it is different than/from the waveshare set of pins.
     
    You need to change:
    * file name change to: ili9486-ads7846-spi1.dts
    * gpio pin selections everywhere in the DTS
    * "adafruit,yx240qv29" should be "ilitek,ili9486"
    * change "rotation" to "rotate"
    * change "reset-gpios = <&pio N N 0>;" to "reset-gpios = <&pio N N 1>;
     
    Then sudo armbian-add-overlay ili9486-ads7846-spi1.dts
    Reboot
     
    (does anyone know the correct DRM driver for ili9486?)

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.