Нужна помощь с DCWinCE serial windbg debugger

Running WinDbg from the Command Line

When you run WinDbg from the command line, you can use the following options:
windbg [-a] [-g] [-h] [-i] [-k [platform port speed]] [-l[text]]
[-m] [-p id [-e event]] [-s[pipe]] [-v] [-w name] [-y path]
[-z crashfile] [filename[.ext] [arguments]]

Syntax Explanation
-a Ignore all bad symbols (but still print warning message).
-g Go now; start executing the process.
-h Causes child processes to inherit access to WinDbg's handles.
-i Ignore workspace; like running without any registry data.
-k [platform port speed] Run as a kernel debugger with the specified options:
platform is the target machine type (i386, mips, alpha, sh)
Windows CE Note: the correct platform switch for SH3 devices is sh
port is the com port (com1 ... comn)
speed is the com port speed (9600, 19200, 57600, ...)
-l [text] Sets the window title for WinDbg.
-m Start WinDbg minimized.
-p id Attach to the process with the given id.
-e event Signal an event after process is attached. Used only for post-mortem debugging (AeDebug).
-s [pipe] Start a remote.exe server, using the named pipe.
-v Verbose option; WinDbg prints module load and unload messages.
-w name Load the named workspace.
-y path Search for symbols along the specified path. You can specify multiple paths by separating them with semicolons.
-z crashfile Debug the specified crash dump file.
filename[.ext] Program to debug or file to edit.
arguments Arguments to program being debugged.