Debugzones without KITL

Hi, I am using WinCE 4.2 with a PXA255 platform. I wouldlike to turn on
debugzones
but from the PC HKLM\Pegasus\Zones reg key. This is because i don't have a
KITL connection but have serial port output. Only problem is in the registry
key i
don't know which bits to set for my NDIS driver. How does one find out which
bits
correspond to whihc driver and then the zone within the driver?

Michel
Thu Jul 20 19:15:09 CDT 2006

Search the driver sources for dpCurSettings. The first element of that
struct will be the name you use to create a DWORD value in the Pegasus
key. The rest of that struct identifies the various debugzones from 0 to 16.

So to enable zones Hub and Pipe of the USB driver you'd create this key
in the dev pc's registry:

[HKEY_CURRENT_USER\Pegasus\Zones]
"USB HCD"=dword:88

Because the dpCurSettings is:

DBGPARAM dpCurSettings = {
TEXT("USB HCD"),
{
TEXT("Hcd"),
TEXT("Init"),
TEXT("Registers"),
TEXT("Hub"),
TEXT("Attach"),
TEXT("Descriptors"),
TEXT("Function"),
TEXT("Pipe"),
TEXT("Transfer"),
TEXT("QH"),
TEXT("TD"),
TEXT("CPhysMem"),
TEXT("Verbose"),
TEXT("Warning"),
TEXT("Error"),
TEXT("Unused")
},
DBG_INIT | DBG_ATTACH | DBG_WARNING | DBG_ERROR
};

And Hub is bit 3 and Pipe is bit 7 which makes 10001000 binary (88 hex).
As you can see, the default debugzones are Init, Attach, Warning and
Error all on.

If you want to turn *all* debug zones on, set the key like this:

[HKEY_CURRENT_USER\Pegasus\Zones]
"USB HCD"=dword:ffff

Do not set the dword value to anything bigger than ffff because it won't
work anymore (so ffffffff doesn't set any debug zones on).

Hope this helps.

Michel Verhagen, eMVP
Embedded Fusion
www.embeddedfusion.com
mverhagen at embeddedfusion dot com

GW wrote:
> Hi, I am using WinCE 4.2 with a PXA255 platform. I wouldlike to turn on
> debugzones
> but from the PC HKLM\Pegasus\Zones reg key. This is because i don't have a
> KITL connection but have serial port output. Only problem is in the registry
> key i
> don't know which bits to set for my NDIS driver. How does one find out which
> bits
> correspond to whihc driver and then the zone within the driver?
>
>

--
Michel Verhagen, eMVP
Embedded Fusion
www.embeddedfusion.com
mverhagen at embeddedfusion dot com

GW
Fri Jul 21 07:53:35 CDT 2006

Thanks Michel, one thing i have a headless device without KITL. Can this
work without
a KITL connection?


"Michel Verhagen (eMVP)" <mverhagen@nospam.embeddedfusion.com> wrote in
message news:OwmI7qFrGHA.2256@TK2MSFTNGP03.phx.gbl...
> Search the driver sources for dpCurSettings. The first element of that
> struct will be the name you use to create a DWORD value in the Pegasus
> key. The rest of that struct identifies the various debugzones from 0 to
> 16.
>
> So to enable zones Hub and Pipe of the USB driver you'd create this key in
> the dev pc's registry:
>
> [HKEY_CURRENT_USER\Pegasus\Zones]
> "USB HCD"=dword:88
>
> Because the dpCurSettings is:
>
> DBGPARAM dpCurSettings = {
> TEXT("USB HCD"),
> {
> TEXT("Hcd"),
> TEXT("Init"),
> TEXT("Registers"),
> TEXT("Hub"),
> TEXT("Attach"),
> TEXT("Descriptors"),
> TEXT("Function"),
> TEXT("Pipe"),
> TEXT("Transfer"),
> TEXT("QH"),
> TEXT("TD"),
> TEXT("CPhysMem"),
> TEXT("Verbose"),
> TEXT("Warning"),
> TEXT("Error"),
> TEXT("Unused")
> },
> DBG_INIT | DBG_ATTACH | DBG_WARNING | DBG_ERROR
> };
>
> And Hub is bit 3 and Pipe is bit 7 which makes 10001000 binary (88 hex).
> As you can see, the default debugzones are Init, Attach, Warning and Error
> all on.
>
> If you want to turn *all* debug zones on, set the key like this:
>
> [HKEY_CURRENT_USER\Pegasus\Zones]
> "USB HCD"=dword:ffff
>
> Do not set the dword value to anything bigger than ffff because it won't
> work anymore (so ffffffff doesn't set any debug zones on).
>
> Hope this helps.
>
> Michel Verhagen, eMVP
> Embedded Fusion
> www.embeddedfusion.com
> mverhagen at embeddedfusion dot com
>
> GW wrote:
>> Hi, I am using WinCE 4.2 with a PXA255 platform. I wouldlike to turn on
>> debugzones
>> but from the PC HKLM\Pegasus\Zones reg key. This is because i don't have
>> a
>> KITL connection but have serial port output. Only problem is in the
>> registry key i
>> don't know which bits to set for my NDIS driver. How does one find out
>> which bits
>> correspond to whihc driver and then the zone within the driver?
>
> --
> Michel Verhagen, eMVP
> Embedded Fusion
> www.embeddedfusion.com
> mverhagen at embeddedfusion dot com

AC
Sat Jul 22 09:25:21 CDT 2006

This is a multi-part message in MIME format.

------=_NextPart_000_000F_01C6ADAB.6E879530
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


> Can this work without a KITL connection?

http://msdn.microsoft.com/library/en-us/wcedebug5/html/wce51conSettingIni=
tialDebugZones.asp?frame=3Dtrue

see "Target device registry"

------=_NextPart_000_000F_01C6ADAB.6E879530
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>&gt; Can this&nbsp;work without =
a KITL=20
connection?<BR></FONT></DIV>
<DIV><A=20
href=3D"http://msdn.microsoft.com/library/en-us/wcedebug5/html/wce51conSe=
ttingInitialDebugZones.asp?frame=3Dtrue"><FONT=20
face=3D"Courier New"=20
size=3D2>http://msdn.microsoft.com/library/en-us/wcedebug5/html/wce51conS=
ettingInitialDebugZones.asp?frame=3Dtrue</FONT></A></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>see "Target device =
registry"</FONT></DIV>
<DIV><FONT face=3D"Courier New" =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000F_01C6ADAB.6E879530--