Serial port for WinDbg

I have an embedded PC (it’s actually a PC system on a VME board) which I
need to debug. This particular board has no 1394 port (and no way to
add a card). It has a USB port which nominally *should* support the USB
debug dongle, but I have been unable to get it to work (it seems to
partially connect during boot, but then loses the connection before
anything useful can be done).

It also has a bunch of serial ports built in. Several (there are 4)
show in Device Manager as “OEM Communications Port”, and are assigned to
COM4 - COM7. It appears that they use MF.SYS and some third-party
driver, so I’m assuming they will NOT work as the debug port.

This board also has another COM port (COM3), which shows in Device
Manager as “Intel(R) Active Management Technology - SOL (COM3)”. It
appears to be a PCI device, using I/O ports (as well as a memory range)
to control it. Is there any chance I will be able to convince Windows
to use this as the debug port?

After my experience with the USB debug port, I figured I would query the
collected wisdom of the group before spending even MORE time on this…

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________

“Michael Jones” wrote in message news:xxxxx@windbg…

(it seems to partially connect during boot, but then loses the connection
before anything useful can be done).

The ONE time I was forced to use USB debugging I had a similar experience.
However, when the hang occurred I did the following:

-> Try to break in.
-> Did It work?
–>Yes! Debug until it hangs again. Go back to beginning.
–>No! Unplug cable, plug back in. Go back to beginning.

Sometimes I would seriously do this loop 4-5 times only to debug for 30
seconds and start again. It was absolutely miserable, but I tracked the
issue down and plan on having the USB debug dongle encased in Lucite (or
Carbonite, if anyone knows a guy).

This board also has another COM port (COM3), which shows in Device Manager
as “Intel(R) Active Management Technology - SOL (COM3)”. It appears to be
a PCI device, using I/O ports (as well as a memory range) to control it.
Is there any chance I will be able to convince Windows to use this as the
debug port?

If you can get the device to look like a legacy COM port, then it might work
(conversation about add-in PCI serial ports found here:
http://www.osronline.com/showthread.cfm?link=127389)

-scott


Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Michael Jones” wrote in message news:xxxxx@windbg…

I have an embedded PC (it’s actually a PC system on a VME board) which I
need to debug. This particular board has no 1394 port (and no way to
add a card). It has a USB port which nominally *should* support the USB
debug dongle, but I have been unable to get it to work (it seems to
partially connect during boot, but then loses the connection before
anything useful can be done).

It also has a bunch of serial ports built in. Several (there are 4)
show in Device Manager as “OEM Communications Port”, and are assigned to
COM4 - COM7. It appears that they use MF.SYS and some third-party
driver, so I’m assuming they will NOT work as the debug port.

This board also has another COM port (COM3), which shows in Device
Manager as “Intel(R) Active Management Technology - SOL (COM3)”. It
appears to be a PCI device, using I/O ports (as well as a memory range)
to control it. Is there any chance I will be able to convince Windows
to use this as the debug port?

After my experience with the USB debug port, I figured I would query the
collected wisdom of the group before spending even MORE time on this…

TIA,

– mkj


//
// Michael K. Jones
// Stone Hill Consulting, LLC
// http://www.stonehill.com
//_______________________________________________