I have a 1394 camera connected with the computer as indicated below (the installations followed the instruction given https://www.mathworks.com/help/imaq/dcam-ieee-1394-firewire-hardware-on-windows.html#f16-76150 by Matlab). But the camera device does not show up in the Image Acquisition Explorer (see the screenshot below). It only recognizes a webcam.
There may be some potential issues with the 1394 host controller driver. I guessed the CMU driver used for the camera is not compatible with the 1394 host controller driver (dependent on PCIe hardware). Need to test a different PCI card to verify that.
However
Related
I have an analog to digital converter (ADC) MCP3008 connected to Raspberry PI 4 via SPI interface.
I need to process the signal from ADC in ODAS library (Open embeddeD Audition System).
ODAS is capable to process signal from a device in real time, but requires the device to be a soundcard.
Therefore I need to make Raspbian recognize SPI input from ADC as a soundcard.
After googling I found out that I need to write a device tree overlay to describe the soundcard.
I read about device tree overlays and viewed the device tree specification, but still can't figure out, which nodes and properties should I describe in the overlay?
Referencing this item:
https://store.gumstix.com/gumstix-pi-compute-dev-board.html
I cannot use the official Pi camera(s) using either the official Raspberry Pi "Buster" disk image or the Pi disk image provided by Gumstix:
Disk image referenced here--> https://store.gumstix.com/raspberry-pi-cm-fast-flash.html
Note: The Gumstix Pi image would "hang" on the rainbow colored splash screen during boot, using the image above. I am using the "fast flash" board to write the images, and have been able to repeatedly (successfully) install the standard Raspbian OS. FYI I have been using Balena Etcher, and it has worked with my other boards.
Also, I followed the official instructions to add camera support in an attempt to understand what I am doing wrong. vcgencmd initially reported no support or detection in raspbian. I was able to add camera support using the blobs mentioned here (I compliled manually and also used the precompiled variant):
https://www.raspberrypi.org/documentation/hardware/computemodule/cmio-camera.md
Final result:
vcgencmd get_camera : supported=1 detected=0
Lastly, yes the camera is enabled, and I have tested the cam/cable on other systems with no issues. I suspect the pin GPIO settings may be to blame, but based on the information in front of me (for this board) I should not be expecting to manually adjust those params. Thanks for any insight….hopefully this is an I-D-10-T error.
First off I should appologize, the page you referenced about getting the disk image is very out of date. We will work to update it soon.
My guess of why it's not booting is likely a hardware imcompatibilty, are you using a Raspberry Pi CM3+?
Give this image a try
https://gumstix-raspbian.s3.amazonaws.com/2019-12-29/raspberrypi-cm3/rpi-4.19.y/2019-09-26-raspbian-buster-lite.img.xz
That's a recently compiled Buster image that has some extra drivers added in to support Geppetto modules. The default Buster image should also work.
To properly support any of our boards, it's best to download the board support package for that particular design. In your case, you're using the Gumstix Pi Compute Dev Board, which can be found
https://geppetto.gumstix.com/#!/design/1045/
Please go to that page and click on the "AutoBSP" button on the top. That will prompt you to download a zip file that will contain some instructions and files needed to configure the Raspberry Pi.
Please let me know if you have any trouble.
Thanks,
Andrew
I have a Raspberry PI with two NFC readers attached. Problem is that the readers get different device numbers each time the system reboots or a reader is detached and attached again.
I therefore created udev rules that create a fixed device name depending on the physical port a device is attached to. E.g. plug in NFC reader in the upper left port leads always to /dev/nfc_a and plugged into the upper right port leads always to /dev/nfc_b.
How can I now configure libnfc to use these devices and report the device names such as /dev/nfc_a as a part of the reading? I am using Node-RED with node-red-contrib-nfc (https://github.com/hardillb/node-red-contrib-nfc) on top of libnfc. My ultimate goal is to safely distinguish the two readers within my Node-RED flow to act differently upon the readings.
I already found the "connstring" configuration but I don't know how to correctly set it for using /dev/nfc_a.
It's been a LONG time since I wrote this node, but looking back at the nodejs library it's based on (nfc) the output message should contain a field called deviceID which should indicate which NFC reader triggered the input.
When I run on my machine I get:
deviceID: 'pn53x_usb:001:005'
Where 001 is the USB bus id and 005 is the device ID, which matches up with the output from lsusb. These should stay static as long as the readers are always plugged into the same USB sockets.
I am building a board based on the STM32F303RET6.
The Processor Datasheet, page 17/section 3.5, mentions programming can be done "using USART1 (PA9/PA10), USART2 (PA2/PA3) or USB (PA11/PA12) through DFU (device firmware upgrade)"
I am using a NUCLEO board with this processor.
I have connected the Vdd, Gnd, D+ and D- pins of USB to a NUCLEO board and disabled the power from the add-on programmer board.
However whenever I reboot it with BOOT0 HIGH the USB never enumerates any device.
I am connecting the pins directly to the USB plug without any external resistor. The datasheet seems to suggest these are not needed.
To make things a bit trickier, this processor has the additional particularity of not having a BOOT1 pin; it is a software bit.
My question is, does the processor actually support DFU by using the built in bootloader?
If so, how should one go about starting it and programming via USB?
Thank you very much,
Pedro.
PS: ST has actually got conflicting information about support for USB programming on this processor. While the Datasheet says it's supported, Application Note AN2606, page 81 (section 19) only mentions support for programming via USART1, USART 2 and I2C. It references the USARTs but it's unclear how they can be used.
I have connected the Vdd, Gnd, D+ and D- pins of USB to a NUCLEO board
and disabled the power from the add-on programmer board.
Check the actual voltage and current on Vdd. The host might limit the current, or shut the port down when the consumption exceeds 100mA before enumeration. Try it with an external power supply.
I am connecting the pins directly to the USB plug without any external
resistor.
You need an 1.5k pullup on D+ (full speed) or D- (low speed). This is from the STM32F3 Discovery schematics (that's an OTG socket, ignore the ID line for regular 4-wire ports)
When there is no pullup, the host can't detect when the device is plugged in, and therefore won't enumerate it.
ST has actually got conflicting information about support for USB programming on this processor. While the Datasheet says it's supported, Application Note AN2606, page 81 (section 19) only mentions support for programming via USART1, USART 2 and I2C.
There is no conflicting information there. Section 19 on page 81 refers to some other controllers.
The capabilities of your STM32F303RET6 are listed in table 36, section 18.1 on page 77. (As I've already pointed it out.) See also table 3 on page 23, line STM32F302xD(E)/303xD(E).
Ex-My Webcam has face detection feature. I don't think this functionality can be achieved by standard device driver model .like Linux assumes everything as file and uses operations like read ,write etc for communicating to driver. So how user space programs uses these functionalities of device drivers?