bjdwp(1) [debian man page]

BJDWP(1)						      General Commands Manual							  BJDWP(1)

NAME

       bjdwp - Command line USB Blackberry Java Debug Wire Protocol

SYNOPSIS

       bjdwp [-h][-p pin][-P password][-v] address port

DESCRIPTION

       bjdwp  is  a  program that supports the Java Debug Wire Protocol over USB, which enables debugging of Java programs directly on your Black-
       berry.

       Support is experimental, and development is focused primarily on the BlackBerry Storm.

OPTIONS

       -p pin PIN of device to talk with.  Only needed if you have more than one Blackberry connected at once.

       -P password
	      Simplistic method to specify device password.  In a real application, this would be done using a more secure prompt.

       -v     Dump verbose protocol data during operation.

       -h, --help
	      Show summary of options.

ARGUMENTS

       The following arguments are required, in order to provide a socket where the JDWP server will listen for connections from the debugger.

       address
	      Most often 'localhost' but can be any IP or hostname on the machine running bjdwp.

       port   Port to listen on.

EXAMPLES

       Start the server and the USB connection to the device:

	    bjdwp localhost 8000

       Then start your java debugger:

	    jdb -connect com.sun.jdi.SocketAttach:hostname=localhost,port=8000

AUTHOR

       bjdwp was initially written for the Barry project by Nicolas VIVIEN.  This manual page was written by Chris Frey.

SEE ALSO

       http://www.netdirect.ca/software/packages/barry

								September 29, 2009							  BJDWP(1)

BIDENTIFY(1)						      General Commands Manual						      BIDENTIFY(1)

NAME

       bidentify - Barry Project's program to identify BlackBerry handhelds

SYNOPSIS

       bidentify [-B busname][-N devname][-h][-v]

DESCRIPTION

       bidentify  scans  the  USB  system for available BlackBerry devices and probes each one it finds, then sends the identifying information to
       stdout in a computer-friendly format.

OPTIONS

       -B busname
	      Specify the USB bus to search for Blackberry devices on.	This is the first number displayed in the output from the  lsusb  command,
	      such  as	002.   If  the busname is numeric on your system, 2 and 002 are equal.	See also the -N option, which can be used together
	      with this option to precisely select the device to work with.

       -N devname
	      Specify the USB device name.  This is the second number displayed in the output from the lsusb command, such as 005.  If the  device
	      name is numeric on your system, 5 and 005 are equal.  See also the -B option.

       -c     If  used	with the -m option, ESN numbers will be displayed in both hex and decimal formats where possible.  If -m is not used, this
	      option has no effect.

       -m     Also show the device's ESN / MEID / IMEI number.	This requires desktop database access, so is an option.   It  will  only  work	on
	      devices that have no password.

       -v     Dump verbose protocol data during operation.

       -h, --help
	      Show summary of options.

RETURN STATUS

       If  bidentify  detects  a  BlackBerry device, but cannot access it for some reason, it will write an error message to stderr describing the
       access problem, and return a count of the number of such failed devices as the error code.  A return code of 0 means there were	no  Black-
       Berry devices found that could not be probed.

       In the event of a fatal error, the message will be written to stderr, with an error code of 1.

AUTHOR

       bidentify is part of the Barry project.	This manual page was written by Chris Frey.

SEE ALSO

       http://www.netdirect.ca/software/packages/barry

								 February 24, 2011						      BIDENTIFY(1)