STM32 TouchGFX with ILI9488 and other RGB666 displays

Поділитися
Вставка
  • Опубліковано 17 січ 2025

КОМЕНТАРІ • 19

  • @jasminefp1278
    @jasminefp1278 Рік тому

    you are so amazing...😭👏👏👏

    • @bluewat
      @bluewat  Рік тому

      Hoping that's a compliment: thank you!

  • @fajartriarso
    @fajartriarso Рік тому +1

    an awesome video, thanks dude, using stm32f411 blackpill edition for touchGFX project. on the bottom of the board there is an eeprom pattern. for the next project, can you make a video about touchgfx + eeprom w25qxx series? it will really help us microcontroller lovers who haven't been able to buy a mcu that supports qspi. Thank You.

    • @bluewat
      @bluewat  Рік тому +2

      You read my mind, Poncolongok! I just completed a more robust version of the library with an easier dragging handling (so an easier sliders, scroll lists, ... handling). I'm working on a video showing it. In the meanwhile I'm starting testing the external single-SPI flash handling. But I need some more time. Unfortulately, that's just my hobby!

    • @fajartriarso
      @fajartriarso Рік тому +1

      @@bluewat I'm looking forward to your next video. happy working, hopefully healthy always.

  • @EdwinFairchild
    @EdwinFairchild 5 місяців тому

    im not sure where or how youre telling touchgfx what display you have and how it knows how to use it

    • @bluewat
      @bluewat  5 місяців тому +1

      you should find answers here: ua-cam.com/video/g1siKaPox88/v-deo.html

    • @sharankuppuswamy8951
      @sharankuppuswamy8951 5 місяців тому

      please watch the previous video to understand this video

    • @sharankuppuswamy8951
      @sharankuppuswamy8951 5 місяців тому

      @@bluewat hi i am able to display but touch is not working

  • @urichaplin1424
    @urichaplin1424 5 місяців тому

    Why you use SPI interface for ILI9341 if it is use FSMC ?

    • @bluewat
      @bluewat  4 місяці тому

      Uri, the ILI9341 communicates via serial or parallel port, but in the video I'm not using (only) that driver: I am using a board mounting a display and the ILI9341.
      Some boards expose the ILI parallel port pins, while others expose the serial ones.
      There are advantages and disadvantages to using one port over the other. The main advantage of using SPI instead of FSMC is that the former requires (many) fewer pins, allowing the display (the driver) to be managed even with smaller uCs or when the pins are involved in other activities.
      I'm thinking to do some test even with parallel port handled displays.

    • @urichaplin1424
      @urichaplin1424 4 місяці тому

      @@bluewat but parallel mode is 16 times faster !( instead of sending 1 bit I send 16).

    • @bluewat
      @bluewat  4 місяці тому

      @@urichaplin1424
      … advantages and disadvantages…

  • @just5444
    @just5444 Рік тому

    What should I modify to be able to use dragging? Now scroll list on TouchGFX doesn't work (only selects elements in list, but doesn't scroll it) ua-cam.com/video/p7GTPM2xNww/v-deo.html&ab_channel=STMicroelectronics

    • @bluewat
      @bluewat  Рік тому

      Hi Coppertail,
      driver handles communication between TouchGFX and the display, should not affect TouchGFX features.
      ... or it does? ... Try to disable the key repeat feature (set _DELAY_TO_KEY_REPEAT_ to _0_ in _z_touch_XPT2046.h_ ) That's the only thing I can suppose having impact on dragging.
      Let me know.

    • @just5444
      @just5444 Рік тому

      @@bluewat Nope, didn't fix it

    • @just5444
      @just5444 Рік тому

      Also one thing I noticed, is that in simulation, when you press and hold button, it changes color and stays until you release button. On my application using this library, when you press a button, it only changes color for a brief moment (almost unnoticable)

    • @bluewat
      @bluewat  Рік тому

      @@just5444 you definitely still have active key repeat.

    • @just5444
      @just5444 Рік тому

      ​@@bluewat Then DELAY_TO_KEY_REPEAT = 0 doesn't disable it. It sets flipTouch to 0, therefore setting isTouch to 0.
      I'm now trying to find a solution.. This method solves drag problem, but then other screens acts weird (I have onscreen keyboard, buttons shows being pressed, but text doesn't appear in typing box ua-cam.com/video/uE6eiTjOP-g/v-deo.html&ab_channel=EEbyKarl)
      z_touch_XPT2046.c: (modify last function)
      uint8_t Touch_TouchGFXSampleTouch(int32_t *x, int32_t *y){
      uint8_t isTouch=0; // preset to no touch
      uint16_t xx=0,yy=0; // need to convert library coordinates type (uint16_t) to TouchGFX one (int32_t)
      if (Touch_GotATouch(0)) // polls interrupt flag not resetting it
      {
      Touch_GetXYtouch(&xx,&yy,&isTouch); // get touch sensor position
      if (isTouch)// received a "no touch"
      {
      isTouch=1;
      *x=xx;
      *y=yy;
      }
      else
      Touch_GotATouch(1);
      }

      return isTouch;
      }