Jump to content

Nuha Arina Rafiuddin

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @spender, looking at your configuration, I dont see anything obviously wrong, I check your wiring at it seem correct . There is some difference with my setting (like I disable spidev on the dts and not enable spidev on armbienEnv.txt) but I am not sure it is the problem since based on your dmesg, look like the kernel driver still successfully loaded. Unfortunately it seem you have to dig at the hardware level to troubleshoot. Here is my suggestion , not in particular order : - Use older kernel in which fbtft_device still exist (I think 4.19, I am sure there is armbian image with that kernel) to test the lcd. It easier using fbtft_device because you dont need to restart to test it. If you can make it work here great, that mean the wiring actually correct and your lcd work, then its a matter of making the mainline kernel work. - Test with logic analyzer, cheap saleae clone and sigrok goes really far. Make sure the signal is actually generated and WITH correct POLARITY. I found out that I have to reverse the reset signal polarity in the dts by doing this. If correct signal is generated but your lcd doesnt display anything, I am afraid your lcd is toast. - Make sure the lcd and driver are in same mode. Ili9341 can work with 8 bit or 9 bit spi, your module might only work with either setting or provide jumper to change the mode. However ili9341 kernel driver only work with 9 bit spi mode, so if you can't make the lcd work in 9 bit mode, I am afraid you cant use it with kernel driver.
  2. That post that I made is the result of the same frustation that you have. With my DT you atleast need to edit the gpio and spi controller used. Try using 5.4+ kernel too, because between 4.9 and 5.4 there are change regarding pin polarity. In my case it happen to the reset line. I have to debug this with logic analyzer Another option is to use old kernel where fbtft_device still available. I switch between 4.9 and 5.4 when doing research about this. Atleast I can be sure that my lcd is actually working
  3. I think you need to add param_spidev_spi_bus on armbianEnv. allwinner overlay example
  4. adding ssd1206 (those tiny monochrome oled) and nokia 5110 lcd Once getting one overlay work, adapting to another lcd is not that hard, assuming the driver actually work
  5. ili9225 : cant make it work Havent been able to make this lcd working properly. There seem to be driver for this in tinydrm, but after reading the source, I feel the driver is wrong. For one, it use 0x2A,0x2B etc to set RAM address, while ili9225 datasheet use 0x20 0x21 . There is flexfb support for this lcd, but the scanning looks bad and no matter what parameter I change , I cant fix it. So I'll give up on this lcd. video showing this : ili9225 test reference : https://crimier.wordpress.com/2019/12/03/ili9225-and-fbtft/
  6. Finally I got my lcd (some of them) to work with armbian on mainline kernel (5.4) using device tree overlay. It should be working on 4.19 kernel too. I test mine on orange pi zero. The one I am able to get working is ili9341 and st7735 based lcd. I'll add more detail later but for now I'd like to get this out. edit 1 : Adding ssd1306 and nokia 5110 overlay to the repo device tree overlay
  7. Just chiming in because armbianEnv corruption happen to me too.
  8. Thanks, I am confused because I see release notes for 5.60 but image in dl.armbian.com only have 5.59
  9. Will the image download updated to 5.60 too, or it is supposed to be "apt upgrade" from 5.59 ?
  10. I retried above case again with orange pi zero using armbian bionic and stretch. The phenomenon happen on both image. Additional things that I found out is that : after first boot : armbianEnv.txte created, armbianEnv.txt still has original content after second boot: armbianEnv.txt content replaced with sshd_config
  11. armbian creating armbianEnv.txte after first boot Hi, this is my first post in this forum, I don't know if this is the correct thread, but I just trying fresh Armbian 5.59 next on nanopim1, orangepi zero dan nanopiduo. After first boot, armbianEnv.txt content is replaced with these : # $OpenBSD: sshd_config,v 1.101 2017/03/14 07:19:07 djm Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sb and armbianEnv.txte file is created with content from original armbianEnv.txt. I verify that armbianEnv.txte is not exist on sd card just after flashing. I tried with 4 Sandisk brand and I can replicate the phenomenon. Is this a bug ?
  • Create New...