R
ReemOthman

  • Oct 26, 2023
  • Joined Sep 11, 2023
  • 0 best answers
  • Hi ReemOthman,

    As a low-level system integrator, I have experience in developing the kernel driver forthe camera modules similar to OAK FFC cameras (AR0234 and others) with Nvidia Jetsons, but not with the depth vision on them yet.

  • Hi ReemOthman ,

    I would say that the OAK-FFC OV9282 is just a MIPI-CSI2 based camera/sensor module. You can use it with other platforms disposing the MIPI-CSI2 Rx interfaces (with or without the need of an adapter board so that the signals match one by one).

    Otherwise, OAK FFC boards have Intel Myriad X (RVC2) or Keembay (RVC3) VPUs that provide not only vision functionalities such as ISP, H264/265 encoding, but also depth mapping and deep learning which are usually heavily computational for platforms without hardware acceleration (such as CUDA in Jetson).

    Currently, with firmware in OAK FFC boards, your selected OAK-FFC OV9282 will work out-of-the box. You will not need to develop the kernel driver for it or to do the ISP calibration / tuning which could take a lot of effort and time (based on my experience with Nvidia Jetson and other platforms such as NXP or TI).

    Also, RVC3 based OAK-FFC boards = RCV2 based OAK-FFC boards + Raspberry Pi 3/4 (not 100% exact in terms of CPU cores).

  • Hi ReemOthman,

    I think that the doc means RVC2 has not supported on-board VIO and SLAM yet. And on-board means that the VIO and SLAM would run directly on the RVC2 without any additional platform (such as Jetson or Raspberry Pi 4 or x86 laptop). But this is not the case of RVC2 but RVC3.

    Meanwhile, Erik meant that you could use RVC2 for SLAM but for this case the RVC2 could only be the sensor (RGB + depth + IMU) and the SLAM would run on the host which could be the Jetson or the Raspberry Pi 4 or the x86 laptop taking the input data from the aforementioned sensor.