Hi Sriram,
On Tue, Feb 28, 2012 at 8:46 AM, Sriram V <vshrirama@xxxxxxxxx> wrote:
> Hi Aguirre Sergio,
>
> On Tue, Feb 28, 2012 at 9:08 AM, Aguirre, Sergio <saaguirre@xxxxxx> wrote:
>> Sriram,
>>
>> On Sun, Feb 26, 2012 at 8:54 AM, Sriram V <vshrirama@xxxxxxxxx> wrote:
>>> Hi,
>>> When I take the dump of the buffer which is pointed by "DATA MEM
>>> PING ADDRESS". It always shows 0x55.
>>> Even if i write 0x00 to the address. I do notice that it quickly
>>> changes to 0x55.
>>> Under what conditions could this happen? What am i missing here.
>>
>> If you're using "yavta" for capture, notice that it clears out the
>> buffers before queuing them in:
>>
>> static int video_queue_buffer(struct device *dev, int index, enum
>> buffer_fill_mode fill)
>> {
>> struct v4l2_buffer buf;
>> int ret;
>>
>> ...
>> ...
>> if (dev->type == V4L2_BUF_TYPE_VIDEO_OUTPUT) {
>> ...
>> } else {
>> if (fill & BUFFER_FILL_FRAME)
>> memset(dev->buffers[buf.index].mem, 0x55, dev->buffers[index].size);
>> if (fill & BUFFER_FILL_PADDING)
>> memset(dev->buffers[buf.index].mem + dev->buffers[index].size,
>> 0x55, dev->buffers[index].padding);
>> }
>> ...
>> }
>>
>> So, just make sure this condition is not met.
>>
>>>
>
> Unfortunately, this condition is met. For some reason, ISS thinks
> it has got valid frame. Whereas the Image data is not populated into
> the buffers.
> The register CSI2_CTX_CTRL1_i[COUNT] keeps getting toggled between 0 and 1
> indicating a frame arrival.
>
> I also notice that on some frames, The first 0x200 bytes contains data
> other than 0x55
> and the rest are 0x55.
>
> Probably this could be related to resolution settings or hsync and
> vsync settings.
> Probably, my chip configuration is faulty.
Hmm, sounds like it.
Can you try adding this to the top of the file?
#define DEBUG
So that the dev_dbg() prints get executed?
I'm curious to see if you detect any ComplexIO errors on omap4iss_csi2_isr()...
>
>>> I do notice that the OMAP4 ISS is tested to work with OV5640 (YUV422
>>> Frames) and OV5650 (Raw Data)
>>> When you say 422 Frames only. Do you mean 422-8Bit Mode?.
>>
>> Yes. When saving YUV422 to memory, you can only use this mode AFAIK.
>>
>>>
>>> I havent tried RAW12 which my device gives, Do i have to update only
>>> the Data Format Selection register
>>> of the ISS for RAW12?
>>
>> Ok, now it makes sense.
>>
>> So, if your CSI2 source is giving, you need to make sure:
>>
>> CSI2_CTX_CTRL2_0.FORMAT[9:0] is:
>>
>> - 0xAC: RAW12 + EXP16
>> or
>> - 0x2C: RAW12
>>
>> The difference is that the EXP16 variant, will save to memory in
>> expansion to 2 bytes, instead of 12 bits, so it'll be byte aligned.
>>
>> Can you try attached patch?
>
> With RAW12 configuration, I dont see any interrupts at all.
Ok,
Then this means your CSI2 transmitter (sensor) is actually sending
YUV422, and not RAW12.
Nevermind that patch then...
Regards,
Sergio
>
>
>>
>> Regards,
>> Sergio
>>
>>>
>>> Please advice.
>>>
>>>
>>> On Thu, Feb 23, 2012 at 11:24 PM, Sriram V <vshrirama@xxxxxxxxx> wrote:
>>>> Hi,
>>>> 1) An Hexdump of the captured file shows 0x55 at all locations.
>>>> Is there any buffer location i need to check.
>>>> 2) I have tried with "devel" branch.
>>>> 3) Changing the polarities doesnt help either.
>>>> 4) The sensor is giving out YUV422 8Bit Mode,
>>>> Will 0x52001074 = 0x0A00001E (UYVY Format) it bypass the ISP
>>>> and dump directly into memory.
>>>>
>>>> On 2/23/12, Aguirre, Sergio <saaguirre@xxxxxx> wrote:
>>>>> Hi Sriram,
>>>>>
>>>>> On Thu, Feb 23, 2012 at 11:25 AM, Sriram V <vshrirama@xxxxxxxxx> wrote:
>>>>>> Hi,
>>>>>> 1) I am trying to get a HDMI to CSI Bridge chip working with OMAP4 ISS.
>>>>>> The issue is the captured frames are completely green in color.
>>>>>
>>>>> Sounds like the buffer is all zeroes, can you confirm?
>>>>>
>>>>>> 2) The Chip is configured to output VGA Color bar sequence with
>>>>>> YUV422-8Bit and
>>>>>> uses datalane 0 only.
>>>>>> 3) The Format on OMAP4 ISS is UYVY (Register 0x52001074 = 0x0A00001E)
>>>>>> I am trying to directly dump the data into memory without ISP processing.
>>>>>>
>>>>>>
>>>>>> Please advice.
>>>>>
>>>>> Just to be clear on your environment, which branch/commitID are you based
>>>>> on?
>>>>>
>>>>> Regards,
>>>>> Sergio
>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Sriram
>>>>>> --
>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>>>>>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Sriram
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Sriram
>
>
>
> --
> Regards,
> Sriram
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
