| |||
| Home > Configuring debug hardware for GDB > rviload command syntax | |||
rviload enables you to load a given binary file onto the target board through a specified debug hardware unit.
rviload [options]... address:file [address:file]...
address:fileA raw binary file to
be loaded at the target memory address file in hexadecimal.address
DELAYAutoconfigure the scan chain and then wait the number
of seconds specified by .DELAY
Option synonym: -a DELAY
Check memory as it is being written.
Option synonym: -c
DEVNUMThe JTAG scan chain device number (default 1). Device 0 refers to the debug hardware unit, so you can only specify devices greater than 0.
Option synonym: -d DEVNUM
Display the command help.
Option synonym: -h
HOSTThe host IP address/name of the debug hardware unit.
Option synonym: -H HOST
The JTAG clock speed in Hz, 0==‘RTCK’ (default 10MHz).
Option synonym: -s
JUMPTOStart executing from this (hex) address after loading.
Option synonym: -j JUMPTO
MODEEnable debug communications in the particular MODE, and must be one of the following:
Raw DCC through client. Raw (unprocessed) data exactly as it exited the DCC register on the target, and is fed to the client.
Raw DCC through TCP/IP port range from 5000. Raw data fed to TCP/IP port in the port range specified.
Virtual Ethernet/TTY with tty channel through client.
Virtual Ethernet/TTY with tty channel through port range from 5000.
The DCC mode for rviload is specified by using a three-letter mode name such as VEP or VEC, whereas the DCC mode for rvigdbconfig is specified by a mode number such as 0, 1 or 2.
Option synonym: -m MODE
PAGEThe target memory page number.
Option synonym: -p PAGE
Do not print any messages.
Option synonym: -q
RULETarget rule code.
Option synonym: -r RULE
To use the rviload utility from a Cygwin bash or Red Hat Linux shell, enter:
$ rviload [option]... address:file [address:file]...
For example:
rviload --host=192.168.1.200 -s0 -j7300000 -mVEC -a0 7300000:C:\DEMOS\ Linux_RVI_DCC\vp-boot.bin