Re: Debug and RELFSD

Tech-Archive recommends: Speed Up your PC by fixing your registry

Have you tried to disable the firewall and/or AntiVirus software to see if
they blocking the communication or not?

"Joe Welfeld" <jwelfeldnospam@xxxxxxxxxxxxx> wrote in message
news:usPhbmjeIHA.5788@xxxxxxxxxxxxxxxxxxxxxxx
Hi All.

(please excuse if this is a second post, I have been having trouble with
posting...)

I am trying to get my NK.bin to boot using debugger and I get so far and
the system hangs...
This is brand new hardware, If I build a release nk.bin and put it on
the hardware to boot locally it will boot.

but if I build a debug version and load it via debug

I get to the point where I am trying to mount the
RELFSD. I can set break points and step through code right up to where
the system hangs. Its not really a hang its a blocking INFINITE call


RelfsdMountThread

which in turn calls

PPSHConnect()


PPSHConnect calls write_header

and then calls read_header

eventually a call to

EdbgRecv(KITL_SVC_PPSH, PpfsEthBuf,&dwLen, INFINITE);

this EdbgRecv is called with an INFINITE timeout and here I set...

My debug window output up until this time is pasted below...

After the "hang" I run ethereal and I can see my ethernet debug is
still
running and there poth sides are trading messages, so the system is still
alive but I am still waiting n this edbgrcv...

Any help ? any Idea what I am missing ?

0 PID:0 TID:0 CEPC Firmware Init
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 g_dwCPUFeatures = 0088a93d
0 PID:0 TID:0 Looking for rom chain
0 PID:0 TID:0 Rom chain NOT found
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000
0 PID:0 TID:0 Booting Windows CE version 5.00 for (x86)
0 PID:0 TID:0 &pTOC = 80227b58, pTOC = 825be294, pTOC->ulRamFree =
8264a000, MemForPT = 00004000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 6543, Secondary pages: 0,
Filesystem pages = 3271
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: 8264f000, extension: 00002000, length:
0198f000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 8023ee28.
0 PID:0 TID:0 Windows CE KernelInit
4294767297 PID:3fdf002 TID:3fdf1de Updated eptr->e32_vsize to = 00092000
4294767297 PID:3fdf002 TID:3fdf1de Scheduling the first thread.
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: KernelInit2:
pCurThread=83fdf030 hCurThread=03fdf1de hCurProc=03fdf002, KernelInit =
80261f90
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
=
00005000
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
=
00022000
4294767317 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
=
00007000
4294767337 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
=
00018000
4294767348 PID:3fdf002 TID:3fdf1de 0x83fdf030: Starting kernel debugger
software probe (KdStub) - KD API version 18
4294767348 PID:3fdf002 TID:3fdf1de 0x83fdf030: Calling KDEnableInt (FALSE,
NULL) without previously calling KDEnableInt (FALSE, p)
4294767362 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module NK.EXE
at
address 0x80220000-0x802B2000 (RW data at 0x825C1000-0x8262F2DF)
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is X86).
Target name: CE Device
Probe name: KdStub
Binary Image should be loaded at 0x80220000 / Data relocated at 0x825c1000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\NK.EXE'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\KD.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\OSAXST1.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\OSAXST0.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\HD.DLL'
4294767405 PID:3fdf002 TID:3fdf1de 0x83fdf030: first = 01750000, last =
02000000, SharedDllBase = 02130000
4294767433 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module
coredll.dll at address 0x03F50000-0x03FF3000 (RW data at
0x01FFE000-0x01FFF765)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\COREDLL.DLL'
4294767455 PID:3fdf002 TID:3fdf1de 0x83fdf030: Did not find emulation code
for x86... using floating point hardware.
4294767516 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module
coredll.dll at address 0x03F50000-0x03FF3000 (RW data at
0x01FFE000-0x01FFF765)
4294767558 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module
filesys.exe at address 0x04010000-0x0407F000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\FILESYS.EXE'
4294767582 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: CertMod.dll not found,
using old OEM Trust Model
4294767583 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FileSystem Starting -
starting with clean file system
4294767584 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FS: initializing ROM/RAM
file system
4294767584 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: SC_CreateAPIHandle:
pvData
== NULL
4294767584 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FS: Registering file
system
ROM, index 2, flags 0x00000031
4294767584 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FS: Mount complete (ROM,
index 2, flags 0x00000031)
4294767585 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: OEMIoControl: Unsupported
Code 0x101008c - device 0x0101 func 35
4294767708 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: Succeeded on CheckFile
4294767708 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: RestoreFile(0x23fb0a22)
called fDelete = TRUE
4294767995 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: PCIReg(key:
Drivers\BuiltIn\PCI\Instance\KITL, device: 0/14/0)
4294768023 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module
fsdmgr.dll at address 0x03C90000-0x03CB3000 (RW data at
0x01FCF000-0x01FCF810)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\FSDMGR.DLL'
4294768047 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FS: Registering file
system
StoreMgr, index 3, flags 0x00000001
4294768048 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: InitSharedHeap: 44000000
10000 c
4294768048 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: InitSharedHeap: return
44000060
4294768076 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module
relfsd.dll at address 0x03E60000-0x03E69000 (RW data at
0x01FEB000-0x01FEBADC)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_DEBUG\RELFSD.DLL'
4294768112 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: RELFSD!DllMain:
DLL_PROCESS_ATTACH
4294768132 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: ReleaseFSD: FSD_MountDisk

Thanks,

Joe W.






.

Relevant Pages

  • Re: Debug and RELFSD
    ... debug on our evaluation platform, ... This is brand new hardware, If I build a release nk.bin and put it on ... The Kernel Debugger connection has been established. ...
    (microsoft.public.windowsce.platbuilder)
  • code hangs after loading hd.dll
    ... dlls to be loaded. ... The Kernel Debugger connection has been established (Target CPU is ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debug and RELFSD
    ... not when relfsd itself loads. ... debug on our evaluation platform, ... The Kernel Debugger connection has been established. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debug and RELFSD
    ... debug on our evaluation platform, ... The Kernel Debugger connection has been established (Target CPU is X86). ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debug and RELFSD
    ... and debug on our evaluation platform (same processor, ... PID:0 TID:0 Looking for rom chain ... The Kernel Debugger connection has been established (Target CPU is ...
    (microsoft.public.windowsce.platbuilder)