uezgui-1788-70WVM LCD controller configuration

lpcware · ‎06-15-2016

Content originally posted in LPCWare by padmaja on Sun Jun 28 23:19:38 MST 2015

hi all,

I am working on uezgui-1788-70wvm. After seen some source codes of LCD controller initialization, i confused in some source files they used I2C EEPROM to access the LCD controller but in some files just initialized IOCON lines and LCDC registers. IN uezgui-1788-70WVM schematics, no connections from LCD to CORTEX for I2C interfacing. can anybody give me the clarity about this LCD controller initialization and display read/write functionality??

thanks in advance..

BR,
padmaja.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by padmaja on Tue Jul 07 03:43:58 MST 2015
hi,

thanks chris. i am closing this thread. i will open a fresh thread for capacitive touch screen and touch events reading through I2C interface

padmaja

lpcware · ‎06-15-2016

Content originally posted in LPCWare by chris.stocker on Mon Jul 06 06:35:51 MST 2015
padmaja,

The simulator files where provided as an example for customers who what to do their GUI developement of emWin on the PC using Visual Studio. Certain file where included in this directory to handle the fact that it is not running on embedded hardware.

The functions you mention are part of SEGGER's emWin and not out uEZ Software. You will not be able to see the actual implementation because the NXP license only covers a binary only license.

You can find the emWin prototypes in the folder "/uEZ/Source/Library/GUI/SEGGER/emWin".

Chris Stocker
TeamFDI

lpcware · ‎06-15-2016

Content originally posted in LPCWare by padmaja on Thu Jul 02 21:57:24 MST 2015

Hey chris,

if LCD code is not dependent on C:\Users\acer\Downloads\uEZ_v2.06c_SourceForge\uEZ_v2.06c_SourceForge\uEZDemos\Build\Simulator\emWin\Config\LCDConfig.c then in platform files C:\Users\acer\Downloads\uEZ_v2.06c_SourceForge\uEZ_v2.06c_SourceForge\uEZ\Source\Platform\emWin\Config\LCDConfig.c doesn't have all functions definitions then how can we understand. For example in _InitController function, called 3 functions LCD_SetSizeEx etc. for those functions i didn't find definitions in uEZ_v2.06c_SourceForge source folder.And you said about this WM_MULTIBUF_Enable(1);
this function definition also i ddin't get. how can i know these definitions??

padmaja

lpcware · ‎06-15-2016

Content originally posted in LPCWare by chris.stocker on Thu Jul 02 07:14:55 MST 2015
padmaja,

There is a callback function in the platform files that handles setting the correct address for the UPBASE, "SUICallbackSetLCDBase" located in "/uEZ/Source/Platform/FDI/uEZGUI_1788_70WVM/uEZGUI_1788_70WVM.c". In the case of emWin this function is called automatically when the "WM_MULTIBUF_Enable(1);" option is enabled. On the SWIM side there is some code we have implemented that will make use of this function for switching between buffers "/uEZ/Source/Library/GUI/FDI/SimpleUI".

The simulation files are not related to the uEZGUI-1788-70WVM.

The SWIM code does not know anything about the LCD and assumes that everything it needs is configured before hand. The actual initialization of SWIM can be trace starting in main.c with the function "SUIInitialize(SIMPLEUI_DOUBLE_SIZED_ICONS, EFalse, EFalse);", the source file for this function is located at "/uEZ/Source/Library/GUI/FDI/SimpleUI/SimpleUI_UtilityFunctions.c".

Chris Stocker
TeamFDI

lpcware · ‎06-15-2016

Content originally posted in LPCWare by padmaja on Thu Jul 02 03:56:25 MST 2015

hi,
Ok, now i understand something better than beore.LCD display don't need I2C interface for displaying, Touchsccreen need I2C1 interface for x,y co-ordinates reading. i"ll work on it and get back to u soon.

thanks

padmaja

lpcware · ‎06-15-2016

Content originally posted in LPCWare by padmaja on Wed Jul 01 22:24:16 MST 2015

chris,

For that DMA FIFO's we have to assign some memory locations for UPBASE and LPBASE. So if we assin 0xA0000000 location for UPBASE, Then we need to I2C interface to communicating this location. i think this location is off chip memory, so that we need I2C interface for accessing EEPROM. If this I2C is not required, is there any specific UPBASE address or any memory location we can assign ? is upper panel frame buffer address is assigned to win->fb? if Yes, in code where is assigning?

