Re: [Discuss-gnuradio] failed to find urb in pending_rqsts: (nil)

2005-04-15 Thread Harald Welte
Thanks for your response, Eric.

On Thu, Apr 14, 2005 at 04:05:49PM -0700, Eric Blossom wrote:

  Does anyone have an idea what's going on?
 
 Haven't seen this before.

seems to be a kernel bug in 2.6.12-rc2, where REAPURB[NDELAY] can return
NULL pointers.  Greg KH's kurrent patchest on top of -rc2 fixes the
problem.  I've now been able to run the wfm_rcv_gui.py and listen to FM
radio :)

I'm now trying to get the same setup running on my notebook (Apple
TiBook IV, 1GHz G4, PC-Card USB2 Adapter).  For some reason debian
unstable doesn't provide the same version of wxPython on ppc than on
i386/x86_64.  Need to investigate why...

btw: My first project for the USRP will be passive sniffing of
ISO14443 A/B (the on-the-air protocol used between rfid readers and tags
or contactless smartcards).  I'll keep you posted on my proceedings.

-- 
- Harald Welte [EMAIL PROTECTED]  http://gnumonks.org/

Privacy in residential applications is a desirable marketing option.
  (ETSI EN 300 175-7 Ch. A6)


pgpB7ihyLG9BX.pgp
Description: PGP signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] No module named wx

2005-04-15 Thread Angilberto Muniz Sb
Similar situation down here in Brazil, but
after adding the softlink it complains with
file not found... or something similar...

Any tips on where to put some break code to help debug
the issue?

Rgrds,

Angilberto.

--- [EMAIL PROTECTED] wrote:
 I fixed it by adding the following softlink:
 
 ln -s ./wx-2.5.5-gtk2-ansi/wx
 
 in the .../lib/python2.3/site-packages
 
 directory.
 
 Worked fine after that.  There is a wx.pth in the
 site-packages directory 
 that Python should use to follow it, but it doesn't
 work.  This was a 
 quick fix.
 
 Hope that helps
 
 
 
 On Thu, 14 Apr 2005, John Clark wrote:
 
  LRK wrote:
  
  On Thu, Apr 14, 2005 at 12:01:11PM -0500, Suvda
 Myagmar wrote:

  
  I also got USRP hardware recently and installed
 the latest baseline and 
  gnuradio packages to test the HW. When I ran an
 example this is what I got:
  
  $ ./usrp_oscope.py
  Traceback (most recent call last):
File usrp_oscope.py, line 26, in ?
  from gnuradio.wxgui import stdgui, fftsink,
 scopesink
File 
 

/home/myagmar/gr/lib/python2.3/site-packages/gnuradio/wxgui/stdgui.py,
 
  line 24, in ?
  import wx
  ImportError: No module named wx
  
  
  Another thing that might give a clue to my
 trouble is while building cvs 
  gnuradio-core make check failed:
  
  $ make check
  
  
 

==
  ERROR: test_gru_import (__main__.test_head)
 

--
  Traceback (most recent call last):
   File ./qa_kludged_imports.py, line 39, in
 test_gru_import
 from gnuradio import gru
   File 
  

/home/myagmar/gnuradio/gnuradio-core/src/python/gnuradio/gru/__init__.py,
 line 37, in ?
 exec from gnuradio.gruimpl.%s import * %
 (f,)
   File string, line 1, in ?
   File 
  

/home/myagmar/gnuradio/gnuradio-core/src/python/gnuradio/gruimpl/freqz.py,
 line 57, in ?
 import Numeric
  ImportError: No module named Numeric

  
  
  Setting PYTHONPATH to
 /home/myagmar/gr/lib/python2.3/site-packages
  is supposed to fix that. Doesn't for me either.
 Still working on why.
  
  There should be another site-packages where
 python is installed, in my
  case /usr/local/lib/python2.4/site-packages. Last
 resort is to put files 
  Numeric.pth and wx.pth in that directory which
 contain the whole path to 
  the packages.

  
  
  I'll chime in on the 'easy to intuit' requirements
 to get any of gr-* 
  up, especially the gr-wxgui.
  Unfortunately other projects press and I have not
 been able to get a 
  working 'graphical' user
  environment up, when most of the antecedent
 'packages' don't seem to 
  just build, and when
  they do the install seems not to place things in
 the 'right' places for 
  building or using the gr-*
  codes sets.
  
  When I have time, I'll continue on.
  
  
  
  ___
  Discuss-gnuradio mailing list
  Discuss-gnuradio@gnu.org
 

http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
  
 
 
 
 ___
 Discuss-gnuradio mailing list
 Discuss-gnuradio@gnu.org

http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
 



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] No module named wx

