FGCOM/dahdi-linux
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

xpp: clobber fpga_load

Browse Source 
* It was replaced long ago by astribank_hexload/astribank_tool/astribank_allow
* It hasn't been used for several releases now, nor updated.
* Time to move into the eternal bit-bucket.
* Left (very) few strings as a tribute...

Signed-off-by: Oron Peled <oron.peled@xorcom.com>
Acked-by: Tzafrir Cohen <tzafrir.cohen@xorcom.com>

git-svn-id: http://svn.astersk.org/svn/dahdi/tools/trunk@10504 17933a7a-c749-41c5-a318-cba88f637d49
This commit is contained in:
Oron Peled 2012-03-15 20:45:57 +00:00 committed by Tzafrir Cohen
parent be70b5b347
commit 65066704be
5 changed files with 20 additions and 1165 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
xpp/Makefile
View File

@ -80,12 +80,12 @@ TARGETS = .perlcheck astribank_is_starting
PROG_INSTALL = astribank_is_starting
MAN_INSTALL = $(PROG_INSTALL:%=%.8)
ifeq (1,$(PBX_USB))
TARGETS += fpga_load \
TARGETS += \
astribank_tool \
astribank_hexload \
astribank_allow \
test_parse
PROG_INSTALL += fpga_load astribank_tool astribank_hexload astribank_allow
PROG_INSTALL += astribank_tool astribank_hexload astribank_allow
endif
ifneq (,$(PERLLIBDIR))
PROG_INSTALL += $(PERL_SCRIPTS)
@ -122,9 +122,6 @@ endif
CFLAGS += -I. -Ixtalk
fpga_load: fpga_load.o hexfile.o
fpga_load: LIBS+=$(EXTRA_LIBS) $(USB_LIB)
astribank_hexload: $(ABHEXLOAD_OBJS)
astribank_hexload: LIBS+=$(EXTRA_LIBS) $(USB_LIB)
astribank_hexload: CFLAGS+=$(OCT_CFLAGS)
@ -138,8 +135,6 @@ astribank_allow: LIBS+=$(EXTRA_LIBS) $(USB_LIB)
astribank_is_starting: astribank_is_starting.o
astribank_is_starting: LIBS+=$(EXTRA_LIBS)
fpga_load.o: CFLAGS+=-D_GNU_SOURCE # We use memrchr()
hex2iic: hex2iic.o iic.o hexfile.o
test_parse: test_parse.o hexfile.o

24
xpp/README.Astribank
View File

@ -45,7 +45,8 @@ Building and Installation
-------------------------
Apart from the standard DAHDI build requirements, you also need:
* *libusb development headers* to build the fpga_load firmware loader.
* *libusb development headers* to build the Astribank firmware tools
(astribank_tool, astribank_hexload, astribank_allow).
This is typically the package libusb-dev on Debian (and derivatives
like Ubuntu) or libusb-devel on RedHat (and derivatives like
CentOS/Trixbox).
@ -561,9 +562,9 @@ Check USB level status. You can use one of the following utilities for it:
- If lsusb shows the Product ID as *11x1* - only the USB firmware is loaded
and not the FPGA firmware is loaded. If this is still the case after
a while - either the firmware loading has failed or you don't have
fpga_load. Make sure you have libusb-dev(el) installed when
building DAHDI. After you have installed it, you may need to re-run
./configure .
astribank_hexload/astribank_tool. Make sure you have libusb-dev(el)
installed when building DAHDI. After you have installed it, you may need
to re-run ./configure .
- It should list all of your Astribank devices. If it doesn't (for
more than period of time needed for the initial firmware
loading) - Check that the Astribank is connected indeed.
@ -698,7 +699,7 @@ Reset the firmware:
Or disconnect the Astribank from the power and reocnnect. On some older
versions of the USB firmware resetting the firmware (or any operation of
fpga_load) would fail if the driver is loaded. Hence you would need to
astribank_tool) would fail if the driver is loaded. Hence you would need to
run `rmmod xpp_usb` . In the end, reload the drivers.
@ -960,9 +961,9 @@ disconnects and then connects again itself with USB Product ID 11x1
(and a new device number).
In the second stage, the "FPGA" firmware is loaded.
The second-stage firmware loading is performed by using program fpga_load,
which is built in the directory xpp/utils and then copied to folder
/usr/sbin during DAHDI installation.
The second-stage firmware loading is performed by using program
astribank_hexload and astribank_tool, which are built in the directory
xpp/utils and then copied to folder /usr/sbin during DAHDI installation.
The command syntax is similar to the syntax of fxload. You can use the
following command in order to load the FPGA firmware manually:
@ -978,13 +979,6 @@ following command in order to load the FPGA firmware manually:
# reenumerate (disconnect and reconnect)
astribank_tool -D /dev/bus/usb/MMM/NNN -n
With older USB firmwares (before the one included in e.g. dahdi-linux
2.2) you needed to use instead of all the above:
# pick the right name according to the device ID. FPGA_1151.hex is for
# 115x Astribanks:
fpga_load -D /dev/bus/usb/MMM/NNN -I /usr/share/dahdi/FPGA_1151.hex
Please note, that NNN value differs from that that was used for the
fxload command due to the fact that device has "reconnected" itself
with another Product ID number. So you need to run lsusb again and get

