Re: Unable to connect remote tools

Tech-Archive recommends: Fix windows errors by optimizing your registry

Is there anything left to load? You've included virtually nothing in the
OS, so I wouldn't expect to see much activity. Does the target control
window work (the Windows CE > prompt)?

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Dilip" <Dilip@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2A8654CA-A9F7-4272-8362-5429152EB1B3@xxxxxxxxxxxxxxxx
Hi Dean Ramsier,

I added one component to my OS Design. It is shell.exe. Upon adding that,
some more are added as dependencies. Totally the included components are
SYSGEN_FULL_CRT, SYSGEN_STRSAFE, SYSGEN_TOOLHELP, SYSGEN_NKMAPFILE,
SYSGEN_MSGQUEUE, SYSGEN_SHELL, SYSGEN_SERDEV, SYSGEN_NKCOMPR,
SYSGEN_STOREMGR. With this new OS configuration please see the below PB
log

---------------------------------------------------------------------------------------
PB Debugger The Kernel Debugger is waiting to connect with target.
PB Debugger The Kernel Debugger has been disconnected successfully.
PB Debugger The Kernel Debugger is waiting to connect with target.
0 PID:0 TID:0 Configuration Registers.
0 PID:0 TID:0 FUNC_MUX_CTRL_0 = 0x80c0000.
0 PID:0 TID:0 FUNC_MUX_CTRL_1 = 0x0.
0 PID:0 TID:0 FUNC_MUX_CTRL_2 = 0x0.
0 PID:0 TID:0 COMP_MODE_CTRL_0 = 0xeaef.
0 PID:0 TID:0 FUNC_MUX_CTRL_3 = 0x4004003f.
0 PID:0 TID:0 FUNC_MUX_CTRL_4 = 0xc0000000.
0 PID:0 TID:0 FUNC_MUX_CTRL_5 = 0xc0000000.
0 PID:0 TID:0 FUNC_MUX_CTRL_6 = 0xb.
0 PID:0 TID:0 FUNC_MUX_CTRL_7 = 0x1000.
0 PID:0 TID:0 FUNC_MUX_CTRL_8 = 0x1200.
0 PID:0 TID:0 FUNC_MUX_CTRL_9 = 0x201008.
0 PID:0 TID:0 FUNC_MUX_CTRL_A = 0x1b0c0006.
0 PID:0 TID:0 FUNC_MUX_CTRL_B = 0x3.
0 PID:0 TID:0 FUNC_MUX_CTRL_C = 0x9000000.
0 PID:0 TID:0 FUNC_MUX_CTRL_D = 0x18.
0 PID:0 TID:0 PULL_DWN_CTRL_0 = 0xbffff000.
0 PID:0 TID:0 PULL_DWN_CTRL_1 = 0x88188fce.
0 PID:0 TID:0 PULL_DWN_CTRL_2 = 0xaf6093e6.
0 PID:0 TID:0 PULL_DWN_CTRL_3 = 0xffff823.
0 PID:0 TID:0 GATE_INH_CTRL_0 = 0x0.
PB Debugger Kernel debugger connected.
0 PID:0 TID:0 CONF_REV = 0x10.
0 PID:0 TID:0 VOLTAGE_CTRL_0 = 0x1fe7.
0 PID:0 TID:0 USB_TRANSCEIVER_CT = 0x186.
0 PID:0 TID:0 LDO_PWRDN_CNTRL = 0x0.
0 PID:0 TID:0 TEST_DBG_CTRL_0 = 0xc0003.
0 PID:0 TID:0 MOD_CONF_CTRL_0 = 0xe0060000.
0 PID:0 TID:0 FUNC_MUX_CTRL_E = 0x0.
0 PID:0 TID:0 FUNC_MUX_CTRL_F = 0x0.
0 PID:0 TID:0 FUNC_MUX_CTRL_10 = 0x18000.
0 PID:0 TID:0 FUNC_MUX_CTRL_11 = 0x0.
0 PID:0 TID:0 FUNC_MUX_CTRL_12 = 0x0.
0 PID:0 TID:0 PULL_DWN_CTRL_4 = 0x0.
0 PID:0 TID:0 PU_PD_SEL_0 = 0x0.
0 PID:0 TID:0 PU_PD_SEL_1 = 0x47010.
0 PID:0 TID:0 PU_PD_SEL_2 = 0x50916400.
0 PID:0 TID:0 PU_PD_SEL_3 = 0x100.
0 PID:0 TID:0 PU_PD_SEL_4 = 0x0.
0 PID:0 TID:0 FUNC_MUX_DSP_DMA_A = 0xa418820.
0 PID:0 TID:0 FUNC_MUX_DSP_DMA_B = 0x16a4a0e6.
0 PID:0 TID:0 FUNC_MUX_DSP_DMA_C = 0x2307b9ac.
0 PID:0 TID:0 FUNC_MUX_DSP_DMA_D = 0x12.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_A = 0x40c2040.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_B = 0x9207185.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_C = 0xe34c2ca.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_D = 0x1349140f.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_E = 0x185d6554.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_F = 0x1d71b699.
0 PID:0 TID:0 FUNC_MUX_ARM_DMA_G = 0x1e.
0 PID:0 TID:0 MOD_CONF_CTRL_1 = 0x6840000.
0 PID:0 TID:0 SECCTRL = 0x0.
0 PID:0 TID:0 CONF_STATUS = 0x0.
0 PID:0 TID:0 RESET_CONTROL = 0x7f.
0 PID:0 TID:0 CONF_1611_CTRL = 0x2.
0 PID:0 TID:0 usCLKRST_CKCTL = 0x150a.
0 PID:0 TID:0 usCLKRST_CKOUT1 = 0x15.
0 PID:0 TID:0 usCLKRST_CKOUT2 = 0x0.
0 PID:0 TID:0 usCLKRST_EWUPCT = 0xff.
0 PID:0 TID:0 usCLKRST_IDLECT1 = 0x0.
0 PID:0 TID:0 usCLKRST_IDLECT2 = 0x3ff.
0 PID:0 TID:0 usCLKRST_IDLECT3 = 0x15.
0 PID:0 TID:0 usCLKRST_RSTCT1 = 0x0.
0 PID:0 TID:0 usCLKRST_RSTCT2 = 0x1.
0 PID:0 TID:0 usCLKRST_SYSST = 0x1000.
0 PID:0 TID:0 g_pCLKM_DPLL1CTL_REG = 0x2793.
0 PID:0 TID:0 ulIMIF_PRIORITY = 0x0.
0 PID:0 TID:0 ulEMIF_SLOW_PRIORITY = 0x0.
0 PID:0 TID:0 ulEMIF_FAST_PRIORITY = 0xf00.
0 PID:0 TID:0 ulEMIF_CONFIG_REG = 0x1f.
0 PID:0 TID:0 ulEMIF_SLOW_CS0_CONFIG = 0x2130b0.
0 PID:0 TID:0 ulEMIF_SLOW_CS1_CONFIG = 0x81808cc3.
0 PID:0 TID:0 ulEMIF_SLOW_CS2_CONFIG = 0x4a1f2.
0 PID:0 TID:0 ulEMIF_SLOW_CS3_CONFIG = 0x88013141.
0 PID:0 TID:0 ulEMIF_FAST_SD_CONFIG = 0x1200f6.
0 PID:0 TID:0 ulEMIF_FAST_SD_MRS = 0x37.
0 PID:0 TID:0 ulEMIF_TIMEOUT1 = 0x0.
0 PID:0 TID:0 ulEMIF_TIMEOUT2 = 0x0.
0 PID:0 TID:0 ulEMIF_TIMEOUT3 = 0x0.
0 PID:0 TID:0 ulEMIF_ENDIANISM = 0x0.
0 PID:0 TID:0 ulEMIFF_CONFIG_REG2 = 0xb.
0 PID:0 TID:0 ulEMIF_CONFIGDYNAMICWAITSTATE = 0xc0.
0 PID:0 TID:0 ulEMIF_SLOW_ABORT_ADDR = 0x0.
0 PID:0 TID:0 ulEMIF_SLOW_ABORT_TYPE = 0x0.
0 PID:0 TID:0 ulEMIF_SLOW_ABORT_TIMEOUT = 0xff.
0 PID:0 TID:0 ulEMIF_SLOW_CS0_CONFIG_ADVANCED = 0x0.
0 PID:0 TID:0 ulEMIF_SLOW_CS1_CONFIG_ADVANCED = 0x22.
0 PID:0 TID:0 ulEMIF_SLOW_CS2_CONFIG_ADVANCED = 0x44.
0 PID:0 TID:0 ulEMIF_SLOW_CS3_CONFIG_ADVANCED = 0x2.
0 PID:0 TID:0 ulEMIF_FAST_DLL_WRT_CONTRL = 0x6.
0 PID:0 TID:0 ulEMIF_FAST_DLL_WRT_STATUS = 0x4a00.
0 PID:0 TID:0 ulEMIF_FAST_SD_MRS_NEW = 0x33.
0 PID:0 TID:0 ulEMIF_FAST_SD_MRS0 = 0x0.
0 PID:0 TID:0 ulEMIF_FAST_SD_MRS1 = 0x0.
0 PID:0 TID:0 ulSDRAM_OPERATION = 0x7.
0 PID:0 TID:0 ulSDRAM_MANUAL_CMD_REG = 0x2.
0 PID:0 TID:0 ulEMIF_FAST_DYN_TIMEOUT1 = 0x0.
0 PID:0 TID:0 ulEMIF_FAST_DYN_TIMEOUT2 = 0x0.
0 PID:0 TID:0 ulEMIF_FAST_DYN_TIMEOUT3 = 0x0.
0 PID:0 TID:0 ulEMIF_FAST_ABORT_ADDR = 0x10000000.
0 PID:0 TID:0 ulEMIF_FAST_ABORT_TYPE = 0x0.
0 PID:0 TID:0 >>> GPIO Registers @ PA=0xFFFBE400, VA=0xABFBE400:
0 PID:0 TID:0 ulREVISON = 0x10
0 PID:0 TID:0 ulSYSCONFIG = 0x0
0 PID:0 TID:0 ulSYSSTATUS = 0x1
0 PID:0 TID:0 ulIRQSTATUS1 = 0x0
0 PID:0 TID:0 ulIRQENABLE1 = 0x0
0 PID:0 TID:0 ulIRQSTATUS2 = 0x0
0 PID:0 TID:0 ulIRQENABLE2 = 0x0
0 PID:0 TID:0 ulWAKEUPENABLE = 0x0
0 PID:0 TID:0 ulDATAIN = 0xE20
0 PID:0 TID:0 ulDATAOUT = 0x0
0 PID:0 TID:0 ulDIRECTION = 0xFFFF
0 PID:0 TID:0 ulEDGE_CTRL1 = 0x302
0 PID:0 TID:0 ulEDGE_CTRL2 = 0x0
0 PID:0 TID:0 ulCLEAR_IRQENABLE1 = 0x0
0 PID:0 TID:0 ulCLEAR_IRQENABLE2 = 0x0
0 PID:0 TID:0 ulCLEAR_WAKEUPENA = 0x0
0 PID:0 TID:0 ulCLEAR_DATAOUT = 0x0
0 PID:0 TID:0 ulSET_IRQENABLE1 = 0x0
0 PID:0 TID:0 ulSET_IRQENABLE2 = 0x0
0 PID:0 TID:0 ulSET_WAKEUPENA = 0x0
0 PID:0 TID:0 ulSET_DATAOUT = 0x0
0 PID:0 TID:0 >>> MPUIO Registers @ PA=0xFFFB5000, VA=0xABFB5000:
0 PID:0 TID:0 usARMIO_INPUT_LATCH = 0x81C
0 PID:0 TID:0 usARMIO_OUTPUT_REG = 0x0
0 PID:0 TID:0 usARMIO_IO_CONTROL = 0xFFFF
0 PID:0 TID:0 usARMIO_KBD_ROW_LATCH = 0xFFF0
0 PID:0 TID:0 usARMIO_KBD_COL_LATCH = 0xFF00
0 PID:0 TID:0 usARMIO_EVENT_MODE = 0xFFE0
0 PID:0 TID:0 usARMIO_IO_INT_EDGE = 0x0
0 PID:0 TID:0 usARMIO_KBD_INT_STAT = 0xFFFE
0 PID:0 TID:0 usARMIO_KBD_INT_MASK = 0xFFFE
0 PID:0 TID:0 usARMIO_IO_INT_MASK = 0xFFFF
0 PID:0 TID:0 usARMIO_IO_DEB_TIME = 0xFE00
0 PID:0 TID:0 usARMIO_IO_DEB_LATCH = 0x800
0 PID:0 TID:0 Setting up softlog at 0x854fc000 for 0x800 entries
0 PID:0 TID:0 Booting Windows CE version 6.00 for (ARM)
0 PID:0 TID:0 &pTOC = 843dbc1c, pTOC = 84313c24, pTOC->ulRamFree =
843e0000, MemForPT = 00001000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 4375, Secondary pages: 0,
Filesystem pages = 2187
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: 843e2000, extension: 00003000, length:
01117000
0 PID:0 TID:0 NKStartup done, starting up kernel.
1 PID:0 TID:0 Windows CE KernelInit
9 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first = c0010000,
last = c0280000
10 PID:400002 TID:2 g_pprcNK == 0x843d9aa0
25 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0001c000
26 PID:400002 TID:410002 Initializing Memory Mapped File Support
27 PID:400002 TID:410002 Scheduling the first thread.
28 PID:400002 TID:410002 Detecting VFP...
28 PID:400002 TID:410002 VFP Not Found!
29 PID:400002 TID:410002 LoaderInit: Initialing loader
45 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0001c000
47 PID:400002 TID:410002 Updated eptr->e32_vsize to = 000a2000
88 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00019000
148 PID:400002 TID:410002 Heap Statistics at 0xC0153A58
186 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader pool
187 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File pool
299 PID:400002 TID:410002 OSAXST0: Platform Name = OMAP5912OSK
387 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'kd.dll'
(0x854E187C) at address 0xC0010000-0xC0045000 in Process 'NK.EXE'
(0x843D9AA0)
431 PID:400002 TID:410002 KD: Starting kernel debugger software probe
(KdStub) - KD API version 22
433 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'NK.EXE'
(0x843D9AA0) at address 0x84040000-0x8405C000 in Process 'NK.EXE'
(0x843D9AA0)
PB Debugger The Kernel Debugger connection has been established (Target
CPU
is ARM).
PB Debugger Target name: CE Device
PB Debugger Probe name: KdStub
PB Debugger Binary Image should be loaded at 0x84040000 / Data relocated
at
0x84396000
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\NK.EXE'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\COREDLL.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\KITL.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\KERNEL.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\OALIOCTL.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\HD.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\OSAXST0.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\OSAXST1.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\K.COREDLL.DLL'
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\KD.DLL'
437 PID:400002 TID:410002 HD: Immediate debugger module load
notifications ACTIVE (slower boot - non real-time).
473 PID:400002 TID:410002 INFO:OALLogSetZones:
dpCurSettings.ulZoneMask:
0x3f
478 PID:400002 TID:410002 Message Queue support initialized,
g_hMsgQHeap
= d0040750
508 PID:400002 TID:630002 OSAXST1: >>> Loading Module 'filesys.dll'
(0x854B84C8) at address 0xC0180000-0xC01E7000 in Process 'NK.EXE'
(0x843D9AA0)
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\FILESYS.DLL'
537 PID:400002 TID:630002 OSAXST1: >>> Loading Module 'fsdmgr.dll'
(0x854B8600) at address 0xC0230000-0xC0275000 in Process 'NK.EXE'
(0x843D9AA0)
PB Debugger Loaded symbols for
'G:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\FSDMGR.DLL'
540 PID:400002 TID:630002 FSDMGR!DllMain: DLL_PROCESS_ATTACH
542 PID:400002 TID:680002 CertMod.dll not found, using old OEM Trust
Model
555 PID:400002 TID:680002 FileSystem Starting - starting with clean
file
system
555 PID:400002 TID:680002 +OALIoCtlHalInitRTC
556 PID:400002 TID:680002 InitializeRTC+
556 PID:400002 TID:680002 +OALIntrRequestSysIntr(1, 0xd00df848,
0x00000008)
556 PID:400002 TID:680002 OALIntrRequestSysIntr: Count 0x1 IRQ_NUM 0x39
557 PID:400002 TID:680002 -OALIntrRequestSysIntr(sysIntr = 34)
557 PID:400002 TID:680002 InitializeRTC: SYS_INTR 34, IRQ D
557 PID:400002 TID:680002 InitializeRTC:0, 01/01/2006 at 12:00:00
557 PID:400002 TID:680002 +RTCSetRealTime 0xD00DFB08
558 PID:400002 TID:680002 -RTCSetRealTime
563 PID:400002 TID:680002 FSDMGR!STOREMGR_Initialize
566 PID:400002 TID:680002 FSDMGR!InitializeStoreAPI
567 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolumeName:
Registered "StoreMgr" at index 2
568 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume:
Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1)
------------------------------------------------------------------------------------

