serial cable debugging not working with windbg

Hi,
As I was not successful in getting networking debugging to work, switched to serial cable mode. But I am facing challenges with this as well.

My target PC status: WIN 10;

  • Location of COM port ( as describe in Devicemanager ) => on PCI standard ISA bridge
  • Earlier my target PC was provisioned using WDK 10 ( for network debugging from VS2015)
  • on restart of the pc, WDKRemoteuser is logged in automatically
  • BCDEdit is configured with debug serial and same baud rate as Host PC.

Host PC: WIN7

  • VS 2015 installed; WDK 10 installed.
  • logged in as admin ; windbg launched as admin; COM port settings are proper.
  • COM port location => on INTEL(R)Q87 LPC COntroller -8C4E

**** Serial cable is tested with Hyper-terminal application on both TARGET-HOST exchanging data properly.

>>> WinDbg says that debuggee is connected. waiting …; while windbg is running, restarted the target pc many times, but still nothing works.

PLEASE HELP ME IN THIS REGARD.
!!! Feel very bad that still stuck in the infrastructure issues, and not able to proceed with Driver development.

srinivaskumar.r@in.bosch.com wrote:

My target PC status: WIN 10;

  • Location of COM port ( as describe in Devicemanager ) => on PCI standard ISA bridge
  • Earlier my target PC was provisioned using WDK 10 ( for network debugging from VS2015)
  • on restart of the pc, WDKRemoteuser is logged in automatically
  • BCDEdit is configured with debug serial and same baud rate as Host PC.

What COM port number? Remember that the kernel debugger can only use
genuine old-fashioned COM ports, COM1 through COM4, using the genuine
old-fashioned well-known I/O port and IRQ numbers. If you have a fancy
PCI serial adapter, the kernel debugger core doesn’t know how to drive it.

Host PC: WIN7

  • VS 2015 installed; WDK 10 installed.
  • logged in as admin ; windbg launched as admin; COM port settings are proper.
  • COM port location => on INTEL(R)Q87 LPC COntroller -8C4E

The host implementation is less critical. You can even use a
USB-to-serial adapter here, if necessary.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.