Old Topic and New Issue/BeagleY-AI

Hello…does anyone know how to use the fan connector correctly or is it even supposed to work for now?

I received that Pi5 connector fan and plugged it in but think I am missing something. For now, I cannot get the fan to turn. Is there an overlay or some type of DTS I need to understand to use the Fan Connector on the BeagleY-AI?

Seth

P.S. Aw and A-Okay…

I got that image (png) from beagleboard.org. It seems maybe the pins are not 100% correct?

I will see…

Okay. Blah…so PWM and GND need an old tyme switch-a-roo.

Seth

It plugs in, the yellow wire is near the edge of the board. Runs out of the box.

1 Like

On kernel 6.1.x? I am currently using kernel 6.1.x and there are four pins.

I figured it out. I changed some .conf files and got mixed up. It seems it updates .conf files in real time now…

Seth

Good, should not have had to change anything, both of mine are out of the box working. Have you had any luck with the camera?

1 Like

Not yet…the camera on CSI? I have not tried USB either. I see there is an out-of-the-box example DTS for it, though.

Seth

P.S. I can try soon. I have an adapter cable and some type of CSI2 camera.

Update…

The fan is still running with the cam plugged in. I will test real quickly.

Yes, csi0, imx219.
Started a proof of concept subsystem that requires a camera and that is turning into a headache. Got out a Pi5 and can take stills at 3400 x whatever res. But it will not play video with opencv. I can see it using libcamera-hello but that is it. I am rebuilding opencv with gtk+ support, that was one of the errors. A while back I dropped the aiy for several reasons and the cam not working was one of them. Hopefully I will get the pi5 up, its almost their. If it turns out the gtk+ fixes it I will look at the aiy again and try to get that one up. Not much posted any place regarding a camera, either no one cares about it or it just does not work without a ton of work.

Running a usb cam on the big box and inferencing with gpu and its so-so performance. Its usb 3 and just okay, not spectacular. I am going to get a hdmi input card and a cam with hdmi output and try that on the big box.

1 Like

I have the darn OV and not the imx.

Seth

219imx is not much of a camera, I would not waste any money on it. If you are building a door cam it would be okay for that but anything serious, not so. It is like looking out the peep hole in a hotel room door.

1 Like

Okay…so.

I have gstreamer and opencv installed now.

I will try to render video now.

Seth

P.S. and another update here…

UPDATE

No cam yet. I am getting a bunch of errors:

[ WARN:0@0.705] global ./modules/videoio/src/cap_gstreamer.cpp
(862) isPipelinePlaying
OpenCV | GStreamer warning: GStreamer: pipeline have not been created

So, with simple opencv source to open a /dev/video(N) device(s), I am receiving pipeline errors.

If you can get it to work I will try that, my pi5 has a hardware issue. It has a low voltage warning pop up on the desktop and it has a funky smell. Its been running for 24 hours straight and still working. It might be moot. Looks good on the powersupply, its under 2 amps with all the cores building opencv. It has a thermal issue going on the usb connectors are hot!! This is first time actually working with it, so that might be normal??

1 Like

Where is your camera connected?

Here is the pi5 error, the gtk+ did not help.

Failed to capture frame.
Traceback (most recent call last):
  File "/home/fred/py-projects/RotaryCaptureAI/target/test_video_opencv.py", line 21, in <module>
    cv2.destroyAllWindows()
cv2.error: OpenCV(4.10.0) /io/opencv/modules/highgui/src/window.cpp:1295: error: (-2:Unspecified error) The function is not implemented. Rebuild the library with Windows, GTK+ 2.x or Cocoa support. If you are on Ubuntu or Debian, install libgtk2.0-dev and pkg-config, then re-run cmake or configure script in function 'cvDestroyAllWindows'

The destroyallwindows error is generated because it never opened a window.

That board only has 4gb, that might be the other issue. It can record .h264 so why is it failing?? The other finger is pointing at the 6.x kernel. I might try to find a 5.x kernel for the pi5, not sure if the aiy bsp supports that version kernel.

Right.

This is what I tried simply. I use ffmpeg and opencv with gstreamer options. Neither are connecting to my cam on CSI1.

Seth

P.S. So, something like this will test /dev/video0 - 2.

ffmpeg -f v4l2 -input_format v4l2 -video_size 640x480 -i /dev/video0 -c:v libx264 -pix_fmt yuv420p -b 1000k -f mpegts -muxdelay 0 -metadata:s:v:0 title="Live Stream" - | gst-launch -v -e -q ! autovideosink

It cannot find gst-launch. So, I just disregard the build from ffmpeg to port the online approach.

I get rid of everything up to -muxdelay 0. I get devices:

  1. device is not for capturing
  2. no such device

another update (r) here…

So, I think gstreamer is the way to go. I will test it real quickly.

Do you have the overlay loaded, and is it actually loading. If it fails the board will still boot because it is skipped.

Yes.

I have an overlay from CSI1.

Seth

Look at the debug and see what happens near FDT loading.

1 Like

Okay.

So, gstreamer works.

ffmpeg works.

My camera will not supply video via the CSI2 1 port. I am sure there are reasons but I do not know of them currently.

I got as far as:

  1. ffmpeg -input_format v4l2 -video_size 640x480 -i /dev/video0 -c:v libx264 -pix_fmt yuv420p -b 1000k -f mpegts -muxdelay 0 -metadata:s:v:0 title=“Live Stream” - | gst-launch -v -e -q ! autovideosink

  2. gcc basic-tutorial-12.c -o basic-tutorial-12 pkg-config --cflags --libs gstreamer-1.0

  3. gst-launch-1.0 v4l2src device=/dev/video0

I get the same error. /dev/video0 is not a capture device. So far, I can remember why this was an issue. It is probably on my end with the beagleboard.org DTS or probably (most likely) my camera type and connection(s).

So, how would I plug in a CSI2 camera adapter to the BeagleY-AI?

Seth

P.S. Right now, I have a imx219 camera on the CSI0 port but…

I am not even sure it plugs in correctly. I got an adapter for the module to the CSI2 port.

Okay…I see an update to the docs. under demos. I will test it now.