The PB stopped loading the modules after the file system is initialized.

What could be the reason for this ?

regards,
Dilip.


"Dean Ramsier" wrote:

Well, for starters the Remote Tools have to run code on the target. Most
of
those tools are going to require support from OS components that you
haven't
included in your OS design.

Unfortunately I don't know what the list of dependencies is for each
tool.
But most of them require the C++ Exception handling support for starters.
You're also likely to need a filesystem...

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Dilip" <Dilip@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F3C1476-3A7F-42D1-A181-1325FE8CBCB3@xxxxxxxxxxxxxxxx
Hi,

I developed KITL for a board in WinCE 6.0. I'm unable to connect the
remote
tools on PB with the kitl. But, all the messages printed using
"KitlDebugOutputString" in the code are appearing on PB debug output.
I'm
using Kitl in interrupt mode .

I created the project in the SMALL FOOT PRINT configuration. Except the
compression componenet I did not add any new component in the
catalogue.

For analyzation please see the log below:

Log on Debug serial port:

DeviceId................. OMAP
pArgs->flags............. 0x9

pArgs->devLoc.IfcType.... 0

pArgs->devLoc.LogicalLoc. 0x4800000

pArgs->devLoc.PhysicalLoc 0x0

pArgs->devLoc.Pin........ 0

