I have GNURadio (and Companion) installed on my RPi. Everything seems to work fine except when I want to use one of the blocks associated with a SDR dongle. When I try to execute the flow graph I get:
"Error in '/usr/bin/python': corrupted double-linked list 0x02272ff8 ***"
I have done a lot of searching and see that others have had this problem but no solutions have been posted.
Further more, I can run another program that I believe uses GNURadio blocks and it accesses the SDR Dongle and works correctly. The program is gqrx. It requires GNURadio to be installed so I assume it uses GNURadio.
How can I get this to work?
Related
I recently started playing with an ESP8266 and wanted to try uploading to it using WSL. I found the Arduino-CLI command and followed some tutorials but couldn't figure out how to upload to the board. The command I tried running is arduino-cli upload -p /dev/ttyS5 --fqbn esp8266:esp8266:arduino-esp8266 Testing because I know that the board is an ESP8266 and the is connected to COM5 on the Windows Arduino app. The code compiles and attempts to connect to the board, but cannot get past that part.
This is the code I was trying to upload.
void setup() {
pinMode(0, OUTPUT);
}
void loop() {
digitalWrite(0, HIGH);
delay(1000);
digitalWrite(0, LOW);
delay(1000);
}
When I execute arduino-cli board list, it shows this.
Port Protocol Type Board Name FQBN Core
serial Unknown
I'm using Windows Terminal for Ubuntu 20.04 and just installed Arduino-CLI.
I also am not sure how to ask stuff cuz it's my first time using StackOverflow, so pls tell me if I'm doing something wrong :)
Edit: So it turns out that I was uploading using the wrong core. I ended up trying every single core listed by arduino-cli board listall esp8266 and it eventually worked with esp8266:esp8266:nodemcuv2 instead of esp8266:esp8266:arduino-esp8266.
Just educated guesses here from my understanding of WSL rather than Arduino.
I'm assuming that you are using WSL2, which doesn't have access to most Windows hardware, including the serial ports.
If that's the case, two options that you might try:
WSL1 does have some better direct hardware access, at the expense of some kernel compatibility (since it attempts to translate syscalls rather than virtualize them). You can try converting the distribution to WSL1 via:
wsl -l -v
# Confirm distribution name
wsl --set-version <distro_name> 1
You might want to back it up first with wsl --export <distro_name> backup.tar.
As mentioned in the comments, you should be able to use the Windows toolchain. You can even run this under WSL2, since Windows commands can be executed there through interop (and would have hardware access). Remember to use the full executable, like /mnt/c/arduino-cli/arduino-cli.exe. And also you'll need to convert any Linux/WSL paths to their Windows equivalent with wslpath.
I have a problem with communication with Atmega644P. I am using C232HM Cable and avrdude. Unfortunately, every attempt of communication ends with the following comment from the command prompt: avrdude: Error: no libftdi or libusb support. Install libftdi1/libusb-1.0 or libftdi/libusb and run configure/make again. I installed following driver from Zadig 2.5: WinUSB (v6.1.7600.16385) and the error still occurs. What should I do?
To get past that error message, you have to do what it says: install the library that AVRDUDE needs and then build AVRDUDE from source in a way that it detects the library and uses it. But I am not sure exactly what you are trying to do and I cannot be sure that this will ultimately work for you. If you haven't built code from sourt before, it can be a challenge.
You never said how you installed AVRDUDE, but you might try downloading a binary version from a different place before you attempt to compile it yourself. The Arduino IDE comes with a version of AVRDUDE, and there is also an AVRDUDE package in MSYS2 (which I contributed).
So, I am learning stm32 mcus, using a nucleo f4 board.
Everything was working fine and now debug launch fails.
Actually, I was doing one debug, closed it and next debug session won't launch.
It starts debug on Linux or on Windows with OpenOCD, but ST-Link GDB debug fails (gdb does work on linux).
This is the error message:
Already did allow the stlink server in the windows firewall.
Avast antivirus was deleting the STLINK server exe file, added an exception and it works.
Also the problem is the mass storage option (that allows use the explorer to grab directly the hex files) and makes conflicts with the ide. I solved the problem using explorer and ejecting the board, then debugger goes fine.
I recently got a new Mbed board - this one is MTS Dragonfly. I can't get flash-disk to show up correctly, and I am wondering if I have got a DOA module, or I am doing something wrong. Does this happens to other Mbed boards?
I have installed drivers from manufacturer website and do have a working serial connection, which defaults to the cellular module. However the flash disk does not show up correctly. Unlike other Mbed boards, I am greeted with a message "please insert disk" and I see no file system.
Interesting part is that the mbed microcontroller - that is the one doing the programming - is on a separate development / breakout board. The target is a separate module that is meant to be used in production.
If I do not insert the target into the development board, and connect development board to the PC, I get the same error. I have looked at diskpart, and when no target is present, it shows up as a 16 KB disk with no partitions or volumes.When the module is inserted, diskpart reports ~512 KB of space, also with no partitions. Thus I guess that I am plugging in the module correctly.
I have seen user discussions for a 'bricked' mbed board (damaged file-system), and this situation looks similar to me.
I tried diskpart to create a partition, or clean the disk, and it throws an IO error.
This question on mbed site
I just tested all of my Mbed boards and discovered that this is a regression in Windows 10 anniversary update.
MTS-Dragonfly and another board, Delta DFCM-NNN40, do not show up with a valid partition on any of my Windows 10 machines. I have a couple of FRDM boards and those work fine.
I tested Ubuntu, and it has no issue displaying the disk drives or programming the boards. I have not tested other versions of Windows. A workable solution is is to use Ubuntu in VirtualBox, and pass it control of the USB device.
I am using USRP2 with RFX2400 Daughterboard. I plan to use the USRP2 for my project.
I downloaded the FPGA (bin) and the Firmware image and through the SD Card burner, I write it to a SD Card.
But I am not able to use the USRP2.
I connect the USRP2 to the Ubuntu system (Direct Connection through Ethernet). I run find_usrps and get the system error:
" No USRPS found"
Also, when I run und_find_devices, I get the error "No UHD devices found".
Please let me know if I am missing some obvious steps. When I turn on the USRP2, only LED F turns on.
I donot see the boot sequence as mentioned here: Youtube
Thanks
Kiran
This is an old question and wonder if you still have the problem?
Did you install the UHD driver?
Did you veryify that it works properly?
Do you have a GbE that is compatible with GR?