Jump to content

All Activity

This stream auto-updates

  1. Last week
  2. It's been some time since I last used the touch routines and I now find that functions have changed and the useful refresher links are now appear broken and a search doesn't reveal any updated resource, eg. broken link to the calibration wiki page with 502 Bad Gateway response? Link Are any updated links available? As an aside, is uGFX V3 going to see the light of day anytime soon or has it been shelved?
  3. Earlier
  4. Yeah your right. Anyway thank you for your help. I know there is something wrong in the path but I'm getting exactly I'm going wrong. Moreover I have pulled these code from repository. These weren't coded by me. I believe as importing so many codes from repository into the single project I'm facing this issue.
  5. That screen needs to include the directory that has that stm header file. Your start up file, your compiler is complaining that it doesn't understand the assembly language. These are both problems relating to your ide and compiler. While we try to help here, we are not experts on those tools, we are ugfx experts. If the clues above don't help you, you will need to get help on a forum that understands your ide and compiler rather than here.
  6. No the start up file is one using is generated by itself when we create the project, I'm not using the wrong one
  7. This is how my include directory looks like. Just like eclipse. I have included the path, can you tell where exactly -l directives can be found here?
  8. with regard to your 2nd screen, that looks like you are using the wrong assembly language variant to compile that start up file. Use the start up file that matches your ide compiler, or alternatively, some ide's allow you to specify the assembler you use.
  9. Most likely cause for this is that the include directories path is not correct. I am not sure how to specify these in your ide, probably in the compiler options. These end up as -I directives in the compiler arguments. The -I directives must include the directory containing those stm header files.
  10. Hello, I am new atollic truestudio. I am facing the above mentioned error despite the file being in that directory. I have attached the image for your reference. The strange thing is after I again rebuild the project, the error will occur in some other file. I have attached another image after rebuilding the project. Every time build it the error changes. I never faced this kind of issue. I'm stuck with this issue it would be great help for me if anyone is able resolve it. Thank you
  11. BTW, a native image in ugfx terminology is a image that has the same pixel format that the ugfx system uses in an unpacked pixel arrangement (maximum of 1 pixel per byte, word or dword depending on the number of the pixel bits)
  12. You can use the BMP image handling in ugfx. BMP images support a 1 bit per pixel format. The only thing you may need to do is to fabricate a BMP header. Because BMP also support RLE encoded formats you may also be able to compress your 1 bit images and so save rom/ram. Writing a bitblit routine for your driver to handle your "special format" image is probably not the best way to handle this. Similarly with your alpha request, use the image processing support built into ugfx. For example, ugfx handles transparent gif's. It also handles PNG images with an alpha channel although al
  13. I'm trying to migrate from another graphics library (u8g2) to uGFX to get eventual support for color screens. I have a number of ROM based bitmaps that are stored in native format. For this display, it is 1 bit per pixel. I tried used the gdispGBlitArea() function to draw them, but found that it assumes pixels take a minimum of one byte. I worked around the problem by enabling the GDISP_HARDWARE_BITFILLS macro and doing the blitting in my driver by implementing gdisp_lld_blit_area(). Is there a plan to add more support at the gdisp layer for native formats? One of the features th
  14. Welcome to the µGFX community & welcome for sharing your workaround, @Matteo Vigni!
  15. Hello, I found a workaround for the double redraw issue and thought I would share. I'm working on an STM32L4 MCU running FreeRTOS. My workaround basically consist in modifying the guiShowPage function this way: void guiShowPage(unsigned pageIndex) { // Hide all pages gwinHide( page1 ); gwinHide( page2 ); gwinHide( page3 ); /* ... */ // Allow the rendering thread to clear the screen gfxYield(); // ADD THIS LINE! // Show page selected page switch ( pageIndex ) { case 0: gwinRaise( page1 ); // ADD THIS LINE! gwinShow( page1 ); break; case 1: gwinRaise( page2
  16. Hello & welcome to the µGFX community! The Zephyr port definitely needs a port to v2.9 to cover for the problem you listed (mainly the type updates) and making it therefore future proof for µGFX v3.0. We would greatly appreciate it if you could provide an updated version of the Zephyr port The Zephyr port was provided by the community member @nathan.loretan and I think µGFX 2.7 or 2.8 was the latest release at that point. However, porting to the current v2.9 version should be very easy as not much changed on µGFX's side (see changelogs). The board files are completely indepe
  17. If the memory of the image you're passing is correct then the following two cases seem the most likely: Your GDISP driver / display controller / display module setup has an issue. Perform tests as explained in my previous post to check. There's an issue in the PNG decoder. You can simply test another PNG image to see whether you have the same issue.
  18. Thanks for your answer, I guess I will try that. I tried to test if the file read was corrupted by looking directly into the memory, it did not seem to be corrupted, the pointer passed to gwinImageOpenMemory was correct, containing the very same data than the original PNG file. Could still be a driver issue or the interaction between the driver and uGFX, I need to look more in depth into that.
  19. Unfortunately nothing comes to mind. Things you can do to proceed: Try to display the same PNG file in an µGFX application you compile as a native desktop application (Windows, Linux, Mac OS...). If that works without any problems there's a good chance that the image you're loading into memory is corrupted at which point you'd need to revisit your USERFS implementation. The PNG decoder is in general known to work although it is not used as often due to large memory requirements for the decompression algorithm. Before all of this it might be worth confirming that your display driver i
  20. Actually I might need some help with my current issue, I managed to open and display a PNG file using OpenMemory function. However, the image displayed is a bit weird: it looks like parts of it are mixed up or removed. I will attach the image I want to display and the actual result I get + the code just to show how it is done. Can someone possibly explain this weird behaviour ? Any help would be appreciated. static GHandle gh_image; /******************************************************************************/ eStatus IF_EINK_DISPLAY_displayImage(uint8_t * const kpu8_imgBuffer, uint16_t
  21. Nevermind, I got it right, I just needed to call gdispFlush() to refresh my screen and it works a bit (still some kind of decompression issue but that is something else)
  22. Hey! I'm trying to use the current version of uGFX (2.9) on a NUCLEO-L452RE running zephyr 2.3.99 as the operating system and a display with a HX8347D LCD-Controller and a XPT2046 Touch-Controller. According to the uGFX Wiki However I ran into some issues trying to get uGFX and Zephyr to work together. I have included uGFX into the Zephyr-Project via Single File Inclusion to accommodate for Zephyrs CMake based build system. The functions _gosPostInit() and _gosInit() are missing in the file gos_zephyr.c. I set a compile-flag to reactivate some deprecated int-Types of
  23. static GHandle gh_image; /******************************************************************************/ eStatus IF_EINK_DISPLAY_displayPNGFile(char * const pc_iFilePath, uint16_t u16_iX, uint16_t u16_iY, uint16_t u16_iWidth, uint16_t u16_iHeight) { uint32_t u32_startTick = HAL_GetTick(); eStatus e_status = eOK; GWidgetInit widget; gwinSetDefaultFont(gdispOpenFont("UI2")); gwinSetDefaultStyle(&WhiteWidgetStyle, FALSE); gdispClear(White); e_status = AP_FILE_MNGR_fillBufferFromFile(pc_iFilePath, g_au8_screenBuffer, CF_IT8951_SCREEN_WIDTH*CF_IT8951_SCREEN_HEIGHT); // App
  24. Hello ! I started this topic because I might need some help to be able to display a PNG image on my screen. I tried to follow everything from the documentation but without success. I will try to explain what I would like to do if possible: the system I use already uses a filesystem (LittleFS), this filesystem contains a PNG file that I want to display on my screen but I do not know well what I have to do to make it works. Should I implement a USERFS ? I tried that but without success, perhaps I did not implement it properly. Otherwise, as my system already contains a file manager, w
  25. why not i can't download uGFX-Studio?
  26. It's a bit difficult to judge based on the image with the angle & blury-ness but it looks like there's an issue in the setup of the display controller scanlines. The ili9341 display controller families are known to have various issues such as mis-matching silicon revisions and suppliers simply shipping a slightly different chip. This usually results in incompatible initialization routines. Check out the GDISP driver file (inside something like /src/drivers/gdisp/ili9341/) and check the initialization routine. Usually the manufacturer and/or supplier of a display module will provide yo
  1. Load more activity
×
×
  • Create New...