Hi All,
I am trying to apply the AMOLED type of LCD.But BOARD AMOLED applied to the normal operation of the WinCE 6.0 is not.In Board has the following message to confirm. But problems are not accounted for the previous Point.On EBOOT AMOLED Type of LCD is a normal behavior.
======================================================================================
Windows CE Kernel for ARM (Thumb Enabled) Built on Sep 25 2009 at 11:04:23--- High Performance Frequecy is 32768 khz---media contains 1 flash regions: Type=2, StartP=0x0, NumP=0x800, NumL=0x0, Sec/Blk=0x40, B/Blk=0x20000, Compact=4.media contains 0 reserved regions:+OALIoCtlHalRtcUpdate()dm9 id errordm9 id errorPHY_AssertResetGPIO147 set lowGPIO147 set highUfnClientLib!UfnCheckPID: WARNING -- using MS reference platform VID/PID 0x045e/0x00ce (not allowed in shipping platforms) DisplayInit + DisplayInit - OMAPDDGPE::DrvEnableDriver * OMAPDDGPE::OMAPDDGPE + LcdPdd_DVI_Select + LcdPdd_DVI_Select - OMAPDisplayController::InitController + OMAPDisplayController::SelectDSSSourceClocks + OMAPDisplayController::SelectDSSSourceClocks - OMAPDisplayController::ResetDSS + OMAPDisplayController::RequestClock + OMAPDisplayController::RequestClock - OMAPDisplayController::ReleaseClock + OMAPDisplayController::ReleaseClock - OMAPDisplayController::ResetDSS - OMAPDisplayController::SetPowerLevel + OMAPDisplayController::RequestClock + OMAPDisplayController::RequestClock - OMAPDisplayController::SetPowerLevel 1 LcdPdd_SetPowerLevel + LcdPdd_SetPowerLevel g_pDispRegs == NULL OMAPDisplayController::SetPowerLevel - OMAPDisplayController::InitController - OMAPDisplayController::InitLCD() + OMAPDisplayController::SetPowerLevel + OMAPDisplayController::SetPowerLevel - LcdPdd_LCD_Initialize + LcdInitGpio + LcdDviEnableControl + = LcdDviEnableControl - LcdDviEnableControl - LcdInitGpio - LcdPdd_LCD_Initialize - LcdPdd_LCD_GetMode + LcdPdd_LCD_GetMode - OMAPDisplayController::InitLCD() - OMAPDisplayController::InitInterrupts + OMAPDisplayController::DssInterruptHandler + OMAPDisplayController::InitInterrupts - OMAPFlatSurface::Initialize + LcdPdd_GetMemory + LcdPdd_GetMemory - OMAPFlatSurface::Initialize - OMAPDDGPE::OMAPDDGPE - OMAPDDGPE::GetModeInfo + OMAPDDGPE::GetModeInfo modeNumber == 0 OMAPDDGPE::SetMode + OMAPFlatSurface::Allocate + OMAPFlatSurface::Allocate + OMAPFlatSurface::Allocate - OMAPFlatSurface::Allocate - OMAPFlatSurface::Stride + OMAPFlatSurface::Stride - OMAPFlatSurface::VirtualAddr + OMAPFlatSurface::VirtualAddr - OMAPFlatSurface::Height + OMAPFlatSurface::Height - OMAPFlatSurface::Width + OMAPFlatSurface::Width - OMAPFlatSurface::Height + OMAPFlatSurface::Height - OMAPFlatSurface::Stride + OMAPFlatSurface::Stride - OMAPFlatSurface::VirtualAddr + OMAPFlatSurface::VirtualAddr - OMAPDisplayController::RotatePipeline + OMAPDisplayController::SetPipelineAttribs + OMAPDisplayController::AccessRegs + OMAPDisplayController::AccessRegs - OMAPFlatSurface::Width + OMAPFlatSurface::Width -
OMAPFlatSurface::Height + OMAPFlatSurface::Height -
OMAPFlatSurface::PixelIncr + OMAPFlatSurface::PixelIncr -
OMAPFlatSurface::RowIncr + OMAPFlatSurface::RowIncr -
OMAPFlatSurface::PhysicalAddr + OMAPFlatSurface::PhysicalAddr -
OMAPFlatSurface::Width + OMAPFlatSurface::Width -
OMAPDisplayController::SetPipelineAttribs - OMAPDisplayController::EnablePipeline + OMAPDisplayController::AccessRegs + OMAPDisplayController::AccessRegs - OMAPDisplayController::EnableLPR + OMAPDisplayController::EnableLPR - OMAPDisplayController::FlushRegs + OMAPDisplayController::FlushRegs - OMAPDisplayController::EnablePipeline - OMAPDisplayController::EnableTvOut + OMAPDisplayController::AccessRegs + OMAPDisplayController::AccessRegs - OMAPDisplayController::EnableTvOut - OMAPFlatSurface::Width + OMAPFlatSurface::Width - OMAPFlatSurface::Height + OMAPFlatSurface::Height - OMAPFlatSurface::Stride + OMAPFlatSurface::Stride - OMAPDDGPE::SetMode - OMAPDDGPE::GetModeInfo + OMAPDDGPE::GetModeInfo modeNumber == 0 Exception 'Data Abort' (4): Thread-Id=05230006(pth=86aa6000), Proc-Id=00400002(pprc=85ff5308) 'NK.EXE', VM-active=01dc0002(pprc=885ad6c0) 'udevice.exe'PC=c0199cbc(gwes.dll+0x00059cbc) RA=c0199ca4(gwes.dll+0x00059ca4) SP=d4f3fdd8, BVA=00000104===============================================================================
Thanks,
I don't completely understand your question. I would first like to get a baseline.
1. What BSP Version are you using?
2. What changes did you make for your LCD in the display driver code? (I assume you have your custom built hw that has this LCD.).
3. Did a debug version of display driver help narrow down the problem?
4. Did you say that when eboot is coming up the display is fine?
---
1. BSP Version is WINCE 6.0
2. EVM Board (DEVKit 800) has LCD. but I Changed LCD Module. That used SPI communication. before LCD Module used I2C Communicate.
3. HW Block is Same EVM Board. HW Block Changed Artwork and LCD Module. I think that some problem is LCD Module.
4. i mean is LCD was work well in the Eboot. (Logo display)
* My questions is Red Color Text
OMAPDDGPE::GetModeInfo + OMAPDDGPE::GetModeInfo modeNumber == 0 ====> I want to find next Step. I can not found 'GetModeInfo' Function Call point.
Exception 'Data Abort' (4): Thread-Id=05230006(pth=86aa6000), Proc-Id=00400002(pprc=85ff5308) 'NK.EXE', VM-active=01dc0002(pprc=885ad6c0) 'udevice.exe'PC=c0199cbc(gwes.dll+0x00059cbc) RA=c0199ca4(gwes.dll+0x00059ca4) SP=d4f3fdd8, BVA=00000104
====> In any case, I want to know what these messages out. (used case) and Where to learn more about the support you please give a hint.
1. WinCE 6.0 is the WinCE version and not the BSP version. You can find the version by looking inside the file PLATFORM\TI_EVM_3530\readme.txt or in BSP documentation (I'm not sure what version you got with DevKit800).
2. I'm not familiar with DEVKit800. The WinCE BSP is only tested on OMAP3530 EVM from Mistral. And latest BSP Version for that is BSP 6.15.00
4. The GetModeInfo is called by the WinCE GWES subsystem. Look under public\COMMON\oak\drivers\display\ddgpe\ddgpe.cpp
Looks like your error is in gwes.dll.
I suggest that you look at TI_EVM_3530\SRC\DRIVERS\LCD\VGA\lcd_vga.c to see if you have made all necessary changes for your LCD.
Thanks for reply.
May I download BSP 6.15.00 Version? and how to download?
My BSP Version is 6.09.00 Version.
You can find it here http://focus.ti.com/docs/toolsw/folders/print/dvsdk-winceomap.html Click on the tab under BSPSRC-WINCEOMAP.
Please note that this is not going to solve your problem. This was just to establish a baseline. I don't believe there were any changes in the LCD related code for quite some time. Also I'm not sure what changes if any the supplier of the DEVKIT800 made to the WinCE BSP for it work on the DEVKIT800 board.
The 6.15 version has only been tested on OMAP3530 EVM from Mistral. You can download the release and compare the files in the Display directory with what you have to see if there are any relevant changes. If you don't seen any major changes then stick with your current version and debug the problem. Eventually I do recommend that you move to the latest version for other fixes.