2005-04-15 Thread Robert McGwier
Fails at work on my SUSE 9.2 install and succeeds at home on my SUSE 9.2 
install.
Running python 2.3.4 at home and Python 2.4.1 at work.  However, I just 
installed
2.4.1 at work.  I got the same error messages before today with 2.3 
first in the path.
Having 2.4.1 first seems not to have helped (or hurt). The stuff you 
listed is in both
the 2.3 and the 2.4 lib and local/lib python site-packages sub-dirs with 
the correct
permissions.  I get two errors:

import wx
says wx cannot be found
and
./burn-basic-eeprpm  -a
says it cannot find usrp_prims
even though both are clearly installed as in your list.  This is a new 
error and just started.

Bob

Eric Blossom wrote:
On Fri, Apr 15, 2005 at 06:22:23AM -0700, Angilberto Muniz Sb wrote:
 

Similar situation down here in Brazil, but
after adding the softlink it complains with
file not found... or something similar...
Any tips on where to put some break code to help debug
the issue?
Rgrds,
Angilberto.
   

Not really.  These are install problems with the python add in's.
Personally I suspect something is wrong with the install and/or you're
PYTHONPATH environment variables are set right.
You can exercise the problem very easily from the command line.
$ python
 

import wx
   

$ python
 

import Numeric
   

Eric
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
 



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] No module named wx - another data point

2005-04-15 Thread Ilia Mirkin
In my limited experience with this stuff, DO NOT install multiple
versions of wxPython. Just have 2.5.

  -Ilia

On Fri, 2005-04-15 at 14:33 -0500, LRK wrote:
 Probably a clue here somewhere.
 
 'import wx'  fails but  'import wxversion'  works
 
 Then I can select the version and get a different error:
 
 
 gr% python
 Python 2.4.1 (#2, Apr 12 2005, 10:46:06) 
 [GCC 3.4.2 [FreeBSD] 20040728] on freebsd5
 Type help, copyright, credits or license for more information.
  import wxversion
  wxversion.select('2.5')
  import wx
 Traceback (most recent call last):
   File stdin, line 1, in ?
   File 
 /usr/gnuradio/gr/lib/python2.4/site-packages/wx-2.5.5-gtk2-ansi/wx/__init__.py,
  line 42, in ?
 from wx._core import *
   File 
 /usr/gnuradio/gr/lib/python2.4/site-packages/wx-2.5.5-gtk2-ansi/wx/_core.py,
  line 11351, in ?
 codecs.lookup(default)
 TypeError: lookup() argument 1 must be string, not None
  
 gr%
 
 



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


RE: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Deqiang chen
note that I actually want to realize an eye diagram.
And the previous email is how I like to realize it.
Does anyone have others ways to realize an eye diagram?


From: Deqiang chen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: Discuss-gnuradio@gnu.org
Subject: RE: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec
Date: Fri, 15 Apr 2005 19:38:32 +
Thanks, guys!
Now I have another problem about how to use split the dat stream.
I would like to split a data stream, put it into parallel streams and show 
these streams on
screen. Note that I would like to show these data streams together in a 
single window.
Could any one give me a hint about how I could do that ?
I actually notice there is gr.serial_to_parallel, but the following code

block_size=1024
   sp=gr.serial_to_parallel(gr.sizeof_float,block_size)
   sink, win = scopesink.make_scope_sink_f (self, panel, Rx Data, 
input_rate)
   vbox.Add (win, 1, wx.EXPAND)

   self.connect (u,c2f_1)
self.connect( c2f_1, sp)
   self.connect(sp,(sink,0))
produce an error , i.e.,
self.connect(sp,(sink,0))
 File 
/usr/local/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py, 
line 114, in connect
   self._connect (points[i-1], points[i])
 File 
/usr/local/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py, 
line 119, in _connect
   self._connect_prim (s, d)
 File 
/usr/local/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py, 
line 127, in _connect_prim
   self._check_type_match (src_endpoint, dst_endpoint)
 File 
/usr/local/lib/python2.3/site-packages/gnuradio/gr/basic_flow_graph.py, 
line 238, in _check_type_match
   raise ValueError, 'source and destination data sizes are different'
ValueError: source and destination data sizes are different

what is wrong with the code ?
Thanks!
david
From: Eric Blossom [EMAIL PROTECTED]
To: Deqiang chen [EMAIL PROTECTED]
CC: Discuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec
Date: Fri, 15 Apr 2005 10:41:42 -0700
On Fri, Apr 15, 2005 at 03:37:27PM +, Deqiang chen wrote:
 hello, Eric,

 I remembered there is an annoucement that FSK can work at 100kbps.
 So I dig it out and take a look at the source code for the FSK (
 fsk_rx.py) . I am a little surprised
 that there are no time recovery there.
 My understanding is that for fsk, if you use noncoherent
 demodulation, you would not need the phase information.  However,
 you still need to know the timing in order to correctly sampling the
 output of correlator or matched filter.  Could you give a hint of
 what is going on here ?
 david
The output rate of gr.quadrature_demod_cf is 8 times the symbol rate.
The selection of the center of the bit is done in gr.simple_correlator.
It watches for a pseudo random sync pattern at the beginning of
each packet and uses this to figure out which of the possible alignments
is best.  A similar technique is used in Bluetooth.
Eric
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] _gnuradio_swig_python import error on Mac OS X

