nt:
> >
> > "The OMAP3 ISP is quite picky about its input 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 un
Peter Meerwald 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 majord.
> 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 tim
h the yavta
> tool. I 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 c
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
a@vger.kernel.org
Sent: 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
ses 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 nex
registers on the CCDC
> and found that the only bit set was the CCDC_BUSY register.
[snip]
> I THINK I'm suffering from a data underflow, where the previous batch
> of images did not complete, or something.
The OMAP3 ISP is quite picky about its input signals and doesn't grace
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(st
running into what looks like the same issue with the
> ccdc getting
> wedged...
>
> Having introduced some debugging into the isr I get:
>
> 55.123840] power on called
> [ 55.135528] interrupt 2147483648
> [ 55.139038] interrupt 2147483648
> [ 55.142578]
errupt 2147483648
[ 55.156188] interrupt 2147483648
[ 55.159576] interrupt 2147483648
[ 55.162994] interrupt 2147483648
[ 55.181854] end of set power
[ 55.241821] get format called
[ 55.245025] get pad format
[ 55.248138] in
[ 55.249877] get format called
[ 55.252990] get pad format
[ 55
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 Came
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,
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 mt9
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 w
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
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
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
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 a
19 matches
Mail list logo
