fpga_load(8) [debian man page]
FPGA_LOAD(8) FPGA_LOAD(8) NAME
fpga_load - Xorcom Astribank (xpp) firmware tool SYNOPSIS
fpga_load [-g] [-r] [-v] -D {/proc/bus/usb|/dev/bus/usb}/BUS/DEV fpga_load [-g] [-v] -D {/proc/bus/usb|/dev/bus/usb}/BUS/DEV -I firmware.hex [-b dump.bin] [-i] fpga_load -h DESCRIPTION
fpga_load loads the FPGA firmware to the Xorcom Astribank device. The syntax resembles that of fxload(8). OPTIONS
-b dump.bin Before writing firmware, bump the processed binary file to dump.bin. -D DEVICE Required. The device to read from/write to. On modern UDEV-based system this is usually /dev/bus/usb/bus_num/device_num, where bus_num and device_num are the first two numbers in the output of lsusb(8). On older systems that use usbfs, it is usually /proc/bus/usb/bus_num/device_num. -r Reset the Astribank and renumerate its USB connection to power on product ID. -g Dump all eeprom data to standard output. -I fireware_file The firmware file to write to the device. -i Show information about the firmware file (valid only with -I option). Example: ./FPGA_1151.hex: Version=3297 Checksum=58270 In particular, the calculated checksum should match the output of sum(1) on the binary firmware file generated by the -b option. -v Increase verbosity. May be used multiple times. -h Displays usage message. SEE ALSO
fxload(8), lsusb(8) AUTHOR
This manual page was written by Tzafrir Cohen <tzafrir.cohen@xorcom.com> . Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. 16 April 2006 FPGA_LOAD(8)
Check Out this Related Man Page
XPP_SYNC(8) User Contributed Perl Documentation XPP_SYNC(8) NAME
xpp_sync - Handle sync selection of Xorcom Astribanks. SYNOPSIS
xpp_sync <auto|dahdi|nn> xpp_sync [-v] DESCRIPTION
On a normal operation one Astribank device provides timing for all the other Astribank devices. When run without parameters, xpp_sync will display a list of Astribanks (xbuses) that are connected and registered as Dahdi spans. The current xpp sync master will be marked. If you this an Astribank is connected and yet it does not appear on the output of xpp_sync, it may be unregistered. Try running dahdi_registration . Parameters auto Automatically selects the best Astribank for syncing. dahdi Gets synchronization from the Dahdi sync master. nn Sets XBUS-nn as sync source. -v Also print the numeric xpp sync rank. (Parameter name is case-insensitive) Example output: Setting SYNC Current sync: 01 Best Available Syncers: + XBUS-01 (usb-0000:00:10.4-3) [usb:12345678] [ PRI_TE PRI_NT PRI_TE PRI_NT ] XBUS-00 (usb-0000:00:10.4-2) [usb:QA-01] [ FXS FXO ] ================================================== WARNING: FXO which is not the syncer cause bad PCM Affected Astribanks are: -------------------------------------------------- XBUS-00 ================================================== In this example we see that the recommended xpp sync master is XBUS-02 - it is the first on the list. It is also the actual syncer, as we can see from the '+' beside it. xpp_sync is normally called from the dahdi init.d script. The parameter it is called with defaults to auto, but it is possible to override that parameter (e.g: set it to dahdi) through the value of XPP_SYNC in /etc/dahdi/init.conf . FILES
/proc/xpp/sync (Deprecated: no longer supported) xpp_sync is essentially a nicer interface to /proc/xpp/sync . That file shows the current xpp sync master (and in what format you need to write to it to set the master). SEE ALSO
dahdi_registration(1), dahdi_cfg(1), README.Astribank perl v5.14.2 2009-09-30 XPP_SYNC(8)