[hpsdr] 20140126cuSDR64 & TK1

Sun Aug 17 20:47:21 PDT 2014

Hi Sid

As I mentioned off list I'm not a fan of Debian based distros because I find apt so difficult to use compared to yum. But by widening my search pattern in apt-cache search I was able to find libfftw3, so I've removed the version I built from sources and installed the package. cuSDR builds OK so I'm happy with that.

Regarding Qt5, I would normally add to PATH but wanted a quick and dirty fix so changing the symlink was favourite. :-)

73, Chris G4NUX

Sent from my iPad

> On 17 Aug 2014, at 23:12, Sid Boyce <g3vbv at blueyonder.co.uk> wrote:
> 
> ***** High Performance Software Defined Radio Discussion List *****
> 
> Hi Chris,
> As mentioned - The first impression is that the TK1 is 64-bit, but it is quad-core 32-bit. It's still a powerful beast, CUDA ensures that.
> 
> The next version apparently due later this year is dual-core 64-bit.
> 
> 20140126_cuSDR64src.tar.gz comes with .o files in bld/o which are compiled x86_64 files, "make clean" will get rid of them, then do "make -j 4".
> 
> Be aware that different distros, Fedora, openSUSE, Ubuntu etc. use different package names so you must refine your search terms.
> Typically all distros provide most stuff so no need to build core applications, libraries or utilities.
> Unless you need a library at a higher level than the distro provides, avoid building and installing what is already provided. You can create deep pits to fall into later, sometimes much later if you are not careful.
> 
> Ubuntu -- apt-cache search fftw.
> Fedora -- yum search fftw.
> openSUSE -- zypper se fftw
> 
> Don't be tempted to enter package names as they may appear in another distro. When in doubt shorten the search string, e.g There are no packages with fftw3 in the name in Fedora while there are many in openSUSE and Ubuntu but again the package names differ.
> # yum search fftw3
> Loaded plugins: langpacks, refresh-packagekit
> Warning: No matches found for: fftw3
> No matches found
> 
> These are the fft libraries installed in Fedora 20.
> # rpm -qa|grep fft
> fftw-libs-quad-3.3.4-3.fc20.x86_64
> fftw-libs-single-3.3.4-3.fc20.x86_64
> fftw-3.3.4-3.fc20.x86_64
> fftw-libs-3.3.4-3.fc20.x86_64
> fftw-libs-double-3.3.4-3.fc20.x86_64
> fftw-devel-3.3.4-3.fc20.x86_64
> fftw-libs-long-3.3.4-3.fc20.x86_64
> 
> Building Qt5, recommend using the instructions for ghpsdr3-alex which work on any platform.
> The instructions on the wiki for building ghpsdr3-alex avoid the use of symlinks, e.g if qt5 is built in /home/fred - "export PATH=/home/fred/qt5/qtbase/bin:$PATH" sets it up to use qt5.
> # qmake -v
> QMake version 3.0
> Using Qt version 5.3.1 in /home/fred/qt5/qtbase/lib
> 73 ... Sid.
> 
>> On 17/08/14 17:37, Chris Smith wrote:
>> ***** High Performance Software Defined Radio Discussion List *****
>> 
>> Hi
>> 
>> Just thought I'd report progress I've made building cuSDR64 on my recently acquired Jetson TK1.
>> 
>> Building Qt-5 was reasonably straightforward. I've been using Qt for some years now, building the libraries from sources under Fedora Linux & OSX. I found the published build instructions using git a bit longwinded but eventually succeeded. Does anyone know what the -j4 option on make does?
>> 
>> Download of the cuSDR source was easy, thanks to Brandt, and, after changing the symlink in /usr/bin so that qmake pointed to the Qt-5 version in /usr/local/Qt-5/bin I could run qmake at the top level of cuSDR to bring the Makefile up to date. I didn't do a make clean so some .o files reported "wrong file type" but removing the 3 offending .o files led me to the next problem - no libfftw3.
>> 
>> I downloaded the source for fftw3 ( wget -c -t0 https://launchpad.net/ubuntu/+archive/primary/+files/fftw3_3.3.3.orig.tar.gz ) and apart from configure requiring a couple of qualifiers ( ./configure --enable-single --enable-shared ) that library built and installed smoothly.
>> 
>> Eventually cuSDR64 built and I could run it on the TK1
>> 
>> It took me a while to find my way around the display (I've not run cuSDR on any platform before) but everything appeared to be working. My Atlas hardware was correctly reported along with ancient f/w versions and I could hear audio from Mercury.
>> 
>> The one problem I'm having is tuning. I don't have a USB mouse with a roller wheel in the shack so the only way I seem to be able to tune is to drag the frequency bar under the display left-right. That is far too crude to tune an individual QSO but got me some audio recognisable as a contact.
>> 
>> One thing which alarms me slightly is that the CPU usage reported is in the range 152-175% I assume that is reporting that more than one core (maybe more than 2) is in use?
>> 
>> Exciting to be able to use my TK1 in anger.
>> 
>> Cheers & 73
>> 
>> Chris G4NUX
>> 
>> 
>> _______________________________________________
>> HPSDR Discussion List
>> To post msg: hpsdr at openhpsdr.org
>> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>> HPSDR web page: http://openhpsdr.org
>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
> 
> 
> -- 
> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
> Senior Staff Specialist, Cricket Coach
> Microsoft Windows Free Zone - Linux used for all Computing Tasks
> 
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/

 1408333641.0