Lines Matching refs:to

7 port. This permits GDB to single step through the kernel, set breakpoints and
9 permits the NMI interrupt button or serial port events to jump the kernel into
19 PDK there is no externally accessible serial port and the serial port to
32 and copy the configuration that you wish to use to .config. Then reconfigure
37       Set this to "Y". This causes all C and Assembly files to be compiled
38       to include debugging information.
42       Set this to "Y". This causes the GDB stub to be compiled into the
47       Set this to "Y" if you want the GDB stub to activate as soon as possible
48       and wait for GDB to connect. This allows you to start tracing right from
53       Set this to "Y" if you wish to be able to use "console=gdb0" on the
54       command line. That tells the kernel to pass system console messages to
56       debugging the serial drivers that'd otherwise be used to pass console
57       messages to the outside world.
59 Then build as usual, download to the board and execute. Note that if
60 "Immediate activation" was selected, then the kernel will wait for GDB to
61 attach. If not, then the kernel will boot immediately and GDB will have to
62 interrupt it or wait for an exception to occur before doing anything with
70 Set the serial port on the computer that's going to run GDB to the appropriate
71 baud rate. Assuming the board's debug port is connected to ttyS0/COM1 on the
89 	welcome to change it and/or distribute copies of it under certain conditions.
90 	Type "show copying" to see the conditions.
95 Attach to the board like this:
110 The kernel can be interrupted whilst it is running, causing a jump back to the
113   (*) Pressing Ctrl-C in GDB. This will cause GDB to try and interrupt the
114       kernel by sending an RS232 BREAK over the serial line to the GDB
116       to the debugger.
125       and DBAR registers to assist debugging.