• Content Count

  • Joined

  • Last visited

About icce

  • Rank

Recent Profile Visitors

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

  1. Follow my attempt to make touch work on Pine64. I confirmed that "ads7846" and "ads7846_device" already installed. Even though there was a warning about missing "system.map" but it seems those modules have been installed. lsmod and ads7846 was there but not ads7846_device. I tried dmesg | grep ads7846 but it gave error: ads7846_device: Unable to get IRQ assigned to gpio_pendown' It seems that Armbian Mainline on Pine64 has not configured assign interrupt for pin?! Or kernel for Pine64 cannot IRQ for GPIO71 sudo modprobe ads7846_device model=7846 cs=1 gpio_pendown=71 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900 Any idea?!
  2. Mainline stable Armbian stable for Pine64 worked great. I have successfully make my 3.5 TFT screen work but not the touch screen. I read some tutorials, mostly guide. This guide for TFT and Touch is really detailed. For touch: - Step 1: ads7846 driver seems ok - Step 2: ads7846_device there is a warning after make and make install, and it said to skip depmod - After this, I tried sudo modprob ads7846 sudo modprob ads7846_device model=7846 cs=1 gpio_pendown=1 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900 ads7846 is ok (confirmed with lsmod). But ads7846_device return invalid argument, it means that module ads7846_device is not in the system. Anyone succeed with Pine64?
  3. @Fenn Do you still have to put something other on armbianEnv.txt and boot.cmd or just put extraaargs to make it worked?
  4. @Igor I double checked my script and made a mistake about fbtft. After followed @martinayotte, the screen changed to black (not fully black), and /dev/fb0 appeared. So I thought that initialized ok, but actually not ok. The working script should be: sudo modprobe fbtft_device name=piscreen gpios=reset:79,dc:78 speed=16000000 The important parts here are choosing right gpios (reset & dc) and speed (for color correction). After this step, the others are almost the same with Rpi. (Pygame should define SDL_FBDEV=/dev/fb0 & SDL_VIDEODRIVER=fbcon ???)
  5. @Igor I have checked your github but no success. The problem I found that modules fbcon is not loaded. When I tried "sudo modprobe fbcon" it return: modprobe: FATAL: Module fbcon not found in directory /lib/modules/4.19.13-sunxi64 PS: I rechecked and fbcon folder still in /sys/class/graphics and while I add fbtft to /dev/fb0. I still don't know why when I set SDL_FBDEV to /dev/fb0 I still get the error.
  6. Thanks @martinayotte for the suggestion. I made LCD initiated and /dev/fb0 appeared. But I got another problem when tried to display something on it. My intention is to use python display information on LCD, so that I use pygame. But when I tried to start screen display there is error which I could not find the answer.
  7. I have a Pine64+ 2GB and use Waveshare 3.5 (A). Armbian Bionic Ubuntu installed. I tried to initiate Waveshare screen by following steps: - Enable spidev0.0 from armbianEnv.txt (confirm with /dev/spidev0.0) - modprobe fbtft by: sudo modprobe fbtft_device name=piscreen But I got error with step 2. Here is the output of dmesg [ 4419.154174] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.163004] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.164436] spidev spi0.0: spidev spi0.0 1000kHz 8 bits mode=0x00 [ 4419.164564] spidev spi0.0: Deleting spi0.0 [ 4419.165176] fbtft_device: GPIOS used by 'piscreen': [ 4419.165183] fbtft_device: 'reset' = GPIO25 [ 4419.165187] fbtft_device: 'dc' = GPIO24 [ 4419.165190] fbtft_device: 'led' = GPIO22 [ 4419.165203] spi spi0.0: fb_ili9486 spi0.0 32000kHz 8 bits mode=0x00 [ 4419.186567] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned. [ 4419.188554] fb_ili9486 spi0.0: fbtft_request_gpios: gpio_request_one('reset'=25) failed with -517 It seems that GPIO25 is not responded. I know that many have success with OrangePi, but no one with Pine64. Any suggestion? Thanks.