rtcansend(1) [debian man page]
RTCANSEND(1) Xenomai RTCANSEND(1) NAME
rtcansend - Xenomai tool for sending CAN messages SYNOPSIS
rtcansend <can-interface> [Options] <can-msg> DESCRIPTION
rtcansend is part of Xenomai. It is used to send messages via a CAN interface. The system must run a suitable Xenomai enabled kernel with the respective module (xeno_native and the CAN driver). OPTIONS
<can-interface> is the CAN interface file. <can-msg> can consist of up to 8 bytes given as a space separated list. rtcansend accepts the following options: -i, --identifier=ID CAN Identifier (default = 1) -r, --rtr send remote request -e, --extended send extended frame -l, --loop=COUNT send message COUNT times -c, --count message count in data[0-3] -d, --delay=MS delay in ms (default = 1ms) -s, --send use send instead of sendto -t, --timeout=MS timeout in ms -L, --loopback=0|1 switch local loopback off or on -v, --verbose be verbose -p, --print=MODULO print every MODULO message -h, --help a usage description SEE ALSO
rtcanconfig(1), rtcanrecv(1) AUTHORS
rtcansend was written by Wolfgang Grandegger <wg@grandegger.com>, Jan Kiszka <jan.kiszka@web.de> and Philippe Gerum <rpm@xenomai.org>. This man page was written by Roland Stigge <stigge@antcom.de>. 2.6.0 2008-04-19 RTCANSEND(1)
Check Out this Related Man Page
SWITCHTEST(1) Xenomai SWITCHTEST(1) NAME
switchtest - Xenomai context switch test SYNOPSIS
switchtest [options] threadspec threadspec... DESCRIPTION
switchtest is part of Xenomai. It can be used to test thread context switches. switchtest creates threads of various types and attempts to switch context between these threads, printing the count of context switches every second. A suitable Xenomai enabled kernel with the respective module (xeno_posix) must be installed. OPTIONS
Each threadspec specifies the characteristics of a thread to be created: threadspec = (rtk|rtup|rtus|rtuo)(_fp|_ufpp|_ufps)*[0-9]* rtk for a kernel-space real-time thread rtup for a user-space real-time thread running in primary mode rtus for a user-space real-time thread running in secondary mode rtuo for a user-space real-time thread oscillating between primary and secondary mode _fp means that the created thread will have the XNFPU bit armed (only valid for rtk) _ufpp means that the created thread will use the FPU when in primary mode0valid for rtus) _ufps means that the created thread will use the FPU when in secondary mode (invalid for rtk and rtup) [0-9]* specifies the ID of the CPU where the created thread will run, 0 if unspecified Passing no threadspec is equivalent to running: switchtest rtkN rtkN rtk_fpN rtk_fpN rtk_fp_ufppN rtk_fp_ufppN rtupN rtupN rtup_ufppN rtup_ufppN rtusN rtusN rtus_ufpsN rtus_ufpsN rtuoN rtuoN rtuo_ufppN rtuo_ufppN rtuo_ufpsN rtuo_ufpsN rtuo_ufpp_ufpsN rtuo_ufpp_ufpsN with N=1,...,nr_cpus, i.e. occurrences of all the arguments for each CPU Passing only the --nofpu or -n argument is equivalent to running: switchtest rtkN rtkN rtupN rtupN rtusN rtusN rtuoN rtuoN similar to the above. switchtest accepts the following options: --help, -h print usage information and exit --lines <lines>, -l <lines> print headers every <lines> lines --quiet or -q prevent this program from printing every second the count of ncontext switches --timeout <duration>, -T <duration> limit the test duration to <duration> seconds --nofpu, -n disables any use of FPU instructions AUTHOR
switchtest was written by Philippe Gerum <rpm@xenomai.org> and Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>. This man page was written by Roland Stigge <stigge@antcom.de>. 2.6.0 2008-04-19 SWITCHTEST(1)