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

    Dead RAW-MIPI-IMX462M

    Scheduled Pinned Locked Moved VEYE MIPI camera
    2 Posts 2 Posters 31 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.
    • R Offline
      roboticsmick
      last edited by

      Does anyone have the schematic or test probe points for the RAW-MIPI-IMX462M? I want to try and debug the device to see if I can find out what is wrong with the board? I want to know if I can replace a regulator or if I got a dud?

      I purchased a RAW-MIPI-IMX462M camera from Aliexpress. This was working correctly on a Radxa Zero 3E for several hours, then began returning zero-byte captures with a large burst of uncorrectable MIPI packet header ECC errors. It finally stopped acknowledging its I2C address entirely.

      Hardware and software

      • Camera: RAW-MIPI-IMX462M, firmware version 0x1090000.
      • Host: Radxa Zero 3E, Debian bullseye, radxa-zero3_debian_bullseye_xfce_b6 image.
      • Kernel: 5.10.160-39-rk356x, installed from rk356x_radxa_zero3w.3E_mvcam.tgz, release v1.3_mvcam, from https://github.com/veyeimaging/rk35xx_radxa/releases.
      • Driver: veye mv series camera driver version: 01.01.08, compiled into that kernel.
      • Device tree node mvcam@3b on i2c@fe5b0000, which is i2c-2.
      • Cable: FFC22P-0.5MM-20CM-Y, opposite-face contacts, silver contacts facing outward as the wiki specifies.
      • Mounting: Stable mounting to desk. No vibrations or stress points to cable or module.

      What worked first

      • i2cdetect -y -r 2 showed UU at 0x3b.
      • Link came up as 2 lanes at 891 Mbps.
      • Default format was Y10_1X10/1920x1080@100/6000.
      • Captures succeeded at 2,764,800 bytes each, which is a 2560-byte stride by 1080 lines.
      • A live streaming loop ran for several minutes at a time.

      The failure, in the order it happened

      Stage 1, i2c perfect and MIPI failing. Captures began returning zero bytes. dmesg showed 5449 CSI errors, of which 5390 were ecc2, uncorrectable two-bit ECC failures on MIPI packet headers. Register reads over i2c at 100 kHz stayed flawless throughout, while the 891 Mbps differential pairs corrupted essentially every packet header.

      Stage 2, silent bus. i2cdetect -y -r 2 became empty at every address and the driver reported mvcam: failed to read chip id.

      Stage 3, no recovery. A new, correctly oriented cable changed nothing. It is now silent on two independent hosts (Pi Zero 2W and Radxa Zero 3E). Tested Radxa and it still works fine with Arducam IMX477 camera.

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

        @roboticsmick 529c0f58-1c2c-4723-a2b2-ab7cee0f61f7-image.jpeg
        You can start by checking if these power supplies are working fine. On the software side, I'd recommend restoring the defaults to give it a try.

        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