Difference between revisions of "Brick: How to trace CAPI events"

From OS4X
Jump to navigation Jump to search
(New page: == Package download == Download the latest Bricktools package from [ftp://ftp.funkwerk-ec.com/bintec/unixtool/] for your platform (i.e. [ftp://ftp.funkwerk-ec.com/bintec/unixtool/bricktool...)
 
 
Line 1: Line 1:
 
== Package download ==
 
== Package download ==
Download the latest Bricktools package from [ftp://ftp.funkwerk-ec.com/bintec/unixtool/] for your platform (i.e. [ftp://ftp.funkwerk-ec.com/bintec/unixtool/bricktools_Linux_2.4.10_i386.tar.gz] for latest Linux support).
+
Download the latest Bricktools package from [ftp://ftp.funkwerk-ec.com/bintec/unixtool/ ftp://ftp.funkwerk-ec.com/bintec/unixtool/] for your platform (i.e. [ftp://ftp.funkwerk-ec.com/bintec/unixtool/bricktools_Linux_2.4.10_i386.tar.gz ftp://ftp.funkwerk-ec.com/bintec/unixtool/bricktools_Linux_2.4.10_i386.tar.gz] for latest Linux support).
  
 
== Configure environment ==
 
== Configure environment ==

Latest revision as of 09:44, 6 May 2011

Package download

Download the latest Bricktools package from ftp://ftp.funkwerk-ec.com/bintec/unixtool/ for your platform (i.e. ftp://ftp.funkwerk-ec.com/bintec/unixtool/bricktools_Linux_2.4.10_i386.tar.gz for latest Linux support).

Configure environment

The tool needed for capi traces expects at least the variable

CAPI_HOST

to be set to a resolvable hostname or IP address to your brick.

Example:

export CAPI_HOST=brick-xm

The optional environment variable

CAPI_PORT

can be set to the corresponding CAPI port of your configured brick (if port 2662 is not your default).

Start trace

The output of "capitrace" can be very excessive, so your best option would be to redirect the output to a logfile for better analysis:

./capitrace > /tmp/capi.log