Thank you very much for your brilliant and performant driver. Also your videos with much backgroundinfos about the implementation are brilliant!!!! THANKS !!!!
This is an awesome video. I'm developing a custom build device using an STM32H723 and a touch screen using an ILI9488 driver chip. I wasn't sure exactly how to integrate TouchGFX with a custom design, but this video pretty much shows you how A-Z. Thanks so much.
Good. Are you working with ILI9488 via serial or parallel interface? Do you know also why there is this difference between the ILI9488 boards? What could have changed in v2.0 boards, to let them work in RGB565?
@@bluewat I have done three interfaces so far. I've decided to only use the RGB565 format as I'll be using TouchGFX and have a larger application with a ton of images. My first board used the 8 bit parallel, but that would only get me like 7-15 FPS because I was using too small a uController and couldn't get one whole byte on a single port so with the over head of bit manipulation it was too slow. I then spun a board with a larger uController and moved to a 16-bit parallel interface. I pushed that design and was able to get pretty decent FPS of maybe 10-20, but I was trying to get by using only the GRAM on the display because my uController didn't have enough to fully drive the display (320*432*16-Bit). I finally just decided to go full out and use the STM32H723 with an 8MB SDRAM and us the LTDC controller and fully drive the RGB interface. Now I have a ton of RAM and ~70 FPS all done by hardware. This is a much more complicated setup, but if you're looking for high performance it pretty cool. It also brings along with it the ability for two layers that the hardware can also blend together and do all kinds of other special effects like have a stationary background layer and another layer that can easily be drawn over it.
after adding all files In z_displ_ST7735.c and z_displ_ST7735_test.c files #include "fonts.h" #include "z_displ_ST7735.h" #include "z_displ_ST7735_test.h" I had to redo the definitions. It is necessary to update the touchgfx application every time the .ioc file is updated. as a result both methods work fine for 42 MB/s with sst7735. good job
Yes, I haven't seen a reference in documentation, but it seems that if you change CubeMX configuration, you need to re-generate TouchGFX project. You shouldn't need to add "fonts" and "_test" files in a TouchGFX project.
Hello Mr. Mauro, thank you very much for sharing. It's been very useful for me. When you have time, I would like to ask you to make a video using TouchGFX, Stm32f411 and W25Q Spi flash. Thanks.
The "Definitive Debuging Method"? That's too much. I can try to show how I move debugging my projects... 1) HW is ok? I usually setup a simple project (a non-TouchGFX project) allowing me to verify that display, touch sensor, flash (if any), other devices are working. That usually running simple test functions you see in other videos here or, anyway, simple basic tests of the devices involved. I keep this project available to run it, testing the system, anytime I have a doubt about it. 2) Is TouchGFX running? a second simple project (maybe just involving a button and a counter as you see here) to see if TouchGFX is correctly set. I use that to check all the configuration (CubeMX and .h configurations) in case of doubt. ...or restarting from here... sometime. 3) So, it is the current project! If the two above tests are working, the problem (because if I'm debugging means I have a problem) is just inside the project I'm developing. Keep in mind that there is ALWAYS a bug somewhere. If it seems that your (my) project is working, it's only because the bug hasn't shown up yet! .
Hi! Really appreciate for your work. Your library helped me a lot. But I want to use more bigger fonts then 'font24.c' in your library. So I edited font24.c file on my own by extending its arranges twice bigger. However, it doesn't work well as original font files. Is there any size limitations for ILI9488 for displaying bigger something? If you have a great idea for displaying bigger fonts in this display, please help me
I agree: ST fonts shown on ILI9488, can appear too small for some needs. In Displ_WChar I added "size" parameter that, if set to 2, "doubles" character width. It should be easy also to double height. Be aware: You can see that there is no a buffer swap inside the WChar function. It means that you have to set buffer size able to store at least 1 char. eg. Font24 is 24x17 pixels per character. In RGB565 it is 24x17x2 = 816 bytes per character, RGB666 needs 1.2k. Doubling with buffer must be > than 2.4k. Doubling width and height it must be >4.8k. Maybe problem you had was just a buffer overriding.
thats a very good and awesome work you have shared to us brother. thanks a lot for that. i have tested it with STM32F401RBT6 with ST7735. it worked well in spi polling mode. but facing problem with DMA and Interrupt mode. the LCD not getting initialized.
Hello thank you so much for this wonderful video, I'm working with the ST7789 240x280 display, I have the driver but I want it to be compatible with touchgfx, advise me on this thank you.
Paul, the above video should indicate all the steps you have to do updating the library you already have. A second possibility is analysing datasheets of ST7735 and ST7789 adapting the above library to your display.
The underlying logic is independent of the display used. But ILI9481 seems having a different configuration in many reference commands (e.g. RAMWR). So, I suppose this library cannot directly work with ILI9481
Hello Burhan, not easy to say, there is a specific tutorial (#3), on TouchGFX support website, about multi-screen projects. Keep an eye on the flash memory occupation!
Dear Mr.Mario First of all, congratulations for your project and to share those great tutorials with us. I tested the library with stm32f407 and ILI9341 and everything works fine but when I tryed to enable the freeRTOS pack in STM32CUBEide , the program stopped working, tft freezes. Are there any possibility of incompatibility of the libray and freeRTOS ? thanks in advanced , best regards!!
Hello , I did everything as you did and it doesn't work at all! i also use the same headerboard (stm32f411ceu6) the code compile without any error! my wiring is fine.... i'm using 3.5" TFT LCD with ILI9488.... I checked everything still get nothing... thank you
Great tutorial, but wiring image seems to be removed from github directory and unfortunately, I don't know how to connect microcontroller to my ILI9488 spi display v1.0 based on this tutorial. Can you upload wiring image somewhere else?
Updated wiring picture. Be aware that you will not be able to run ILI9488 board V1.0 on TouchGFX. It doesn't handle RGB565, as stated here: ua-cam.com/video/020k2vbLAPc/v-deo.html
Unfortunately I haven't an ILI9486L board in my drawers. After a quick reading of its datasheet, it seems that ILI9486L and ILI9488 work exactly the same way on SPI (they seems only to have a different color resolution on parallel communication, same commands. "After a quick reading"). But... I don't know the board you are referring: if it is SPI and uses XPT2046 touch driver (or if it is a no-touch board), you could try to set library as ILI9488_V1 and, if it works, you could try also ILI9488_V2 which gives faster results. Let me know how it goes.
Hello everyone I'm using touchGFX and 3.5" display with ili9488 I managed to work with it and it shows everything as I wanted, but the issue is that when I power up the uC, sometimes it doesn't show anything and I need to reset the uC!!!! I ran debug and there was no error or something else... My uC is stm32f405rgt6... What would be wrong...? Thanks in advance:)
@@sharankuppuswamy8951 have you checked the communication between the uC and the touch? Or did you check the wiring?? Also , maybe it's about the calibration... Watch the video about calibration and set the parameters, it should work... At least it worked for me:)
Dear MR.Mauro I tested the library with STM32F429 and worked perfectly.Do you think is it possoble to work with STM32H743 MCU? I tried tried and till now didn´t work. thanks, best regards!!!!!
Thank you very much for your brilliant and performant driver.But i am facing some issue i am using version 2.1 so it is not displaying properly but touch is working could you please help me with this
what's the 3.5 resolution? As per what I see on datasheet, 9341 handles 240x320 displays: library should work without any changes. Anyway, if display has a different resolution, you should just set its size on z_displ_ILI9XXX.h around line 175
Dear Mr.Mario, every thing works fine but buttons on the bottom activate when touch on the top, I am using ILI9341 in landscape mode, I tried with changing "Displ_Init(Displ_Orientat_90)" to Displ_Orientat_270 , display rotate along with buttons but touch also rotate, also test by changing the "define T_ROTATION_xx". Please direct me to how to fix it?
That seems to be something related to touch sensor calibration. Try to check it. you could follow guideline here: ua-cam.com/video/KS5u2-6yruU/v-deo.html or here: github.com/maudeve-it/ILI9XXX-XPT2046-STM32/tree/main/4-CALIBRATION
Can you guide on how to do the same process with a custom display that uses IC6211 (i have to develop it from scratch) via i2c , i'm a bit lost on what functions i should use so that they can work with touchgfx , thank you .
Setting up TouchGFX driver from scratch, for a custom display... well... there is a full website from ST to keep in consideration. If you already developed a set of APIs for your display, you should find all the information you need in this video (maybe together with the following videos in the playlist). Can you show me where you are getting confused? Reducing it to the minimum, we could say that you need just to develop: int touchgfxDisplayDriverTransmitActive() and void touchgfxDisplayDriverTransmitBlock(const uint8_t* pixels, uint16_t x, uint16_t y, uint16_t w, uint16_t h) That's for the display. Then you have to learn to use TouchGFX.
thanks @@bluewat ,I'm currently working with an STM32U599 and a custom display equipped with an IC6211 driver. The setup involves I2C and MIPI DSI with 2 lanes. Right now, I'm setting up the project for the first time and am a bit concerned about the initial configuration. Should I enable LTDC along with the DSI host? My goal is to first display colors and images before integrating TouchGFX. I want to ensure everything is working properly before moving on to using TouchGFX. I also noticed that the frame buffer location might need to be adjusted when switching to TouchGFX. Could you share your thoughts on the best approach to smoothly transition through these steps? Thank you for your guidance!
Hi Mr. Vecchi, Many thanks for this very informative video. But for some reason this ST7735 library is not working with touchgfx for me, although I have the display working directly with another driver. This means, my pin connections and SPI configuration is ok. I think I followed all the instructions you mentioned in the GitHub, but no success. Is there a chance that you are missing something in the GitHub for ST7735 part?
I resolved the issue by merging the other driver's init function and your TouchGFX implementation in the z_displ_ST7735.c file:) Anyway, thanks again for the information and the code that you provided in theVideo/GitHub.
Thanks for all of your help on this! I've got it around 90% working with an ILI9488 and STM32H7, however I have run into a couple of issues near the end: 1.) When using the touch functionality with TouchGFX, the LCD will randomly turn all white when rapidly touching the screen and requires a hardware reset to fix. I've narrowed it down to the T_IRQ pin as the culprit and it seems like frequent touches cause it to catch in some loop (not 100% sure)? 2.) The update speed of my LCD seems much slower to your example (this especially shows when holding down one of the arrow buttons and the counter ticks up much slower) when set up with similar settings as yours. Do you have any ideas on how to fix either of these issues?
Hi Sean, about question 1) As per what I can say, what you report indicates a problem on SPI communication, so I would follow theese steps: - (obvious) check for a stable and affordable SPI wiring - check SPI speed: I was never able to go over 50Mbps but in case of problems try to slow it down, I've seen (and shown in some video) that different displays can have different behavour. Remember that the SPI speed is not defined in CubeMX but by DISPL_PRESCALER define in "z_displ_ILI9XXX.h". - set also "output speed" to pins involved in display: working ad 50 Mbps I've seen that they have to be set "high" at least. But the meaning of these "lables" depends on the uC. Check your datasheet. This should fix your problem 1)
About problem 2: that's a strange behaviour. I've seen that different uC can have different performances and unexpectedly enhanced SPI/DMA devices can bring to a slower performances with short data transfer. But that should not mean a "much slower" display as you say. Have you tried to increase the buffer size ("block size") on TouchGFX configuration in CubeMX? Having "pin availability" on the uC it is better to separate touch SPI by the LCD one. It will increase the overall TouchGFX performance. I know that current library available on my GitHub page needs working a little fixing it to work on two separated SPI ports. I will provide in a short time a new release easing the two configuration (single or double SPI port) along with enhancements for the usage of complex TouchGFX widgets.
Hi Mr.Mauro , thank you very much for sharing. i need emergency help .. i m trying to display a touch interface in 3.5" TFT SPI with ILI9488 driver .. i followed exactly the steps you show nut i have 25 error when i build .. i need ILI9488 driver for STM32F401RE nucleo or for STM32F407VG discovery i have both .. which one is compatible with ILI9488
25 errors... well... that seems non "exactly" the same as following proposed steps...🙂 Send me the list of errors, maybe I can halp you to fix something, or at least the reason for that. I propose you to not overload this message system, movin to GitHub and opening an issue: github.com/maudeve-it/ILI9XXX-XPT2046-STM32/issues That's also easier to use.
@@bluewat i have 3 errors just like the video before enabling the interrupt of PA12 ..but after i have 25 error ..btw i m using STM32F401RE and i think that's the problem ..there is the errors ../TouchGFX/target/generated/TouchGFXGeneratedHAL.hpp:21:10: fatal error: touchgfx/hal/HAL.hpp: No such file or directory......./TouchGFX/target/generated/STM32DMA.hpp:21:10: fatal error: touchgfx/hal/BlitOp.hpp: No such file or directory ...... ../TouchGFX/target/STM32TouchController.hpp:28:10: fatal error: platform/driver/touch/TouchController.hpp: No such file or directory and more
@@mokhlessezd2106 I do not see why F401 should be a problem. Why are you supposing that? What are the limits are you knowing I don't see? By above messages, it seems that TouchGFX project has to be generated. Keep in mind that TouchGFX must be THE LAST item generated in your project: e.g. if you make some changes in CubeMX, after having generated the device configuration you MUST open Designer and re-generate TouchGFX project. Try that: maybe that's the only problem. Now. Mokhless. If you like I help you, you have to help me. Do you see how is hard understanding your above post? If you need more technical help, please, post a message on GitHub, allowing you to post screenshots, program files and so on.
Thank you very much for your video. On my board, I have an STM32F411CEU6, the LCD chip is an ILI9488, and the touchscreen chip is an XPT2046. I followed your tutorial and successfully flashed it onto the board, but my screen is all white. Can you help me, please? Thank you!
A full white screen should mean that SPI communication is not proceeding. A lot of possible origins... Not considering obvious questions about checking correct CubeMX configuration and wiring, one possibility is the GPIO speed of the pins involved in communication (CS and D/C for instance). Try to set them high or very high. Once working you will try to slow them down until working. Another possibility, if you are prototyping on a breadboard, is that you are pushing too much the SPI port speed, having an unstable wiring. While prototyping I use a quite slow speed (even below 2 Mbps), pushing it up in the final part of developing or just when I move the project to the developed PCB I don't remember if using a wrong color format leads to a "white screen". Try RGB666: that should be compatible with any display...
@@abhijithmandava9314 Assuming ,you set parameters in the display .h file and touch one, If you get a full white display after initialization there there are probably errors on SPI. 1) doublecheck display wiring 2) verify speed (maximum output speed in CubeMX) of pins involved in display communication and control. 3) try to run SPI at a lower speed (remember that SPI baudrate is controlled by DISPL_PRESCALER parameter, regardless what set in CubeMX) By the way: but Have you changed your above first question after I answered to you? really???
Checked 1 and 2 before, will try 3. Thx for suggestion. Tried posting 1st question with more info, but character limit didn't let me post. Reduced it to very information lacking question and that was accepted. After your answer I tried modifying it so I can add further info but same issue.
No, I don't have it. ILI9342C seems to be an evolution of 9341 and the basic commands (what I'm using in library) seems to be the same. Same resolution. You could try to set library handling ILI9341 and see. Your display is an SPI one, right?
@@bluewat I'll do some testing. But I think I'm going to have a problem. 1.stm32 f103c8 not authentic >> Unable to upload data(Because the real thing is very rare) 2.because I use STM32CubeIDE 1.10.0 3.Do you have a way to upload data, please advise me.
Dear Mauro, I am writing to you because i used to your great video: ua-cam.com/video/g1siKaPox88/v-deo.html that prepare own project in which I use STM32L476 and display SPI 4", ILI9488 from aliexpres. I have a problem because the touch on the bottom of adisplay is worse than the touch on the top of the display - the touch is inaccurate and I had to touch a few times on the display. I change a display but it did not help. I have set full touchGFX Mode, SPI 20 Mbit/s prescaler touch 4, prescaler touch 16. Can you give me a advice where is a problem? I will be very happy. Best regards, Kamil
Actually I remember I've seen that there is a range of touch SPI speed where the sensor still works and replies to queries but giving low precision results. Try to drastically slow down touch spi speed and see the results. Keep in mind that touch sensor needs a communication of just a couple of bytes: you will see that a slow touch-SPI port doesn't affects the global TouchGFX project performance. Let me know
Hii , everything went well, but wheni build the code i got 7 error before i have started writing in main.c. i am gettig undefined reference to `touchgfxSignalVSync', undefined reference to `touchgfx_init' and undefined reference to `touchgfx_taskEntry'. I have no idea how could i fixed that, do you know what it might cause that??? I have included two libs like you showed in video. I am using STM32F411, cube IDE 1.6.1, touchGFX 4.19.1 ( i did try 4.22 but i can't even open ApplicationTemplate.touchgfx.part from cubeIDE so i installed older version and works, i did changed in cubeMX under software packages 4.19.1)
Hi, if you are not using TouchGFX (I suppose you aren't), in z_displ_ILI9XXX.h you have just yo set a comment on line: "#define DISPLAY_USING_TOUCHGFX" (change that line into "// #define DISPLAY_USING_TOUCHGFX" ) otherwise functions will look for an integration to that package. More info on github.com/maudeve-it/ILI9XXX-XPT2046-STM32 and into the same z_displ_ILI9XXX.h file
Thank you very much for your brilliant and performant driver. Also your videos with much backgroundinfos about the implementation are brilliant!!!! THANKS !!!!
Glad to see you like my videos, Tiwag
This is an awesome video. I'm developing a custom build device using an STM32H723 and a touch screen using an ILI9488 driver chip. I wasn't sure exactly how to integrate TouchGFX with a custom design, but this video pretty much shows you how A-Z. Thanks so much.
Good.
Are you working with ILI9488 via serial or parallel interface?
Do you know also why there is this difference between the ILI9488 boards? What could have changed in v2.0 boards, to let them work in RGB565?
@@bluewat I have done three interfaces so far. I've decided to only use the RGB565 format as I'll be using TouchGFX and have a larger application with a ton of images. My first board used the 8 bit parallel, but that would only get me like 7-15 FPS because I was using too small a uController and couldn't get one whole byte on a single port so with the over head of bit manipulation it was too slow. I then spun a board with a larger uController and moved to a 16-bit parallel interface. I pushed that design and was able to get pretty decent FPS of maybe 10-20, but I was trying to get by using only the GRAM on the display because my uController didn't have enough to fully drive the display (320*432*16-Bit). I finally just decided to go full out and use the STM32H723 with an 8MB SDRAM and us the LTDC controller and fully drive the RGB interface. Now I have a ton of RAM and ~70 FPS all done by hardware. This is a much more complicated setup, but if you're looking for high performance it pretty cool. It also brings along with it the ability for two layers that the hardware can also blend together and do all kinds of other special effects like have a stationary background layer and another layer that can easily be drawn over it.
@@bluewat Not sure about the Rev of the ILI9488. I'm working of the the 1.0 datasheet.
after adding all files
In z_displ_ST7735.c and z_displ_ST7735_test.c files
#include "fonts.h"
#include "z_displ_ST7735.h"
#include "z_displ_ST7735_test.h"
I had to redo the definitions.
It is necessary to update the touchgfx application every time the .ioc file is updated.
as a result both methods work fine for 42 MB/s with sst7735. good job
Yes, I haven't seen a reference in documentation, but it seems that if you change CubeMX configuration, you need to re-generate TouchGFX project.
You shouldn't need to add "fonts" and "_test" files in a TouchGFX project.
Hello Mr. Mauro, thank you very much for sharing. It's been very useful for me. When you have time, I would like to ask you to make a video using TouchGFX, Stm32f411 and W25Q Spi flash. Thanks.
keep in touch!
Hi Mauro.... Could give us a global debug procedure ? Thank you..!
The "Definitive Debuging Method"? That's too much. I can try to show how I move debugging my projects...
1) HW is ok? I usually setup a simple project (a non-TouchGFX project) allowing me to verify that display, touch sensor, flash (if any), other devices are working. That usually running simple test functions you see in other videos here or, anyway, simple basic tests of the devices involved. I keep this project available to run it, testing the system, anytime I have a doubt about it.
2) Is TouchGFX running? a second simple project (maybe just involving a button and a counter as you see here) to see if TouchGFX is correctly set. I use that to check all the configuration (CubeMX and .h configurations) in case of doubt. ...or restarting from here... sometime.
3) So, it is the current project! If the two above tests are working, the problem (because if I'm debugging means I have a problem) is just inside the project I'm developing.
Keep in mind that there is ALWAYS a bug somewhere. If it seems that your (my) project is working, it's only because the bug hasn't shown up yet!
.
@@bluewat Thank you... but I'm askiing for a simple procedura .... The idea is .... where to set 4 or 5 breakpoints ...
Hi! Really appreciate for your work. Your library helped me a lot.
But I want to use more bigger fonts then 'font24.c' in your library. So I edited font24.c file on my own by extending its arranges twice bigger.
However, it doesn't work well as original font files. Is there any size limitations for ILI9488 for displaying bigger something?
If you have a great idea for displaying bigger fonts in this display, please help me
I agree: ST fonts shown on ILI9488, can appear too small for some needs.
In Displ_WChar I added "size" parameter that, if set to 2, "doubles" character width.
It should be easy also to double height.
Be aware: You can see that there is no a buffer swap inside the WChar function. It means that you have to set buffer size able to store at least 1 char.
eg. Font24 is 24x17 pixels per character. In RGB565 it is 24x17x2 = 816 bytes per character, RGB666 needs 1.2k. Doubling with buffer must be > than 2.4k. Doubling width and height it must be >4.8k.
Maybe problem you had was just a buffer overriding.
Very good 👍
👌
I checked 2 versions of TouchGFX 4.21 and 4.24 but can't find the Gaugee you used in your example.
Good job!!!
Thank you, Bob.
good
👍
Nice Video!
Thank you.
thats a very good and awesome work you have shared to us brother. thanks a lot for that. i have tested it with STM32F401RBT6 with ST7735. it worked well in spi polling mode. but facing problem with DMA and Interrupt mode. the LCD not getting initialized.
using TouchGFX?
@@bluewat tried both , only polling worked for me in both direct and touchGFX modes.
@@bluewat it occupied 52k of 64K ram as of now with out any special images, but made 2 screens and 3 widgets.
Hello thank you so much for this wonderful video, I'm working with the ST7789 240x280 display, I have the driver but I want it to be compatible with touchgfx, advise me on this thank you.
Paul,
the above video should indicate all the steps you have to do updating the library you already have.
A second possibility is analysing datasheets of ST7735 and ST7789 adapting the above library to your display.
is it possible to do it with ili9481 using this library? i am unable to find the exact library for ili9481, can anyone help?
The underlying logic is independent of the display used. But ILI9481 seems having a different configuration in many reference commands (e.g. RAMWR). So, I suppose this library cannot directly work with ILI9481
Thanks You !
👋
I really like your work and thank you for sharing. I added 2nd page in TouchGFX, I got a lot of errors.
Hello Burhan,
not easy to say,
there is a specific tutorial (#3), on TouchGFX support website, about multi-screen projects.
Keep an eye on the flash memory occupation!
Sarebbe bellissimo se Lei potessi fare : "LVGL + Square Line Studio " ...!!!
Sembra quasi una forma di stalking
Dear Mr.Mario First of all, congratulations for your project and to share those great tutorials with us. I tested the library with stm32f407 and ILI9341 and everything works fine but when I tryed to enable the freeRTOS pack in STM32CUBEide , the program stopped working, tft freezes. Are there any possibility of incompatibility of the libray and freeRTOS ? thanks in advanced , best regards!!
Hi Fernando,
unfortunately I have no experiences with FreeRTOS, so I can't help you about this point.
Hello , I did everything as you did and it doesn't work at all! i also use the same headerboard (stm32f411ceu6) the code compile without any error! my wiring is fine.... i'm using 3.5" TFT LCD with ILI9488.... I checked everything still get nothing... thank you
I had te same problem... I fix it so : #define ILI9488_V1 in z_displ_ILI9XXX.h...good luck..
Great tutorial, but wiring image seems to be removed from github directory and unfortunately, I don't know how to connect microcontroller to my ILI9488 spi display v1.0 based on this tutorial. Can you upload wiring image somewhere else?
Updated wiring picture.
Be aware that you will not be able to run ILI9488 board V1.0 on TouchGFX.
It doesn't handle RGB565, as stated here: ua-cam.com/video/020k2vbLAPc/v-deo.html
@@bluewat Thanks buddy, I didn't noticed that.
Hello Mr. Mauro
thanks a lot for your good tutorial.
I have one question.
Can I use this tutorial for ili9486L driver?
Unfortunately I haven't an ILI9486L board in my drawers.
After a quick reading of its datasheet, it seems that ILI9486L and ILI9488 work exactly the same way on SPI (they seems only to have a different color resolution on parallel communication, same commands. "After a quick reading").
But... I don't know the board you are referring: if it is SPI and uses XPT2046 touch driver (or if it is a no-touch board), you could try to set library as ILI9488_V1 and, if it works, you could try also ILI9488_V2 which gives faster results.
Let me know how it goes.
@@bluewat thank you. sure, I will test it...
sorry because in some places it appears that the ILI9488 screen only works with a pencil?
Using fingers you need less precision than using pencils.
So you shouldn't have any problem.
Have you tried to setup a library calibration?
Hello everyone
I'm using touchGFX and 3.5" display with ili9488
I managed to work with it and it shows everything as I wanted, but the issue is that when I power up the uC, sometimes it doesn't show anything and I need to reset the uC!!!!
I ran debug and there was no error or something else...
My uC is stm32f405rgt6...
What would be wrong...?
Thanks in advance:)
i have the same problem is the touch working for u?
@@sharankuppuswamy8951 yes the touch is working properly, what's your problem exactly? It doesn't show anything sometimes???
@@Muhammad-qf9vl touch is not working
@@sharankuppuswamy8951 have you checked the communication between the uC and the touch? Or did you check the wiring?? Also , maybe it's about the calibration... Watch the video about calibration and set the parameters, it should work... At least it worked for me:)
Dear MR.Mauro
I tested the library with STM32F429 and worked perfectly.Do you think is it possoble to work with STM32H743 MCU? I tried tried and till now didn´t work. thanks, best regards!!!!!
Have you seen this?
github.com/maudeve-it/ILI9XXX-XPT2046-STM32/issues/3
Thank you very much for your brilliant and performant driver.But i am facing some issue i am using version 2.1 so it is not displaying properly
but touch is working could you please help me with this
Could I use the same library for ili9341 3.5 you use with ili9341 2.8 240x320 ?
what's the 3.5 resolution? As per what I see on datasheet, 9341 handles 240x320 displays: library should work without any changes. Anyway, if display has a different resolution, you should just set its size on z_displ_ILI9XXX.h around line 175
Dear Mr.Mario, every thing works fine but buttons on the bottom activate when touch on the top, I am using ILI9341 in landscape mode, I tried with changing "Displ_Init(Displ_Orientat_90)" to Displ_Orientat_270 , display rotate along with buttons but touch also rotate, also test by changing the "define T_ROTATION_xx". Please direct me to how to fix it?
That seems to be something related to touch sensor calibration. Try to check it.
you could follow guideline here:
ua-cam.com/video/KS5u2-6yruU/v-deo.html
or here:
github.com/maudeve-it/ILI9XXX-XPT2046-STM32/tree/main/4-CALIBRATION
Can you guide on how to do the same process with a custom display that uses IC6211 (i have to develop it from scratch) via i2c , i'm a bit lost on what functions i should use so that they can work with touchgfx , thank you .
Setting up TouchGFX driver from scratch, for a custom display... well... there is a full website from ST to keep in consideration.
If you already developed a set of APIs for your display, you should find all the information you need in this video (maybe together with the following videos in the playlist).
Can you show me where you are getting confused?
Reducing it to the minimum, we could say that you need just to develop:
int touchgfxDisplayDriverTransmitActive() and
void touchgfxDisplayDriverTransmitBlock(const uint8_t* pixels, uint16_t x, uint16_t y, uint16_t w, uint16_t h)
That's for the display.
Then you have to learn to use TouchGFX.
thanks @@bluewat ,I'm currently working with an STM32U599 and a custom display equipped with an IC6211 driver. The setup involves I2C and MIPI DSI with 2 lanes. Right now, I'm setting up the project for the first time and am a bit concerned about the initial configuration. Should I enable LTDC along with the DSI host?
My goal is to first display colors and images before integrating TouchGFX. I want to ensure everything is working properly before moving on to using TouchGFX. I also noticed that the frame buffer location might need to be adjusted when switching to TouchGFX. Could you share your thoughts on the best approach to smoothly transition through these steps?
Thank you for your guidance!
Hi Mr. Vecchi,
Many thanks for this very informative video. But for some reason this ST7735 library is not working with touchgfx for me, although I have the display working directly with another driver. This means, my pin connections and SPI configuration is ok. I think I followed all the instructions you mentioned in the GitHub, but no success. Is there a chance that you are missing something in the GitHub for ST7735 part?
I resolved the issue by merging the other driver's init function and your TouchGFX implementation in the z_displ_ST7735.c file:) Anyway, thanks again for the information and the code that you provided in theVideo/GitHub.
👍
Thanks for all of your help on this! I've got it around 90% working with an ILI9488 and STM32H7, however I have run into a couple of issues near the end:
1.) When using the touch functionality with TouchGFX, the LCD will randomly turn all white when rapidly touching the screen and requires a hardware reset to fix. I've narrowed it down to the T_IRQ pin as the culprit and it seems like frequent touches cause it to catch in some loop (not 100% sure)?
2.) The update speed of my LCD seems much slower to your example (this especially shows when holding down one of the arrow buttons and the counter ticks up much slower) when set up with similar settings as yours.
Do you have any ideas on how to fix either of these issues?
Hi Sean,
about question 1)
As per what I can say, what you report indicates a problem on SPI communication, so I would follow theese steps:
- (obvious) check for a stable and affordable SPI wiring
- check SPI speed: I was never able to go over 50Mbps but in case of problems try to slow it down, I've seen (and shown in some video) that different displays can have different behavour. Remember that the SPI speed is not defined in CubeMX but by DISPL_PRESCALER define in "z_displ_ILI9XXX.h".
- set also "output speed" to pins involved in display: working ad 50 Mbps I've seen that they have to be set "high" at least. But the meaning of these "lables" depends on the uC. Check your datasheet.
This should fix your problem 1)
About problem 2:
that's a strange behaviour. I've seen that different uC can have different performances and unexpectedly enhanced SPI/DMA devices can bring to a slower performances with short data transfer. But that should not mean a "much slower" display as you say.
Have you tried to increase the buffer size ("block size") on TouchGFX configuration in CubeMX?
Having "pin availability" on the uC it is better to separate touch SPI by the LCD one. It will increase the overall TouchGFX performance.
I know that current library available on my GitHub page needs working a little fixing it to work on two separated SPI ports.
I will provide in a short time a new release easing the two configuration (single or double SPI port) along with enhancements for the usage of complex TouchGFX widgets.
Hi Mr.Mauro , thank you very much for sharing. i need emergency help .. i m trying to display a touch interface in 3.5" TFT SPI with ILI9488 driver .. i followed exactly the steps you show nut i have 25 error when i build .. i need ILI9488 driver for STM32F401RE nucleo or for STM32F407VG discovery i have both .. which one is compatible with ILI9488
25 errors... well... that seems non "exactly" the same as following proposed steps...🙂
Send me the list of errors, maybe I can halp you to fix something, or at least the reason for that.
I propose you to not overload this message system, movin to GitHub and opening an issue: github.com/maudeve-it/ILI9XXX-XPT2046-STM32/issues
That's also easier to use.
@@bluewat i have 3 errors just like the video before enabling the interrupt of PA12 ..but after i have 25 error ..btw i m using STM32F401RE and i think that's the problem ..there is the errors ../TouchGFX/target/generated/TouchGFXGeneratedHAL.hpp:21:10: fatal error: touchgfx/hal/HAL.hpp: No such file or directory......./TouchGFX/target/generated/STM32DMA.hpp:21:10: fatal error: touchgfx/hal/BlitOp.hpp: No such file or directory
...... ../TouchGFX/target/STM32TouchController.hpp:28:10: fatal error: platform/driver/touch/TouchController.hpp: No such file or directory
and more
@@mokhlessezd2106 I do not see why F401 should be a problem. Why are you supposing that? What are the limits are you knowing I don't see?
By above messages, it seems that TouchGFX project has to be generated. Keep in mind that TouchGFX must be THE LAST item generated in your project: e.g. if you make some changes in CubeMX, after having generated the device configuration you MUST open Designer and re-generate TouchGFX project.
Try that: maybe that's the only problem.
Now. Mokhless. If you like I help you, you have to help me. Do you see how is hard understanding your above post? If you need more technical help, please, post a message on GitHub, allowing you to post screenshots, program files and so on.
@@bluewat thank you very much sir .. i sent an issue on github
@@bluewat I'm also getting 25 errors including disp.h and disp.c and touch.c files, how to rectify this issue
Thank you very much for your video. On my board, I have an STM32F411CEU6, the LCD chip is an ILI9488, and the touchscreen chip is an XPT2046. I followed your tutorial and successfully flashed it onto the board, but my screen is all white. Can you help me, please? Thank you!
A full white screen should mean that SPI communication is not proceeding.
A lot of possible origins...
Not considering obvious questions about checking correct CubeMX configuration and wiring, one possibility is the GPIO speed of the pins involved in communication (CS and D/C for instance). Try to set them high or very high. Once working you will try to slow them down until working.
Another possibility, if you are prototyping on a breadboard, is that you are pushing too much the SPI port speed, having an unstable wiring. While prototyping I use a quite slow speed (even below 2 Mbps), pushing it up in the final part of developing or just when I move the project to the developed PCB
I don't remember if using a wrong color format leads to a "white screen". Try RGB666: that should be compatible with any display...
I already tried everything. Like setting gpio speed very high etc. But screen is still all white. But I still thank for your vedio.
@@HsuanderYT Hello, i have the same problem... could you solve it?
@@bluewat My problem is the same as him does:(((
I had te same problem... I fix it so : #define ILI9488_V1 in z_displ_ILI9XXX.h...good luck..
We're using an STM32F103VET6 and our Display is SPI based ILI9488 V1. The display didn't light up tho. Can you help?
Can you provide any more information about the error?
It's a V1.0 so you are not using Touch GFX, right?
What's the error?
@@bluewat Yes, we're not using touch GFX and are trying to run your test functions. The display just initializes and remains blank.
@@abhijithmandava9314 Assuming ,you set parameters in the display .h file and touch one, If you get a full white display after initialization there there are probably errors on SPI.
1) doublecheck display wiring
2) verify speed (maximum output speed in CubeMX) of pins involved in display communication and control.
3) try to run SPI at a lower speed (remember that SPI baudrate is controlled by DISPL_PRESCALER parameter, regardless what set in CubeMX)
By the way: but Have you changed your above first question after I answered to you? really???
Checked 1 and 2 before, will try 3. Thx for suggestion. Tried posting 1st question with more info, but character limit didn't let me post. Reduced it to very information lacking question and that was accepted. After your answer I tried modifying it so I can add further info but same issue.
Are you work with ILI9342C driver?
No, I don't have it.
ILI9342C seems to be an evolution of 9341 and the basic commands (what I'm using in library) seems to be the same. Same resolution.
You could try to set library handling ILI9341 and see.
Your display is an SPI one, right?
@@bluewat Ok, I will try use you library later.
Hi, I was wondering 3.5 V1.0 not working and is there any way to make v1.0 working?
No way to use it with TouchGFX.
TouchGFX and 3.5" V1.0 display don't share the same color format.
@@bluewat If I don't use If I TouchGFX I want it to be displayed on screen only not Touch🙂
Thank you very much for the answer.
But maybe…
… converting RGB666 to RGB565…
… for sure with a relevant impact on the overall performance.
HI, I updated just now library andling conversion RGB565 ->RGB666.
So now TouchGFX should work also with ILI9488V1.0
@@bluewat I'll do some testing. But I think I'm going to have a problem.
1.stm32 f103c8 not authentic >> Unable to upload data(Because the real thing is very rare)
2.because I use STM32CubeIDE 1.10.0
3.Do you have a way to upload data, please advise me.
can i add your github link in my video for same type of video
sure
Dear Mauro,
I am writing to you because i used to your great video:
ua-cam.com/video/g1siKaPox88/v-deo.html
that prepare own project in which I use STM32L476 and display SPI 4", ILI9488 from aliexpres.
I have a problem because the touch on the bottom of adisplay is worse than the touch on the top of the display - the touch is inaccurate and I had to touch a few times on the display. I change a display but it did not help.
I have set full touchGFX Mode, SPI 20 Mbit/s prescaler touch 4, prescaler touch 16.
Can you give me a advice where is a problem?
I will be very happy.
Best regards,
Kamil
Maybe, it is a calibration problem?
ua-cam.com/video/020k2vbLAPc/v-deo.html
github.com/maudeve-it/ILI9XXX-XPT2046-STM32/tree/main/4-CALIBRATION
@@bluewat I calibrated it in the near past. Maybe, a problem is with SPI settings? - reading touch data is to slow or to fast?
Actually I remember I've seen that there is a range of touch SPI speed where the sensor still works and replies to queries but giving low precision results. Try to drastically slow down touch spi speed and see the results. Keep in mind that touch sensor needs a communication of just a couple of bytes: you will see that a slow touch-SPI port doesn't affects the global TouchGFX project performance.
Let me know
Hii , everything went well, but wheni build the code i got 7 error before i have started writing in main.c. i am gettig undefined reference to `touchgfxSignalVSync', undefined reference to `touchgfx_init' and undefined reference to `touchgfx_taskEntry'. I have no idea how could i fixed that, do you know what it might cause that??? I have included two libs like you showed in video. I am using STM32F411, cube IDE 1.6.1, touchGFX 4.19.1 ( i did try 4.22 but i can't even open ApplicationTemplate.touchgfx.part from cubeIDE so i installed older version and works, i did changed in cubeMX under software packages 4.19.1)
ok i just got it to work... i had to change it to C++. but i don't get it how you were able to compile it without error with C.
Hi,
if you are not using TouchGFX (I suppose you aren't), in z_displ_ILI9XXX.h you have just yo set a comment on line:
"#define DISPLAY_USING_TOUCHGFX"
(change that line into
"// #define DISPLAY_USING_TOUCHGFX"
) otherwise functions will look for an integration to that package.
More info on
github.com/maudeve-it/ILI9XXX-XPT2046-STM32
and into the same z_displ_ILI9XXX.h file
@@bluewat i did use older version of TouchGFX and it worked without errors, ty.