The
mvs-tools are some useful tools for the mvBlueLYNX, needed especially for the mvIMPACT library. The tools are installed by default if you received a mvBlueLYNX with mvIMPACT licenses. On the CD the mvs-tools
IPK package is placed in the
IPK feed folder. The tools are specified below.
With this bash script a application can be killed by entering the name of the application and not the PID.
Usage:
This are some profiling tools. They allows you to profile your application (see also:
Profiling).
This bash script helps you to set the image path system variable
VL_FILE_DIR needed for the
mvIMPACT samples and demos. For more details see
How to generate a mvIMPACT example.
This bash script helps you to set the library path system variable
LD_LIBRARY_PATH. It can be used for the mvIMPACT libraries if this are not installed on the mvBlueLYNX but they are placed in a mounted folder. For more details please check
How to generate a mvIMPACT example.
To install the
mvIMPACT library licenses on the mvBlueLYNX you need this tools. The main installation tool is the bash script
lic_install. The other two tools are needed for some check during the installation. For more details please see
Licensing.
This are some useful aliases on the mvBlueLYNX which are set by executing the file
/etc/profile. This file will be executed by default when you login on the mvBlueLYNX via
telnet or
serial interface.
With this bash scrip the resolution of the frame buffer can be changed. It uses the standard
fbset call.
The
get model info bash script shows what kind of mvBlueLYNX you are using. It decodes the model information regarding CPU frequency (
MHz), sensor type (
CCD,
CMOS, etc.), resolution (
XRes x
YRes), sensor color (
C /
G), system version.
The
change console number bash script is useful to change the
ppcboot_env entry
console_nr. By executing
chconsno [
new no] this entry will be changed.
Note that after changing this ppcboot entry you need to reboot the mvBlueLYNX to activate the change. The entry can be changed from 0 up to 2 where:
- console_nr=0 means that the serial console is placed on ttyS0
- console_nr=1 means that the serial console is placed on ttyS1 and ttyS0 can be used for other things (e.g. PicoGUI serial mouse)
- console_nr=2 there is no serial console available
This bash script can be used to show the used and available memory. The standard free tool is called in a loop each 5 seconds. The script can be exit with [
CTRL ]+[
C ]. It is useful to detect memory leaks in the application.
This bash script can be used to enable the Run Length Enconding (RLE) on the mvBlueLYNX.
As the name suggests, the
genlogs tool generates some log files and saves them as a
tar file under
/tmp . The log files are:
- ppcboot_env.log , entries of
/proc/ppcboot_env - dmesg.log , dmesg outputs (Kernel messages)
- ipkgstatus.log , software state on the mvBlueLYNX
- lics.log , state of mvIMPACT licenses (since version 1.11.2)
- ps.log , list of all running processes (since version 1.11.3)
- logread.log , local logger (since version 1.11.3)
The prefix of the log files is the serial number of the mvBlueLYNX. To ease possible support, please send this tar file to the support.
This bash script can be used to enable the Hardware Real-Time Controller on the mvBlueLYNX (known from mvBlueFOX cameras).
This tool checks, if
boa is installed and makes an entry to the rcS file. With it the server will start automatically during the next boot.
- Note:
- The webserver only starts, if it is installed.
To install the mvs-tools package file you have to make the following entry:
mvBL:/# ipkg install mvs-tools_1.2_ppc603e.ipk
The name of the file contains:
| the package name : | mvs-tools |
| the package version : | 1.2 |
| the packege target : | ppc603e |
To install this package from a URL (this URL does not really exist!):
mvBL:/# ipkg install http:
To upgrade this package to a newer version:
mvBL:/# ipkg upgrade mvs-tools
To remove this package:
mvBL:/# ipkg remove mvs-tools
For more details please see Installing IPK packages.
