Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Code Block
[cpo@rdcds204]$ powerpc-rtems-gdb -nw pgpforward
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-redhat-linux-gnu --target=powerpc-rtems4.7"...
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
download_entry ()
    at ../../../../../../../../RTEMS/c/src/lib/libbsp/powerpc/rce405/dlentry/dlentry.S:14
14      ../../../../../../../../RTEMS/c/src/lib/libbsp/powerpc/rce405/dlentry/dlentry.S: No such file or directory.
        in ../../../../../../../../RTEMS/c/src/lib/libbsp/powerpc/rce405/dlentry/dlentry.S
warning: no shared library support for this OS / ABI
Current language:  auto; currently asm
(gdb) break init_executive
Breakpoint 1 at 0x24f0
(gdb) c
Continuing.
Can't send signals to this remote system.  SIGUSR2 not sent.

Breakpoint 1, 0x000024f0 in init_executive ()

Debug RCE applications with the Multi-Function-Display

Each RCE has 2 8-character LED multi-function-display (MFD) chips on the front-panel (4 MFDs per board, since there are 2 RCEs per board). The first of these two is controlled by powerPC software in the FX60: it displays the value stored in a DCR register. The second is controlled by firmware in the 4 FX20 FPGAs (2 characters per FX20).

Debug RCE applications with the console

The default console application is usually stored as image 0 in the configuration flash and can be loaded by setting the front panel boot selector to 0 and by resetting the RC element. The console application provides three servers, each one with different functionality and each one accessed through a different UNIX application:

...

From a machine connected on the base interface subnet of the RCE with IP address/name <hostname> <hostname> type:

Code Block
console_host -h <hostname>

The application above will show a command line prompt if the connection to <hostname> <hostname> is successful. Currently the following commands may be issued through this command line:

...

From a machine connected on the base interface subnet of the RCE with IP address/name <hostname> <hostname> type:

Code Block
debug_host -h <hostname> -f <exename>

Where <exename> <exename> is the file name, in the local UNIX file system, of the application which is currently running in the RCE and that is being debugged. The application above will show a command line prompt if the connection to <hostname> <hostname> is successful. Currently the following commands may be issued through this command line:

Code Block
gettime: printPrint the current time in the RC elementRCE
settime: setSet the current time in the RCE to be the same as in the UNIX host
getexceptions: printPrint the exceptions (if any) recorded by the RCE since the last reset/power-on
clearexceptions: clearClear all the recorded exceptions
getmessageslog: printPrint all messages recorded by the RCE since the last reset/power-on
clearmessagesclearlog: clearClear all the recorded messages
getcontextcontext: showsShows a stack dump of the different threads running in the RCE
dumpstatsstats: showsShows a dump of thelocal and RCE network statistics
resetstats: Reset local and RCE network statistics
burst <npackets> <nbytes>: sendsSends <npackets> UDP ethernet packets from the UNIX host to the RCE
burstrequest <npackets> <nbytes>: sendsSends <npackets> raw ethernet packets from the RCE to the UNIX host
echorequest <npackets> <nbytes>: sendsSends <npackets> UDP packets from the UNIX host to the RCE,
                                 the RCE echoes back each packet it receives

Note that the <nbytes> <nbytes> arguments in the commands above indicates the maximum number of bytes contained in the packet payload. The actual number of payload bytes is a flat distribution random number between 0 and <nbytes> <nbytes>.

upload

From a machine connected on the base interface subnet of the RCE with IP address/name <hostname> <hostname> type:

Code Block
upload_elf_host -h <hostname> -i <imgnum> -f <filename>

Where <filename> <filename> is the file name, in the local UNIX file system, of the ELF file which is to be stored at image number <imgnum> <imgnum> in the RCE configuration flash memory. Note the image number must be between 1 and 15. Image 0 is a protected "safe" image that can only be programmed via the JTAG cable. You can then use the bootcfg command described in the console command line above to make the newly flashed image boot-able from the RCE.