Nice, if you get anywhere and have progress to share I have two IMX219 modules here to test.
Best, Mat
Pushed… Commits · v5.10.x-ti-unified · BeagleBoard.org / BeagleBoard-DeviceTrees · GitLab
debian@BeagleBone:/opt/source/dtb-5.10-ti$ dmesg | grep imx
[ 9.734750] imx219 4-0010: supply VANA not found, using dummy regulator
[ 9.741556] imx219 4-0010: supply VDIG not found, using dummy regulator
[ 9.748236] imx219 4-0010: supply VDDL not found, using dummy regulator
[ 9.969642] imx219 6-0010: supply VANA not found, using dummy regulator
[ 9.976433] imx219 6-0010: supply VDIG not found, using dummy regulator
[ 9.983083] imx219 6-0010: supply VDDL not found, using dummy regulator
debian@BeagleBone:/opt/source/dtb-5.10-ti$ sudo /opt/edge_ai_apps/init_script.sh
CSI Camera 0 detected
device = /dev/video2
name = imx219 6-0010
format = [fmt:SRGGB8_1X8/1920x1080]
subdev_id = 2
isp_required = yes
CSI Camera 1 detected
device = /dev/video18
name = imx219 4-0010
format = [fmt:SRGGB8_1X8/1920x1080]
subdev_id = 5
isp_required = yes
git clone -b v5.10.x-ti-unified https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees.git
cd ./BeagleBoard-DeviceTrees/
make
sudo make install_arm64
fdtoverlays /overlays/BBAI64-CSI0-imx219.dtbo /overlays/BBAI64-CSI1-imx219.dtbo
Regards,
3 Likes
Thanks, I connected my official RPi V2 NoIR camera to port CSI0 and it was detected via the edge ai init scripts after following your instructions.
I appreciate the quick turn around and effort, will be having fun with this over the weekend.
Mat
Quick follow-up as I’ve been trying to test some of the Edge AI apps and was wondering if you’ve been able to run one of the Python examples?
After running the init_script.sh the camera is seen although I see the following two messages before detecting my camera on CSI0:
- line 120: ntpd: command not found
- line 124: /usr/lib/python3.8/site-packages/dlr/counter/ccm_config.json: No Such file or directory
I then try to run one of the python examples from /opt/edge_ai_apps/apps_python:
sudo ./app_edgeai.py …/configs/rpiV2_cam_example.yaml
The error I’m getting is:
“Error - libdlr.so: cannot open shared object file: No such file or directory”
Are you able to get this example running? I just flashed my AI-64 w/ latest Nov 1st flasher w/ Edge AI apps. I also followed the AI-64 update procedure.
Best, Mat
Run:
sudo apt update
sudo apt upgrade
It should upgrade the ti-edgeai-apps-src-8.2 package.
Then,
sudo /opt/edge_ai_apps/init_script.sh
Will work…
Now beyond that… There still be dragon’s, and i haven’t got an image of the imx yet…
Regards,
That did the trick, I can run the Edge AI demos now although only the video/image sources seem to function.
I cannot get an image either through the IMX219 example although it kids now.
1 Like
I’ve been following this thread, but just wanted to pop in to say – I’m also interested in CSI camera support, and have one of these cameras.
Hi @RobertCNelson, i’m just checking in to find out if TI’s been able to shed light on the missing data stream from the IMX219?
Best, Mat
Hi.
Is IMX219 activation going on?
I have RPI camera V1.3 / V2.0 / V2.1 and connected the above camera to the CSI port.
The above procedure was carried out.
H/W Connected.
CSI0 - RPI Camera V2.0
CSI1 - RPI Camera V2.1
debian@BeagleBone:~$ sudo /opt/edge_ai_apps/init_script.sh
[sudo] password for debian:
CSI Camera 0 detected
device = /dev/video2
name = imx219 6-0010
format = [fmt:SRGGB8_1X8/1920x1080]
subdev_id = 2
isp_required = yes
CSI Camera 1 detected
device = /dev/video18
name = imx219 4-0010
format = [fmt:SRGGB8_1X8/1920x1080]
subdev_id = 5
isp_required = yes
debian@BeagleBone:~$
CSI0 - /dev/video2
CSI1 - /dev/video18
ebian@BeagleBone:~$ v4l2-ctl --list-devices
j721e-csi2rx (platform:4500000.ticsi2rx):
/dev/video2
/dev/video3
/dev/video4
/dev/video5
/dev/video6
/dev/video7
/dev/video8
/dev/video9
/dev/video10
/dev/video11
/dev/video12
/dev/video13
/dev/video14
/dev/video15
/dev/video16
/dev/video17
/dev/media0
j721e-csi2rx (platform:4510000.ticsi2rx):
/dev/video18
/dev/video19
/dev/video20
/dev/video21
/dev/video22
/dev/video23
/dev/video24
/dev/video25
/dev/video26
/dev/video27
/dev/video28
/dev/video29
/dev/video30
/dev/video31
/dev/video32
/dev/video33
/dev/media1
vxd-dec (platform:vxd-dec):
/dev/video0
vxe-enc (platform:vxe-enc):
/dev/video1
debian@BeagleBone:~$
I don’t know j721e-csi2rx.
We have proceeded so far, and EDGEAI has not been implemented with CSI0+IMX219(RPI camera) combinations.
1 Like
@RobertCNelson Does the recent Bullseye release include support for these CSI cameras? And/or in general is there any progress? I see the 5.10.153-ti-arm64-r86 kernel tree (Commits · 5.10.153-ti-arm64-r86 · BeagleBoard.org / Linux · GitLab) has recent work on other CMOS chips.
Hey, I followed your steps, added the overlays and got similar response from dmesg | grep imx
[ 9.606925] imx219 4-0010: supply VANA not found, using dummy regulator
[ 9.735400] imx219 4-0010: supply VDIG not found, using dummy regulator
[ 9.834726] imx219 4-0010: supply VDDL not found, using dummy regulator
[ 10.034995] imx219 4-0010: failed to read chip id 219
[ 10.239032] imx219: probe of 4-0010 failed with error -5
[ 10.364886] imx219 6-0010: supply VANA not found, using dummy regulator
[ 10.502978] imx219 6-0010: supply VDIG not found, using dummy regulator
[ 11.041430] imx219 6-0010: supply VDDL not found, using dummy regulator
debian@BeagleBone:~$ sudo i2cdetect -y -r 6
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
And my init_script has couple of issues:
- It tries to edit files of python3.8/dlr but I have python3.9 from boot (commented it)
- The ntpd time setting didn’t work (I commented it)
Init scripts output:
debian@BeagleBone:/opt/edge_ai_apps$ sudo ./init_script.sh
Unable to setup formats: Invalid argument (22)
I googled further and found that this might be an issue with yavta package, though no luck yet
My kernel is 5.10.90-ti-arm64-r28
Okay, so here is an update:
I installed a new kernel via sudo apt install linux-version command
So my current kernel is 5.10.153-ti-arm64-r84
I tried to install a newer one, but It just cannot switch to it (maybe some advice?)
Then, it still didn’t work, so I installed the edge-ai apps.
Though I run into problems:
debian@BeagleBone:/opt$ sudo apt install ti-edgeai-apps-src-8.2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libllvm11 libvulkan1 mesa-vulkan-drivers python3-gitdb python3-smmap
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
ti-edgeai-apps-src-8.2
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
94 not fully installed or removed.
Need to get 0 B/77.9 MB of archives.
After this operation, 87.5 MB of additional disk space will be used.
(Reading database ... 135379 files and directories currently installed.)
Preparing to unpack .../ti-edgeai-apps-src-8.2_8.2.0.14-0~bullseye+20221117_arm64.deb ...
Unpacking ti-edgeai-apps-src-8.2 (8.2.0.14-0~bullseye+20221117) ...
dpkg: error processing archive /var/cache/apt/archives/ti-edgeai-apps-src-8.2_8.2.0.14-0~bullseye+20221117_arm64.deb (--unpack):
trying to overwrite '/opt/edge_ai_apps/PROCESSOR-SDK-LINUX-SK-TDA4VM_manifest.html', which is also in package ti-edge-ai-apps-08-00-00-05 1.20211130.8-0~bullseye+20211203
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/ti-edgeai-apps-src-8.2_8.2.0.14-0~bullseye+20221117_arm64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
I tried to install the package manually into my dir, via --force-all (I am quite desperate and pissed off)
And, I run the script:
debian@BeagleBone:~/huy/opt/edge_ai_apps$ sudo ./init_script.sh
CSI Camera 1 detected
device = /dev/video2
name = imx219 4-0010
format = [fmt:SRGGB8_1X8/1920x1080]
subdev_id = 2
isp_required = yes
debian@BeagleBone:~/huy/opt/edge_ai_apps$ uname -r
5.10.153-ti-arm64-r84
So, it is at least detected 
I tried to get some image from guvcview, but having some ioctl errors:
debian@BeagleBone:~$ guvcview --device=/dev/video2
Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
V4L2_CORE: ERROR opening V4L2 interface for /dev/v4l-subdev2
V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
V4L2_CORE: ERROR opening V4L2 interface for /dev/v4l-subdev1
Failed to query video capabilities: Inappropriate ioctl for device
libv4l2: error getting capabilities: Inappropriate ioctl for device
V4L2_CORE: ERROR opening V4L2 interface for /dev/v4l-subdev0
V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.V4L2_CORE: Unable to find parent usb device.GUVCVIEW: version 2.0.6
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (UVCIOC_CTRL_MAP) Error: Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
- FORMAT NOT SUPPORTED BY DECODER -
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: (VIDIOC_ENUM_FRAMEINTERVALS) Error enumerating frame intervals
V4L2_CORE: Unable to enumerate frame sizes Inappropriate ioctl for device
V4L2_CORE: Control 0x80000000 failed to query with error -1
buggy V4L2_CTRL_FLAG_NEXT_CTRL flag implementation (workaround enabled)
V4L2_CORE: (get control values) empty control list
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM sysdefault
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM sysdefault
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port
ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port
ALSA lib pcm_a52.c:823:(_snd_pcm_a52_open) a52 is only for playback
ALSA lib conf.c:5200:(snd_config_expand) Unknown parameters {AES0 0x6 AES1 0x82 AES2 0x0 AES3 0x2 CARD 0}
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM iec958:{AES0 0x6 AES1 0x82 AES2 0x0 AES3 0x2 CARD 0}
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_hw.c:1829:(_snd_pcm_hw_open) Invalid value for card
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM dmix
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
V4L2_CORE: (VIDIOC_G_PARM) error: Inappropriate ioctl for device
V4L2_CORE: Unable to set 1/25 fps
V4L2_CORE: (VIDIOC_G_PARM) error: Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Resource temporarily unavailable
V4L2_CORE: (VIDIOC_G_PARM) error: Inappropriate ioctl for device
V4L2_CORE: Unable to set 1/1 fps
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
^CGUVCVIEW Caught signal 2
V4L2_CORE: Could not grab image (select timeout): Inappropriate ioctl for device
Hi!
Is there some progress on this? As I understand, IMX219 support got stuck on stage ‘camera is detected but no image data can be obtained’.
I just bought the board, connected Waveshare stereo camera based on IMX219, configured overlays and got the same results as user based_on above. (AI demos with USB camera are working fine, but i want to experiment with stereo)
Or am I missing something?
Thanks
PS: Linux image 5.10.168-ti-arm64-r108.
2 Likes
Has anyone solved this camera issue. I would also like to connect a stereo camera
1 Like
@Tron ,
I tried w/ a camera and LCD. Super hard to grasp for the likes of me. It is like the cam feed needs a driver just for connecting to the outer devices one could use to view the camera output.
I have not totally wrapped it up yet. I did get a i2c camera that has a GPIO on it and works at 3.3v but I have no way to tell just yet how to interface a GUI, output of cam, and then control it.
The i2c cam controls seem simple enough but it must have been preprogrammed before me.
I just throw in some menial 35 lines and bam, output. So, I know there is more to it.
Seth
P.S. Anyway, @Tron , I bet people are working on things in the meantime. I really have no clue. I am not a circle type but why not is the idea. “Why not have the stereo cameras work?” Right…
1 Like
As always beaglebone hardware is great but always hard to get software support. TDA4VM is in itself quite a complex chip for average joe. It would be nice if experienced developers supporting the hardware could at least leave pointers about where could be probable issues. I am quite surprised that cameras are still not functioning for long time on a hardware with camera processing as USP.
2 Likes
I think, do not quote me, beagleboard.org is a 501(c) about education, supporting hardware (Open Source Hardware), and there may not be hundreds of supporters ready to give free docs. and issues relative to every person.
I am not saying you are every person. But…at times.
- I feel less than important.
- B/c I am less than important.
- I say 1. and 2. b/c I have weaseled my way into their .org as an outsider and still trying to gather data and learn.
Luckily, their community assistants and random people like me try to pitch in. You are right. It is a very overwhelming chip w/ a lot of data to wrap oneself into while breaking into the chip and its intricacies.
I am the average joe here. I know I am. If I was not, I would have built my own board and tried the “waters.”
Seth
P.S. I think we may all need a bit of patience w/ them and everyone else. I say that to make it known that I believe that their .org is not filled w/ unlimited resources or heavy backing but…
That is what I think. I mean, to name drop here, rcn-ee knows a whopper of some data and can easily rehearse it simply. I, Seth, seem upset and over it. But…
@Tron , do not give up. I think there were some people building w/ the Encoders and Decoders. I am guessing as usual but hopefully this will help people better understand the input/output camera interface and Display too. I cannot wait until someone grasps the display part…
Porting the ins to the outs while knowing the internals is never easy. DEDICATION!
I am learning slowly that dedication is rewarding and takes FOREVER! Ha.
I even failed at the /boot/firmware/extlinux/extlinux.conf additions being supplied to the overlays sections all while changing the order of things. Some people know that DTS stuff well. I try when I can…okay. Enough of me for now.
Reply!
Oh and @Tron , I may be wasting your time. Heads up! But if you stick around, try to stick around. The more, the better is what someone said once or twice.
Tron, Have you seen this thread yet:
A few of us have succesfully used it. Not quite user friendly yet.