Changes between Version 1 and Version 2 of Debugging/GdbSerialMonitor


Ignore:
Timestamp:
Jan 5, 2016, 8:17:10 PM (4 years ago)
Author:
Ralph Holmes
Comment:

Fix broken link(s).

Legend:

Unmodified
Added
Removed
Modified
  • Debugging/GdbSerialMonitor

    v1 v2  
    33= GDB Serial Monitors =
    44
     5The GNU debugger GDB allows you to debug your RTEMS application, BSP, and RTEMS itself. GDB can be found here:
    56
    6 The GNU debugger GDB allows you to debug your RTEMS application, BSP, and RTEMS itself. GDB can be found here -
    7 [[BR]]
    8   http://sources.redhat.com/gdb/
     7  https://www.sourceware.org/gdb/
    98
    10 GDB comes with a remote protocol. You can find detail about the protocol in the GDB documentation -
    11 [[BR]]
    12   http://sources.redhat.com/gdb/current/onlinedocs/gdb_18.html#SEC149
     9GDB comes with a remote protocol. You can find detail about the protocol in the GDB documentation:
     10
     11  https://sourceware.org/gdb/current/onlinedocs/gdb/Remote-Protocol.html#Remote-Protocol
    1312
    1413The remote protocol can be used over a serial port to a target or using TCP/IP. Here we look at a GDB serial monitor that lets you connect to your target.
     14
    1515= Thread-Aware GDB Stubs =
    1616
    17 
    18 The RTEMS source tree includes thread aware GDB serial stubs for some of the supported CPU families.  The shared portion of this code is located in http://www.rtems.com/viewvc/rtems/c/src/lib/libbsp/shared/gdbstub.  Code adapting the shared portion to particular CPU families is available for the following processors:
     17The RTEMS source tree includes thread aware GDB serial stubs for some of the supported CPU families.  The shared portion of this code is located in [source:rtems/c/src/lib/libbsp/shared/gdbstub].  Code adapting the shared portion to particular CPU families is available for the following processors:
    1918
    2019 *  i386
     
    2322 *  MIPS
    2423
    25 If you adapt this support to another processor family, please submit that work.  If you are interested in working on TCP/IP based gdb stubs, there is a set of those available at SLAC.
     24If you adapt this support to another processor family, please submit that work.  If you are interested in working on TCP/IP based GDB stubs, there is a set of those available at SLAC.
     25
    2626= Non-Thread Aware GDB Stubs =
    27 
    2827
    2928If an RTEMS thread-aware GDB stub is not available for your processor, GDB itself supplies a few working stubs for the following processors:
     
    3433 * sparc
    3534
    36 Check GDB for newer stubs. You may find other on the net, for example http://sourceforge.net/projects/gdbstubs/.
     35Check GDB for newer stubs. You may find others on the net, for example http://sourceforge.net/projects/gdbstubs/.
    3736
    3837Copy the GDB stub into your BSP and get it to compile. You need to write a ''putDebugChar'' and ''getDebugChar'' routine that interfaces to your target's serial port. You also need to provide a ''exceptionHandler'' routine and the m68k stub require you declare the ''exceptionHook'' variable. The GDB documentation provides the detail needed to achieve this.