pArgs->ip4address........ 1

pDevice->Name............ s

pDevice->ifcType......... 0

pDevice->id.............. 0x4800000

pDevice->resource........ 0

pDevice->type............ 2

pDevice->pDriver......... 0x84279000

+SMCInit

SMC Ethernet card detected at I/O base 0xA2800000

SMC Ethernet Address: 00:0E:99:02:80:66

SMC config reg val: 000032B1
SMC Reset complete2

-SMCInit

KITL: *** Device Name OMAP ***

-OALIntrRequestSysIntr(sysIntr = 16)
KITL: using sysintr 0x10

VBridge:: built on [Sep 6 2006] time [19:25:01]

VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes

Tx buffer [0xA42AFC00] to [0xA42B3C00].

Rx buffer [0xA42B3C20] to [0xA42B7C20].

VBridge:: NK add MAC: [0-E-99-2-80-66]

Connecting to Desktop

Connecting to Desktop .. resending

KITL: Connected host IP: 1 Port: 2824

KeyIndex 0 = -1
KeyIndex 1 = -1
KeyIndex 2 = -1
KeyIndex 3 = -1
KeyIndex 4 = -1
KeyIndex 5 = -4194305
KeyIndex 6 = -4194305
KeyIndex 7 = -1
+KITLRegisterDfltClient, service:0
+KITLRegisterDfltClient, service:1
Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service PPSH
ProcessAdminMsg: Receive Config message for service DBGMSG
!Received config for unrecognized service KDBG
ProcessAdminMsg: Receive Config message for service PPSH
ProcessAdminMsg: Receive Config message for service DBGMSG
!Received config for unrecognized service KDBG
+KITLRegisterDfltClient, service:2
ProcessAdminMsg: Receive Config message for service KDBG
ProcessAdminMsg: Receive Config message for service KDBG
KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KdpDeleteBreakpoint: Invalid handle

