Replies: 6 comments 4 replies
|
I will 100% get the V3 supported. I only have the V4 which I only recently realized was actually discontinued. The V4L just came out last month. I expect to have them all fully supported once I can test. Currently OrcSDR pulls a "pinned" V4 dongle version of my esp-rtl-sdr driver. That repo does have v3 branch but it is experimental and untested. I dont quite have the full setup suite accounted for yet. You are correct, there are 3 different display's for the M5Tab5 at this point. I still need to reconcile that as well. I appreciate the discorse and will work on all of the issues above. If you feel inclined, you can point an A.I. of your choice at both repo's and ask it to test the V3 driver on the current OrcSDR origin/main and have a go. Thanks again for the interaction. |
|
RTL-SDR Blog V3 testing is now available in an experimental OrcSDR build. We updated OrcSDR to use the new multi-dongle driver while keeping RTL-SDR Blog V4 as the tested compatibility baseline; V4 should continue to work as before. The experimental pre-release includes an M5Burner-ready image: https://github.com/hardcoreerik/OrcSDR/releases/tag/v0.2.0-beta.6-multidongle-rc1 If you can test your Blog V3, please report whether OrcSDR detects it, starts streaming, retunes, and receives FM/VHF/UHF stations at 24 MHz or above. Frequencies below 24 MHz should be blocked because the V3 does not use the Blog V4 HF upconverter path. Please include the frequencies tested, reception results, and any message shown by OrcSDR. Blog V3 support remains provisional until we receive hardware results. We are also looking for the same testing from Nooelec NESDR SMArt V5 owners. |
|
Hi! I've tested the pre-release firmware that you provided with the RTL-SDR v3 that I own (still the first series of the Tab 5). I've loaded the firmware onto the SD card and I installed it with Launcher. If I turn the Tab 5 on without the SDR connected and everything loads fine, and the touchscreen works fine. Once I plug the SDR in it gives me the blue screen again, and it boot loops. |
|
I can confirm the following on the latest pre-release beta6 running on the ST7123 TAB5: RTLSDR pre-v3 = light blue/black boot loop 
|
|
Thank you for testing the experimental Blog V3 build. The blue-screen reboot loop on insertion is not an acceptable result, and I do not want to guess at the cause without the failure evidence. Could you attach one complete serial log covering:
Please also include the exact Tab5 revision, release filename, and whether Launcher performed an app-only installation or a full-device flash. If the console remains responsive long enough, include: The V3 path remains provisional. A successful build or profile match is not a hardware acceptance result. |
|
`LASH_SD ready bus=sdmmc *** PLUGGED IN V3 HERE *** assert failed: usbh_dev_close usbh.c:1058 (dev_obj->dynamic.num_ctrl_xfers_inflight == 0) Stack memory: ELF file SHA256: 9057a5e4c I (6079) esp_core_dump_flash: Save core dump to flash... *** NEXT CRASH HAPPENS HERE IF V3 LEFT PLUGGED IN *** |
|
@unixpunk, thank you again for testing the pre-V3, V3, V4, and V4L dongles. Since your original test, we have published newer experimental candidates. The current one is Multi-Dongle RC3: https://github.com/hardcoreerik/OrcSDR/releases/tag/v0.2.0-beta.6-multidongle-rc3 Your earlier serial log showed OrcSDR closing the USB device while a control transfer was still active. RC3 contains a driver repair for that USB-transfer drain problem. It passed repeated insertion and removal testing with our Blog V4, but we still need someone with physical V3 hardware to tell us whether it fixes the V3 boot loop. If you are willing to retest, please start with the RTL-SDR Blog V3:
If it still blue-screens or boot-loops, please attach one complete serial log from before insertion through the first failure and reboot. Please test the pre-V3 separately and identify its exact model if possible. V4L is noted, but this three-receiver candidate does not currently claim V4L support. One unrelated RC3 warning: do not press Check for Updates while Wi-Fi is off. We reproduced that reboot and are repairing it in issue #87 and PR #88. These tests will help us separate successful USB detection from actual reception support. Thank you for having the hardware and taking the time to help. |
|
@merendaio @unixpunk, we now have a newer Multi-Dongle RC4 build with confirmed RTL-SDR Blog V3C support: https://github.com/hardcoreerik/OrcSDR/releases/tag/v0.2.0-beta.6-multidongle-rc4 RC3 did not solve the V3 insertion failure as intended. The RC4 work went further: we reproduced the USB failure, repaired the driver's device handling, and then tested with a physical RTL-SDR Blog V3C. On the tested V3C, OrcSDR now:
The matching driver work has now been merged into Support for earlier Blog V3 models is still experimental, and V4L is not currently claimed as supported. If you can test RC4 with those receivers, that would be very useful. Please include:
Thank you for supplying the earlier hardware tests and crash log. That evidence directly helped identify and repair the USB failure. |
|
Hi! I've tested the firmware you linked.
Thank you for your work! |
|
Really appreciate you guys staying engaged with this and actually testing it. That kind of feedback has been a huge help. I’ve done a ton of work on the RTL-SDR side since this discussion started, especially around the V3/V3C. I’ve been deep into the driver, tuning behavior, crystal handling, PLL/IF stuff, and the differences between the V3/V3C and V4. I’ve also added a lot more control around gain. We now have proper manual gain control, access to the available tuner gain steps, and much better control over how gain behaves across the different dongles instead of just relying on one generic setting. That’s been especially useful on AM/HF and with amplified antennas where too much gain can actually make reception worse. A lot of this work has come directly from people testing different dongles and reporting when something didn’t behave the way I expected. Someone saying “this works on my V4 but not my V3C” gives me something real to chase down instead of just guessing. I’ve also been doing a lot of work on AM/HF and shortwave. There’s a new dedicated Shortwave dashboard coming together now that should be released pretty shortly. The goal is for it to feel like an actual shortwave radio experience instead of just another generic tuning screen. So seriously, keep the testing and weird reports coming. Even when something is broken, it usually ends up helping make the project better. Thanks again. |
Uh oh!
There was an error while loading. Please reload this page.
Hi there. As an avid radio amateur, I’m really interested in all software related to radio listening, so I’ve downloaded and installed the program. I can confirm the issue with the blue screens; as soon as I can, I’ll connect it to my PC via USB to see if it works, and then I’ll test it with an RTL V3 dongle, hoping it’s supported. I’d also like to check my Tab 5’s chip configuration, given that it was one of the early models... Congratulations on the great work.
All reactions