downloading problem

Hi

Iam working in a hardware kit which has PXA 270 processor. I couldnot
download the image(NK.BIN) to the RAM of the hardware kit. Iam getting
a debug message as "TAPI NOT READY". A closer look through the
platform's release directory caused me to know that the EBOOT.bin files
where missing. What files are actually needed for downloading?. How to
overcome with this problem? What all components i should add to my
platform?


Thanks,
Meribha

Voidcoder
Fri Mar 10 03:56:46 CST 2006

Where are you getting the "TAPI NOT READY" message?
If you don't have EBOOT, how do you try to upload the
NK.BIN?

Normally EBOOT.NB0 (not EBOOT.BIN) must be placed
to your boot flash, DOC or whatever you have there.
NK.BIN is the actual OS image that has to be uploaded
to device by the help of EBOOT running on the device side.

What BSP are you using to build the OS image? Does the
KIT vendor provide a BSP for it?


<meribha.sherline@gmail.com> wrote in message news:1141964239.679686.82220@j52g2000cwj.googlegroups.com...
> Hi
>
> Iam working in a hardware kit which has PXA 270 processor. I couldnot
> download the image(NK.BIN) to the RAM of the hardware kit. Iam getting
> a debug message as "TAPI NOT READY". A closer look through the
> platform's release directory caused me to know that the EBOOT.bin files
> where missing. What files are actually needed for downloading?. How to
> overcome with this problem? What all components i should add to my
> platform?
>
>
> Thanks,
> Meribha
>

meribha
Tue Mar 14 02:32:04 CST 2006

Hi

Thanks for your reply.

While downloading image from platform builder installed system to the
kit through ethernet cable, i get the TAPI NOT READY message in the
platform builder debug messages window.

We got the BSP downloaded from web. It seems the BSP does not have
adequate files required for downloading(eboot files). Can you suggest
me how to proceed with creating eboot files. Since my Processor is
PXA270, can i adapt the eboot files of intel pxa27x BSP. I have
platform builder wince5.0.

Thanks a lot
Meribha

Voidcoder
Tue Mar 14 03:18:46 CST 2006

You don't really need eboot since it is already running on
your device. This may be eboot or any other bootloader,
it doesn't really matter at this stage. As far as you can attach
from the Platform Builder and upload the image to the device,
lets assume eboot is already running on device.

The problem with "TAPI NOT READY" is a different issue.
Probably some required components are missing in your
current OS design, or some required registry entries are not
set in registry, etc. Do not forget the BSP is not the same thing
as OS design, it is just a board hardware specific code. Even
you got a BSP from the H/W vendor, you still need to configure
properly your OS design, add required features, etc.

Is the "TAPI NOT READY" the only message you can
see in the debug trace window? What module it comes from?
AsyncMac?


<meribha.sherline@gmail.com> wrote in message news:1142325124.073501.317960@p10g2000cwp.googlegroups.com...
> Hi
>
> Thanks for your reply.
>
> While downloading image from platform builder installed system to the
> kit through ethernet cable, i get the TAPI NOT READY message in the
> platform builder debug messages window.
>
> We got the BSP downloaded from web. It seems the BSP does not have
> adequate files required for downloading(eboot files). Can you suggest
> me how to proceed with creating eboot files. Since my Processor is
> PXA270, can i adapt the eboot files of intel pxa27x BSP. I have
> platform builder wince5.0.
>
> Thanks a lot
> Meribha
>

meribha
Tue Mar 14 06:16:17 CST 2006

Hi

Thank u so much.

Here is the debug trace, which we got when downloading the image from
platform builder.

