Kernel debug using serial cable

Hello,

On a target running windows embedded 7-32 I ran (from CMD):

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200

Then I rebooted the target.

On the host PC I ran WinDbg and chose Kernel Debug and set baud rate, port.

Using HyperTerminal I can see that the line between the 2 PCs is OK.

When I tried to ‘break’ nothing happens. I failed to get the prompt.

On the Windbg I’m getting:

Opened \.\com1
Waiting to reconnect…

Can you help ?

Best regards,
Z.V

Have you installed debugger on target?

WDK 8.1: Use WDK Test Target Setup (a MSI)
WDK 7/SDK: Install, but select debugging tools only…

Good luck!

Thomas F. Divine

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, March 18, 2015 10:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Kernel debug using serial cable

Hello,

On a target running windows embedded 7-32 I ran (from CMD):

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200

Then I rebooted the target.

On the host PC I ran WinDbg and chose Kernel Debug and set baud rate, port.

Using HyperTerminal I can see that the line between the 2 PCs is OK.

When I tried to ‘break’ nothing happens. I failed to get the prompt.

On the Windbg I’m getting:

Opened \.\com1
Waiting to reconnect…

Can you help ?

Best regards,
Z.V


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Did you check this post?
http://www.osronline.com/cf.cfm?PageURL=showlists.cfm?list=NTDEV

  1. Maybe your cable is not good for windbg. Have you used it with other
    machine(s)?
  2. Try baudrate 19200 or 9600.

– pa

On 18-Mar-2015 16:38, veredz72@ wrote:

Hello,

On a target running windows embedded 7-32 I ran (from CMD):

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200

Then I rebooted the target.

On the host PC I ran WinDbg and chose Kernel Debug and set baud rate, port.

Using HyperTerminal I can see that the line between the 2 PCs is OK.

When I tried to ‘break’ nothing happens. I failed to get the prompt.

On the Windbg I’m getting:

Opened \.\com1
Waiting to reconnect…

Can you help ?

Best regards,
Z.V

Hi Thomas,

On the target I installed WinDbg.
But I still can not connect from the host to the target.

After the WinDbg installation on the host I ran again:

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200
reboot

Did not try yet Pavel’s solution to change baud rate to 9600.

On the target + host I ran Hyper Terminal both configured to 115200,8,n and
tried to send few characters from target to host.

It worked fine.

Best regards,
Z.V

-----Original Message-----
From: Thomas F. Divine
Sent: Wednesday, March 18, 2015 5:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Kernel debug using serial cable

Have you installed debugger on target?

WDK 8.1: Use WDK Test Target Setup (a MSI)
WDK 7/SDK: Install, but select debugging tools only…

Good luck!

Thomas F. Divine

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, March 18, 2015 10:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Kernel debug using serial cable

Hello,

On a target running windows embedded 7-32 I ran (from CMD):

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200

Then I rebooted the target.

On the host PC I ran WinDbg and chose Kernel Debug and set baud rate, port.

Using HyperTerminal I can see that the line between the 2 PCs is OK.

When I tried to ‘break’ nothing happens. I failed to get the prompt.

On the Windbg I’m getting:

Opened \.\com1
Waiting to reconnect…

Can you help ?

Best regards,
Z.V


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

It is a little picky.

IIRC the target serial port must be some specific chip. Hight check that…

Thomas

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Zvi Vered
Sent: Thursday, March 19, 2015 12:43 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Kernel debug using serial cable

Hi Thomas,

On the target I installed WinDbg.
But I still can not connect from the host to the target.

After the WinDbg installation on the host I ran again:

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200 reboot

Did not try yet Pavel’s solution to change baud rate to 9600.

On the target + host I ran Hyper Terminal both configured to 115200,8,n and
tried to send few characters from target to host.

It worked fine.

Best regards,
Z.V

-----Original Message-----
From: Thomas F. Divine
Sent: Wednesday, March 18, 2015 5:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Kernel debug using serial cable

Have you installed debugger on target?

WDK 8.1: Use WDK Test Target Setup (a MSI) WDK 7/SDK: Install, but select
debugging tools only…

Good luck!

Thomas F. Divine

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Wednesday, March 18, 2015 10:38 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Kernel debug using serial cable

Hello,

On a target running windows embedded 7-32 I ran (from CMD):

bcdedit /debug on
bcdedit /dbgsettings serial debugport:1 baudrate:115200

Then I rebooted the target.

On the host PC I ran WinDbg and chose Kernel Debug and set baud rate, port.

Using HyperTerminal I can see that the line between the 2 PCs is OK.

When I tried to ‘break’ nothing happens. I failed to get the prompt.

On the Windbg I’m getting:

Opened \.\com1
Waiting to reconnect…

Can you help ?

Best regards,
Z.V


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Hello,

I set the target (and host) to 9600 and tried it but results are the same.

Target is running Win7-64 embedded. Is it possible that the cause is in the image I built ?

Best regards,
Z.V

On 23-Mar-2015 04:45, xxxxx@gmail.com wrote:

I set the target (and host) to 9600 and tried it but results are the same.

Target is running Win7-64 embedded. Is it possible that the cause is in the image I built ?

Frankly… I haven’t dealt with Win.Embedded a lot.
How do you configure the kernel debugger there at build time? Is the com
port built-in (and visible in the BIOS) or some add-on device?
– pa

Pavel A. wrote:

On 23-Mar-2015 04:45, xxxxx@gmail.com wrote:
> I set the target (and host) to 9600 and tried it but results are the same.
>
> Target is running Win7-64 embedded. Is it possible that the cause is in the image I built ?
Frankly… I haven’t dealt with Win.Embedded a lot.
How do you configure the kernel debugger there at build time? Is the com
port built-in (and visible in the BIOS) or some add-on device?

Windows 7 Embedded is just Windows 7. The only difference is that you
have very fine-grained control over which components are included in the
system. The kernel (and hence kernel debugger) is the same.


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