Development kits expose a 15-pin CSI connector. Factory camera modules expect a board-to-board, several voltage rails, and a clean MCLK. That mismatch is why people design adapter PCBs: dedicated 24 MHz crystal, selectable 1.8/2.8 V I/O, core and analog rails, impedance-matched CSI lanes, I2C and power-down. The 2025 .com article called one of those boards JetsonCamLink. The engineering problem is larger than a nickname.
The gap
- Factory modules want regulated VDDIO, VCORE, VDDA. A Pi pin does not always give those.
- MCLK from a crystal beats a noisy derived clock if you care about image.
- Impedance and length on CSI-2 are RF problems, not jumper-wire problems.
- Rockchip RK3588-class boards, Jetson Nano/NX, and Pi CSI are cousins, not the same pinout.
The Camemake shortcut
If you can, buy a module already built for the host. Pi-labelled and Jetson-labelled SKUs in MIPI camera modules exist so you do not invent an adapter for a standard eval. When the camera is a custom flex for a Rockchip or an OEM carrier, we design that flex as part of the custom camera module flow. Open adapter designs are useful in the lab. Production still wants one BOM, one flex, one test.
Do not start from a random 30-pin camera and a hope. Start from the host, then the connector, then the sensor. That order keeps you out of a beautiful module that never clocks.