Re: [Discuss-gnuradio] Volk machine: ssse3_32 segmentation faults (was RE: How to diagnose make test failures)

2013-04-25 Thread Barry Jackson 

On 24/04/13 22:09, Johnathan Corgan wrote:

On Wed, Apr 24, 2013 at 1:56 PM, Johnathan Corgan
 wrote:

On Wed, Apr 24, 2013 at 10:50 AM, Brian Stamper  wrote:


114: AssertionError: 39 != 31
114: AssertionError: 0.8 != 0.0 within 4 places


Now that's just being unreasonable :)

Actually, I recall seeing these same failures sometime in the past,
and am looking around to see if I can find the reference.


This was reported last January in the course of a thread related to
failures with Boost 1.5.2:

https://lists.gnu.org/archive/html/discuss-gnuradio/2013-01/msg00360.html

It's not clear what there is in common with your system and the one
having the issue there, but you might review that whole thread and see
if anything jumps out at you.

Hi folks - all my tests in that thread were on x86_64 and we have since 
moved to boost-1.53 which has resolved most of those issues.


I am following this thread with interest as we now have errors in i586 
builds (Brian - I added details to your other thread that got no response)

https://lists.gnu.org/archive/html/discuss-gnuradio/2013-04/msg00455.html

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

[Discuss-gnuradio] IIR filter

2013-04-25 Thread Chuck Ritola 
Does anyone have a working example of the IIR filter block in GNU
Radio Companion that I can see, and the filter designer app, table, or
equation which generated the coefficients?

The GRC documentation states "fftaps and fbtaps must have equal
numbers of taps", however biquad IIRs traditionally have three B
coefficients (feed forward) and 2 A coefficients (feed backward). This
conflicts with the 'Direct Form 1' shown here:
https://en.wikipedia.org/wiki/Digital_biquad_filter

Is b0 already implied to be set to 1 automatically, with the
expectation that I would normalize all values to b0?

Or, do I need to specify b0, then for the A coeffs put a zero as a placefiller?

Negating A coeffs doesn't appear fix the issue in either case.

Also, I noticed that if I set an unequal number of coefficients (in
violation of the docs) there still is no error. (it still doesn't work
though)

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

Re: [Discuss-gnuradio] IIR filter

2013-04-25 Thread Sreeraj Rajendran 


>Does anyone have a working example of the IIR filter block in GNU
>Radio Companion that I can see, and the filter designer app, table, or
>equation which generated the coefficients?

Could you try grc files attached in 
http://lists.gnu.org/archive/html/discuss-gnuradio/2012-08/msg00128.html. I 
think those were tested with gnuradio-3.6.1.

You can either use gr_filter_design tool (new version) or scipy functions 
(scipy.signal.iirdesign/scipy.signal.iirfilter) for designing IIR filters.

>Negating A coeffs doesn't appear fix the issue in either case.

To know more about the negation of  "a coeffs" please follow this thread: 
http://www.ruby-forum.com/topic/4408052.

-Sreeraj___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Power_cycling USRP N200

2013-04-25 Thread Zooz Engineer 
Dear All,


I am working on USRP N200 and sometimes I access them through a remote desktop. 
However, when a problem happens and I need to power cycle the boards, I have to 
do that physically. Is there any method that I can execute a program or a 
command to power cycle the boards?


Thanks,


Zohair




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

Re: [Discuss-gnuradio] Volk machine: ssse3_32 segmentation faults (was RE: How to diagnose make test failures)

2013-04-25 Thread Brian Stamper 
On Thu, Apr 25, 2013 at 4:43 AM, Barry Jackson  wrote:
> On 24/04/13 22:09, Johnathan Corgan wrote:
[snip]
>>
>> This was reported last January in the course of a thread related to
>> failures with Boost 1.5.2:
[snip]
> Hi folks - all my tests in that thread were on x86_64 and we have since
> moved to boost-1.53 which has resolved most of those issues.
>
> I am following this thread with interest as we now have errors in i586
> builds (Brian - I added details to your other thread that got no response)
> https://lists.gnu.org/archive/html/discuss-gnuradio/2013-04/msg00455.html
>

Thank you Johnathan, and that's great news, Barry. My system reports
boost-1.48, which I thought would be okay based on this dependency
list, as referenced in the build instructions:
http://gnuradio.org/doc/doxygen/build_guide.html which says boost
>=1.35.