14
xpp/astribank_hexload.8
View File

@ -17,11 +17,15 @@ astribank_hexload \- Xorcom Astribank (xpp) firmware loader
.SH DESCRIPTION
.B astribank_hexload
is a second-stage firmware loader for Xorcom Astribanks. Note that some
older models use fpga_load(8) instead.
is a second-stage firmware loader for Xorcom Astribanks.
It is used to load a file in the Intel HEX format into a Xorcom
Astribank. It can be used to load either an FPGA firmware or a PIC
Note that some very old models use fpga_load(8) instead.
This legacy tool hasn't been used for several releases.
It can be found in version 2.6 and below of dahdi-tools.
The astribank_hexload(8) program is used to load a file in the
Intel HEX format into a Xorcom Astribank.
It can be used to load either an FPGA firmware or a PIC
firmware. It is normally run by the script xpp_fxloader.
.SH OPTIONS
@ -92,7 +96,7 @@ what you'd normally use for FXS, FXO and T1.
.RE
.SH SEE ALSO
fxload(8), lsusb(8), astribank_tool(8), fpga_load(8)
fxload(8), lsusb(8), astribank_tool(8)
.SH AUTHOR
This manual page was written by Tzafrir Cohen <tzafrir.cohen@xorcom.com> .

86
xpp/fpga_load.8
View File

@ -1,86 +0,0 @@
.TH "FPGA_LOAD" "8" "16 April 2006" "" ""
.SH NAME
fpga_load \- Xorcom Astribank (xpp) firmware tool
.SH SYNOPSIS
.B fpga_load
[\fB-g\fR] [\fB-r\fR] [\fB-v\fR] \fB-D \fR{/proc/bus/usb|/dev/bus/usb}/\fIBUS/DEV\fR
.B fpga_load
[\fB-g\fR] [\fB-v\fR] \fB-D \fR{/proc/bus/usb|/dev/bus/usb}/\fIBUS/DEV\fR \fB-I \fIfirmware.hex\fR [\fB-b \fIdump.bin\fR] [\fB-i\fR]
.B fpga_load -h
.SH DESCRIPTION
.B fpga_load
loads the FPGA firmware to the Xorcom Astribank device.
The syntax resembles that of fxload(8).
.SH OPTIONS
.B -b
.I dump.bin
.RS
Before writing firmware, bump the processed binary file to
.I dump.bin\fR.
.RE
.B -D
.I DEVICE
.RS
Required. The device to read from/write to. On modern UDEV-based system
this is usually /dev/bus/usb/\fIbus_num\fR/\fIdevice_num\fR,
where \fIbus_num\fR and \fIdevice_num\fR are the first two numbers in the
output of lsusb(8).
On older systems that use usbfs, it is usually
/proc/bus/usb/\fIbus_num\fR/\fIdevice_num\fR.
.RE
.B -r
.RS
Reset the Astribank and renumerate its USB connection to power on product ID.
.RE
.B -g
.RS
Dump all eeprom data to standard output.
.RE
.B -I
.I fireware_file
.RS
The firmware file to write to the device.
.RE
.B -i
.RS
Show information about the firmware file (valid only with \fB-I\fR option).
Example:
.PP
./FPGA_1151.hex: Version=3297 Checksum=58270
In particular, the calculated checksum should match the output of \fIsum(1)\fR
on the binary firmware file generated by the \fB-b\fR option.
.RE
.B -v
.RS
Increase verbosity. May be used multiple times.
.RE
.B -h
.RS
Displays usage message.
.RE
.SH SEE ALSO
fxload(8), lsusb(8)
.SH 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.

1052
xpp/fpga_load.c
View File

File diff suppressed because it is too large Load Diff