RVIvec command syntax

RVIvec enables you to make a virtual Ethernet connection to a device. RVIvec uses a passive connection that it can connect to the device at the same time as a debugger or other application, as long as both applications use an identical .rvc file. The virtual Ethernet connection is then maintained, as long as RVIvec is still running, even after the debugger that started the device executing has quit.


RVIvec [options]

--config RVCfile

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

Option synonym: -f RVCfile

--devnum device

The device to connect to. Default 1.

Option synonym: -d device


Display the command help.

Option synonym: -h

--jump address

Optional. Start processor from this (hex) address.


This means that a passive connection cannot be used, so this option prevents a connection while a debugger or other application is running.

Option synonym: -j address

--mode mode

As with rviload, mode can be either VEC or VEP. The default is VEC.

Option synonym: -m mode


Optional. This option means that RVIvec polls for any asynchronous messages that are returned from the debug hardware unit, and displays them to stdout.

Option synonym: -v


Typically, an image is first loaded onto a target (using rvd, rviload or rviahbload) and has started executing. For example:

RVIvec -f rvi.rvc
RVI virtual ethernet utility.Started channel 0x504344.Virtual ethernet enabled.Hit return to quit.

Show/hideSee also

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