Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A dt-overlay-mchp for adding two cameras for mpfs_video #4

Open
alihgh1993 opened this issue Jan 29, 2025 · 4 comments
Open

A dt-overlay-mchp for adding two cameras for mpfs_video #4

alihgh1993 opened this issue Jan 29, 2025 · 4 comments

Comments

@alihgh1993
Copy link

Hi,
I have a PolarFire SoC Video Kit, and I want to set up both of its cameras.
For now, I have bitbaked the mpfs-dev-cli image, but I am only able to get one of the cameras working.
How can I enable the second camera?

@shravanI35088
Copy link
Contributor

Hi

Currently, the video kit reference design includes only one enabled camera.

Thanks,
Shravan

@alihgh1993
Copy link
Author

alihgh1993 commented Jan 29, 2025

Thanks for your reply

So, what is the procedure to add the second camera?
I added th FPGA block design for the second camera based on the first camera design.
I also changed the devicetree to add the second camera but I did not get any result.
Should I also change the kernel modules?

Thanks

@shravanI35088
Copy link
Contributor

Hi,

If the FPGA design and device tree overlay have been correctly added, and the overlay file (dtbo + some-spi-client-header) has been included in the Libero SPI data client, you should be able to see two nodes, /dev/video0 and /dev/video1, after booting the board. Each node corresponds to one camera.

Thanks

@alihgh1993
Copy link
Author

Hi,
Thanks for your response.
I should search more about spi-client-header, because I dont know what is it and why is it related to the camera.
I thought I only need to modify the I2c of the board not the spi

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants