xorcom 16 port fxs firmware problem...

maikcat

Joined
Apr 24, 2009
Messages
38
Likes
0
Points
0
#1
hi all,

i am trying to setup a usb xorcom 16 port fxs
and i there is no way to properly initialize it...

lsusb shows:

Bus 001 Device 006: ID a0e4:1131

i found this: http://docs.tzafrir.org.il/dahdi-tools/ ... g_firmware

when i gave:
fxload -t fx2 -D /dev/bus/usb/001/006 -I /usr/share/dahdi/USB_FW.hex

it changed its ID from a0e4:1130 to a0e4:1131..

i read that next i should give:
astribank_hexload -D /dev/bus/usb/001/006 -F /usr/share/dahdi/FPGA_1131.hex

but there is no FPGA_1131.hex file and its id supposed to be e4e4 but it is a0e4..
also tried FPGA_FXS but no lack...

the output is:

INFO: usb:001/006: ID=A0E4:1131 [Xorcom LTD / Astribank / ]
INFO: Loading hexfile to FPGA: /usr/share/dahdi/FPGA_FXS.hex (version 6799)
mpp_funcs.c:391: ERROR(process_command): Got ACK (for OP=0x5 [DEV_SEND_START]): 1 - Last command failed
mpp_funcs.c:710: ERROR(mpp_send_start): process_command failed: -71
astribank_hexload.c:99: ERROR(load_hexfile): Failed hexfile send start: -71
astribank_hexload.c:218: ERROR(main): Loading firmware to FPGA failed


any ideas to what should i do?

my test enviroment

elastix 2.0.3 (no updates..)

Thank you in advance.

Michael.
 

jgutierrez

Joined
Feb 28, 2008
Messages
5,737
Likes
0
Points
0
#2
Try the following:

1. yum update elastix -y
2. yum update -y
3. reboot the server
4. Go to System, and Hardware detector tool
5. Click on advanced, and choose replace dahdi channel
 

maikcat

Joined
Apr 24, 2009
Messages
38
Likes
0
Points
0
#3
thank you jgutierrez for answering,

i updated the enviroment but when i try to detect the card
elastix finds nothing....

any other things to try?

thank you again.

michael.
 

jgutierrez

Joined
Feb 28, 2008
Messages
5,737
Likes
0
Points
0
#4
Your xorcom should work correctly, try to plug it into another USB port, and try again.
What happens if you execute:
service dahdi restart
(paste the output)
 

maikcat

Joined
Apr 24, 2009
Messages
38
Likes
0
Points
0
#5
hi there,

just to inform you that i contacted xorcom,
they said that the firmware was corrupt (a0e4 id shown on lsusb)
give them remote (ssh) and they fix it.. :)

thank you for answering my post.

Michael.
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,887
Members
17,565
Latest member
omarmenichetti
Top