I'll have to try a manual upgrade of boost and run some of my
tests/volk_configs again and report back.

Brian

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

Re: [Discuss-gnuradio] GSOC ideas [802.11]

2013-04-25 Thread 2_...@libero.it 
Hi guys,
I've a question(maybe this is spam): I'm thinking about my proposal,where I 
want move some part on cuda( in this way,you can also see/verify the difference 
in term of performance). Is cuda okay for you, or do you prefer openCL?

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

Re: [Discuss-gnuradio] GSOC ideas [802.11]

2013-04-25 Thread Martin Braun (CEL) 
On Thu, Apr 25, 2013 at 04:38:19PM +0200, 2_...@libero.it wrote:
> Hi guys,
> I've a question(maybe this is spam): I'm thinking about my proposal,where I 

As long as you don't want an investment of 100 from us, it's
probably not spam :)

> want move some part on cuda( in this way,you can also see/verify the 
> difference 
> in term of performance). Is cuda okay for you, or do you prefer openCL?

I'm not sure you will be able to do either for this project. Have you
checked the mailing list archives? Getting GPU-based processing into a
GNU Radio flowgraph is quite hard, given the structure of the
scheduler. Also, which elements are you hoping to accelerate?

To answer your question, the more portable, the better, so my gut says
OpenCL > CUDA.

MB

-- 
Karlsruhe Institute of Technology (KIT)
Communications Engineering Lab (CEL)

Dipl.-Ing. Martin Braun
Research Associate

Kaiserstraße 12
Building 05.01
76131 Karlsruhe

Phone: +49 721 608-43790
Fax: +49 721 608-46071
www.cel.kit.edu

KIT -- University of the State of Baden-Württemberg and
National Laboratory of the Helmholtz Association


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

Re: [Discuss-gnuradio] Master build failure for ARM when building cross

2013-04-25 Thread Philip Balister 
On 04/24/2013 02:18 PM, Johnathan Corgan wrote:
> On Wed, Apr 24, 2013 at 10:56 AM, Philip Balister  wrote:
> 
>> I've been trying to find something in next that did not propagate
>> through from the fix and am not having any luck finding it.
> 
> Thanks for all the version testing.  I'll be working on this today.
> 

I did one last test using OE. I did builds for the qemux86 and
qemux86-64 machines. Only the x86-64 gnuradio-next build succeeded.

Looks like next has an issue on 32 bit builds.

Philip

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

Re: [Discuss-gnuradio] IIR filter

2013-04-25 Thread Sreeraj Rajendran 


>Thanks for the example links, they were very helpful. There were two
>things I was doing wrong: First I didn't use square brackets for the
>sets, and to use the biquad calculator featured on earlevel.com, the B
>coefficients needed to start with a 1.0 filler and the rest negated
>like this:
>
>Feed-forward taps: [a0,a1,a2]
>Feedback taps: [1,-b1,-b2]

>The linked .grc files work for me. (GRP 4.6.1) The filters therein
>behave as expected.

>Where is the new version?
>https://github.com/gnuradio/gnuradio/blob/next/gr-filter/python/design/filter_design.py
>This one turns my cursor into a crosshair and does nothing else until I kill 
>it.

Try launching gr_filter_design in apps 
(https://github.com/gnuradio/gnuradio/tree/next/gr-filter/apps/)

>The link you sent mentioned a new version but I haven't found it;
>googling "gr_filter_design" doesn't bring it up. I just see the
>FIR-only versions.

Default "gr_filter_design" in "next" branch supports IIR filter design. Also 
have a look at examples folder (gr_filtdes_*). 


-Sreeraj___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] usrp_spectrum sense

2013-04-25 Thread Mike Jameson 
Hi Azim,

This seems to work for me, just update the function on line 265 with the
following two lines:

power_db = float(20*math.log10(power))
print freq, power, power_db

Cheers,

Mike

--
Mike Jameson M0MIK BSc MIET
Email: m...@scanoo.com
Web: http://scanoo.com


On 22 April 2013 03:57, Aziem Aziem  wrote:

> hi mike,
>
> how can i convert the m.data in usrp spectrum sense in dB
>
> log = gr.nlog10_ff(10, self.fft_size,
> -20*math.log10(self.fft_size)-10*math.log10(power/self.fft_size))
>
> not clear with it... any suggestion?
>
> tq
>
> azim
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Error in Building UHD on Windows

2013-04-25 Thread Zooz Engineer 



Dear All,

I am trying to install UHD on windows from source code. I have installed the 
prerequisites:

cmake-2.8.10.2-win32-x86
boost_1_51_setup32
python-2.6.6
Cheetah-2.2.2.win32-py2.6
msysGit-fullinstall-1.8.1.2-preview20130201
Visual studio 2010 express

I follwowed the steps detailed here: 
http://files.ettus.com/uhd_docs/manual/html/build.html#build-instructions-windows.
 After applying the fifth step in CMake I get the following error message. 

Do you have any idea why this is happening?

Thank you,

Zo

The C compiler identification is MSVC 16.0.30319.1
The CXX compiler identification is MSVC 16.0.30319.1
Check for working C compiler using: Visual Studio 10
Check for working C compiler using: Visual Studio 10 -- broken
CMake Error at C:/Program Files (x86)/CMake 
2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message):
  The C compiler "C:/Program Files (x86)/Microsoft Visual Studio
  10.0/VC/bin/cl.exe" is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: C:/UHD/host/build/CMakeFiles/CMakeTmp

  

  Run Build Command:C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
  cmTryCompileExec215809703.vcxproj /p:Configuration=Debug
  /p:VisualStudioVersion=10.0

  Microsoft (R) Build Engine version 4.0.30319.17929

  [Microsoft .NET Framework, version 4.0.30319.18034]

  Copyright (C) Microsoft Corporation.  All rights reserved.

  

  Build started 25/04/2013 21:57:38.

  Project
  "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
  on node 1 (default targets).

  PrepareForBuild:

Creating directory "cmTryCompileExec215809703.dir\Debug\".
Creating directory "C:\UHD\host\build\CMakeFiles\CMakeTmp\Debug\".

  InitializeBuildStatus:

Creating 
"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.unsuccessfulbuild"
 because "AlwaysCreate" was specified.

  ClCompile:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\CL.exe /c /Zi 
/W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D 
"CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t 
/Zc:forScope /Fo"cmTryCompileExec215809703.dir\Debug\\" 
/Fd"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb" 
/Gd /TC /analyze- /errorReport:queue testCCompiler.c  /Zm1000 
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01 for 
80x86
Copyright (C) Microsoft Corporation.  All rights reserved.

cl /c /Zi /W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D 
"CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t 
/Zc:forScope /Fo"cmTryCompileExec215809703.dir\Debug\\" 
/Fd"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb" 
/Gd /TC /analyze- /errorReport:queue testCCompiler.c  /Zm1000 

testCCompiler.c

  ManifestResourceCompile:

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\rc.exe /nologo 
/fo"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.embed.manifest.res"
 cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703_manifest.rc 

  Link:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\link.exe 
/ERRORREPORT:QUEUE 
/OUT:"C:\UHD\host\build\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec215809703.exe"
 /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib 
shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST 
/ManifestFile:"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.intermediate.manifest"
 /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG 
/PDB:"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb"
 /SUBSYSTEM:CONSOLE /STACK:"1000" /TLBID:1 /DYNAMICBASE /NXCOMPAT 
/IMPLIB:"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.lib"
 /MACHINE:X86 
cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.embed.manifest.res
cmTryCompileExec215809703.dir\Debug\testCCompiler.obj  /machine:X86 /debug 

  LINK : fatal error LNK1123: failure during conversion to COFF: file invalid
  or corrupt
  [C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj]

  Done Building Project
  "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
  (default targets) -- FAILED.

  

  Build FAILED.

  

  "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
  (default target) (1) ->

  (Link target) -> 

LINK : fatal error LNK1123: failure during conversion to COFF: file invalid 
or corrupt 
[C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj]

  

  0 Warning(s)
  1 Error(s)

  

  Time Elapsed 00:00:00.64

  

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  


CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

cmake_minimum_required(VERSION 2.8)

[Discuss-gnuradio] Fwd: USRP1 control GPIOs on SBX boards

2013-04-25 Thread Nelson Pina 
Hi Sean,

thanks for your feedback.. I'm still trying to get this working but the
problem persists. Every time I use the "uhd::device_addr_t addr" class
necessary to initialize an "uhd::usrp::multi_usrp::make" object, the GRC
program fails.

Do I need to do something in the swig.i or the Python files to
use "uhd::device_addr_t addr" class? I will send you my .cc and .h files,
y«if you can take a look on those I will be very thankful.