that _EEPROM_read is in uEZ_v2.06c_SourceForge\uEZDemos\Build\Simulator\emWin\Config\LCDConfig.c file. used in _InitOtherLCD function. is this file is not related to uezgui-1788-70wvm?? in lpc_swim.c file, there is no LCD configuration register settings. for that swim.c file contained functions were ok, but LCD initialization function is not there. Is Initialization part is only we just write LCD_registers to specified values according to our usage, io lines configure accordinf to our LCD or any other things that we need to do ??

thanks in advance

padmaja

lpcware · ‎06-15-2016

Content originally posted in LPCWare by chris.stocker on Wed Jul 01 11:47:02 MST 2015
padmaja,

I'm not sure where in the code you are seeing the reference for I2C related to the LCD, but in the case of the uEZGUI-1788-70WVM no I2C communication is needed to operate the display.

Essentially the frame buffer would be a two-dimensional array, so this function updates the value of a "pixel" at location [x][y]. It uses "y * win->xpsize" to move to the start of the correct "row" and then "[x]" to offset to the correct "column". In this case the frame buffer would be a two-dimensional array of 800 x 480 16-bit values.

Chris Stocker
TeamFDI

lpcware · ‎06-15-2016

Content originally posted in LPCWare by padmaja on Wed Jul 01 03:42:08 MST 2015

hi,

i have configured LCD. But i have doubt if we assign 0xA0000000 as a UPBASE addr then we need to configure I2C1 for communicating with EEPROM?? and in "swimm_driver_put_pixel" function one statement is there
                                                                   "(win->fb + y * win->xpsize)[x] = color;"   can anybody please explain this statement. i understood something like win->fb is framebuffer starting address
                         y is y co-ordinate
                        win->xpsize is x physical address
                        x is x co-ordinate

So, with (win->fb + y * win->xpsize) this we will get some address. address[x] = color. For each address it has 800 locations like array. my assumption is right or wrong?? if this is wrong, could you please explain me this instruction.

thanks

padmaja

lpcware · ‎06-15-2016

Content originally posted in LPCWare by chris.stocker on Tue Jun 30 08:19:58 MST 2015
padmaja,

The best place to start for seeing the flow of the LCD initialization is in the platform file, "/uEZ/Source/Platform/FDI/uEZGUI_1788_70WVM/uEZGUI_1788_70WVM.c". the function "UEZPlatform_LCD_Require" is where the code starts initializing the LPC1788 and the display. This function defines the pins of the LPC1788 that will be used to control the display data as well as the PWM to control the backlight brightness.

The next place to look is the HAL setup of the LCD controller called in the require function, "LPC17xx_40xx_LCDController_Require" located at "/uEZ/Source/Processor/NXP/LPC17xx_40xx/LPC17xx_40xx_LCDController.c". This driver handle setting the pins to to proper modes and any processor specific register settings.

The next step would be to look at the display specific driver for the platforms defined LCD, defined in Config_Build.h of the application. For the uEZGUI-1788-70WVM the defined display is "LCD_CONFIG_MICROTIPS_UMSH_8596MD_20T". You can reference compile time specific setting for this display in "/uEZ/Include/Device/LCD/Config_LCD.h". Inside the require routine you will notice a macro called "UEZ_LCD_INTERFACE_ARRAY" which is defined as "LCD_Microtips_UMSH_8596MD_20T_InterfaceArray" when this display is selected. This tell the compiler to use the driver located at "/uEZ/Source/Devices/LCD/MicroTips/UMSH-8596MD-20T/Microtips_UMSH_8596MD_20T.c". Display specific timing and setting are setup here and call the HAL layer to handle the register settings.

Writing to the display to display data can be done via the Framebuffer, address 0xA0000000, either directly or using a graphics package like NXP's SWIM or SEGGER's emWin both are available in uEZ. You can also find more information about the LCD API on our website.

http://www.teamfdi.com/uez/docs/group__u_e_z_l_c_d.html

For the most part the uEZ API is very similar in structure. You have the high level API which links to a generic driver, which then links to the HAL layer. These linkages are setup during initialization and begin at the function "uEZPlatformStartup", typically located in "main.c" of the application.

Chris Stocker
TeamFDI