Jump to content

Joel Bodenmann

Administrators
 View Profile  See their activity

  • Posts

    2,620

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by Joel Bodenmann

  2. supported compiler versions

    in Support

    Posted

    I fully agree with @inmarket here. We've yet to come across a C-Compiler that can't handle µGFX. We're running this project for over 7 years now and never encountered any issue on this end of things.

    As before: We're happy to help where we can - but you need to provide a bit more information. 

  4. Integration with own memory area

    in Support

    Posted

    Hello & welcome to the µGFX-Community!

    The Linux framebuffer driver is meant to directly operate on the framebuffer memory provided by the Linux kernel (if this feature is enabled). It's a device such as /dev/fb0 (or similar) that the Linux kernel provides as a framebuffer.
    If you do not want to use this framebuffer but render to a different display you'll have to provide a GDISP driver for this.

    As you mention SPI I assume that you have a dedicated display controller. In that case, check whether your display controller is already supported by the µGFX library. Otherwise you'll have to write your own driver.

  6. STM32F767ZI + RA8875 Colors wrong

    in Support

    Posted

    This is most likely a mismatch of the color formats.

    Check the color format configuration of your GDISP driver (eg. /drivers/gdisp/RA8875/gdisp_lld_conf.h). It defaults to RGB565.
    You have to ensure that the display controller on the other end is using the same color format as specified in the GDISP driver configuration.

  8. how to integrate into a cubeMX makefile project?

    in Support

    Posted

    Hi,

    Unfortunately, we never worked with CubeMX enerated Makefiles ourselves. However, there are plenty of community members that did this successfully. As it's Makefile based you should definitely be able to just follow the official Makefile guide that you quoted in your post. 

    Maybe someone like @cpu20 could help here (he's this community's IDE expert).

  9. Compilation error

    in Support

    Posted

    That sounds an awful lot like an issue in / related to the GDISP driver that you're using.

    You can use the GDISP TestStub driver to compile & run with that. It's an empty driver that doesn't do anything but allows to pass compilation of the GDISP module. This way you can ensure that the rest of the system is running properly.

  10. Compilation error

    in Support

    Posted

    15 hours ago, kpapr1 said:

    I don't see "GFX_NEED_GDISP" anywhere in my gfxconfig.h, but I have enabled this option -->    "#define GFX_USE_GDISP                                TRUE".

    You're using an older version of the library. We'd recommend using the latest master branch of the official repository or getting the latest stable v2.9 release from the downloads section.

  13. I want to register the callback on each window

    in Support

    Posted

    Have a look at the various GWIN (and widgets) documentation. Especially the /demos directory that comes as part of the library might be a valuable resource. the /demos/modules/gwin and /demos/applications applications will demonstrate the proper use of the event system to dispatch widget events.

  16. ST7567 LCD Controller

    in Support

    Posted

    There's a list of all supported controllers on the website/homepage.
    You can also have a look at the /drivers directory.

    And as @inmarket said: Adding a new driver is very easy. There's documentation and plenty of existing samples including drivers for very similar display controllers.

  20. Donations

    in Development and Feedback

    Posted

    Hi,

    We appreciate your motivation to donate. Once we started selling commercial licenses we decided to take down the donation option. Money is clearly the main hold-back issue here as we can't afford more man-power but donations usually don't result in an amount and steady supply of money that would allow to improve this.

    We're close to release µGFX v2.9. It's already ready - we just need to do the actual release. µGFX v3.0 is also making progress :)

  21. CAN Dashboard Project

    in User Projects

    Posted

    Hello & Welcome to the µGFX community!

    There are many factors to consider such as the resolution and color space you want. The more pixels you have to control the more resources you'll need (memory, CPU, bandwidth, ...). For something of this size the newer STM32F4 families or the STM32F7/STM32H7 microcontrollers are extremely popular. If you're not very experienced I'd stay away from the STM32H7 for the moment as support for it seems to be quite scarce on all levels (including debugger support). The STM32F7 is by now pretty well established but tends to be a lot harder to work with compared to an "old school" STM32F4 due to newly introduced technologies such as the memory cache which can lead to many sleepless nights: http://www.chibios.org/dokuwiki/doku.php?id=chibios:articles:cortexm7_dma_guide 

    The STM32F429/STM32F439/STM32F469 are extremely well supported and will most likely provide enough resources for what you're after. Also, you can get various development boards for those with displays so you can get yourself familiar with all the software components before you have to mess with custom hardware.

  22. STM32L1 nucleo + ILI9225

    in Support

    Posted

    The ILIxxxx display controllers are known to suffer from differences across series and revisions. Also, some (chinese) sources love to sell you an ILI9225 as an ILI9220 and so on. Therefore, once you confirmed that the SPI is working correctly, try to grab the initialization code (sequence) from your supplied and plug it into the init() function of the corresponding µGFX driver.

    Another thing you might want to do is trying to read out the display controllers version register / chip ID. This will tell you exactly what display controller you have and will also confirm that the communication is working well.

×
×
  • Create New...