Debug problem when adding display driver.
- From: Team Denayer <TeamDenayer@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 9 Dec 2005 02:00:02 -0800
We are working with Platform Builder .NET 4.2 with an ARMV4I based platform
with a PXA250 processor
When we add the display driver to our image and do a debug build, we don't
get anything on the display. the last output we get on the terminal is:
"Enabling adapter ints". After that, we get: "0x23CA8FA2: KITLSend(0): Timed
out waiting for ack (AckExpected: 22, TxSeq: 30)" which keeps repeating
itself.
Here is our debugger output:
Kernel debugger is waiting to connect with target.
0 PID:0 TID:0 Booting Windows CE version 4.20 for (ARM)
0 PID:0 TID:0 &pTOC = 800c231c, pTOC = 8032653c, pTOC->ulRamFree =
8040b000, MemForPT = 00000000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 14504, Secondary pages: 0,
Filesystem pages = 7252
0 PID:0 TID:0
Booting kernel with clean memory configuration:
0 PID:0 TID:0 Memory Sections:
0 PID:0 TID:0 [0] : start: 8040c000, extension: 00004000, length:
038a8000
0 PID:0 TID:0 Sp=ffffc7cc
2 PID:0 TID:0 Windows CE KernelInit
4294767296 PID:3cb7002 TID:3cb7262 Updated eptr->e32_vsize to = 000ab000
4294767297 PID:3cb7002 TID:3cb7262 Scheduling the first thread.
4294767298 PID:3cb7002 TID:3cb7262 0x83cb7024: KernelInit2:
pCurThread=83cb7024 hCurThread=03cb7262 hCurProc=03cb7002, KernelInit =
800dbab4
4294767299 PID:3cb7002 TID:3cb7262 0x83cb7024: Detecting VFP...
4294767299 PID:3cb7002 TID:3cb7262 0x83cb7024: VFP Not Found!
4294767300 PID:3cb7002 TID:3cb7262 0x83cb7024: Updated eptr->e32_vsize to =
00016000
4294767302 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module NK.EXE at
address 0x800B8000-0x80163000 (RW data at 0x803D6000-0x804042EB)
Kernel debugger connected (KDBG stream opened).
Kernel Version 1169 loaded at 0x800b8000, data relocated at 0x803d6000
Debugger connection established (Target CPU is ARM).
Loaded symbols for 'C:\PROJECTS\WINCE\MYXSILO\RELDIR\XSILODEBUG\NK.EXE'
Loaded symbols for 'C:\PROJECTS\WINCE\MYXSILO\RELDIR\XSILODEBUG\KD.DLL'
Finished re-loading kernel modules.
Loaded symbols for 'C:\PROJECTS\WINCE\MYXSILO\RELDIR\XSILODEBUG\COREDLL.DLL'
Loaded symbols for 'C:\PROJECTS\WINCE\MYXSILO\RELDIR\XSILODEBUG\FILESYS.EXE'
Loaded symbols for 'C:\PROJECTS\WINCE\MYXSILO\RELDIR\XSILODEBUG\FSDMGR.DLL'
Loaded symbols for 'C:\PROJECTS\WINCE\MYXSILO\RELDIR\XSILODEBUG\RELFSD.DLL'
4294767319 PID:3cb7002 TID:3cb7262 0x83cb7024: first = 01fe0000, last =
02000000, SharedDllBase = 03e90000
4294767333 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module
coredll.dll at address 0x03F80000-0x03FFD000 (RW data at
0x01FFF000-0x01FFF818)
4294767437 PID:e3ca0262 TID:e3ca023e 0x83ca0000: >>> Loading module
filesys.exe at address 0x04010000-0x04063000
4294767448 PID:e3ca0262 TID:e3ca023e 0x83ca0000: FileSystem Starting -
starting with clean file system
4294767593 PID:e3ca0262 TID:e3ca023e 0x83ca0000: >>> Loading module
fsdmgr.dll at address 0x03F20000-0x03F3D000 (RW data at 0x01FF5000-0x01FF5760)
4294767602 PID:e3ca0262 TID:e3ca023e 0x83ca0000: >>> Loading module
relfsd.dll at address 0x03F50000-0x03F5B000 (RW data at 0x01FF9000-0x01FF9ABC)
4294767627 PID:e3ca0262 TID:e3ca023e 0x83ca0000: FSREG: Logging in default
user.
4294767627 PID:e3ca0262 TID:e3ca023e 0x83ca0000: SetCurrentUser: Logging out
(nobody), logging in default
4294767627 PID:e3ca0262 TID:e3ca023e 0x83ca0000: FS: Using default path
"\profiles\"
4294767628 PID:e3ca0262 TID:e3ca023e 0x83ca0000: SetCurrentUser: User hives
not supported -- using same registry for all users
4294767629 PID:e3ca0262 TID:e3ca023e 0x83ca0000: FS: Using default path
"Windows\"
4294767657 PID:e3ca0262 TID:e3ca023e 0x83ca0000: FS: Using default path
"Windows\"
4294767660 PID:e3ca0262 TID:e3ca023e 0x83ca0000: Filesystem initialized!
4294767661 PID:3cb7002 TID:23ca8fa2 0x83ca5a3c: InitializeJit
And then it doesn't say anything anymore.
When we do a release build it works just fine.
Can anyone please tell us what the problem is here?
TIA,
Sören & Lars.
.
- Prev by Date: Re: Run .NET application
- Next by Date: Re: help on eboot from NAND flash
- Previous by thread: Run .NET application
- Next by thread: Display problems in 5.0
- Index(es):
Relevant Pages
|