The Kernel Debugger is waiting to connect with target.
0 PID:0 TID:0 OEM Init: Initializing the Registry library...
0 PID:0 TID:0 OEM Init: Registry library initialized.
0 PID:0 TID:0 Sp=ffffc7cc
258 PID:3fdf002 TID:3fdf266 Starting kernel debugger software probe
(KdStub) - KD API version 18
262 PID:3fdf002 TID:3fdf266 >>> Loading module NK.EXE at address
0x80100000-0x80152000 (RW data at 0x827F6000-0x8285815F)
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is
ARM).
Target name: CE Device
Probe name: KdStub
Binary Image should be loaded at 0x80100000 / Data relocated at
0x827f6000
Loaded
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\NK.EXE',
no matching symbolic information found.
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\KD.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\OSAXST1.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\OSAXST0.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\HD.DLL'
265 PID:3fdf002 TID:3fdf266 >>> Loading module coredll.dll at
address 0x03F00000-0x03FF1000 (RW data at 0x01FFE000-0x01FFF7A5)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\COREDLL.DLL'
267 PID:a3fccc1e TID:a3fccbfa >>> Loading module coredll.dll at
address 0x03F00000-0x03FF1000 (RW data at 0x01FFE000-0x01FFF7A5)
269 PID:a3fccc1e TID:a3fccbfa >>> Loading module filesys.exe at
address 0x04010000-0x0409F000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\FILESYS.EXE'
271 PID:a3fccc1e TID:a3fccbfa CertMod.dll not found, using old OEM
Trust Model
273 PID:a3fccc1e TID:a3fccbfa FileSystem Starting - starting with
clean file system
275 PID:a3fccc1e TID:a3fccbfa FS: initializing ROM/RAM file system
276 PID:a3fccc1e TID:a3fccbfa FS: Registering file system ROM,
index 2, flags 0x00000031
276 PID:a3fccc1e TID:a3fccbfa FS: Mount complete (ROM, index 2,
flags 0x00000031)
279 PID:a3fccc1e TID:a3fccbfa OEMIoControl: Unsupported Code
0x101008c - device 0x0101 func 35
317 PID:a3fccc1e TID:a3fccbfa Succeeded on CheckFile
318 PID:a3fccc1e TID:a3fccbfa RestoreFile(0x63fb6c06) called
fDelete = TRUE
1463 PID:a3fccc1e TID:a3fccbfa >>> Loading module fsdmgr.dll at
address 0x03C20000-0x03C4E000 (RW data at 0x01FD1000-0x01FD1808)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\FSDMGR.DLL'
1465 PID:a3fccc1e TID:a3fccbfa FS: Registering file system StoreMgr,
index 3, flags 0x00000001
1467 PID:a3fccc1e TID:a3fccbfa InitSharedHeap: 44000000 10000 c
1468 PID:a3fccc1e TID:a3fccbfa InitSharedHeap: return 44000060
1472 PID:a3fccc1e TID:a3fccbfa >>> Loading module relfsd.dll at
address 0x03DE0000-0x03DEB000 (RW data at 0x01FE9000-0x01FE9ADC)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\RELFSD.DLL'
1477 PID:a3fccc1e TID:a3fccbfa FS: Registering file system Release,
index 4, flags 0x00000000
1477 PID:a3fccc1e TID:a3fccbfa Mounted ReleaseFSD volume '\Release'
1484 PID:a3fccc1e TID:a3fccbfa size of 'dbglist.txt' = 00000000
1486 PID:a3fccc1e TID:a3fccbfa FS: Mount complete (Release, index 4,
flags 0x00000000)
1487 PID:a3fccc1e TID:a3fccbfa FSREG: Unable to read value
"NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
1487 PID:a3fccc1e TID:a3fccbfa FSREG: Logging in default user.
1488 PID:a3fccc1e TID:a3fccbfa FSREG: Unable to read value
"DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
1488 PID:a3fccc1e TID:a3fccbfa SetCurrentUser: Logging out (nobody),
logging in default
1489 PID:a3fccc1e TID:a3fccbfa FS: Using default path "\profiles\"
1490 PID:a3fccc1e TID:a3fccbfa BuildPath: profiles
1491 PID:a3fccc1e TID:a3fccbfa BuildPath: profiles\default
1492 PID:a3fccc1e TID:a3fccbfa SetCurrentUser: User hives not
supported -- using same registry for all users
1493 PID:a3fccc1e TID:a3fccbfa FS: Using default path "Windows\"
1494 PID:a3fccc1e TID:a3fccbfa OEMIoControl: Unsupported Code
0x10100d0 - device 0x0101 func 52
1495 PID:a3fccc1e TID:a3fccbfa OEMIoControl: Unsupported Code
0x10100f8 - device 0x0101 func 62
1518 PID:a3fccc1e TID:a3fccbfa FS: Using default path "Windows\"
1523 PID:a3fccc1e TID:a3fccbfa FSREG: Unable to read value "DBFlags"
under HKEY_LOCAL_MACHINE\init\BootVars
1664 PID:a3fccc1e TID:a3fccbfa
Initializing Database
1667 PID:a3fccc1e TID:a3fccbfa DB:Validation: Name already exists
DB_notify_events
1668 PID:a3fccc1e TID:a3fccbfa DB:CeCreateDatabase failed
1670 PID:a3fccc1e TID:a3fccbfa Filesystem initialized!
1671 PID:a3fccc1e TID:a3fccbfa FILESYS: Waiting for kernel to be
ready to launch apps
1673 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
SYSTEM/DevMgrApiSetReady
1674 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
SYSTEM/PowerManagerReady
1674 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
SYSTEM/GweApiSetReady
1675 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event ReleaseFSD
1676 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
system/events/notify/APIReady
1678 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
SYSTEM/ShellAPIReady
1679 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
SYSTEM/BatteryAPIsReady
1679 PID:a3fccc1e TID:a3fccbfa FILESYS: Launching apps
1680 PID:a3fccc1e TID:a3fccbfa FILESYS: Launching shell.exe
1683 PID:83faad46 TID:83faad22 >>> Loading module coredll.dll at
address 0x03F00000-0x03FF1000 (RW data at 0x01FFE000-0x01FFF7A5)
1685 PID:83faad46 TID:83faad22 >>> Loading module toolhelp.dll at
address 0x03DC0000-0x03DC6000 (RW data at 0x01FE5000-0x01FE5058)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\TOOLHELP.DLL'
1686 PID:83faad46 TID:83faad22 >>> Loading module shell.exe at
address 0x06010000-0x0602B000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\SHELL.EXE'
1704 PID:83faad46 TID:83faad22 InitSharedHeap: 44000000 0 c
1704 PID:83faad46 TID:83faad22 InitSharedHeap: return 44000060
1731 PID:83faad46 TID:83faad22 Shell: No extension DLLs found
1733 PID:a3fccc1e TID:a3fccbfa FILESYS: Launching device.exe
1735 PID:c3fa1442 TID:c3faaabe >>> Loading module coredll.dll at
address 0x03F00000-0x03FF1000 (RW data at 0x01FFE000-0x01FFF7A5)
1739 PID:c3fa1442 TID:c3faaabe >>> Loading module pm.dll at address
0x03E90000-0x03EB3000 (RW data at 0x01FF6000-0x01FF6708)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PM.DLL'
1741 PID:c3fa1442 TID:c3faaabe >>> Loading module devmgr.dll at
address 0x03EE0000-0x03EF9000 (RW data at 0x01FFC000-0x01FFC6B4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\DEVMGR.DLL'
1742 PID:c3fa1442 TID:c3faaabe >>> Loading module device.exe at
address 0x08010000-0x08014000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\DEVICE.EXE'
1754 PID:c3fa1442 TID:c3faaabe InitSharedHeap: 44000000 0 c
1754 PID:c3fa1442 TID:c3faaabe InitSharedHeap: return 44000060
1803 PID:c3fa1442 TID:c3faaabe *** DLL_PROCESS_ATTACH - Current
Process: 0x42, ID: 0xc3fa1442 ***
1834 PID:c3fa1442 TID:c3faaabe +InitDeviceFileSystems
1835 PID:a3fccc1e TID:c3faaabe FS: Registering file system $device,
index 5, flags 0x00000001
1836 PID:a3fccc1e TID:c3faaabe FS: Registering file system $bus,
index 6, flags 0x00000001
1836 PID:c3fa1442 TID:c3faaabe -InitDeviceFileSystems: status is 1
1838 PID:c3fa1442 TID:c3faaabe >>> Loading module ceddk.dll at
address 0x03BB0000-0x03BB9000 (RW data at 0x01FC9000-0x01FC90C4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\CEDDK.DLL'
1840 PID:c3fa1442 TID:c3faaabe Ceddk!CalibrateStallCounter: Enter
1841 PID:c3fa1442 TID:c3faaabe Ceddk!CalibrateStallCounter: Could
not find stall counter
1842 PID:c3fa1442 TID:c3faaabe Ceddk!BeginCalibration: min(3251)
max(3612)
1861 PID:c3fa1442 TID:c3faaabe Ceddk!BeginCalibration: Elapsed is
3497
1862 PID:c3fa1442 TID:c3faaabe Ceddk!BeginCalibration: Delay is 27
1866 PID:a3fccc1e TID:a3fccbfa FILESYS: SignalStarted loop = 2
1881 PID:c3fa1442 TID:c3faaabe DEVICE!DevloadInit
1881 PID:c3fa1442 TID:c3faaabe DEVICE!InitDevices: Root Key is
Drivers\BuiltIn.
1882 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2
1883 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2
1888 PID:c3fa1442 TID:c3faaabe >>> Loading module busenum.dll at
address 0x03EC0000-0x03ECA000 (RW data at 0x01FF8000-0x01FF8514)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\BUSENUM.DLL'
1960 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\WaveDev\BusPrefix) returned 2
1964 PID:c3fa1442 TID:c3faaabe >>> Loading module pxa27x_wavedev.dll
at address 0x01840000-0x0184C000
Loaded
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PXA27X_WAVEDEV.DLL',
no matching symbolic information found.
1972 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Serial1\BusPrefix) returned 2
1976 PID:c3fa1442 TID:c3faaabe >>> Loading module pxa27x_serial.dll
at address 0x018D0000-0x018DC000
Loaded
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PXA27X_SERIAL.DLL',
no matching symbolic information found.
2085 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Serial2\BusPrefix) returned 2
2196 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Serial3\BusPrefix) returned 2
2306 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Usbfn\BusPrefix) returned 2
2311 PID:c3fa1442 TID:c3faaabe >>> Loading module pxa27x_usbfn.dll
at address 0x01830000-0x01840000
Loaded
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PXA27X_USBFN.DLL',
no matching symbolic information found.
2321 PID:c3fa1442 TID:c3faaabe DEVFS_CreateFileW:
I_CreateDeviceHandle('BuiltInPhase1_0_19_0') failed for name type 'bus'
2322 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCCARD\Prefix) returned 2
2323 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCCARD\BusPrefix) returned 2
2326 PID:c3fa1442 TID:c3faaabe >>> Loading module pcc_serv.dll at
address 0x01870000-0x01893000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PCC_SERV.DLL'
2353 PID:c3fa1442 TID:c3faaabe CardBus.DLL DLL_PROCESS_ATTACH
2358 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Battery\BusPrefix) returned 2
2362 PID:c3fa1442 TID:c3faaabe >>> Loading module battdrvr.dll at
address 0x01810000-0x01819000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\BATTDRVR.DLL'
2391 PID:c3fa1442 TID:c3faaabe DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\NDIS\BusPrefix) returned 2
2396 PID:c3fa1442 TID:c3faaabe >>> Loading module cxport.dll at
address 0x03A70000-0x03A81000 (RW data at 0x01FB6000-0x01FB770C)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\CXPORT.DLL'
2398 PID:c3fa1442 TID:c3faaabe >>> Loading module ndis.dll at
address 0x03840000-0x038A2000 (RW data at 0x01F93000-0x01F941F4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\NDIS.DLL'
2422 PID:c3fa1442 TID:c3faaabe CXPORT:dllentry ProcessAttach
2423 PID:c3fa1442 TID:c3faaabe CXPORT:+GetRegSettings
2424 PID:c3fa1442 TID:c3faaabe CXPORT:-GetRegSettings
2425 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(16),
limit 20000 bytes
2426 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(32),
limit 20000 bytes
2426 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(48),
limit 20000 bytes
2427 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(64),
limit 20000 bytes
2427 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(96),
limit 20000 bytes
2428 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(128),
limit 20000 bytes
2428 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(256),
limit 20000 bytes
2428 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(356),
limit 20000 bytes
2429 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(476),
limit 20000 bytes
2429 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(512),
limit 20000 bytes
2430 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(1024),
limit 20000 bytes
2430 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(1600),
limit 20000 bytes
2431 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(2048),
limit 20000 bytes
2431 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(4096),
limit 20000 bytes
2432 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(8192),
limit 20000 bytes
2432 PID:c3fa1442 TID:c3faaabe CXPORT:InitBlockPool - Pool(-1),
limit 20000 bytes
2467 PID:c3fa1442 TID:c3faaabe NDIS: RebindAdaptersOnResume = 0
2467 PID:c3fa1442 TID:c3faaabe NDIS: PcmciaNeedsMapToScrap = 0
2474 PID:c3fa1442 TID:c3faaabe >>> Loading module irsir.dll at
address 0x03E70000-0x03E82000 (RW data at 0x01FF4000-0x01FF4660)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\IRSIR.DLL'
2497 PID:c3fa1442 TID:c3faaabe ==>NdisInitializeWrapper
2498 PID:c3fa1442 TID:c3faaabe <==NdisInitializeWrapper
2498 PID:c3fa1442 TID:c3faaabe ==>NdisMRegisterMiniport:
NdisWrapperHandle 0003D6F0
2499 PID:c3fa1442 TID:c3faaabe ==>ndisRegisterMiniportDriver:
NdisWrapperHandle 0003D6F0
2500 PID:c3fa1442 TID:c3faaabe <==ndisRegisterMiniportDriver:
MiniBlock 0003D760
2500 PID:c3fa1442 TID:c3faaabe NdisMRegisterMiniport: MiniBlock
0003D760
2501 PID:c3fa1442 TID:c3faaabe <==NdisMRegisterMiniport: MiniBlock
0003D760, Status 0
2502 PID:c3fa1442 TID:c3faaabe
2505 PID:c3fa1442 TID:c3faaabe ndisMInitializeAdapter: Miniport
0003D960,
2510 PID:c3fa1442 TID:c3faaabe ==>ndisQueueMiniportOnDriver:
Miniport 0003D960, MiniBlock 0003D760
2511 PID:c3fa1442 TID:c3faaabe <==ndisQueueMiniportOnDriver:
Miniport 0003D960, MiniBlock 0003D760, rc 1
2514 PID:c3fa1442 TID:c3faaabe ==>NdisMSetAttributesEx: Miniport
0003D960
2521 PID:c3fa1442 TID:c3faaabe >>> Loading module vmini.dll at
address 0x03700000-0x0370B000 (RW data at 0x01F7B000-0x01F7B670)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\VMINI.DLL'
2545 PID:c3fa1442 TID:c3faaabe ==>NdisInitializeWrapper
2546 PID:c3fa1442 TID:c3faaabe <==NdisInitializeWrapper
2546 PID:c3fa1442 TID:c3faaabe ==>NdisMRegisterMiniport:
NdisWrapperHandle 00037480
2547 PID:c3fa1442 TID:c3faaabe ==>ndisRegisterMiniportDriver:
NdisWrapperHandle 00037480
2548 PID:c3fa1442 TID:c3faaabe <==ndisRegisterMiniportDriver:
MiniBlock 0003B580
2548 PID:c3fa1442 TID:c3faaabe NdisMRegisterMiniport: MiniBlock
0003B580
2549 PID:c3fa1442 TID:c3faaabe <==NdisMRegisterMiniport: MiniBlock
0003B580, Status 0
2550 PID:c3fa1442 TID:c3faaabe
2551 PID:c3fa1442 TID:c3faaabe ndisMInitializeAdapter: Miniport
0003E060,
2556 PID:c3fa1442 TID:c3faaabe ==>ndisQueueMiniportOnDriver:
Miniport 0003E060, MiniBlock 0003B580
2557 PID:c3fa1442 TID:c3faaabe <==ndisQueueMiniportOnDriver:
Miniport 0003E060, MiniBlock 0003B580, rc 1
2558 PID:c3fa1442 TID:c3faaabe ==>NdisMSetAttributesEx: Miniport
0003E060
2559 PID:c3fa1442 TID:c3faaabe VMini:: RX thread priority set to:
[131]
2561 PID:c3fa1442 TID:c3faaabe NDIS: Adapter VMINI1 - NOT using
OPTIMIZED RX handler
2566 PID:c3fa1442 TID:c3faaabe >>> Loading module asyncmac.dll at
address 0x03AD0000-0x03AE0000 (RW data at 0x01FBB000-0x01FBB988)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\ASYNCMAC.DLL'
2590 PID:c3fa1442 TID:c3faaabe ==>NdisInitializeWrapper
2591 PID:c3fa1442 TID:c3faaabe <==NdisInitializeWrapper
2591 PID:c3fa1442 TID:c3faaabe ==>NdisMRegisterMiniport:
NdisWrapperHandle 0003E980
2592 PID:c3fa1442 TID:c3faaabe ==>ndisRegisterMiniportDriver:
NdisWrapperHandle 0003E980
2593 PID:c3fa1442 TID:c3faaabe <==ndisRegisterMiniportDriver:
MiniBlock 0003E9F0
2593 PID:c3fa1442 TID:c3faaabe NdisMRegisterMiniport: MiniBlock
0003E9F0
2594 PID:c3fa1442 TID:c3faaabe <==NdisMRegisterMiniport: MiniBlock
0003E9F0, Status 0
2595 PID:c3fa1442 TID:c3faaabe
2596 PID:c3fa1442 TID:c3faaabe ndisMInitializeAdapter: Miniport
0003EC08,
2601 PID:c3fa1442 TID:c3faaabe ==>ndisQueueMiniportOnDriver:
Miniport 0003EC08, MiniBlock 0003E9F0
2602 PID:c3fa1442 TID:c3faaabe <==ndisQueueMiniportOnDriver:
Miniport 0003EC08, MiniBlock 0003E9F0, rc 1
2604 PID:c3fa1442 TID:c3faaabe ==>NdisMSetAttributesEx: Miniport
0003EC08
2605 PID:c3fa1442 TID:c3faaabe ASYNCMAC:MpQueryInfo: OID
0x10116/Unknown OID not supported
2606 PID:c3fa1442 TID:c3faaabe ASYNCMAC:MpQueryInfo: OID
0xFD010100/Unknown OID not supported
2613 PID:c3fa1442 TID:c3faaabe >>> Loading module ws2.dll at address
0x03A10000-0x03A24000 (RW data at 0x01FAE000-0x01FAEB24)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\WS2.DLL'
2614 PID:c3fa1442 TID:c3faaabe >>> Loading module winsock.dll at
address 0x03A30000-0x03A36000 (RW data at 0x01FB0000-0x01FB008C)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\WINSOCK.DLL'
2615 PID:c3fa1442 TID:c3faaabe >>> Loading module pptp.dll at
address 0x03A90000-0x03ACA000 (RW data at 0x01FB9000-0x01FB9A0C)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PPTP.DLL'
2662 PID:c3fa1442 TID:c3faaabe ==>NdisInitializeWrapper
2663 PID:c3fa1442 TID:c3faaabe <==NdisInitializeWrapper
2663 PID:c3fa1442 TID:c3faaabe ==>NdisMRegisterMiniport:
NdisWrapperHandle 0003F530
2664 PID:c3fa1442 TID:c3faaabe ==>ndisRegisterMiniportDriver:
NdisWrapperHandle 0003F530
2665 PID:c3fa1442 TID:c3faaabe <==ndisRegisterMiniportDriver:
MiniBlock 0003F5A0
2665 PID:c3fa1442 TID:c3faaabe NdisMRegisterMiniport: MiniBlock
0003F5A0
2666 PID:c3fa1442 TID:c3faaabe <==NdisMRegisterMiniport: MiniBlock
0003F5A0, Status 0
2666 PID:c3fa1442 TID:c3faaabe
2668 PID:c3fa1442 TID:c3faaabe ndisMInitializeAdapter: Miniport
0003F7A0,
2673 PID:c3fa1442 TID:c3faaabe ==>ndisQueueMiniportOnDriver:
Miniport 0003F7A0, MiniBlock 0003F5A0
2674 PID:c3fa1442 TID:c3faaabe <==ndisQueueMiniportOnDriver:
Miniport 0003F7A0, MiniBlock 0003F5A0, rc 1
2676 PID:c3fa1442 TID:c3faaabe ==>NdisMSetAttributesEx: Miniport
0003F7A0
2677 PID:c3fa1442 TID:c3faaabe -MiniportQueryInformation C00000BB
2684 PID:c3fa1442 TID:c3faaabe >>> Loading module pxa27x_dm9000.dll
at address 0x017A0000-0x017A8000
Loaded
'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\PXA27X_DM9000.DLL',
no matching symbolic information found.
2686 PID:c3fa1442 TID:c3faaabe ==>NdisInitializeWrapper
2686 PID:c3fa1442 TID:c3faaabe <==NdisInitializeWrapper
2687 PID:c3fa1442 TID:c3faaabe ==>NdisMRegisterMiniport:
NdisWrapperHandle 00040270
2688 PID:c3fa1442 TID:c3faaabe ==>ndisRegisterMiniportDriver:
NdisWrapperHandle 00040270
2688 PID:c3fa1442 TID:c3faaabe <==ndisRegisterMiniportDriver:
MiniBlock 000402E0
2689 PID:c3fa1442 TID:c3faaabe NdisMRegisterMiniport: MiniBlock
000402E0
2690 PID:c3fa1442 TID:c3faaabe <==NdisMRegisterMiniport: MiniBlock
000402E0, Status 0
2691 PID:c3fa1442 TID:c3faaabe
2692 PID:c3fa1442 TID:c3faaabe ndisMInitializeAdapter: Miniport
00043518,
2697 PID:c3fa1442 TID:c3faaabe ==>ndisQueueMiniportOnDriver:
Miniport 00043518, MiniBlock 000402E0
2698 PID:c3fa1442 TID:c3faaabe <==ndisQueueMiniportOnDriver:
Miniport 00043518, MiniBlock 000402E0, rc 1
2700 PID:c3fa1442 TID:c3faaabe ==>NdisMSetAttributesEx: Miniport
00043518
2702 PID:c3fa1442 TID:c3faaabe ***NDIS*** (a, 534)
3605 PID:c3fa1442 TID:a3f08fd2 AM: Tapi not ready yet... Checking
again in 1 second
Thanks
Meribha

Voidcoder
Tue Mar 14 06:38:30 CST 2006

Make sure you have included the following features
to your current OS design:

- Telephony API (TAPI 2.0)
- Telephony API (TAPI 2.0)->Unimodem support


<meribha.sherline@gmail.com> wrote in message news:1142338577.748188.202470@z34g2000cwc.googlegroups.com...
> Hi
>
> Thank u so much.
>
> Here is the debug trace, which we got when downloading the image from
> platform builder.
>
> The Kernel Debugger is waiting to connect with target.
> 0 PID:0 TID:0 OEM Init: Initializing the Registry library...
> 0 PID:0 TID:0 OEM Init: Registry library initialized.
> 0 PID:0 TID:0 Sp=ffffc7cc
> 258 PID:3fdf002 TID:3fdf266 Starting kernel debugger software probe
> (KdStub) - KD API version 18
> 262 PID:3fdf002 TID:3fdf266 >>> Loading module NK.EXE at address
> 0x80100000-0x80152000 (RW data at 0x827F6000-0x8285815F)
> Kernel debugger connected.
> The Kernel Debugger connection has been established (Target CPU is
> ARM).
> Target name: CE Device
> Probe name: KdStub
> Binary Image should be loaded at 0x80100000 / Data relocated at
> 0x827f6000
> Loaded
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\NK.EXE',
> no matching symbolic information found.
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\KD.DLL'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\OSAXST1.DLL'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\OSAXST0.DLL'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\HD.DLL'
> 265 PID:3fdf002 TID:3fdf266 >>> Loading module coredll.dll at
> address 0x03F00000-0x03FF1000 (RW data at 0x01FFE000-0x01FFF7A5)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\COREDLL.DLL'
> 267 PID:a3fccc1e TID:a3fccbfa >>> Loading module coredll.dll at
> address 0x03F00000-0x03FF1000 (RW data at 0x01FFE000-0x01FFF7A5)
> 269 PID:a3fccc1e TID:a3fccbfa >>> Loading module filesys.exe at
> address 0x04010000-0x0409F000
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\FILESYS.EXE'
> 271 PID:a3fccc1e TID:a3fccbfa CertMod.dll not found, using old OEM
> Trust Model
> 273 PID:a3fccc1e TID:a3fccbfa FileSystem Starting - starting with
> clean file system
> 275 PID:a3fccc1e TID:a3fccbfa FS: initializing ROM/RAM file system
> 276 PID:a3fccc1e TID:a3fccbfa FS: Registering file system ROM,
> index 2, flags 0x00000031
> 276 PID:a3fccc1e TID:a3fccbfa FS: Mount complete (ROM, index 2,
> flags 0x00000031)
> 279 PID:a3fccc1e TID:a3fccbfa OEMIoControl: Unsupported Code
> 0x101008c - device 0x0101 func 35
> 317 PID:a3fccc1e TID:a3fccbfa Succeeded on CheckFile
> 318 PID:a3fccc1e TID:a3fccbfa RestoreFile(0x63fb6c06) called
> fDelete = TRUE
> 1463 PID:a3fccc1e TID:a3fccbfa >>> Loading module fsdmgr.dll at
> address 0x03C20000-0x03C4E000 (RW data at 0x01FD1000-0x01FD1808)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\FSDMGR.DLL'
> 1465 PID:a3fccc1e TID:a3fccbfa FS: Registering file system StoreMgr,
> index 3, flags 0x00000001
> 1467 PID:a3fccc1e TID:a3fccbfa InitSharedHeap: 44000000 10000 c
> 1468 PID:a3fccc1e TID:a3fccbfa InitSharedHeap: return 44000060
> 1472 PID:a3fccc1e TID:a3fccbfa >>> Loading module relfsd.dll at
> address 0x03DE0000-0x03DEB000 (RW data at 0x01FE9000-0x01FE9ADC)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\COLIBRI\RELDIR\COLIBRI_ARMV4I_DEBUG\RELFSD.DLL'
> 1477 PID:a3fccc1e TID:a3fccbfa FS: Registering file system Release,
> index 4, flags 0x00000000
> 1477 PID:a3fccc1e TID:a3fccbfa Mounted ReleaseFSD volume '\Release'
> 1484 PID:a3fccc1e TID:a3fccbfa size of 'dbglist.txt' = 00000000
> 1486 PID:a3fccc1e TID:a3fccbfa FS: Mount complete (Release, index 4,
> flags 0x00000000)
> 1487 PID:a3fccc1e TID:a3fccbfa FSREG: Unable to read value
> "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
> 1487 PID:a3fccc1e TID:a3fccbfa FSREG: Logging in default user.
> 1488 PID:a3fccc1e TID:a3fccbfa FSREG: Unable to read value
> "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
> 1488 PID:a3fccc1e TID:a3fccbfa SetCurrentUser: Logging out (nobody),
> logging in default
> 1489 PID:a3fccc1e TID:a3fccbfa FS: Using default path "\profiles\"
> 1490 PID:a3fccc1e TID:a3fccbfa BuildPath: profiles
> 1491 PID:a3fccc1e TID:a3fccbfa BuildPath: profiles\default
> 1492 PID:a3fccc1e TID:a3fccbfa SetCurrentUser: User hives not
> supported -- using same registry for all users
> 1493 PID:a3fccc1e TID:a3fccbfa FS: Using default path "Windows\"
> 1494 PID:a3fccc1e TID:a3fccbfa OEMIoControl: Unsupported Code
> 0x10100d0 - device 0x0101 func 52
> 1495 PID:a3fccc1e TID:a3fccbfa OEMIoControl: Unsupported Code
> 0x10100f8 - device 0x0101 func 62
> 1518 PID:a3fccc1e TID:a3fccbfa FS: Using default path "Windows\"
> 1523 PID:a3fccc1e TID:a3fccbfa FSREG: Unable to read value "DBFlags"
> under HKEY_LOCAL_MACHINE\init\BootVars
> 1664 PID:a3fccc1e TID:a3fccbfa
> Initializing Database
> 1667 PID:a3fccc1e TID:a3fccbfa DB:Validation: Name already exists
> DB_notify_events
> 1668 PID:a3fccc1e TID:a3fccbfa DB:CeCreateDatabase failed
> 1670 PID:a3fccc1e TID:a3fccbfa Filesystem initialized!
> 1671 PID:a3fccc1e TID:a3fccbfa FILESYS: Waiting for kernel to be
> ready to launch apps
> 1673 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
> SYSTEM/DevMgrApiSetReady
> 1674 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event
> SYSTEM/PowerManagerReady
> 1674 PID:a3fccc1e TID:a3fccbfa FS: Creating signal event