KITL: Leaving polling mode... 0x8429F940
KITL Checking client registrations
+RegisterClientPart2: Id 0x00000000
KITL Timer thread started, (hTh: 0x00520002, pTh: 0x85EF1CE4)
Closing Handle of Timer Thread
-RegisterClientPart2 returns 1
+RegisterClientPart2: Id 0x00000001
-RegisterClientPart2 returns 1
KITL Creating IST
KITL Interrupt thread started (hTh: 0x005A0002, pTh: 0x85ECC51C), using
SYSINTR 16
Enabling adapter ints...
+IOCTL_HAL_POST_INIT Done

Log on the PB:
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 7238, Secondary pages:
0,
Filesystem pages = 3619
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: 842c2000, extension: 00004000, length:
01c46000
0 PID:0 TID:0 NKStartup done, starting up kernel.
1 PID:0 TID:0 Windows CE KernelInit
13 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first =
c0010000,
last = c0160000
14 PID:400002 TID:2 g_pprcNK == 0x842b9aa0
15 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0001c000
16 PID:400002 TID:410002 Scheduling the first thread.
16 PID:400002 TID:410002 Detecting VFP...
17 PID:400002 TID:410002 VFP Not Found!
18 PID:400002 TID:410002 LoaderInit: Initialing loader
19 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0001c000
20 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0008d000
21 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00019000
71 PID:400002 TID:410002 Heap Statistics at 0xC012F8F8
76 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader pool
78 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File pool
103 PID:400002 TID:410002 OSAXST0: Platform Name = OMAP5912OSK
137 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'kd.dll'
(0x85EF1744) at address 0xC0010000-0xC0045000 in Process 'NK.EXE'
(0x842B9AA0)
139 PID:400002 TID:410002 KD: Starting kernel debugger software
probe
(KdStub) - KD API version 22
140 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'NK.EXE'
(0x842B9AA0) at address 0x84040000-0x8405C000 in Process 'NK.EXE'
(0x842B9AA0)
PB Debugger The Kernel Debugger connection has been established (Target
CPU
is ARM).
PB Debugger Target name: CE Device
PB Debugger Probe name: KdStub
PB Debugger Binary Image should be loaded at 0x84040000 / Data
relocated
at
0x84276000
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\NK.EXE'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\COREDLL.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\KITL.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\KERNEL.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\OALIOCTL.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\HD.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\OSAXST0.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\OSAXST1.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\K.COREDLL.DLL'
PB Debugger Loaded symbols for
'D:\WINCE600\OSDESIGNS\SFP_OMAP5912\SFP_OMAP5912\RELDIR\OMAP5912_OSK_ARMV4I_DEBUG\KD.DLL'
144 PID:400002 TID:410002 HD: Immediate debugger module load
notifications ACTIVE (slower boot - non real-time).
180 PID:400002 TID:410002 INFO:OALLogSetZones:
dpCurSettings.ulZoneMask:
0x3f
182 PID:400002 TID:620002 Filesys doesn't exist, no app started


