> For the complete documentation index, see [llms.txt](https://docs.holybro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holybro.com/autopilot/pixhawk-baseboards/pixhawk-jetson-baseboard/csi-camera-setup.md). # CSI Camera setup Popular cameras supported out of the box include IMX219 camera modules, such as the Raspberry Pi Camera Module V2. For the CSI camera, basically you could benefit from the Nvidia guide {% embed url="" %} Nvidia Jetson CAM guide {% endembed %} {% hint style="info" %} You may need to connect your Jetson to a display before attempting NVIDIA's CSI camera guide. {% endhint %} The Holybro Jetson carrier board can have two CSI cameras connected. To give a short intro, you can try the following commands in the terminal in case your carrier board is connected to a display screen: ``` nvgstcapture-1.0 ``` To open the capture on a specific CAM, you can pass the following (assuming we want to test cam1 on Orin\_camera 1): ``` nvgstcapture-1.0 sensor-id=1 ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.holybro.com/autopilot/pixhawk-baseboards/pixhawk-jetson-baseboard/csi-camera-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.