Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| wiki:tower_networking_inc:devices:debugger [2025/08/20 14:45] – created poco | wiki:tower_networking_inc:devices:debugger [2025/08/20 14:49] (current) – poco |
|---|
| To see the list of debuggers currently accessible, use the <code>lstdbg</code> command. This will show a list of debuggers and their logical address. You can then see the list of devices that are accessible by the debugger using the \<code>scan</code> command; if the debugger address is <color orange>63168</color>, then input <code>scan devices using 63168</code>. The scan command shows a list of device that are accessible by the debugger and their corresponding network address. Using the <code>watch</code> command on the listed device addresses, detailed information about the device can then be seen on the debugger. For example, if the scanned device address is <color orange>41216</color>, then input <code>watch 41216 using 63168</code>. | To see the list of debuggers currently accessible, use the <code>lstdbg</code> command. This will show a list of debuggers and their logical address. You can then see the list of devices that are accessible by the debugger using the \<code>scan</code> command; if the debugger address is <color orange>63168</color>, then input <code>scan devices using 63168</code>. The scan command shows a list of device that are accessible by the debugger and their corresponding network address. Using the <code>watch</code> command on the listed device addresses, detailed information about the device can then be seen on the debugger. For example, if the scanned device address is <color orange>41216</color>, then input <code>watch 41216 using 63168</code>. |
| |
| It may be unwieldly to keep typing address of the debugger if you always debug from the same debugger. Use the <color green>always routine</color> command to set the default debugger to use. For example, given that the debugger address is <color orange>51727</color> and we always want to use that, input <code>always using 51727</code>. This allows you to then type any debugger related commands without the <code>using ...</code> part. This means that instead of typing <code>scan devices using 51727</code>, you would only need to type <code>scan devices\</code>. | It may be unwieldly to keep typing address of the debugger if you always debug from the same debugger. Use the <color green>always routine</color> command to set the default debugger to use. For example, given that the debugger address is <color orange>51727</color> and we always want to use that, input <code>always using 51727</code>. This allows you to then type any debugger related commands without the <code>using ...</code> part. This means that instead of typing <code>scan devices using 51727</code>, you would only need to type <code>scan devices</code>. |
| |
| |
| You can always refer to the <color green>netsh</color> guide for help. Always remember that the command <code>man</code> (short for manual) is a useful way to find out more about a command. To use the command, simply type \<code>man</code> or <code>man <name of program you want to find out></code> | You can always refer to the <color green>netsh</color> guide for help. Always remember that the command <code>man</code> (short for manual) is a useful way to find out more about a command. To use the command, simply type \<code>man</code> or <code>man <name of program you want to find out></code> |
