Huimin I would like to seek your team's advice on the changes to FSIN GPIO pin. Previously, We have used MXIO46 and 41 taking reference to FFC-4P and early version of OAK-D-LR. I recently observe that the new schematic of OAK-D-LR change the FSIN pin back to MXIO46, as it is pwm capable. I have three questions: Can we and should we also adopt this design? So that I could use PWM function to help all-AR0234 setup to work with FSIN. Understand AR0234 cannot trigger by themselves. If so, how should I enable the pwm function programmatically? Also, As MXIO46 was previously occupied by BNO085 IMU_BOOTN. Can I follow the new OAK-D-LR design, to reroute the IMU? Would it work with develop branch straight away? with a custom BoardConfig?
Huimin Another related question, does it matter at all, if I connect 4 MIPI CAMs to their individual CAMX_CLK pins, or to connect like the following like FFC-4P design? I wish I can do the individual connection instead of combining them like FFC-4P.
erik Hi Huimin , Yes, MXIO46 will be the default for FSYNC going forward. IMU will also be connected in the same way as on the OAK-D-LR in most cases or at least where that is possible. It's WIP on the firmware side I don't think it's in develop branch yet.
erik Huimin Regarding cam clock signals - cameras can be connected to individual CLK pins if there are enough available. It is actually better to have dedicated clock pins for each camera in case different cameras need different reference clock signals. But depends on what we support in FW by default though (would need to check board configs).
