diff options
author | tzafrir <tzafrir@5390a7c7-147a-4af0-8ec9-7488f05a26cb> | 2007-05-17 19:34:32 +0000 |
---|---|---|
committer | tzafrir <tzafrir@5390a7c7-147a-4af0-8ec9-7488f05a26cb> | 2007-05-17 19:34:32 +0000 |
commit | 5b68efc40a339a8ae3d9d137c7b9af809c3f5519 (patch) | |
tree | 365f4c82a3123daebaf9a8d41817916c1dd74bf4 /xpp/README.Astribank | |
parent | 5174fc292d1a6184271a39aea2826b57f177454e (diff) |
* Tested with zaptel-1.2.17.1
* Add D-Channel TX, RX and BAD frames count in /proc/xpp/XBUS-*/XPD-*/bri_info
* Adjust output of xpp_sync script. Pad for 8 port BRI.
* Added a debugging module parport_debug (not compiled by default).
* Added an optional patch to zaptel:
- compiles only if ZAPTEL_SYNC_TICK is defined
- Allow interested driver to register for "sync" notification.
- Does not affect drivers that do not use this feature.
* Added external synchronization feature:
- Only if ZAPTEL_SYNC_TICK feature is compiled in
- Than XPP may be synchronized by another card (e.g: an Astribank
with FXS can be synchronized by a Digium PRI card).
- May be enabled/disabled in runtime via the 'sync_tick_active' module
parameter to the xpp.ko module.
* Fixed a potential bug in D-Channel hexdump printing.
* New visual indications in BRI leds:
- Constant ON RED/GREEN: Shows the port type -- NT/TE.
- Very fast "double blink": Layer1 work, no D-Channel yet.
- Steady blinking (1/2 sec): D-Channel trafic detected.
* xpp_fxloader moved to /usr/share/zaptel .
* adj_clock removed: never really used.
* Debugfs code now disabled by default.
* Now we have Zaptel::Hardware and a sample zaptel_hardware script (not
(installed by default).
* We also have a sample perl zapconf (not installed by default) which
aims at replacing genzaptelconf (sans the modules detection).
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.2@2529 5390a7c7-147a-4af0-8ec9-7488f05a26cb
Diffstat (limited to 'xpp/README.Astribank')
-rw-r--r-- | xpp/README.Astribank | 19 |
1 files changed, 14 insertions, 5 deletions
diff --git a/xpp/README.Astribank b/xpp/README.Astribank index 102ae62..a240f36 100644 --- a/xpp/README.Astribank +++ b/xpp/README.Astribank @@ -49,9 +49,9 @@ All firmware files should be copied to a new directory: The xpp_fxloader and xpp_fxloader.usermap should be copied to: /etc/hotplug/usb/ -Note that loading through udev is not yet provided. Run +Run: - /etc/hotplug/usb/xpp_fxloader load + /usr/share/zaptel/xpp_fxloader load to load firmware. @@ -114,10 +114,10 @@ Zaptel as a single span. This will basically be 8 analog channels. Loading Firmware: """""""""""""""" -Normally this is done using the script xpp_fxloader.If it works fine, -you don't need to bother reading this section. +Normally this is done using the script /usr/share/zaptel/xpp_fxloader . +If it works fine, you don't need to bother reading this section. Once the firmware is loaded the USB ID of the Astribank changes to e4e4 -1132, and the driver can pick it up. You'll also see the top led lit. +11x2, and the driver can pick it up. You'll also see the top led lit. First and foremost: the simplest and most useful tool to debug problems here is lsusb. The output of lsusb should show exactly if the device is @@ -211,6 +211,15 @@ Newer versions of the USB firmware can now be reset using 'fpga_load -r'. This will only work when the device is not used by the driver, so you may need to 'rmmod xpp_usb' in order to reset the firmware. +Also try: + + rmmod xpp_usb; /usr/share/zaptel/xpp_fxloader reset + # if asterisk was running: you may need to stop/restart it now. + # if there are some "disconnected" spans in /proc/xpp/xbuses + # wait a while, until you see the 1152 IDs again, and then: + /etc/init.d/zaptel start + # and start/restrart asterisk. + Loading The Modules: """"""""""""""""""" |