Unable to start VisualKernel debug session over COM port

Sysprogs forums Forums VisualKernel Unable to start VisualKernel debug session over COM port

This topic contains 1 reply, has 2 voices, and was last updated by  support 4 years, 7 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #6307

    mcmordie
    Participant

    Hi,

    I have an ARM target and am debugging from VisualKernel on a Windows 7 laptop with a x86 VM host for kernel compilation.  Symbols load correctly and verify as the correct version.  I am able to start kgdb on the serial console of the target using the following command:

    echo g > /proc/sysrq-trigger

    However, when I launch the debug session from VisualKernel, it times out waiting for the target-select remote :55145 command to complete.

    Is this target-select command right for a COM port debug session?  Do I guess right that you are redirecting from a TCP port to the COM1 that my device is attached to?  If so, is there a way to test that this is working?

    Any other thoughts on why the debug session won’t start?  I was able to do this with a trial version some months back– everything worked fine.

    I have “Kernel connection mode” = “Use a built-in Kernel Debugger (KGDB) via a COM port”.  Other settings for the com port on the linux and windows sides look good.  I have verified using the console that I get the starting KGDB message.

    Best,

    Dave

     

    #6318

    support
    Keymaster

    Please double-check the COM port settings in the Windows Device Manager and ensure that the speed and the parity settings match the settings on the Linux side.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.