Next: Writing a test case, Previous: Adding a new board, Up: Extending DejaGnu [Contents][Index]
The following fields are in the board_info
array. These are
set by the set_board_info
procedure (or add_board_info
procedure for appending to lists). Both procedures take a field name
and a value for the field (or is added to the field), respectively.
Some common board info fields are shown below.
Field | Example value | Description |
compiler | [find_gcc] | The path to the compiler to use. |
cflags | -mca | Compilation flags for the compiler. |
ldflags | [libgloss_link_flags] [newlib_link_flags] | Linking flags for the compiler. |
ldscript | -Wl,-Tidt.ld | The linker script to use when cross compiling. |
libs | -lgcc | Any additional libraries to link in. |
shell_prompt | cygmon> | The command prompt of the remote shell. |
hex_startaddr | 0xa0020000 | The Starting address as a string. |
start_addr | 0xa0008000 | The starting address as a value. |
startaddr | a0020000 | |
exit_statuses_bad | 1 | Whether there is an accurate exit status. |
reboot_delay | 10 | The delay between power off and power on. |
unreliable | 1 | Whether communication with the board is unreliable. |
sim | [find_sim] | The path to the simulator to use. |
objcopy | $tempfil | The path to the objcopy program. |
support_libs | ${prefix_dir}/i386-coff/ | Support libraries needed for cross compiling. |
addl_link_flags | -N | Additional link flags, rarely used. |
remotedir | /tmp/runtest.[pid] | Directory on the remote target in which executables are downloaded and executed. |
These fields are used by the GCC and GDB tests, and are mostly only useful to somewhat trying to debug a new board file for one of these tools. Many of these are used only by a few testcases, and their purpose is esoteric. These are listed with sample values as a guide to better guessing if you need to change any of these.
Board Info Fields For GCC & GDB
Field | Sample Value | Description |
strip | $tempfile | Strip the executable of symbols. |
gdb_load_offset | "0x40050000" | |
gdb_protocol | "remote" | The GDB debugging protocol to use. |
gdb_sect_offset | "0x41000000"; | |
gdb_stub_ldscript | "-Wl,-Teva-stub.ld" | The linker script to use with a GDB stub. |
gdb,noargs | 1 | Whether the target can take command line arguments. |
gdb,nosignals | 1 | Whether there are signals on the target. |
gdb,short_int | 1 | |
gdb,target_sim_options | "-sparclite" | Special options to pass to the simulator. |
gdb,timeout | 540 | Timeout value to use for remote communication. |
gdb_init_command | "set mipsfpu none" | A single command to send to GDB before the program being debugged is started. |
gdb_init_commands | "print/x \$fsr = 0x0" | Same as gdb_init_command, except that this is a list, more commands can be added. |
gdb_load_offset | "0x12020000" | |
gdb_opts | "–command gdbinit" | |
gdb_prompt | "\\(gdb960\\)" | The prompt GDB is using. |
gdb_run_command | "jump start" | |
gdb_stub_offset | "0x12010000" | |
use_gdb_stub | 1 | Whether to use a GDB stub. |
wrap_m68k_aout | 1 | |
gcc,no_label_values | 1 | |
gcc,no_trampolines | 1 | |
gcc,no_varargs | 1 | |
gcc,stack_size | 16384 | Stack size to use with some GCC testcases. |
ieee_multilib_flags | "-mieee" | |
is_simulator | 1 | |
needs_status_wrapper | 1 | |
no_double | 1 | |
no_long_long | 1 | |
noargs | 1 | |
target_install | {sh-hms} |
Next: Writing a test case, Previous: Adding a new board, Up: Extending DejaGnu [Contents][Index]