Migrating Windows CE.NET 4.2 to CE 5.0 on OMAP1510 platform

Hi All,

I am migrating Windows CE.NET 4.2 to CE 5.0 on OMAP1510 platform.
The BSP is working fine with CE.NET 4.2.  The same BSP we built it in
CE 5.0 and downloaded into target device but image is not getting
displayed.  We debugged it and found that CE Core schedulerInit is
failing, means that MDCreateThread is executing but after that no
response.

MDCreateThread(pCurThread, pStack, pCurProc->e32.e32_stackmax,
(LPVOID)SystemStartupFunc, 0, TH_KMODE, 0);

RETAILMSG(1,(L"Sched: MDCreateThread is done\r\n")); //removable

what could be the problem? Any suggestion is appreciated..

Thanks in Advance
Srinivas

Hi,

We are migrating Windows CE.NET 4.2 to CE 5.0 on OMAP1510 platform.  The BSP 
is working fine with CE.NET 4.2.  The same BSP we build it CE 5.0 and 
downloaded into target device but image is not getting displayed.  We 
debugged it and found that CE Core schedulerInit is failed, means that 
MDCreateThread is executing but after that no response.


"<Drive name>:\WINCE500\Private\WINCEOS\COREOS\NK\KERNEL\kwin32.c"

    HeapInit();
    lpWriteDebugStringFunc(TEXT("HeapInit done.... \r\n"));

    InitMemoryPool();
    lpWriteDebugStringFunc(TEXT("InitMemPool..Done...\r\n"));

    ProcInit();
    lpWriteDebugStringFunc(TEXT("SchdInit....Starts.....\r\n"));

    SchedInit();
    lpWriteDebugStringFunc(TEXT("Scheduling the first thread. msg by 
Vadivel\r\n"));

"<Drive name>:\WINCE500\Private\WINCEOS\COREOS\NK\KERNEL\schedule.c"


MDCreateThread(pCurThread, pStack, pCurProc->e32.e32_stackmax, 

(LPVOID)SystemStartupFunc, 0, TH_KMODE, 0);

RETAILMSG(1,(L"Sched: MDCreateThread is done\r\n")); //removable

what could be the problem?

There's a list of things that you have to do to port a platform to CE 5 in 
the help.  Which of those things have you done?

In the Contents of Help: How-to Topics | Migration How-to Topics...

Paul T.

"Migrating CE.NET 4.2 to CE 5.0" <Migrating CE.NET 4.2 to CE 

I seem to have lost the actual problem original post but I'd be concerned 
about the following messages in the output:

"OEMInitDebugSerial: KITL initialization failed."

If KITL isn't set up to work correctly and the system is enabled for KITL 
then it will just stop and wait for a KITL connection that will never 
happen.

-- 
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Hi Steve Maillet,

As per your statement,
"
 If KITL isn't set up to work correctly and the system is enabled for KITL 
 then it will just stop and wait for a KITL connection that will never 
 happen.
"  
in that case how I am getting other debug message like,

CDSetupInit+
LCDSetupRegs: LCD registers initial values.
    LCD Control = 0xfe000cec.
    LCD Timing0 = 0x27030cef.
    LCD Timing1 = 0x802093f.
    LCD Timing2 = 0xfc000002.
    MCU_CKCTL   = 0x250a.
LCDSetupRegs: Setting LCD registers for 240x320, 16BPP @ 60+/-3Hz.
LCDSetupRegs: LCD controller maximum frequency = 168000000.
LCDSetupRegs: Total PCLKs per HSYNC = 288.
LCDSetupRegs: Total HSYNCs per VSYNC = 333.
LCDSetupRegs: PCLKs per VSYNC = 95904.
LCDSetupRegs: PCLK (MIN, MID, MAX) 5466528, 5754240, 6041952 (Hz).
LCDSetupRegs: Frame buffer in ISRAM.
LCDSetupRegs: At LCDDIV = 8, LCDClockFreq = 21000000Hz,
    PCD = 4, Total Divisor = 32.
    PixFreq = 5250000Hz, FrameRate = 55Hz.
LCDSetupRegs: At LCDDIV = 4, LCDClockFreq = 42000000Hz,
    PCD = 7, Total Divisor = 28.
    PixFreq = 6000000Hz, FrameRate = 63Hz.
LCDSetupRegs: Using LCDDIV = 4, PCD = 7.
LCDSetupRegs: LCD registers final values.
    LCD Control = 0xfe000cec.
    LCD Timing0 = 0x27030cef.
    LCD Timing1 = 0x802093f.
    LCD Timing2 = 0xfc000007.
    MCU_CKCTL   = 0x250a.
LCDSetupDMA: DMA registers initial values.
    DMA LCD Control = 0x0.
    DMA LCD TopF1 = 0x11fc2000.
    DMA LCD BotF1 = 0x11fe781e.
LCDSetupDMA: Frame buffer in ISRAM.
LCDSetupDMA: Palette entry 0 (0x88000000) = 0x4000.
LCDSetupDMA: DMA registers final values.
    DMA LCD Control = 0x40.
    DMA LCD TopF1 = 0x20000000.
    DMA LCD BotF1 = 0x2002581e.
OEMInit is done!!! by Vadivel
OEMInit: is done! by Vadivel.
Booting Windows CE version 5.00 for (ARM)

&pTOC = 80049a74, pTOC = 81a4ff2c, pTOC->ulRamFree = 84087000, MemForPT = 
00000000

Old or invalid version stamp in kernel structures - starting clean!

Configuring: Primary pages: 7542, Secondary pages: 0, Filesystem pages = 3771

Booting kernel with clean memory configuration:

Memory Sections:
[0] : start: 84088000, extension: 00002000, length: 01d76000

Sp=ffffc7cc

ARMInit done.

Windows CE KernelInit

Heap Init done

Init memory Pool done

Proc Init done

Updated eptr->e32_vsize to = 000ac000

Scheduler: Do Virtual alloc is done

Scheduler: MDCreateThread starts...

pl can you give me a sucession/soluation that will useful to me.

Thanks,
Vadivel