Hi, I’m trying to bring up an Arducam V3Link Camera Kit on a TI SK-AM62P-LP board running Android Automotive OS v14. I haven’t been able to add the camera at all, it’s never worked since I got it. The setup guide I found references a patch that looks like it was written for the SK-AM62A-LP, not the AM62P. Has anyone else run into this?
Thanks for the details. Before we dig into the possible platform mismatch, can you confirm which documentation you’ve been following? We have a Quick Start Guide for the V3Link camera on TI platforms. Have you worked through it, and if so, at which step did things break? It would help to know whether the failure is during device tree/patch application, driver loading, or when the camera fails to enumerate.
I followed the product page (https://www.arducam.com/product/arducam-v3link-camera-kit-for-ti-development-boards/) and the Quick Start Guide here: Quick Start Guide - Arducam Wiki. I applied the patch from that guide, but the patch seems to target the SK-AM62A-LP. I’m on the SK-AM62P-LP for an automotive use case, so I’m not sure the changes even apply correctly.
Got it. That guide and its patch were originally written around the AM62A, so it’s very possible the device tree/overlay changes don’t map cleanly onto the AM62P. Can you tell me exactly where it stopped? For example, did the patch fail to apply, did the build fail, or did the camera still not show up after booting? Any error output would help. Also, just to be sure: is the board actually an SK-AM62P-LP, or could it be the SK-AM62-LP? The two are different SoCs and that matters for the kernel/dts side.
The board is an SK-AM62P-LP. I’m afraid I don’t have logs saved from the last attempt, I was mostly following the guide step by step and stopped when I realized the patch references the AM62A device tree. The camera never enumerated after boot. I can re-run the steps and capture where it actually fails if you can point me at what to check.
Please do, re-run the setup and capture the failure point. The key thing we need to pin down is which step in the Quick Start Guide breaks on the AM62P: whether the patch applies cleanly, whether the dts/overlay changes build, and whether the V3Link driver actually loads. Since the patch was written for the AM62A, it may need to be adapted for the AM62P. For now the root cause isn’t determined yet, and we’re waiting on confirmation of the exact failing step. Report back with the output and we’ll go from there.