I have a RPI 4 running in Raspian (Dec 2020) and they use Pulse audio on top of ALSA.
The ARM portaudio lib calls functions in the Jack audio lib so if I link that lib
with the portaudio lib in a C program, the program compiles and links error free but freezes immediately after start.
A Python program that uses portaudio through the pyaudio lib works (also on RPI 4).
I have some real understanding problems about these libs.
C code --> Portaudio lib --> Jack audio.lib --> ALSA
and Python code --> pyaudio lib --> Portaudio lib --> Pulse audio.lib --> ALSA
or is it possible that portaudio can call ALSA directly and how to do that?
The portaudio.com website seems to be down (for good or just temporary?)
Related
I download source code iot-device-sdk-embedded-c from github.
I only change config for tool-chain and then compiler it successfully. But it stop in connect step(iotc_connect_to), when I run example "iot_core_mqtt_client" in my device(MIPS+uclibc). This example work in google shell, x86_64 linux and ARM linux.
My Device:
CPU: MIPS
OS: Linux 3.10.14
tool-chain : CC=mips-linux-uclibc-gnu-gcc-4.7.2 AR=mips-linux-uclibc-gnu-gcc-ar
Can iot-device-sdk-embedded-c run in MIPS+uclibc?
What do I need to change?
I think I got the answer....
"SOCK_STREAM" is defined to 1 for any other architectures, but it is defined to 2 for MIPS.
And then iotc_bsp_io_net_posix.c didn't use socket.h file from MIPS include folder.
That's reason why my device can't send data to server.
I try to flash the IBM InternetOfThingsKit Freescale K64F board with a binary compiled at mbed.org. I set the platform to "Ethernet IoT Starter Kit" and compiled the hello-world blinking LED example without any compiler errors.
After I copied the bin file on the mbed flash drive I instantly found the fail.txt file on the flashdrive. Even before pressing the button to flash the binary. The failed.txt file contains "INVALID BINARY NVIC".
I also tried it with "FRDM-K64F" instead of "InternetOfThingsKit" platform.
This is a MAC related problem. Starting with Yosemite MAC has a problem to mount the device in the right way and end up with a scrambled bin file which is then rejected by the bootloader. I still have the problem with OSX 10.10.5. Solution is to use a Linux machine or Virtual Box with a Linux OS.
http://embedxcode.weebly.com/blog/mbed-on-mac-os-x-yosemite-bug-and-time-to-innocence
I have an extremely bare-bones Linux system that consists of basically nothing more than a kernel and a few statically-linked binaries. I have replaced init with my own program. All drivers are compiled into the kernel. It works fine, but now I want OpenGL support. I can compile DRM support into the kernel and install Mesa 3D library which should work with the open source ATI Radeon driver, but is that enough? Do I still need to load modules into the kernel? And how are shared libraries linked at runtime? Does gcc include code in the binaries that searches for shared libraries?
I have a Freescale i.MX board on which I run the Linux 3.0.35 kernel.
I want to test if the Kernel Crypto API of my Linux system works. I just found out the test program is called tcrypt. I see that under /lib/modules/ there is a tcrypt.ko in the drivers directory. This being the case, is there anyway I can test run this library? How do I call it? Do I need to reconfigure my kernel to "enable" something to call it?
Please keep in mind that I am new to kernel API's.
I had to compile the kernel modules. This built the "tcrypt.ko" module too. Then I used "insmod" command to load the module. Once loaded, the module was started with :
modprobe tcrypt sec=1 mode=200
(where mode is the algorithm to test)
I have a simple Arduino sketch that spans several files. There is a function signature in an h file, and the definition in the C file.
If I attempt to compile ("Verify") the sketch, I get "undefined reference" errors to the function defined in a C file. Changing the file name from *.c to *.cpp resolves the issue, but I don't want to define the file as a C++ file. Is it possible to compile plain old C files in Arduino?
The Arduino IDE is very limited, my advice: avoid it. You have some alternatives you can find here: http://arduino.cc/playground/Main/DevelopmentTools
Develop for Arduino using Minibloq graphical programming environment.
Arduino CMake build system
Ino command line toolkit for Arduino
Develop for Arduino using AVR-Ada
Develop for Arduino using Eclipse
Develop for Arduino using Bitlash
Run Arduino from the command line
Build using Cmake
Build using Scons
Build using build_arduino.py
Getting a Chumby talking to Arduino
Running Arduino on the XO laptop (AKA the $100 laptop)
Arduino in Sharp Netwalker
Arduino on OpenSolaris
Using Arduino Libraries in CodeBlocks
Develop for Arduino using Kdevelop
Using assembly language source files in the Arduino IDE: Assembly in Arduino