diff options
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: """"""""""""""""""" |