2005-04-15 Thread Jonathan Jacky
I build gnuradio-core from the 2.5 tarball on Mac OS X.
After make and make install completed without error messages,
I tried make check in my gnuradio-core-2.5. (I learned here in January 
that on OS X, make install must precede make check).

Every one of the qa_*.py checks fails with this same traceback:
Traceback (most recent call last):
  File ./qa_add_and_friends.py, line 23, in ?
from gnuradio import gr, gr_unittest
  File 
/Users/jon/gnuradio/gnuradio-core-2.5/src/python/gnuradio/gr/__init__.py\
, line 27, in ?
from gnuradio_swig_python import *
  File 
/Users/jon/gnuradio/gnuradio-core-2.5/src/lib/swig/gnuradio_swig_python.\
py, line 5, in ?
import _gnuradio_swig_python
ImportError: No module named _gnuradio_swig_python
I find I have these files under my gnuradio-core-2.5:
 gnuradio-core-2.5/src/lib/swig/_gnuradio_swig_python.la
 gnuradio-core-2.5/src/lib/swig/.libs/_gnuradio_swig_python.la
 gnuradio-core-2.5/src/lib/swig/.libs/_gnuradio_swig_python.lai
 gnuradio-core-2.5/src/lib/swig/.libs/_gnuradio_swig_python.dylib
I find that make install also installed these:
 /Library/Python/2.3/gnuradio/gr/_gnuradio_swig_python.la
 /Library/Python/2.3/gnuradio/gr/_gnuradio_swig_python.dylib
However, I don't find a _gnuradio_swig_python.py, .pyc, or .pyo anywhere
I thought it might be a problem with the Python path, but python can import 
other .py files from under /Library/Python/2.3 without an explicit path being 
given.  In a python terminal session, print sys.path shows the path includes
'/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/
site-packages', which is a link to /Library/Python/2.3.

Any suggestions?  Am I supposed to have a _gnuradio_swig_python.py,.pyc, 
or .pyo somewhere?  Is python supposed to import 
_gnuradio_swig_python.la,.lai, or .dylib?

Jon Jacky

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] crude compiler for WaveData

2005-04-15 Thread Larry Doolittle
Guys -

I took a first stab at an FX2 WaveData compiler, since I don't touch
Microsoft-only software (GPIFTool) with a 3.048 meter pole.  This attempt
is good enough to recreate the WaveData definition in usrp1_gpif.c from
the following source code:

-- cut here --

// GPIF Ctrl Outputs
CTL 0= WEN# CMOS 0
CTL 1= REN# CMOS 0
CTL 2= OE#  CMOS 0
CTL 3= CLRSTCMOS 0
CTL 4= unused   CMOS 0
CTL 5= BOGUSCMOS 0

// GPIF Rdy Inputs
RDY0 = EF#   // hello world
RDY1 = FF#
RDY2 = unused
RDY3 = unused
RDY4 = unused
RDY5 = TCXpire
//FIFOFlag = FIFOFlag
//IntReady = IntReady

Waveform 0: singlerd
 state 0:  ;  wait 1
 state 1:  ;  wait 1
 state 2:  ;  wait 1
 state 3:  ;  wait 1
 state 4:  ;  wait 1
 state 5:  ;  wait 1
 state 6:  ;  wait 1

Waveform 1: singlewr
 state 0:  sgl  activate ;  wait 1
 state 1:  WEN# activate ;  if (EF#) then idle else idle
 state 2:  WEN# activate ;  wait 1
 state 3:  WEN# activate ;  wait 1
 state 4:  WEN# activate ;  wait 1
 state 5:  WEN# activate ;  wait 1
 state 6:  WEN# activate ;  wait 1

Waveform 2: FIFORd
 state 0:  REN# OE#  ;  wait 1 
 state 1:  OE# activate  ;  if (TCXpire) then 2 else 1
 state 2:  OE#   ;  wait 1
 state 3:;  if (TCXpire) then idle else idle

Waveform 3: FIFOWr
 state 0:   ;  wait 1
 state 1:  activate ;  if (TCXpire) then idle else 1
 state 2:  activate ;  wait 1
 state 3:  activate ;  wait 1
 state 4:  activate ;  wait 1
 state 5:  activate ;  wait 1
 state 6:  activate ;  wait 1

-- cut here --

Additional status:
  Totally ignores flowstate.
  Sets state 7 bytes to zero.
  Need suggestions for handling FIFOFlag, TCXpire, IntReady, and non-CMOS CTLs.
  Documentation is nonexistent.
  Tested on debian sarge/sid, perl v5.8.4.

Tiny tarball attached.  Comments appreciated.

  - Larry


ezusb-gpif.tar.gz
Description: Binary data


signature.asc
Description: Digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio