MikroElektronika Forum

There are new ILI chips which are mounted in new TFT screens. I try to use 16bit TFT ILI9486 with others library from your, but without success. Not compatible.

I made compare datasheets for ILI9431 and ILI9486 and there is no simple upgrade. Similiar but not identical.

Would you make support for this chip in graphical libraries and VisualTFT ?

Bertold

Hi,

Thank you for this proposal,
I will pass this to our developers.

Regards,

I have modified the definition of the ILI9481 TFT driver and I have had a good result. You can create with VTFT with the ILI9481 drivers to generate the codes and then replace ILI9481 with ILI9486, review the example attached.

HELLO CAN OPERATE A TFT DISPLAY WITH ILI9486 CONTROLLER AND I WORK CORRECTLY, NOW I AM WITH CONTROLLER ILI9488 BUT I COULD NOT.

HAMSL wrote:I have modified the definition of the ILI9481 TFT driver and I have had a good result. You can create with VTFT with the ILI9481 drivers to generate the codes and then replace ILI9481 with ILI9486, review the example attached.

any news for the SPI ILI9488?

Hi,

I believe that I answered you on this forum:
viewtopic.php?f=160&t=76952&p=306586#p306586

Kind regards,
Jovana

For SPI Display controller you could see the https://simple-circuit.com/pic-mcu-ili9 ... -projects/
Haven't tried it yet, although I've managed to compile it.
There must be a way to generate the VTFT code for a certain display controller and transfer it to your custom one, as HAMSL says above. HAMSL's try was made in MIROC for ARM.

Hi

You wrote:

There must be a way to generate the VTFT code for a certain display controller and transfer it to your custom one

There appears to be plenty of ILI9486 and ILI9488 SPI/8 Bit/16 Bit libraries on the internet or you can write your own.

It is also fairly easy to use these libraries with ME compilers.

It is not difficult to use the *_driver.c output file from Visual TFT for anything you want to do with it. First make a VTFT project with the correct screen size (e.g 320x240 or 800x480, etc) and any MCU (it is not important) and generate the VTFT code. Included in the generated files will be a “ *_driver.c file“. This *_driver.c file is an ascii text file which contains all the information about all the screen objects in the project.

There are many ways to extract information from a Visual TFT driver.c file. Here are two ways. There are many other ways.

1. Manually edit the driver.c file and include it in your project. If you are not using the ME graphics library, you can truncate the file after the screen object information and dump the ME functions in the driver.c file. You then need to write functions (probably in a library) to extract the object information from the driver.c file, manipulate the information, and draw the objects on each screen as required. You can either use the ME designed structures in the *_objects.h file or design your own screen object structures.

2. Write a programme in Visual C++ that runs on a pc and loads a selected Visual TFT driver.c file into the pc memory, extracts the required information from the driver.c file, manipulates that information, and then outputs files ( .c and .h files) which contain screen object information in a format which conforms to the requirements of the existing graphics library and functions on the target device. In this way, Visual TFT can be used to design screens for non ME compilers or ME compilers with non ME graphics libraries. If I were you and I wanted to use Visual TFT to design screens for a non ME compiler (such as the STM32CubeIDE compiler using the BSP graphics library) or an ME compiler which uses a non ME graphics library, I would probably write a programme like the one shown below.

Hi

Further to my email above, if anyone wants to use Visual TFT to design screens for non ME compilers and/or non ME graphics libraries (including SPI connected ILI9486 and ILI9488 TFT screens) then please write me an email at auslame@outlook.com.

rus51

Greetings
also i need a library for ili9486 8 bit 480x320 tft.
i have to start a project with a pic18f46k22 and mikroc pro compiler.
can someone help me please?