From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B22A1E00B63; Wed, 11 Nov 2015 07:50:30 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 91E69E007AE for ; Wed, 11 Nov 2015 07:50:26 -0800 (PST) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id AA7E0F81199; Wed, 11 Nov 2015 08:50:25 -0700 (MST) Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id E830EF81199; Wed, 11 Nov 2015 08:50:24 -0700 (MST) To: meta-freescale@yoctoproject.org References: <56410F42.6080707@pseudoterminal.org> <564360A8.6050901@gmail.com> <564361DB.1020701@pseudoterminal.org> From: Gary Thomas Message-ID: <564363C1.5020600@mlbassoc.com> Date: Wed, 11 Nov 2015 08:50:25 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <564361DB.1020701@pseudoterminal.org> Subject: Re: [meta-fsl-arm-extra] nitrogen6x: ov5642 support in master/jethro broken X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 15:50:30 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2015-11-11 08:42, Carlos Rafael Giani wrote: > Yes, same here. The thing is, my camera is an ov5642 module. What's really interesting is that the ov5642 doesn't seem to even show up on the I2C bus with the newer kernel: 3.10.53: root@nitrogen6x:~# i2cdetect -r -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- UU UU -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 3.14.28: root@nitrogen6x:~# i2cdetect -r -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 0x3d is the ov5642 and 0x3e is ov5640_mipi > > On 2015-11-11 16:37, Gary Thomas wrote: >> On 2015-11-10 18:56, Ian Coolidge wrote: >>> Carlos, >>> >>> To follow up, I tested both the 3.14.28 image on jethro and the old 3.10.53 fido image in the blogpost I mentioned and both worked. Granted it took me two tries to get the ribbon >>> cable seated properly, maybe you're having the same issues? >>> >>> You should see "camera ov5640 is found" in dmesg if it properly detects the hardware. Then you can run this gst command to show it on the screen "gst-launch-1.0 imxv4l2videosrc >>> device=/dev/video0 ! autovideosink". >> >> I just verified this on my SabreLite which has OV5642 & OV5640_MIPI installed. >> With the 3.10.53 kernel built in July, both sensors are found and function. >> With the 3.14.28 kernel built today, only the OV5640_MIPI is found. >> >>> >>> Thanks! >>> -Ian Coolidge >>> >>> On Tue, Nov 10, 2015 at 3:25 PM, Ian Coolidge > wrote: >>> >>> Hello Carlos, >>> >>> What kernel are you running? If it's the new 3.14.28 kernel you'll need to upgrade your u-boot version to our 2015.07 u-boot. I've written a blogpost about it here: >>> https://boundarydevices.com/compiling-latest-u-boot-for-i-mx6-2015-edition/. >>> >>> If you want to keep your old u-boot version, or want an image that works for the old u-boot, we have images on this blogpost that will work and have been tested against that >>> hardware: https://boundarydevices.com/fido-release-of-yocto/ >>> >>> Thanks, >>> -Ian Coolidge >>> >>> On Mon, Nov 9, 2015 at 2:29 PM, Otavio Salvador > wrote: >>> >>> Hello Carlos, >>> >>> On Mon, Nov 9, 2015 at 7:25 PM, Carlos Rafael Giani >>> > wrote: >>> > I tried to use the nitrogen6x' camera, and saw that no ov5642 hardware was >>> > detected. The kernel module was loaded. >>> > With the fido kernel and the exact same hardware, it works just fine. >>> > Is this a known issue? >>> >>> Added Boundary's fellows on Cc. >>> >>> -- >>> Otavio Salvador O.S. Systems >>> http://www.ossystems.com.br http://code.ossystems.com.br >>> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 >>> >>> >>> >>> >>> > -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------