Do, I need to include any other OS components to get it working ?

Could anybody tell the reason why I'm unable to connect the remote
tools
to
the target ?

Dilip





.

Relevant Pages

  • Cannot boot image when including USB Storage Class Driver
    ... PCI Device Configurations present)... ... Receive Config message for service DBGMSG ... PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS ... 4294767495 PID:400002 TID:680002 FSVOL: Opening existing volume ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Unable to connect remote tools
    ... PB Debugger The Kernel Debugger has been disconnected successfully. ... Old or invalid version stamp in kernel structures - starting clean! ... Receive Config message for service DBGMSG ...
    (microsoft.public.windowsce.embedded)
  • Unable to connect remote tools
    ... I developed KITL for a board in WinCE 6.0. ... Receive Config message for service DBGMSG ... KdpDeleteBreakpoint: Invalid handle ...
    (microsoft.public.windowsce.embedded)
  • Re: Unable to connect remote tools
    ... Receive Config message for service DBGMSG ... KdpDeleteBreakpoint: Invalid handle ...
    (microsoft.public.windowsce.embedded)
  • Re: {newbie} Help getting an NK.BIN image running on a x86 DOS machine
    ... It looks to me like you are using hive-based registry. ... I made some good progress today getting my x86-based "CEPC" target to ... PB Debugger The Kernel Debugger is waiting to connect with target. ...
    (microsoft.public.windowsce.embedded)