Thanks again.

Best regards,

*Nelson Pina*
Product Developer
Hardware










*n.p...@tomorrow-options.com*
*T* +351 220 301 596 (PT)
*T* +44 114 213 2712 (UK)

*www.tomorrow-options.com
*Porto // Portugal
Sheffield // United Kingdom



 
  




On Tue, Apr 23, 2013 at 8:31 PM, Sean Nowlan wrote:

>  On 04/23/2013 02:06 PM, Nelson Pina wrote:
>
>Hi everyone,
>
>  I have been trying to make a gnuradio out-of-the-tree block that is able
> to control the four GPIOs, currently attached to LED's, of the SBX
> daughter-boards working with an USRP motherboard.
>
>  I wonder if anyone can help me on this, making a functional draft code of
> such a block:
>
>  1 integer input - that will define the state of the GPIOs
>  1 parameter - to define the motherboard serial number
>
>  I believe that for people with knowledge of C++, and Python this is a
> very simple module, unfortunately that is not my area since I'm a hardware
> engineer and I only work with C.
>
>  I tried some approaches, using the gr_modtool to create the module, but
> it always fails with GRC running errors like:
>
> **
>
> Traceback (most recent call last):
>   File
> "/home/to-nelsonpina/Desktop/locus_gnuradio/GRC_files/top_block.py", line
> 16, in 
> import gpio
>   File "/usr/local/lib/python2.7/dist-packages/gpio/__init__.py", line 45,
> in 
> from gpio_swig import *
>   File "/usr/local/lib/python2.7/dist-packages/gpio/gpio_swig.py", line
> 26, in 
> _gpio_swig = swig_import_helper()
>   File "/usr/local/lib/python2.7/dist-packages/gpio/gpio_swig.py", line
> 22, in swig_import_helper
> _mod = imp.load_module('_gpio_swig', fp, pathname, description)
> ImportError: /usr/local/lib/libgnuradio-gpio.so: undefined symbol:
> _ZN3uhd4usrp10multi_usrp4makeERKNS_13device_addr_tE
>
> *
>
>
> This is most likely a failure to define the SWIG header file
> appropriately, or possibly you've _declared_ a class that SWIG found but
> you haven't _defined_ it. Finally because I just found this out the hard
> way, if you're using the new code structure with block.h, block_impl.h, and
> block_impl.cc, be aware that block.h needs to declare an abstract class and
> its method declarations need to be pure virtual. block_impl.h declares the
> concrete class and block_impl.cc provides concrete method definitions.
>
> If you want to unmangle that symbol, type this:
>
> c++filt _ZN3uhd4usrp10multi_usrp4makeERKNS_13device_addr_tE
>
> I will appreciate all the help I can get from you guys.
>
>  Best regards,
>  __
>*Nelson Pina*
> Product Developer
> Hardware
>
>
>
>
>
>
>
>
>
>
> *n.p...@tomorrow-options.com*
> *T* +351 220 301 596 (PT)
> *T* +44 114 213 2712 (UK)
>
> *www.tomorrow-options.com
> *Porto // Portugal
> Sheffield // United Kingdom
>
>     
> 
>  
>      
> 
>
>
>
> ___
> Discuss-gnuradio mailing 
> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>


locus_gpio_vv.cc
Description: Binary data
/* -*- c++ -*- */
/* 
 * Copyright 2013 <+YOU OR YOUR COMPANY+>.
 * 
 * This is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation; either version 3, or (at your option)
 * any later version.
 * 
 * This software is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this software; see the file COPYING.  If not, write to
 * the Free Software Foundation, Inc., 51 Franklin Street,
 * Boston, MA 02110-1301, USA.
 */


#ifndef INCLUDED_LOCUS_GPIO_VV_H
#define INCLUDED_LOCUS_GPIO_

Re: [Discuss-gnuradio] Error in Building UHD on Windows

2013-04-25 Thread Zooz Engineer 
I think I am missing something in the build variables. What are the variables 
that need to be set?

Cheers,
Zo

From: xtmpcvs...@hotmail.com
To: discuss-gnuradio@gnu.org
Subject: Error in Building UHD on Windows
Date: Thu, 25 Apr 2013 20:27:38 +







Dear All,

I am trying to install UHD on windows from source code. I have installed the 
prerequisites:

