linux-dect

linux-dect@lists.osmocom.org

80 discussions

by henrik hansen

Hey, my Asterisk got a problem with the chan_dect module. I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions debian*CLI> module load chan_dect Unable to load module chan_dect Command 'module load chan_dect' failed. [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. Could someone help me, getting this fixed? -- -- Mit freundlichen Grüßen Henrik Hansen

13 years

Re: debt 6.0 rf band

by Frédéric LECAILLE

On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote: > Updated patch attached > <usdect.diff> Ok thank you a lot Patrick. Here are the results: with your last patch: dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 *The frequency is always 0 MHz* The kernel logs seems to be OK: [15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27 So I have tried your last patch with mine to force the rf_band to 1: dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on... About trx2: dect-transceiver-list --name trx2 DECT Transceiver trx2: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0 slot 0: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 (no a-crc-errors) If I remember well, with only my patch which forces the rf_band to 3 we got for trx2: dect-transceiver-list --name trx2 I see that slot0 is scanning: DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0

13 years

debt 6.0 rf band

by Frédéric LECAILLE

Hello, I am trying to use a dosh&amand PCI card… this one: 01:03.0 Communication controller: Quicklogic Corporation COM-ON-AIR Dosch&Amand DECT (rev 32) Subsystem: Device 1786:0001 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 20 Region 0: Memory at ddefe000 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: com_on_air_pci with the dect kernel stack… I have managed to compile the kernel 3.2.0 with this config: CONFIG_DECT=m CONFIG_DECT_DEBUG=y CONFIG_DECT_CSF=m CONFIG_DECT_RAW=m CONFIG_DECT_CCF=m CONFIG_DECT_LU1_SAP=m CONFIG_DECTDEVICES=y CONFIG_DECT_VTRX=m CONFIG_DECT_COA_PCI=m CONFIG_DECT_COA=m CONFIG_DECT_COA_U2785=y CONFIG_DECT_COA_FIRMWARE=y CONFIG_DECT_COA_P64=y The driver seems to work but the issue is that I am trying to use it in USA for an American client, and I did not managed to make this card use the 1.9Mhz band (rf band 3 I guess). When I run this command: dect-transceiver-list --name trx2 I see that slot0 is scanning: DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0 but it nevers uses RF band 3 channel. For you information I have patch the driver this way to set the default debt rf band to 3: [root@localhost linux-2.6]# git diff diff --git a/drivers/dect/coa/sc1442x.c b/drivers/dect/coa/sc1442x.c index 73b9869..89b0a55 100644 --- a/drivers/dect/coa/sc1442x.c +++ b/drivers/dect/coa/sc1442x.c @@ -698,6 +698,7 @@ static u64 sc1442x_set_band(const struct dect_transceiver *t { struct coa_device *dev = dect_transceiver_priv(trx); +printk("setting band %d\n", band->band); return dev->radio_ops->map_band(dev, band); } diff --git a/net/dect/transceiver.c b/net/dect/transceiver.c index 706899d..25278af 100644 --- a/net/dect/transceiver.c +++ b/net/dect/transceiver.c @@ -19,6 +19,8 @@ #include <net/dect/mac_csf.h> #include <net/dect/transceiver.h> +static int rf_band = 3; +module_param(rf_band, int, 0); static LIST_HEAD(dect_transceiver_list); static int dect_transceiver_notify(struct dect_transceiver *trx, unsigned long event); @@ -651,7 +653,7 @@ int dect_register_transceiver(struct dect_transceiver *trx) if (err < 0) goto out; - err = dect_transceiver_set_band(trx, DECT_DEFAULT_BAND); + err = dect_transceiver_set_band(trx, rf_band); if (err < 0) goto out; Thank you in advance for any help. Fred

13 years

anyone for hire for dedected install and config for PCI card?

by Jeff Doucette

Is there anyone available for hire to help me get Dedected like CLI tools working with OcmocomDECT. I have the Com on Air PCI card and can't figure out how to get the driver to work. I need some guidence and willing to pay for it. Please advise, J BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }

13 years

State of Work?

by henrik hansen

Hello List, I'm new to the osmocomDECT project and just bought 2 com-on-air PCI Cards. After reading the list archive, i have some questions about the state of the project. What features do we suport at the moment? Can i build a dect cell with asterisk support? is handover within a cell about multiple basestations supported? if i can help, test or support the project with hardware, so please tell ;) -- -- Mit freundlichen Grüßen Henrik Hansen

13 years

The LMX3161 still not supported ?

by ol ol

Hi! Is there any news on the chipset support LMX3161? COA card III-type of still does not work with osmocom soft? Thanks, Blago.

13 years, 1 month

How to build Wireshark-1.6.7 against patched libpcap

by chiccus2003＠libero.it

Hi, I do not know how to build Wireshark-1.6.7 against patched libpcap. The Kernel 3.2.0+ is built and installed in directory: umberto@umberto-desktop:/usr/src The patched libpcap + libnl +libdect are built and installed in directory: umberto@umberto-desktop:/usr/src/tools Also the source directory wireshark-1.6.7 is in directory: umberto@umberto-desktop:/usr/src/tools I do: cd wireshark-1.6.7$ sudo ./configure --with-pcap=/usr/local/lib and I get the error: ........ checking for connect... yes checking whether to use libpcap for packet capture... yes checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... no checking for pcap_open_live in -lpcap with -lcfg -lodm... no checking for pcap_open_live in -lpcap with -lpfring... no configure: error: Can't link with library libpcap. andrea@andrea-desktop:/usr/src/tools/wireshark-1.6.7$ What should I do? (Pci card installed) With best regards, Umberto

13 years, 2 months

How to build Wireshark-1.6.7 against patched libpcap

by chiccus2003＠libero.it

Hi, I do not know how to build Wireshark-1.6.7 against patched libpcap. The Kernel 3.2.0+ is built and installed in directory: umberto@umberto-desktop:/usr/src The patched libpcap + libnl +libdect are built and installed in directory: umberto@umberto-desktop:/usr/src/tools Also the source directory wireshark-1.6.7 is in directory: umberto@umberto-desktop:/usr/src/tools I do: cd wireshark-1.6.7$ sudo ./configure --with-pcap=/usr/local/lib and I get the following error: ........ checking for connect... yes checking whether to use libpcap for packet capture... yes checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... no checking for pcap_open_live in -lpcap with -lcfg -lodm... no checking for pcap_open_live in -lpcap with -lpfring... no configure: error: Can't link with library libpcap. andrea@andrea-desktop:/usr/src/tools/wireshark-1.6.7$ But if I run “./configure”, then when I run “sudo wireshark” can not find the interface dect. There are only interfaces: "any" - "lo" - "usb0". What should I do? (Pci card installed) With best regards, Umberto

13 years, 3 months

Problems Building DECT Stack

by Sebastian ---

Hi First Problem: When I try to Build libdect (libnl was build and Installed without any critical errors): root@bt:/home/libdect# sh configure checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a thread-safe mkdir -p... /bin/mkdir -p checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed configure: Documentation build disabled checking for nl_socket_alloc in -lnl... no configure: error: No suitable version of libnl found Second Problem: When I Put in my com-on-air PCMCIA Card, and look in Kern.log: Apr 19 19:06:26 bt kernel: [ 13.847922] com_on_air_cs 0.0: DECTDataDevice PCMCIA F22 Apr 19 19:06:26 bt kernel: [ 13.888290] com_on_air_cs 0.0: Radio type U2785B Apr 19 19:06:26 bt kernel: [ 13.901784] com_on_air_cs 0.0: Loading firmware ... Apr 19 19:06:26 bt kernel: [ 13.996529] pcmcia 0.1: pcmcia: registering new device pcmcia0.1 (IRQ: 3) Apr 19 19:06:26 bt kernel: [ 13.996740] com_on_air_cs 0.1: DECTDataDevice PCMCIA F22 Apr 19 19:06:26 bt kernel: [ 13.996818] com_on_air_cs 0.1: failed to enable PCMCIA device Apr 19 19:06:26 bt kernel: [ 13.996880] com_on_air_cs: probe of 0.1 failed with error -13

13 years, 4 months

Protocol mismatch error

by Tasha

Hello Patrick, I am currently working on my master thesis in computer science in which I'm trying to exploit you great open source software linux DECT-Stack. I plan to use it for controlling a Com-On-Air PCI ISDN card (Dosch&Amand). However, I'm facing problems with operating libdect, dectmon. To be more precise, after installing software and trying to run it I always get the following error message: dect_netlink_init: Protocol mismatch dect_init: Bad file descriptor root@dect:~/dectmon# valgrind src/dectmon ==4479== Memcheck, a memory error detector ==4479== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==4479== Using Valgrind-3.6.1-Debian and LibVEX; rerun with -h for copyright info ==4479== Command: src/dectmon ==4479== dectmon > ==4479== Warning: invalid file descriptor -1 in syscall close() dect_netlink_init: Protocol mismatch dectmon > dect_open_handle: Bad file descriptor ==4479== ==4479== HEAP SUMMARY: ==4479== in use at exit: 65,329 bytes in 189 blocks ==4479== total heap usage: 305 allocs, 116 frees, 74,326 bytes allocated ==4479== ==4479== LEAK SUMMARY: ==4479== definitely lost: 0 bytes in 0 blocks ==4479== indirectly lost: 0 bytes in 0 blocks ==4479== possibly lost: 0 bytes in 0 blocks ==4479== still reachable: 65,329 bytes in 189 blocks ==4479== suppressed: 0 bytes in 0 blocks ==4479== Rerun with --leak-check=full to see details of leaked memory ==4479== ==4479== For counts of detected and suppressed errors, rerun with: -v ==4479== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 39 from 6) root@dect:~/dectmon# and for any dect-command in asterisk: No such command 'dect show portables' Since my master degree depends highly on successful usage of your software I want to ask you for help and would very appreciate it. It would be very nice if you could give me an advise on how the problem can be solved. Please let me know if you need additional info, esp. in case the error text is not enough for you to be able to analyze the error. Thank you in advance! Best Regards, Tasha

13 years, 5 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linux-dect