Logging not working in OOT module

2020-06-02 Thread John Langworthy
Hi, On my ubuntu desktop installation using GR 3.8.1.0, my OOT module happily sends its log output to the python console. Perfect. My embedded ubuntu server installation, also GR 3.8.1.0, does not send log output to the console. Messages disappear, somewhere, and I do rather need them. Both were built with log4cpp. I followed the instructions at https://wiki.gnuradio.org/index.php/Logging and have included GrMiscUtils, but the function GR_LOGGING() isn’t in there. The CMakeCache for the OOT finds log4cpp include and library, for both. Advanced properties are identical for both. Its not a python stdout flushing issue, because I’ve tried to manully flush on a timer and run python with -u. I cant see anything weird or different between installations in in gnuradio-runtime.conf or gr_log_default.conf. I’m totally stuck.  Any help very greatly appreciated. Thank you  



Re: Thank You and Congrats

2020-06-02 Thread Marcus Müller

Hi John,

Yay! It seems building a good SDR framework is indeed a bit of rocket 
science.


Cheers,
Marcus

On 31/05/2020 00.53, John Malsbury wrote:

Just wanted to say “thank you” and “congrats”

The cumulative intellect and work products of this community  were seen 
in action by lots of people today (more than ever I think) - whether 
they realize it or not. :)


Ben, I realize that I probably misused a hyphen there.




smime.p7s
Description: S/MIME Cryptographic Signature


Re: scopemeter

2020-06-02 Thread Marcus Müller

Yes!

On 02/06/2020 10.15, Stéphane Ancelot wrote:

Hi,
My question is about using gnuradio as a scopemeter,
I have  files in which have been recorded up to 15 signals during eg 30 
seconds (motion => ref speed, act speed, torque ...) ,

I would like to visualize data and whynot apply some filters
Is this possible ?
Regards,
Stéph




smime.p7s
Description: S/MIME Cryptographic Signature


scopemeter

2020-06-02 Thread Stéphane Ancelot
Hi,
My question is about using gnuradio as a scopemeter,
I have  files in which have been recorded up to 15 signals during eg 30
seconds (motion => ref speed, act speed, torque ...) ,
I would like to visualize data and whynot apply some filters
Is this possible ?
Regards,
Stéph


Re: Building gnuradio and hooking into neonv8

2020-06-02 Thread Johannes Demel

Hi John,

VOLK tries to figure out the correct flags for you. We run CI tests for 
aarch64, so these seem to work. Unless you have a good reason to set 
compiler flags, I'd recommend to stick with what CMake detects for you.


The line `-- CPU is armv8, Overruled arch neonv7` tells you that armv8 
was detected. Thus, we disable neonv7 and enable neonv8 if the compiler 
supports it. On another system you'd see the inverse. We had a 
discussion if it would be reasonable to enable both archs and select the 
correct one during runtime but apparently you either have one arch or 
the other, never both.


Cheers
Johannes

On 30.05.20 14:56, John Langworthy wrote:

Hi Ron,

Just seen your last. I had written this before you sent it, but thought 
worth sharing anyway


Building volk with that toolchain does fail, see directly below. See 
also further down, cmake output from volk without it (which is successful).


(gr_py36) pi@raspberry:~/volk/build$ cmake -DCMAKE_BUILD_TYPE=Release 
-DPYTHON_EXECUTABLE=~/.conda/envs/gr_py36/python3/bin 
-DCMAKE_TOOLCHAIN_FILE=../cmake/Toolchains/arm_cortex_a72_hardfp_native.cmake 
../


-- The C compiler identification is GNU 7.5.0

-- The CXX compiler identification is GNU 7.5.0

-- Check for working C compiler: /usr/bin/gcc

-- Check for working C compiler: /usr/bin/gcc -- broken

CMake Error at /usr/share/cmake-3.10/Modules/CMakeTestCCompiler.cmake:52 
(message):


   The C compiler

     "/usr/bin/gcc"

   is not able to compile a simple test program.

   It fails with the following output:

     Change Dir: /home/pi/volk/build/CMakeFiles/CMakeTmp

 Run Build Command:"/usr/bin/make" "cmTC_ba179/fast"

     /usr/bin/make -f CMakeFiles/cmTC_ba179.dir/build.make 
CMakeFiles/cmTC_ba179.dir/build


     make[1]: Entering directory '/home/pi/volk/build/CMakeFiles/CMakeTmp'

     Building C object CMakeFiles/cmTC_ba179.dir/testCCompiler.c.o

     /usr/bin/gcc   -march=armv8-a -mtune=cortex-a72 -mfpu=neon-fp-armv8 
-mfloat-abi=hard    -o CMakeFiles/cmTC_ba179.dir/testCCompiler.c.o   -c 
/home/pi/volk/build/CMakeFiles/CMakeTmp/testCCompiler.c


     gcc: error: unrecognized command line option ‘-mfpu=neon-fp-armv8’

     gcc: error: unrecognized command line option ‘-mfloat-abi=hard’

     CMakeFiles/cmTC_ba179.dir/build.make:65: recipe for target 
'CMakeFiles/cmTC_ba179.dir/testCCompiler.c.o' failed


     make[1]: *** [CMakeFiles/cmTC_ba179.dir/testCCompiler.c.o] Error 1

     make[1]: Leaving directory '/home/pi/volk/build/CMakeFiles/CMakeTmp'

     Makefile:126: recipe for target 'cmTC_ba179/fast' failed

     make: *** [cmTC_ba179/fast] Error 2

   CMake will not be able to correctly generate this project.

Call Stack (most recent call first):

   CMakeLists.txt:23 (project)

-- Configuring incomplete, errors occurred!

Without the toolchain, I get:

(gr_py36) pi@raspberry:~/volk/build$ cmake -DCMAKE_BUILD_TYPE=Release 
-DPYTHON_EXECUTABLE=~/.conda/envs/gr_py36/bin/python3.6 ../


-- Build type set to Release.

-- Extracting version information from git describe...

--

-- Python checking for python >= 3.4

-- Python checking for python >= 3.4 - found

--

-- Python checking for mako >= 0.4.2

-- Python checking for mako >= 0.4.2 - found

-- Looking for C++ include filesystem

-- Looking for C++ include filesystem - not found

-- Looking for C++ include experimental/filesystem

-- Looking for C++ include experimental/filesystem - found

-- Performing Test CXX_FILESYSTEM_NO_LINK_NEEDED

-- Performing Test CXX_FILESYSTEM_NO_LINK_NEEDED - Failed

-- Performing Test CXX_FILESYSTEM_STDCPPFS_NEEDED

-- Performing Test CXX_FILESYSTEM_STDCPPFS_NEEDED - Success

-- Looking for aligned_alloc

-- Looking for aligned_alloc - found

-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")

-- Checking for module 'orc-0.4 > 0.4.11'

--   No package 'orc-0.4' found

-- orc files (missing: ORC_LIBRARY ORC_INCLUDE_DIR ORCC_EXECUTABLE)

-- Found Doxygen: /usr/bin/doxygen (found version "1.8.13") found 
components:  doxygen missing components:  dot


-- QA Testing is enabled.

--   Modify using: -DENABLE_TESTING=ON/OFF

-- System profiling is disabled.

--   Modify using: -DENABLE_PROFILING=ON/OFF

-- Looking for cpuid.h

-- Looking for cpuid.h - not found

-- Looking for intrin.h

-- Looking for intrin.h - not found

-- Looking for fenv.h

-- Looking for fenv.h - found

-- Looking for dlfcn.h

-- Looking for dlfcn.h - found

-- Compiler name: GNU

-- Performing Test HAVE_WERROR_UNUSED_CMD_LINE_ARG

-- Performing Test HAVE_WERROR_UNUSED_CMD_LINE_ARG - Failed

-- Performing Test have_mfloat_abi_softfp

-- Performing Test have_mfloat_abi_softfp - Failed

-- Performing Test have_mfloat_abi_hard

-- Performing Test have_mfloat_abi_hard - Failed

-- Performing Test have_funsafe_math_optimizations

-- Performing Test have_funsafe_math_optimizations - Success

-- Performing Test have_mfpu_neon

-- Performing Test have_mfpu_neon - Failed

-- Performing Test have_m32

-- Performing Test have