cmake-2.8.10.2-win32-x86
boost_1_51_setup32
python-2.6.6
Cheetah-2.2.2.win32-py2.6
msysGit-fullinstall-1.8.1.2-preview20130201
Visual studio 2010 express

I follwowed the steps detailed here: 
http://files.ettus.com/uhd_docs/manual/html/build.html#build-instructions-windows.
 After applying the fifth step in CMake I get the following error message. 

Do you have any idea why this is happening?

Thank you,

Zo

The C compiler identification is MSVC 16.0.30319.1
The CXX compiler identification is MSVC 16.0.30319.1
Check for working C compiler using: Visual Studio 10
Check for working C compiler using: Visual Studio 10 -- broken
CMake Error at C:/Program Files (x86)/CMake 
2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message):
  The C compiler "C:/Program Files (x86)/Microsoft Visual Studio
  10.0/VC/bin/cl.exe" is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: C:/UHD/host/build/CMakeFiles/CMakeTmp

  

  Run Build Command:C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
  cmTryCompileExec215809703.vcxproj /p:Configuration=Debug
  /p:VisualStudioVersion=10.0

  Microsoft (R) Build Engine version 4.0.30319.17929

  [Microsoft .NET Framework, version 4.0.30319.18034]

  Copyright (C) Microsoft Corporation.  All rights reserved.

  

  Build started 25/04/2013 21:57:38.

  Project
  "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
  on node 1 (default targets).

  PrepareForBuild:

Creating directory "cmTryCompileExec215809703.dir\Debug\".
Creating directory "C:\UHD\host\build\CMakeFiles\CMakeTmp\Debug\".

  InitializeBuildStatus:

Creating 
"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.unsuccessfulbuild"
 because "AlwaysCreate" was specified.

  ClCompile:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\CL.exe /c /Zi 
/W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D 
"CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t 
/Zc:forScope /Fo"cmTryCompileExec215809703.dir\Debug\\" 
/Fd"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb" 
/Gd /TC /analyze- /errorReport:queue testCCompiler.c  /Zm1000 
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01 for 
80x86
Copyright (C) Microsoft Corporation.  All rights reserved.

cl /c /Zi /W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D 
"CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise /Zc:wchar_t 
/Zc:forScope /Fo"cmTryCompileExec215809703.dir\Debug\\" 
/Fd"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb" 
/Gd /TC /analyze- /errorReport:queue testCCompiler.c  /Zm1000 

testCCompiler.c

  ManifestResourceCompile:

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\rc.exe /nologo 
/fo"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.embed.manifest.res"
 cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703_manifest.rc 

  Link:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\link.exe 
/ERRORREPORT:QUEUE 
/OUT:"C:\UHD\host\build\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec215809703.exe"
 /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib 
shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST 
/ManifestFile:"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.intermediate.manifest"
 /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG 
/PDB:"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb"
 /SUBSYSTEM:CONSOLE /STACK:"1000" /TLBID:1 /DYNAMICBASE /NXCOMPAT 
/IMPLIB:"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.lib"
 /MACHINE:X86 
cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.embed.manifest.res
cmTryCompileExec215809703.dir\Debug\testCCompiler.obj  /machine:X86 /debug 

  LINK : fatal error LNK1123: failure during conversion to COFF: file invalid
  or corrupt
  [C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj]

  Done Building Project
  "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
  (default targets) -- FAILED.

  

  Build FAILED.

  

  "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
  (default target) (1) ->

  (Link target) -> 

LINK : fatal error LNK1123: failure during conversion to COFF: file invalid 
or corrupt 
[C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj]

  

  0 Warning(s)
  1 Error(s)

  

  Time Elapsed 00:00:00.64

Re: [Discuss-gnuradio] Error in Building UHD on Windows

2013-04-25 Thread Josh Blum 


On 04/25/2013 03:27 PM, Zooz Engineer wrote:
> 
> 
> 
> Dear All,
> 
> I am trying to install UHD on windows from source code. I have
> installed the prerequisites:
> 
> cmake-2.8.10.2-win32-x86 boost_1_51_setup32 python-2.6.6 
> Cheetah-2.2.2.win32-py2.6 
> msysGit-fullinstall-1.8.1.2-preview20130201 Visual studio 2010
> express
> 
> I follwowed the steps detailed here:
> http://files.ettus.com/uhd_docs/manual/html/build.html#build-instructions-windows.
> After applying the fifth step in CMake I get the following error
> message.
> 
> Do you have any idea why this is happening?
> 

