I would like to use a SPI Interfaced LCD Display while still using all of the emWin tools. For this project I can not use a parallel interface. Is there anyone who can point me in the right direction to do this. Thanks
Thanks for reaching out Renesas Engineering Community.
Please let me inform you that FSP has already integrated the SEGGER emWin and the graphic libraries can be used for free.
You can easily start creating your own graphics application by using the the SEGGER emWin stack which has an other stack configured below the rm_emwin_port which is a middleware in FSP that it is providing code to combine the code from the Segger libraries with the code for the graphics peripherals provided.
In the website of EK-RA6M3G you can find plenty of examples with graphic applications and application notes of how to develop them step by step.
Please check the example provided here which is using the Segger emWin stack and the AppWizard app .
Getting Started with the Graphics Application – Application Project - Sample Code
Could you please specify what do you mean by saying I cannot use a parallel interface? Does this mean that you want to develop a bare metal application for graphics?
The EK-RA6M3G uses a display that has a parallel input either 8 or 16 bits plus control lines. I need to use a display that has a SPI input to drive it 3 lines plus control. I do not a configuration setting on r-glcdc for a SPI port.
I can see. In this case unfortunately we do not have an example to share with you, which is using the SEGGER emWin libraries with an SPI LCD. But generally you can add the Segger emWin stack to generate code in your fsp project without adding below the middleware rm_emwin_port and make your own implementation to use the SPI instead of the GLCDC peripheral.
I can share with you an application note which is using the segger emWin library with an SPI LCD but this application note is for RX Family.
Hope this helps!
John, if you have not sorted this out already, you can go to the SEGGER emWin site and get drivers for a variety of SPI interfaced chips. However, this may involve spending money.
There should be driver files for a SPI interface file from the vendor. Just write an adapter layer to call the FSP HAL SPI calls instead of what the panel vendor provides. Import this code in the the project and build.