Hello from Gregg C Levine
Here's my problem. As part of my work, hobby if you will, I build
small transmitters. These are based on those created by author R
Stuart Mackay in his book, "Bio-medical telemetry; sensing and
transmitting biological information from animals and man", and here's
the libra
On Tue, Jan 17, 2006 at 06:10:43PM -0500, Brian Dunn wrote:
> Hi Eric -
>
> I've taken a guess at what needs to be done to look at the RD and WR
> signals needed for USB debugging. If I'm way off, could you point me
> in the right direction? The two main questions I have are
> 1) What do we
On Tue, Jan 17, 2006 at 02:01:37PM -0500, Michael Dickens wrote:
> Eric - We do have a logic analyzer, but with the basic connectors.
> Thus we'd think about changing the FPGA code to route the usbctl[]
> signals to a daughtercard for viewing. I can tell that at least 2 of
> the files you'r
Berndt:
My apologies, I was not explicit. The quotes were placed around that
phrase because it was picked from the 3.1 beta release notes. There is
a serious conflict in using SSE/SSE2/FFTW3.01 and gcc-3.4.[1-3] that was
apparently fixed in later versions of gcc.
Bob
Berndt Josef Wulf w
I've been working with the usrp_std fpga design. By including/removing
various circuits the device utilization ranges from 6% (no TX or RX) to 87%
(full design). I propose that we add conditional compile macros to make it
easier for custom fpga designs to select the circuits to be compiled. For
Has anyone tried this recently? I've updated to latest cvs and when I run
usrp_fft.py with the -8 option I get the following error:
Traceback (most recent call last):
File "./usrp_fft.py", line 220, in ?
main ()
File "./usrp_fft.py", line 216, in main
app = stdgui.stdapp(app_flow_graph,
Ryan - Your compile issue is that "string.h" isn't in the include
path (-I or otherwise) to get the prototype for the function
"memset". According to the SDCC Manual < http://sdcc.sourceforge.net/
doc/sdccman.html/node13.html >, -if- there is an issue then setting
"SDCC_INCLUDE" and/or "SDC