If you google for "failure during conversion to COFF: file invalid",
have tried any of the things suggested in the stack overflow forums?

Many of the posts seem to indicate that its a visual studio 2012
stomping on files in 2010 or some .net installer doing something similar.

-josh

> Thank you,
> 
> Zo
> 
> The C compiler identification is MSVC 16.0.30319.1 The CXX compiler
> identification is MSVC 16.0.30319.1 Check for working C compiler
> using: Visual Studio 10 Check for working C compiler using: Visual
> Studio 10 -- broken CMake Error at C:/Program Files (x86)/CMake
> 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:61 (message): 
> The C compiler "C:/Program Files (x86)/Microsoft Visual Studio 
> 10.0/VC/bin/cl.exe" is not able to compile a simple test program.
> 
> It fails with the following output:
> 
> Change Dir: C:/UHD/host/build/CMakeFiles/CMakeTmp
> 
> 
> 
> Run Build
> Command:C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe 
> cmTryCompileExec215809703.vcxproj /p:Configuration=Debug 
> /p:VisualStudioVersion=10.0
> 
> Microsoft (R) Build Engine version 4.0.30319.17929
> 
> [Microsoft .NET Framework, version 4.0.30319.18034]
> 
> Copyright (C) Microsoft Corporation.  All rights reserved.
> 
> 
> 
> Build started 25/04/2013 21:57:38.
> 
> Project 
> "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
>
> 
on node 1 (default targets).
> 
> PrepareForBuild:
> 
> Creating directory "cmTryCompileExec215809703.dir\Debug\". Creating
> directory "C:\UHD\host\build\CMakeFiles\CMakeTmp\Debug\".
> 
> InitializeBuildStatus:
> 
> Creating
> "cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.unsuccessfulbuild"
> because "AlwaysCreate" was specified.
> 
> ClCompile:
> 
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\CL.exe /c
> /Zi /W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D
> "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise
> /Zc:wchar_t /Zc:forScope /Fo"cmTryCompileExec215809703.dir\Debug\\"
> /Fd"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb"
> /Gd /TC /analyze- /errorReport:queue testCCompiler.c  /Zm1000 
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01
> for 80x86 Copyright (C) Microsoft Corporation.  All rights reserved.
> 
> cl /c /Zi /W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D
> "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /RTC1 /MDd /GS /fp:precise
> /Zc:wchar_t /Zc:forScope /Fo"cmTryCompileExec215809703.dir\Debug\\"
> /Fd"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb"
> /Gd /TC /analyze- /errorReport:queue testCCompiler.c  /Zm1000
> 
> testCCompiler.c
> 
> ManifestResourceCompile:
> 
> C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\rc.exe
> /nologo
> /fo"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.embed.manifest.res"
> cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703_manifest.rc
> 
> 
> Link:
> 
> C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\link.exe
> /ERRORREPORT:QUEUE
> /OUT:"C:\UHD\host\build\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec215809703.exe"
> /INCREMENTAL /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib
> shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib
> /MANIFEST
> /ManifestFile:"cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.intermediate.manifest"
> /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG
> /PDB:"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.pdb"
> /SUBSYSTEM:CONSOLE /STACK:"1000" /TLBID:1 /DYNAMICBASE /NXCOMPAT
> /IMPLIB:"C:/UHD/host/build/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec215809703.lib"
> /MACHINE:X86
> cmTryCompileExec215809703.dir\Debug\cmTryCompileExec215809703.exe.embed.manifest.res
>
> 
cmTryCompileExec215809703.dir\Debug\testCCompiler.obj  /machine:X86 /debug
> 
> LINK : fatal error LNK1123: failure during conversion to COFF: file
> invalid or corrupt 
> [C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj]
>
>  Done Building Project 
> "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
>
> 
(default targets) -- FAILED.
> 
> 
> 
> Build FAILED.
> 
> 
> 
> "C:\UHD\host\build\CMakeFiles\CMakeTmp\cmTryCompileExec215809703.vcxproj"
>
> 
(default target) (1) ->
> 
> (Link target) ->
> 
> LINK : fatal error LNK1123: failure du

Re: [Discuss-gnuradio] USRP1 control GPIOs on SBX boards

2013-04-25 Thread Josh Blum 

> _mod = imp.load_module('_gpio_swig', fp, pathname, description)
> ImportError: /usr/local/lib/libgnuradio-gpio.so: undefined symbol:
> _ZN3uhd4usrp10multi_usrp4makeERKNS_13device_addr_tE
> 


I think this would indicate that this swig module was not linked against
UHD. There is a GR_SWIG_LIBRARIES variable that needs to have
${UHD_LIBRARIES} in it.

-josh

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

Re: [Discuss-gnuradio] Installing GNU Radio: Use binaries!

2013-04-25 Thread Arturo Rinaldi 

Il 19/04/13 11:21, Martin Braun (CEL) ha scritto:

Hi all,

one point of yesterday's developer's call was the available binaries.

A while back, installing GNU Radio meant installing it from source.
Anything else wasn't really an option, which is why Marcus wrote
build-gnuradio to make that as painless as possible.

Things have changed! I would like to point out the fantastic work that
has been done by Maitland, who makes our Debian (and therefore Ubuntu)
packages, as well as the guys from Ettus, who host binaries for Ubuntu,
Fedora and Windows.

Nowadays, you don't need to install from source. In fact, if you're new
to all of this, we recommend you don't. If you install from binaries,
you have a GNU Radio version that's just fine.

There's only one caveat: On some systems, the distributed packages might
be a bit too old. If it's older than 3.6.0, installing by hand is
better.

Of course, if you're a developer and need the latest and greatest
features, you can still use our git or tarballs. But if you're just
trying it all out, just make your own life easier by using the binaries.

Hopefully we can get rid of the myth that GNU Radio is hard to install!

MB



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Hi Martin, sorry to bother you. I was wondering if there is a way to 
build the deb from the source tarball. I made some time an attemp with 
the following commands :


$ mkdir build
$ cd build
$ cmake -DCPACK_GENERATOR=deb ../
$ make package

and i almost was successful in doing that, however i had some issues 
with the control version and the correct naming of the file. I am asking 
this because binaries for ubuntu 13.04 are not still available and i'd 
like to build one on my own.are these ones I've listed all the 
correct steps to perform to build a binary file of gnuradio or not ?


Thank you in advance

Kind  Regards,

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

Re: [Discuss-gnuradio] Installing GNU Radio: Use binaries!

2013-04-25 Thread Johnathan Corgan 
On Thu, Apr 25, 2013 at 3:56 PM, Arturo Rinaldi  wrote:


> Hi Martin, sorry to bother you. I was wondering if there is a way to build
> the deb from the source tarball. I made some time an attemp with the
> following commands :
>
> $ mkdir build
> $ cd build
> $ cmake -DCPACK_GENERATOR=deb ../
> $ make package
>
> and i almost was successful in doing that, however i had some issues with
> the control version and the correct naming of the file. I am asking this
> because binaries for ubuntu 13.04 are not still available and i'd like to
> build one on my own.are these ones I've listed all the correct steps to
> perform to build a binary file of gnuradio or not ?
>

The CMake package infrastructure inside the GNU Radio source code tree is
maintained and supported by Ettus Research, which also distributes their
generated .deb files on their website as a free service to the GNU Radio
community.  The official GNU Radio packages for Debian (that also get
picked up by Ubuntu) are maintained by Maitland Bottoms, who has published
his packaging tools repository on the list here.

If you have been using the Ubuntu packages in the past, I recommend you use
Maitland's scripts, as the two different approaches to package generation
are not compatible.

-- 
Johnathan Corgan
Corgan Labs - SDR Training and Development Services
http://corganlabs.com
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] TDMA Engine Error

2013-04-25 Thread Josh Blum 

>   File "/home/s/tdm/tdma_radio.py", line 70, in __init__
> freq=freq,
>   File "/home/s/.grc_gnuradio/tdma_hier.py", line 76, in __init__
> self.tdma_engine =
> precog.tdma_engine(initial_slot,slot_interval,guard_interval,number_of_slots,lead_limit,link_speed)
>   File "/usr/local/lib/python2.7/dist-packages/precog/tdma_engine.py", line
> 100, in __init__
> self.set_tag_propagation_policy(extras_swig.TPP_DONT)
> NameError: global name 'extras_swig' is not defined
> 

Looks like an import got removed from that file, but I dont think its
needed.

try changing this trouble line to

self.set_tag_propagation_policy(gnuradio.extras.TPP_DONT)

Or if that doesnt work

from gnuradio import extras
self.set_tag_propagation_policy(extras.TPP_DONT)

-josh

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