Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. Re: WBX's specs (Ingmar Meins)
2. Re: Heap(memory allocation) errors while building
rx_samples_to_file utility in windows (Chomal, Sunil)
----------------------------------------------------------------------
Message: 1
Date: Fri, 11 Mar 2011 07:59:57 +1100
From: Ingmar Meins <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] WBX's specs
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Andrew,
It's a software-defined-transceiver, your transmitter specs are almost
completely reliant on the code you write for it.
All other specs appear to be readily available in this forum or on their
website, diagrams, specifications etc.
IM
On 11/03/2011 6:42 AM, Feng Andrew Ge wrote:
> To folks in Ettus Research:
>
> I need to fill some forms which ask for specs of WBX. I have tried my
> best searing online, but failed. Would you please spend some time
> telling me WBX's following specs?
>
>
> At the transmitter side:
>
> (1) what's its output device, e.g., ceramic diode, transistor, or
> something else?
>
> (2) what's the relative level in dB of the highest powered harmonic
> above the 3rd?
>
> (3) What's the spurious level, e.g, the *maximum* *value* of
> *spurious* *emission* (in *dB*) *relative* to the *fundamental*, which
> occurs outside the --60 dBc point on the transmitter *fundamental*
> *emission* spectrum but does not occur on a harmonic of the
> *fundamental* frequency?
>
>
> At the receiver side:
>
> (1) what's the tuning method, by synthesizer?
>
> (2) What are specs of the IF band filter on the daughterboard (or
> mother board)?
>
> (3) what is the RF pre-selection type, e.g., tunable cavity?
>
> (4) What are the typical IF operating frequency? Are they discrete
> values or continuous? It seems that USRP1 tunes to discrete IF
> frequencies.
>
> (5) Is the oscillator tuned above or below the tuned (or specified)
> frequency?
>
> (6) what's the sensitivity in dBm? Would you specifiy criteria
> used, e.g., 12dB SINAD?
>
> (7) Is there any image rejection on WBX?
>
> (8) Is there any spurious rejection? If so, what's the value in dB?
>
>
> Thanks very much,
>
> Andrew
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20110311/18b2ae4a/attachment-0001.html>
------------------------------
Message: 2
Date: Fri, 11 Mar 2011 16:46:17 +0530
From: "Chomal, Sunil" <[email protected]>
To: "'[email protected]'" <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [USRP-users] Heap(memory allocation) errors while
building rx_samples_to_file utility in windows
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi Josh,
As suggested by you, I am retrying to build the uhd from scratch..
The thing is I am not sure where the problem is? I use cmake gui to configure
and generate. But I am not sure whether cmake has done the job properly.
This is how my cmake cache looks like...
########################
# EXTERNAL cache entries
########################
//boost enable dynamic linking
BOOST_ALL_DYN_LINK:BOOL=OFF
//Path to a file.
Boost_INCLUDE_DIR:PATH=D:/Program Files/boost/boost_1_44
//Boost diagnostic define
Boost_LIB_DIAGNOSTIC_DEFINITIONS:STRING=-DBOOST_LIB_DIAGNOSTIC
//Semicolon separated list of supported configuration types, only
// supports Debug, Release, MinSizeRel, and RelWithDebInfo, anything
// else will be ignored.
CMAKE_CONFIGURATION_TYPES:STRING=Debug;Release;MinSizeRel;RelWithDebInfo
//C++ compiler
CMAKE_CXX_COMPILER:FILEPATH=cl
//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING= /DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR
//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=/D_DEBUG /MDd /Zi /Ob0 /Od /RTC1
//Flags used by the compiler during release minsize builds.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /D NDEBUG
//Flags used by the compiler during release builds (/MD /Ob1 /Oi
// /Ot /Oy /Gs will produce slightly less optimized but smaller
// files).
CMAKE_CXX_FLAGS_RELEASE:STRING=/MD /O2 /Ob2 /D NDEBUG
//Flags used by the compiler during Release with Debug Info builds.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /D NDEBUG
//Libraries linked by defalut with all C++ applications.
CMAKE_CXX_STANDARD_LIBRARIES:STRING='kernel32.lib user32.lib gdi32.lib
winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib
advapi32.lib '
//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING= /STACK:10000000 /machine:X86
//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL
//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO
//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO
//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL
//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/Program Files/UHD
//Path to a program.
CMAKE_LINKER:FILEPATH=D:/cygwin/bin/link.exe
//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319/MSBuild.exe
//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING= /STACK:10000000 /machine:X86
//Flags used by the linker during debug builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL
//Flags used by the linker during release minsize builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO
//Flags used by the linker during release builds.
CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO
//Flags used by the linker during Release with Debug Info builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL
//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=UHD
//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc
//Flags for Fortran compiler.
CMAKE_RC_FLAGS:STRING=' '
//Flags used by the linker during the creation of dll's.
CMAKE_SHARED_LINKER_FLAGS:STRING= /STACK:10000000 /machine:X86
//Flags used by the linker during debug builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/debug /INCREMENTAL
//Flags used by the linker during release minsize builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO
//Flags used by the linker during release builds.
CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING=/INCREMENTAL:NO
//Flags used by the linker during Release with Debug Info builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL
//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=OFF
//If true, cmake will use relative paths in makefiles and projects.
CMAKE_USE_RELATIVE_PATHS:BOOL=OFF
//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make. This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=OFF
//Enable to build NSIS packages
CPACK_BINARY_NSIS:BOOL=ON
//Enable to build ZIP packages
CPACK_BINARY_ZIP:BOOL=OFF
//Enable to build ZIP source packages
CPACK_SOURCE_ZIP:BOOL=ON
//Graphviz Dot tool for using Doxygen
DOXYGEN_DOT_EXECUTABLE:FILEPATH=DOXYGEN_DOT_EXECUTABLE-NOTFOUND
//Doxygen documentation generation tool (http://www.doxygen.org)
DOXYGEN_EXECUTABLE:FILEPATH=DOXYGEN_EXECUTABLE-NOTFOUND
//git command line client
GIT_EXECUTABLE:FILEPATH=GIT_EXECUTABLE-NOTFOUND
//lib directory suffix
LIB_SUFFIX:STRING=
//Path to a program.
PYTHON_EXECUTABLE:FILEPATH=D:/cygwin/bin/python.exe
//Path to a program.
RST2HTML_EXECUTABLE:FILEPATH=RST2HTML_EXECUTABLE-NOTFOUND
//Value Computed by CMake
UHD_BINARY_DIR:STATIC=D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build
//Value Computed by CMake
UHD_SOURCE_DIR:STATIC=D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host
I then go to VC and load the vc solution .I see 6 projects there and I choose
ALL_BUILD to build (in Release mode). But I get the following output(even the
very first time),which makes me feel that nothing is actually built and there
is some problem in the make file itself or I am missing some steps (but how do
I confirm that?)
------ Rebuild All started: Project: ZERO_CHECK, Configuration: Release Win32
------
Checking Build System
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/docs/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/include/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/include/uhd/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/include/uhd/transport/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/include/uhd/types/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/include/uhd/usrp/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/include/uhd/utils/CMakeFiles/generate.stamp
is up-to-date.
CMake does not need to re-run because
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/build/usrp_e_utils/CMakeFiles/generate.stamp
is up-to-date.
------ Rebuild All started: Project: ALL_BUILD, Configuration: Release Win32
------
Building Custom Rule
D:/EttusResearch-UHD-Mirror-4c7cc6b/EttusResearch-UHD-Mirror-4c7cc6b/host/CMakeLists.txt
CMake does not need to re-run because
D:\EttusResearch-UHD-Mirror-4c7cc6b\EttusResearch-UHD-Mirror-4c7cc6b\host\build\CMakeFiles\generate.stamp
is up-to-date.
========== Rebuild All: 2 succeeded, 0 failed, 0 skipped ==========
Also I see no executables or libraries generated from the build...
Regards
Sunil
> -----Original Message-----
> From: [email protected] [mailto:usrp-users-
> [email protected]] On Behalf Of Josh Blum
> Sent: Friday, March 11, 2011 12:48 AM
> To: [email protected]
> Subject: Re: [USRP-users] Heap(memory allocation) errors while building
> rx_samples_to_file utility in windows
>
>
>
> On 03/10/2011 11:03 AM, Chomal, Sunil wrote:
> > Hi, Till now I was using the rx_samples_to_file.exe which I got from
> > the binary packages from http://www.joshknows.com/gnuradio_port for
> > collecting data from USRP N210.(I could not build the gnu radio
> > successfully for windows:()
> >
>
> What was the error?
>
> > Now I am trying to change the rx_samples_to_file utility to enable
> > continuous streaming of data out of usrp N210. In the process ,I am
> > trying to first re-generate the rx_samples_to_file.exe from the
> > source file. I am using the uhd dll and uhd lib,I got from the
> > binary package. Boost dlls I downloaded separately. I was able to
> > generate the exe, but I am facing some, Heap(memory allocation) issue
> > while running the exe. I am using the Visual Studio10 for my work.
> >
>
> The prebuilt stuff is somewhat out of date. Its possible there is an ABI
> difference between the lib and headers used when building the app.
>
> Try to rebuilt uhd from scratch and link your app against the dll/lib
> you just built. Also, make sure everything is built in Release mode.
>
> -Josh
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20110311/22550176/attachment.html>
------------------------------
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
End of USRP-users Digest, Vol 7, Issue 20
*****************************************
