Jump to content

mrroland

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Ok, I finally got a workaround: I connected the digitizer to a cheap USB touchscreen driver I ordered from China. Touchscreen instantly worked. I only had to invert the x-axis. So I guess there is a design flaw in the touchscreen driver circuit on the lcd pcb.
  2. Hi, Thanks for the reply. First solution didn't work for me. When I wanted to try the second one I discovered that the armbian image from the download section uses a 3.x kernel, so I can't run the script for the accelerated drivers. I tried to install a desktop environment to the nightly build with 4.x kernel, but I couldn't get it to work... But I think it's a kernel issue because the purple line is visible as soon as the boot sequence starts. This won't happen with the official odroid image. I guess I should stick to the official image for now and compile the kernel modules I'm missing for that version.
  3. Hi Guys, I tested both the odroid official and armbian images for the XU4. Both run well, but I prefer the armbian image. I have attached my 800x480 hdmi display, it works, but there's a purple line at the left side of the display. ( I think it's one pixel wide) This is not the case with the odroid official image, so I guess it's a configuration issue. I took a look at the boot. ini file, but I don't see anything that rings a bell. Can somebody point me to the right direction?
  4. Thanks for the reply. Moving the topic is no problem, I didn't realize I should have posted it in this section. Its indeed a strange error, everything should be working.... Can't imagine this is a driver issue.
  5. A coworker of mine gave me a 5 inch hdmi touchscreen (waveshare knockoff). Getting hdmi to work properly on my orangepi pc was done in a few minutes. But the touchscreen drives me nuts. It came with a xpt2046 so I loaded the ads7846 driver I compiled from fbtft. No error messages, but also no response to a touch. It took me a week to finally realize that not the wiring, the driver or Armbian is was the problem, but the touch digitizer was. So I ordered a new one on my favorite Chinese site and installed it on the lcd. Finally I got a response to touching the screen, but I was not able to calibrate it with xinput_calibrator. After manually calibrating it I found out why... When moving my pen over the touch area in a straight line from right to left, the right halve of the screen gives a accurate touch. But when I reach the left halve of the screen the cursor starts moving up.... Disappointed that I received a broken digitizer I ordered a new (different) one from an other store while complaining to the seller of the broken one. I received the other digitizer and replaced the broken one only to find out that the problem still exists... I decided that the xpt2046 was faulty and replaced it with a ads7846. I'm working in a electronics factory and was lucky to find out we had a few on stock. Expecting the problem to be solved now I hooked up the screen and tried. Disappointment all over... Still the same issue. So I am with my hands in my hair... Any help would be greatly be appreciated.
  6. Ok, Just in case anyone else is having the same problem: check your nodm config. You will get very strange behavior if nodm is not properly configured.
  7. I have a 320x240 ili9341 based lcd. Based on the instructions on this forum I hooked it up to my orangepi pc (latest desktop) , loaded the fb kernel driver and run some tests. MPlayer (sudo SDL_VIDEODRIVER=fbcon SDL_FBDEV=/dev/fb8 mplayer -vo sdl -framedrop test.mpg) runs fine. The display shows the video without any problems. Also some python scripts work fine (clock etc..) But anything else fails.... con2fbmap 1 8 does nothing Using FRAMBUFFER=/dev/fb8 startx (or any other program) just starts everything in the main display (hdmi). I need to be able to run any program I want on the spi lcd. Am I missing something?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines