osmocom_fft and osmocom_siggen #34
Comments
|
To access the other binaries under . /Applications/GNURadio.app/Contents/MacOS/usr/bin/grenv.shThe Now you should be able to run other programs in osmocom_fft --helpDoes that work for you? Disclaimer: From my former sys-admin days, I've learned to appreciate zsh, especially for its simplified startup script sequence --- as highlighted in If you do want to modify your shell's startup files, try something like: if test -e /Applications/GNURadio.app/Contents/MacOS/usr/bin/grenv.sh ; then
. /Applications/GNURadio.app/Contents/MacOS/usr/bin/grenv.sh
fiso that if you ever move the GNURadio.app bundle, then your shell won't complain too much. |
|
I've looked at run-grc and I've created run-fft: and run-siggen: I'm getting the option list running ./run-fft -help and ./run-siggen -help With wifi disabled ./run-siggen works: |
|
I don't have any ideas for the crash when wifi is enabled. @cfriedt any ideas? Regarding the small scripts, I have some small fixes for Your script has the right idea, but for those command line tools, try this template: (This won't fix your crash.) #!/bin/sh
. /Applications/GNURadio.app/Contents/MacOS/usr/bin/grenv.sh
exec osmocom_fft "${@}"#!/bin/sh
. /Applications/GNURadio.app/Contents/MacOS/usr/bin/grenv.sh
exec osmocom_siggen "${@}"Summary: (Feel free to ignore or use only pieces of these tips. Use " around ${@} to expand correctly for all input arguments, such as spaces or whatever. Use If you'd like a single script to let you run any of the commands in /Applications/GNURadio.app/Contents/MacOS/usr/bin, then try saving this file to #!/bin/sh
prog="$1"
# shift will drop $1 and shift over the rest of the args so $2 becomes $1, $3 becomes $2, etc...
shift
. /Applications/GNURadio.app/Contents/MacOS/usr/bin/grenv.sh
exec "${prog}" "${@}"Then you should be able to run ~/gr osmocom_fft --help
~/gr osmocom_siggen --helpThe nifty part of restructuring your scripts like this (using exec, no &, and " around $@), is that now if you wanted to automate setting up your project, you can write a master script to launch your subprocesses, keeping track of their child PID's, and killing them when you're done. #!/bin/sh
# Launch osmocom_siggen in background and save its pid:
~/gr osmocom_siggen --some --args &
pid_siggen=$!
# Launch osmocom_fft in background and save its pid:
~/gr osmocom_fft --some --other --args &
pid_fft=$!
# do other stuff, collect your data, etc...
# now shut down:
kill $pid_siggen $pid_fftThis job control wouldn't be possible if the Sorry I won't be of much help to resolve the crash when wireless is enabled, but I hope the scripting pointers will help build empires. |
|
@dholl thank you so much for your help now when I try to run osmocom_siggen sometimes it works (even with wifi enabled) sometimes it crashes (even with wifi disabled), this is the crash window: |
|
Eeck, this looks very similar to #22 . @cfriedt , Any luck with your crash diagnostics? Do you think your troubles and @gilbertoverg's are related? (I develop my own hardware, and don't have other vendors' hardware to poke at the moment... Do I need any special hardware to try reproducing this crash on my own? What's a minimal test I could try?) |
Closed
|
I'm using an hackrf to test osmocom_siggen and osmocom_fft, I can also test osmocom_fft with an airspy. I'm getting the crash 1 second after running the script |
|
This is interesting: if I remove the two check marks from the xquartz security settings, osmocom_siggen crashes far more often than having only the "authenticate connections" enabled |
|
This is more interesting: I'm running wireshark listening the loopback interface, when osmocom_siggen starts correctly this is what I'm getting: |
|
I've temporary disabled the loopback interface with |
|
@dholl you can reproduce this crash without any special hardware, simply try to run osmocom_siggen with no arguments, if it works it prints: if it crashes: |
|
@cfriedt I'm still not able to run osmocom_fft, this is what I'm getting: |
|
@gilbertoverg pull requests are welcome. |
|
@cfriedt after a long day I found a fix for osmocom_fft (I'm not a python programmer): |
|
Nice! I feel your pain - I'm also not too happy with Python, but it seems to be what all the hip kids are using these days ;-) |
|
Closing due to inactivity, and because the stack trace referenced was fixed in PR #48 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I can see that osmocom_fft and osmocom_siggen are present inside /GNURadio.app/Contents/MacOS/usr/
How can I run both?
Thank you
The text was updated successfully, but these errors were encountered: