Hi @yipingwang Thank you. The camera we are using is the TechNexion AR0235, and we would like to use it with the CSI and CSI/DSI slots.
Let me confirm with the AE team.
Hi @yipingwang Thank you for your help, but the camera still isn't working. Do you have any suggestions?
Normal operation: line 6 = high , line 4 = low .
hi @yipingwang
@yipingwang @I applied the following settings, but the camera initialization still failed
hankwang_0-1790059212233.png
Hi @yipingwang
Thank you for confirming that J14 A10 (DSICSI_RST_SYNC) and A11 (DSICSI_EN_PWDN) are controlled via U81 (ADP5585). We've confirmed the ADP5585 on our board (i2c address 0x34, reporting as adp5585-00) probes successfully and is exposed to Linux as gpiochip9 with 11 GPIO lines (0-10; line 5 is reserved for PWM per our device tree).
Could you help us map these two signals to the exact ADP5585 GPIO pins (e.g. R0-R4/C0-C4 per the datasheet), and the corresponding Linux gpiochip line number (0-10)? Also, what is the correct polarity (active-high/active-low) for each signal?
We've already brute-force tested all pairwise combinations of the 10 available lines (90 combinations, both pulled low simultaneously) without success — the camera's boot-state register (0x3004) remains 0x0000 in every case. A precise pin mapping from the schematic or UM12022 would let us verify directly rather than continuing to guess.
On the 19 mm × 19 mm i.MX 95 EVK , The reset and standby pins on the i.MX95 EVK DSI/CSI connector (J14) are controlled through the ADP5585 GPIO expander U81 , not directly by i.MX95 GPIOs:
In the device tree, reference U81 for reset-gpios and pwdn-gpios . Use NXP’s imx95-19x19-evk-os08a20-combo.dtb overlay as the example for enabling the second camera on the shared DSI/CSI port.