signals and doesn't
gracefully handle missing or extra sync pulses for instance. A CCDC
won't become idle! message usually indicates that the CCDC received a
frame of unexpected size (this can happen if the sensor stops in the
middle of a frame for instance), or that the driver had no time
for instance. A CCDC won't become idle!
message usually indicates that the CCDC received a frame of unexpected size
(this can happen if the sensor stops in the middle of a frame for instance),
or that the driver had no time to process the end of frame interrupt before
the next frame arrived (either
Peter Meerwald pmeerw at pmeerw.net writes:
Hello Peter,
Many thanks for posting your solution. Your idea sounds great and I'll give
it a try on next monday.
Thanks again.
Best Regards, Tom
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to
configured it to wait for pressing ENTER before giving the STREAMON
command. So now sometimes all works fine. I grab my images and they are as I
imagined. But sometimes I get the ccdc won't become idle error. I really
don't understand what this error causes.
Are there any clear reasons what
command. So now sometimes all works fine. I grab my images and they are as I
imagined. But sometimes I get the ccdc won't become idle error. I really
don't understand what this error causes.
Are there any clear reasons what this problem causes?
Best regrads, Tom
--
To unsubscribe from this list: send
: Monday, September 9, 2013 4:07:33 PM
Subject: ov3640 sensor - CCDC won't become idle!
Hi all,
as the subject says I got a problem with the ccdc.
My pipeline is: sensor - ccdc - memory
By doing some research I found a appropriate answer from Laurent:
The OMAP3 ISP is quite picky about its input
. A CCDC won't become idle!
message usually indicates that the CCDC received a frame of unexpected size
(this can happen if the sensor stops in the middle of a frame for instance),
or that the driver had no time to process the end of frame interrupt before
the next frame arrived (either because
Hi Andrew,
On Monday 21 November 2011 00:54:04 Andrew Tubbiolo wrote:
Hi All:
I'm having fun with my new camera project that uses the mt9p031
camera. I'm getting nice raw stills, and that's great, but every 16 or
so images I take I get a troublesome error.
CCDC won't become idle
Hi All:
I'm having fun with my new camera project that uses the mt9p031
camera. I'm getting nice raw stills, and that's great, but every 16 or
so images I take I get a troublesome error.
CCDC won't become idle!
The message is coming from...
static int ccdc_isr_buffer(struct isp_ccdc_device
[ 55.619201] interrupt 512
[ 55.629180] interrupt 256
[ 55.705627] interrupt 2147483648
[ 55.725738] interrupt 512
[ 55.735687] interrupt 256
[ 55.740417] omap3isp omap3isp: CCDC won't become idle!
[ 55.811645] interrupt 2147483648
[ 55.832000] interrupt 512
[ 55.842010] interrupt 256
Hi Laurent,
I'm just trying to get an mt9v034 sensor working on a beagle xm.
Everything more or less works, except that after a random number
of frames of capture, I tend to get won't become idle messages
and the vd0 and vd1 interrupts tend to turn up at same time.
I was just wondering if there
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote:
Hi Laurent,
I'm just trying to get an mt9v034 sensor working on a beagle xm.
Everything more or less works, except that after a random number
of frames of capture, I tend to get won't become idle messages
and the vd0 and vd1
Hi Sakari,
On Tuesday 05 July 2011 14:19:16 Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote:
Hi Laurent,
I'm just trying to get an mt9v034 sensor working on a beagle xm.
Everything more or less works, except that after a random number
of frames of
On 07/05/11 13:19, Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote:
Hi Laurent,
I'm just trying to get an mt9v034 sensor working on a beagle xm.
Everything more or less works, except that after a random number
of frames of capture, I tend to get won't
On Tue, Jul 05, 2011 at 02:48:57PM +0100, Jonathan Cameron wrote:
On 07/05/11 13:19, Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote:
Hi Laurent,
I'm just trying to get an mt9v034 sensor working on a beagle xm.
Everything more or less works, except
On Tuesday 05 July 2011 16:38:07 Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 02:48:57PM +0100, Jonathan Cameron wrote:
On 07/05/11 13:19, Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote:
Hi Laurent,
I'm just trying to get an mt9v034 sensor
On 07/05/11 16:02, Laurent Pinchart wrote:
On Tuesday 05 July 2011 16:38:07 Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 02:48:57PM +0100, Jonathan Cameron wrote:
On 07/05/11 13:19, Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote:
Hi Laurent,
I'm just
On Tue, Jul 05, 2011 at 05:02:52PM +0200, Laurent Pinchart wrote:
On Tuesday 05 July 2011 16:38:07 Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 02:48:57PM +0100, Jonathan Cameron wrote:
On 07/05/11 13:19, Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron
[ 55.725738] interrupt 512
[ 55.735687] interrupt 256
[ 55.740417] omap3isp omap3isp: CCDC won't become idle!
[ 55.811645] interrupt 2147483648
[ 55.832000] interrupt 512
[ 55.842010] interrupt 256
Repeat last 4 lines ad infinitum or if lucky till my program gives up
and closes everything
19 matches
Mail list logo
