-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS Sonoma Crash #1011
Comments
Same for me: Crashed Thread: 14 Dispatch queue: CA DispatchGroup Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x24a is not in any region. Bytes before following region: 140737488227766 |
Mac Mini M1, Sonoma. PC register does not match crashing frame (0x0 vs 0x100D2D2D0) Crashed Thread: 35 Dispatch queue: CA DispatchGroup Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x24a is not in any region. Bytes before following region: 140722850856374 Error Formulating Crash Report: |
2021 Macbook Pro M1, upgraded to Sonoma and now CubicSDR crashes at startup with similar message the others have already posted: Notes: Crashed Thread: 15 Dispatch queue: CA DispatchGroup Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 |
same on 2019 MBP upgraded to Sonoma |
Same here 2020 MBP after Sonoma upgrade, reopen doesn't take Process: CubicSDR [1801] Date/Time: 2023-10-15 10:39:53.9834 -0700 Sleep/Wake UUID: 13F80E1B-2976-4E1E-87EC-1DD6E5E92760 Time Awake Since Boot: 15000 seconds System Integrity Protection: enabled Crashed Thread: 3 Dispatch queue: CA DispatchGroup Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 |
Same on iMac Intel i7 |
Tried compiling it from scratch this morning and it works again for me. You'll need all of the dependencies installed first but usually I do this for a new C/C++ project on MacOS:
If that doesn't report any errors then just run
And see if there's a package for it. If there is I install it and try again. And that's how I got CubicSDR running on my machine. It's awful, but it works. |
Since the current unreleased version seems to be without this bug (and I can't manage to build it myself), would it make sense to create a new release? After all, the old one is already over 1.5 years old. @cjcliffe |
Agreed with cixio. I can't seem to get that built, either. A new version release would be very much appreciated. |
+1 on OP, will try building |
Never mind, I can't figure out these dependencies. |
For any still interested, 0.2.3 opens right away for me on Sonoma. Try that one! |
And I'll confirm that, v0.2.3 works fine on Sonoma (M1 Macbook Pro). |
Without looking at any of the code, my first guess would be dependency updates, but take that with a grain of salt. |
Thanks, works also on my 2021 14'' M1 Pro
The actual code works also great (if you build it yourself), but I couldn't get the soapy modules running as I dont understand the build manual. |
This covered my attempt: brew install cmake liquid-dsp wxwidgets … but I'm not sure what I already had installed that might have helped. Anyhow, got b959ff compiled and working on macOS "Sonoma" 14.2 (23C64). |
Just finished building v0.2.8 for Apple ARM, if somebody want to give it a try https://github.com/radito/CubicSDR/releases/tag/0.2.8 |
Okay thanks, i'm taking a look into it. |
Can confirm using RSP1A on Mac M1 Pro with latest OS. Also have RTL-SDR V4 and HF+ Discovery to test with if needed. |
CubicSDR build with added SoapySDR Bundle config If there's a macOS error ignore it, just right click -> open Feedback would be useful to validate if the issue is fixed. |
can you try
see if that helps ? |
Thanks for the suggestion, I had hoped it would help, but... |
Sorry, after digging more in the build system just figure it out my soapy sdr isn't in this build directory, because it's referenced using homebrew Need some adjustment, hope it will be fixed. |
Umm, apologies, but... are you asking me to run that command in shell, or just thinking out loud what you're going to do to make another build? |
No, you're fine. Because rn im using soapySDR from homebrew and it's referenced in another directory. maybe that's what's causing the problem. |
So i have 3 different SDR's. one is the SDRPlay1a. I have both API installed.. the 2.x and the 3.x. Long way of saying that one of those installed Soapy along with it. I think it was the 2.x API. its installed here by default /usr/local/bin/SoapySDRUtil ~ % SoapySDRUtil --probe Soapy SDR -- the SDR abstraction library###################################################### Probe device -- Device identificationdriver=SDRplay I also have a RTL-SDR V4 and Airspy HF+ Discovery to test anything with if needed. |
https://github.com/radito/CubicSDR/releases/tag/0.2.8-3 0.2.8-3 build I hope it works |
BINGO! I had to allow some exceptions thru my firewall (Little Snitch), but it does work fine now. Thanks for persevering! :) |
Here is what I see now. Should I see SDRPLAY in the list?
SoapySDRUtil --info
######################################################
## Soapy SDR -- the SDR abstraction library ##
######################################################
Lib Version: v0.7.0-g69c16e98
API Version: v0.7.0
ABI Version: v0.7
Install root: /usr/local
Search path: /usr/local/lib/SoapySDR/modules0.7
Module found: /usr/local/lib/SoapySDR/modules0.7/libsdrPlaySupport.so
(0.1.0-12c3db6)
Available factories... sdrplay
[image: Screenshot 2024-03-11 at 2.08.36 PM.png]
…On Mon, Mar 11, 2024 at 12:56 PM Radito ***@***.***> wrote:
https://github.com/radito/CubicSDR/releases/tag/0.2.8-3
0.2.8-3 build
Add multiple sdr library and fix conflicting build path from homebrew.
—
Reply to this email directly, view it on GitHub
<#1011 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQILZJC63SQDSTP2XEGGDTYXXV3DAVCNFSM6AAAAAA5T54TNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBZGA4TCMRWG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think that might be the problem with my library, i'm taking a look
|
@mg1011 Can you try my latest build see if it's working, Added multiple library [FORK] Include libsdrplay_api.so.3.14 and libaudioSupport.so Thanks |
Wow, working well! Rig Control/Tracking works and also noticed some more options showing up with this one. |
Appears that that is a CLONE of the SDRPlay? I wonder if its not working
because the drivers/api for SDRPlay don't work with the clone ?
…On Tue, Mar 19, 2024 at 3:04 AM cts409 ***@***.***> wrote:
Hello!
On my Air M1, the latest build v.0.2.8-4 starts, but the SDR is not
displayed.
Tested on "POP MSI SDR NANO" and "POP MSI SDRPro".
2024-03-17.00.45.13.png (view on web)
<https://github.com/cjcliffe/CubicSDR/assets/163987563/c61e7b06-0fee-4de0-83e2-766b432318d5>
—
Reply to this email directly, view it on GitHub
<#1011 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQILZIEJ6Z7ZQMOZDWVVPDYY7WRFAVCNFSM6AAAAAA5T54TNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBWGIYDKMRSHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Can you try |
macOS Ventura
On macOS Ventura and arm64_CubicSDR-0.2.7-Darwin it was detected and worked. I tried downgrading from macOS Sonoma to macOS Ventura and everything started working. |
$ SoapySDRUtil --probe Soapy SDR -- the SDR abstraction library###################################################### Probe device |
Looks like the driver doesn't detect that SDR. Has it worked on your Mac before ? This is what the SDRPlay RSP1A (non clone) looks like when running the probe. SoapySDRUtil --probe Soapy SDR -- the SDR abstraction library###################################################### Probe device -- Device identificationdriver=SDRplay -- Peripheral summaryChannels: 1 Rx, 0 Tx -- RX Channel 0Full-duplex: YES |
Yes, it worked for macOS Ventura and Arm64_CubicSDR-0.2.7-Darwin. But perhaps I also installed the SDRplay_RSP_API-MacOSX-2.13.2.pkg driver, I don’t remember. I'll downgrade my MacBook and test it again. |
Letter to GitHub team: I realize it’s probably because I did something stupid, but Let me explain: The only USB to Serial cable I had ended in a Male DB9 connector. I had to use a gender-changer, and I have learned since then that when you do that, pins 2 and 3 are switched. I believe that cable confused CubicSDR and it wrote something in its config file that is preventing the startup of the SDRplay box now. Why do I think that?
So, I just got a new USB-Serial cable made by Dtech and running the FTDI chip. I have their driver that is specific for If only I could get the SDRplay box started again… Possible Solution: Where is it? Oh, here’s a screenshot of how it looks now, minus the beach ball. It doesn’t get captured for some reason. So, can you tell me where the config file is so I can delete it? |
OK. I found the Config file, deleted it, and it all works. |
@SpaceCadet1249 The build uses the same code as the repo, there's nothing changed. And it appears @mg1011 can use rig control and has no problem. |
For the build i'm including the library from the official SDRPlay website the version is SDRplayAPI-macos-installer-universal-3.14.0.pkg From your case it seems the soapySDR hasn't detected the SDR and probably the the clone is not supported by this API ? I'm not so sure can you try this specific api version in sonoma and do the probe again ? |
@radito |
Works. Thanks! |
@cts409 If you're interested, here's a short video of SDRplay trying to initialize. Bear in mind it tries to come up with the RF frequency set to zero. I have tried setting it to, say 15Mhz before initializing, but get the same results. To exit the program at this point, I have to do a Forced quit. The only way I can get it to initialize is to blow away the config.xml file AND unplug and replug the SDRplay USB cable. SDRplay.not.Initializing.mp4 |
This solved the issue for me. |
@radito Thanks for all the effort to make something available for ARM64. I've followed so far on a Apple M3 Pro with Sonoma 14.5, but had no final success. Is there some further advice?
|
@radito Thanks for the hint, you're right, I grabbed the With |
Hello:
That version is working fine for me too.
Thanks!
Vic
On May 29, 2024, at 2:04 AM, jforge ***@***.***> wrote:
@radito<https://github.com/radito> Thanks for the hint, you're right, I grabbed the 0.2.8-aarch64 from elsewhere.
With 0.2.8-4 everything looks fine from my side.
Screenshot.2024-05-29.at.11.00.28.png (view on web)<https://github.com/cjcliffe/CubicSDR/assets/307481/92675d46-a4df-432f-a611-efa1ad0e468c>
—
Reply to this email directly, view it on GitHub<#1011 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHHKSKBY7T76AC2DWPGNFWLZEWK2XAVCNFSM6AAAAAA5T54TNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWHEYTGMRSHA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Crashes at startup:
Crashed Thread: 4 Dispatch queue: CA DispatchGroup
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000024a
Exception Codes: 0x0000000000000001, 0x000000000000024a
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [17843]
The text was updated successfully, but these errors were encountered: