Jump to content

JakeSays

Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Thanks much for the code. It was educational but not complete enough to work. But it was very helpful in writing my own driver. So as it stands I now have both the display and touch working! Would you be interested in a pull request for this specific card? Thanks again for all your help -Jake
  2. That would be awesome! Thanks!
  3. Now that I have the framebuffer working I've gone back to using the adafruit kernel drivers. The drivers handle calibration so I think I'm ok there. However the next issue I'm facing is how do I read the touch screen values? From what I've gathered from the ugfx source I'll need to write a ginput driver that pulls events from /dev/input/touchscreen, which is how the adafruit stmpe driver exposes events. The format of the events is straight forward. Here's sample output from evtest /dev/input/touchscreen: Event: time 1451488716.725099, type 3 (EV_ABS), code 0 (ABS_X), value 1925 Event: time 1451488716.725099, type 3 (EV_ABS), code 1 (ABS_Y), value 2226 Event: time 1451488716.725099, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 137 Event: time 1451488716.725099, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1451488716.725099, -------------- EV_SYN ------------ Event: time 1451488716.781826, type 3 (EV_ABS), code 24 (ABS_PRESSURE), value 0 Event: time 1451488716.781826, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1451488716.781826, -------------- EV_SYN ------------ Am I on the right track? Also, what is a toggle input device? Thanks, -Jake
  4. AHH! Success! I have the framebuffer working Thank you SO much for your help
  5. I tried using the frame buffer, but when it ran I got an incompatible color format error. I should mention though that I'm using the custom framebuffer (fbtft) from adafruit. I only need to support the PiTFT as the environment is embedded. I added a mutex and locked/unlocked in aquirebus/releasebus, but ran in to huge lock contention issues when I enabled the touch screen. Drawing speed slowed to the point where there was seconds between each pixel being rendered while drawing the calibration screen. A lot of those errors were unrelated. I should've cleaned it up before posting. I was in experiment mode. I'm going to give these a try with a fresh code base. Thanks!
  6. Ok I think I may have coded myself in to a rat hole here. I'll explain what it is I'm trying to do and perhaps you guys could provide some guidance? I have a Raspberry Pi 2 B and an adafruit 2.8" lcd/touch screen. The lcd is controlled by an ILI9341, and the ts by an STMPE610. The device also exposes the STMPE610 interrupt line. My goal is to get uGFX to work with both the lcd and ts. Also I cannot use the framebuffer because the uGFX framebuffer driver does not support RGB565. What would be the suggested way to proceed? I really appreciate all your help -Jake
  7. Actually its not a missing header issue. It's related to the single file build method. For some reason GDISP_DRIVER_VMT is undefined when gdisp_driver.h is included in gdisp_pixmap.c If I comment out gdisp_pixmap.c from gdisp_mk.c and add gdisp_pixmap.c directly to my project the GDISPVMT_pixmap related errors go away. However now I'm getting "GDISP: Unsupported color system for low level drivers" it appears RGB565 is not supported in a lot of places.
  8. Ok I see how GDISPVMT_* works. It is declared in gdisp_driver.h by a macro overload of GDISP_DRIVER_VMT. So yeah I'm missing some headers.
  9. Using the uGFX ILI9341 driver I can draw on the LCD just fine. here is line 33 of gdisp_pixmap.c: #define GDISP_DRIVER_VMT GDISPVMT_pixmap GDISPVMT_pixmap is not defined anywhere, which causes the compile error. My environment is: Host: Windows 10, VisualGDB, Visual studio 2015. Using visualgdb. I cross compile using their raspberry pi toolchain. This works fine as I have written several apps using it. Target: Raspberry Pi2, Raspbian jessie. Also, I'm using the all-in-one build method (ie no make files) I tried using acquire/release_bus() to isolate the two controllers from each other (using a gfxMutex), and change speed. When I do this drawing performance tanks and then eventually stops all together. The bitbucket repo (https://bitbucket.org/jakesays/ugfx is public, but currently it is a direct mirror of yours. One more thing: the motivation for going down the direct SPI route is the linux framebuffer driver doesn't support RGB565. If it did I'd use that. Thanks -Jake
  10. Hey thanks for the response Here's a link to my compiler output: http://pastebin.com/62YQYDuZ Also I do have GDISP_NEED_PIXMAP defined to TRUE. My target environment is a raspberry pi via direct SPI access to an Adafruit PiTFT 2.8" display. Both the LCD and touch screen use SPI. I can get the basic demo to work just fine using the ILI9341 driver. My bigger issue is getting the touch screen to work. The driver is an STMPE610, so I've been trying to get the '610 support in uGFX to work. Using a pixmap as an intermediate framebuffer is an experiment to work around the two controllers fighting over the SPI bus. In regard to GDISPVMT_pixmap and LLDSPEC missing, I cannot locate them in the source tree using grep. Thanks, -Jake
  11. I'm trying to use the pixmap driver and i'm getting GDISPVMT_pixmap and LLDSPEC missing errors. I cannot find GDISPVMT_pixmap anywhere in the source tree. Any ideas?
×
×
  • Create New...