VEYE IMAGING Forum
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc
    • Register
    • Login

    307 MCLK dtb setting

    Scheduled Pinned Locked Moved CS MIPI camera
    2 Posts 2 Posters 847 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      srikanthkrish
      last edited by srikanthkrish

      Hi I am working with the veye cs mipi 307 camera module. I am trying to use the camera module with a custom carrier board instead of the dev kit with jetson nano.

      the camera module works fine with the jetson nano dev kit, but its not working with our custom carrier board. I was looking at the datasheet for the imx307 and comparing with the dtb and driver that veye has on the github repo. My question is:

      • Do you have a clock generator chip on the cs_mipi_imx307 module ? The datasheet mentions clock should be either 37.125 or 74.25 MHZ but jetson nano can only do 24 MHz and veye dtb has mclk=24Mhz.
      • In the veye i2c driver, you are writing to register addresses that are different from the datasheet, do you have another chip on board that is handling the i2c comms ? which means we do not have raw access to the i2c pins on the imx307 ?

      Also is it possible for you to share the schematic of the 307 module ? would be helpful in debugging our issues.

      veye_xummV 1 Reply Last reply Reply Quote 0
      • veye_xummV Offline
        veye_xumm @srikanthkrish
        last edited by

        @srikanthkrish

        @srikanthkrish said in 307 MCLK dtb setting:

        Do you have a clock generator chip on the cs_mipi_imx307 module ? The datasheet mentions clock should be either 37.125 or 74.25 MHZ but jetson nano can only do 24 MHz and veye dtb has mclk=24Mhz.

        The camera itself has a clock, so it does not require a clock signal from the motherboard.

        @srikanthkrish said in 307 MCLK dtb setting:

        In the veye i2c driver, you are writing to register addresses that are different from the datasheet, do you have another chip on board that is handling the i2c comms ? which means we do not have raw access to the i2c pins on the imx307 ?

        The module itself comes with an isp module, and the output data format is YUV. you can't access the sensor directly.

        @srikanthkrish said in 307 MCLK dtb setting:

        Also is it possible for you to share the schematic of the 307 module ? would be helpful in debugging our issues.

        Sorry, I can't fully disclose our schematics. You can refer to the datasheet on wiki.veye.cc.

        Questions will be answered as soon as possible, please be patient.
        如果你使用中文,请直接用中文提问。
        May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • First post
          Last post