RVIahbload command syntax

RVIahbload uses an access port that is bridged to the system bus, which might be Advanced High-performance Bus (AHB) or Advanced Extensible Interface (AXI). Although this direct route has speed improvements, there are additional compliations to consider. For example, loading is performed in the physical memory map.

You specify the files to load in the same way as for rviload, that is, by using -bin addr:binary file or you can specify ELF files which load to a fixed location (--elf file.elf). The debug unit to which you want to connect is specified by a .rvc file, and you cannot supply an address or hostname as in the case of rviload. When the file has downloaded, you can use the -jump option to start the target executing. For this to succeed, however, the device must support execution.


RVIahbload [options]

--bin address:file

Load binary image file at specified (hex) address.

Option synonym: -i address:file

--bus busnum

Override the detected AHB bus to use for the download.

Option synonym: -b busnum

--config RVCfile

Provides the full path of the .rvc config file to use.

Option synonym: -f RVCfile

--devnum device

The device to use for the download. Default 1.

Option synonym: -d device

--elf filename

Elf file to load. Cannot be supplied at same time as -i.

Option synonym: -e filename


Display the command help.

Option synonym: -h

--jump address

Start executing from this (hex) address after loading if supported by device.

Option synonym: -j address


The following are examples of how to use RVIahbload:

RVIahbdownload -f rvi.rvc -i 8000:myprog.bin -d3 -b1 -j 0x8000

This loads the binary file myprog.bin to address 0x8000 on device 3 using bus 1 and starts executing it.

RVIahbdownload --file rvi2.rvc --elf my.elf

This loads the ELF file my.elf to the target, selecting the AHB bus by default.

Show/hideSee also

Copyright © 2010-2011 ARM. All rights reserved.ARM DUI 0498D