TDA2: The difference between TDA2HVBRQABC(R)Q1 and TDA2SXBTQABC(R)Q1

Hi,

you can check the difference between TDA2HV and TDA2SX in "Table 3-1. Device Comparison" in device's Datasheet:
www.ti.com/.../tda2sx.pdf

(I have pinged the SW experts to comment on the problem you observe)

Regards,
Yordan

Thank you

I am looking forward to hear the opinion soon

Hi,

By any chance, is it possible that the luma and chroma are swapped? May be, can you dump one of the image and offline analyze it, in one of the YUV viewer?

Regards,
Brijesh

I've already checked the display with another grabber deivce and have triple checked the swap possibility. so do you think it should be same whether using TDA2HVBRQABC(R)Q1 or TDA2SXBTQABC(R)Q1 if I use same vision SDK s/w?

Hi,

Are you testing it out with some fixed input pattern?

Rgds,
Brijesh

Hi

Yes, the color pixed pattern(white,yellow,red,blue,black bar) from the camera is being used for this debugging

Strange, is it possible to probe the vip input lines and check all bits lines are toggling..

Rgds,
Brijesh

Yes, that is also checked by an oscilloscope. every data bits and clock are toggling

ok, what processing is enabled in VIP? do you do any scaling, chroma conversion etc.. in VIP path?

Rgds,
Brijesh

Crop is enabled but the same software works fine in another H/W using a TDA2HVBRQABC(R)Q1

ok, i see you are probing at IPC_in on A15, can you first probe at the capture output, then dup, then select and see if where bits are getting missed. Also i am assuming pinmux is setup correctly for the VIP input in both the cases..

Rgds,
Brijesh

Hello ,

I am assuming that you are probing the image data at the IPC In on A15, could you please confirm the same?

Rgds,
Brijesh

That is correct . I'm probing the image at the IPC in on A15 with image analyzer in ccs v8 and display the monitor as well . You mean i can probe right behind of VIP in IPU1-0? If that so, Can you please tell me the file name and buffer on vision sdk? I thought that source part is generated automatically so i didnt take care much for this debugging reason

Thank you

Hi,

Yes, you could buffer at the each link's output and see where is the problem. 

For the capture, put break point on the capture callback and once it calls Fvid2_Dequeue API, you could get the buffer address from the Fvid2_FrameList.frames[0].addr[0][0]..  Take buffer address from this variable and then dump buffer from the CCS memory window.

Rgds,

Brijesh

Ok i will try to probe at those points thank you

Hi

Just to double check, do you mean that the file name is fvid2_drvMgr.c in /ti_component/drivers/pdk_01_08_00_16/packages/ti/drv/vps/src/fvid2/src path ?

If there is no different output coming out with probing the point on A15, Can I make sure the vision SDK s/w is absolutly compatible with both SOCs ?

which means no need to change anything on S/W(VIP part) to apply both sides ?

Thank you

 

  

No, if you are using VIP capture link, then you could put breakpoint on CaptureLink_drvProcessData function. After it calls Fvid2_Dequeue, at around line 744, you could get the address of the captured frame in frameList.frames[0]->addr[0][0].

Rgds,

Brijesh

I've just probed the point which you have mentioned above, however it does same. it comes up exact same address value where on A15
Thank you

You mean, the input buffer containing YUV still have missing 2 bits??

Rgds,
Brijesh

I mean the image from memory dump still looks green

But more strange thing is that the data signal on h/w comes in to the TDA2X

Can you please share the image you captured?

Also can you please help me understand how sensor is connected to VIP??

sure,

Hi MB,

I was asking if you could dump this memory, from the address 0x8b187e00 and size 1280*2*720 and share it here. You could dump the memory from the CCS memory windows. Just right click on CCS memory window and select save memory option, it will ask for the start address, size and format, save it in binary format..

Rgds,
Brijesh

Hi

As you said, I've attached the binary file

Thank you

memory dump.dat

Hi MB,

From the dump, it looks like the data is 12bit, not really 8bit per component. I dont really see any msb 4 bits set. could you please check if the YUV input is 12bit or 8bit per component?

Rgds,
Brijesh

Hi

The yuv data is 16bit from a camera that is composed of 8bit per Y and another 8bit per U and V

My final guess is 4bit missing on UV TDA2X_mb.pptx

I've attached the block diagram with the result of mesuring. can you please check it out which is possible to force to miss 4bit on S/W side?

Thank you

p.s : Blue display   : 0xEB43  correct

       Green display : 0x0B03   wrong

Hi MB,

I have one question, i see that you are using vin2a in 16bit input mode, but these pins are muxed with the vout2 pins. Is it possible that when you are overwriting pinmux setting of vin2a when you set pinmux for vout2?
vin6a is also muxed with the mcasp and other modules.
Essentially when it is running, could you please recheck pinmux settings for the ports where you are seeing issue?

Rgds,
Brijesh

Hi
Can you please point out the points what i need to see for configuring pinmux for those you mentioned above?
Furthermore, An another H/W using TDA2HVBRQABC(R)Q1 is working as with those setup

Thank you

Hi MB,

In both the HW, SW is same? Absolutely no change in SW?
When the usecease is running, you could open CCS memory window and check PAD IO registers for the VIP input ports..

Rgds,
Brijesh

Yes absolutely same. I use a sd card to run the s/w . So there is no chance to put different one

Thank you

Hi MB,

You could check the difference between these two devices at below link.

www.ti.com/.../sprs951e.pdf

I don't any difference in VIP and DSS between these two device..

Are you sure the other HW components (Serializer/Deserializer, their configuration etc..) are also same between them?

Rgds,
brijehs

Yes 100% same except DDR memory size(512mb and 1G) and the soc
Is there any chance the TDA2SX is malfunctioning? I have heard the TDA2SX we have that is ES sample version

ok, lets start with the pinmux register, can you dump pinmux registers for vin2a and vin6a and share it? Dump from CCS memory window when usecase is already running..

Rgds,
Brijesh

Sure i will share it when it is ready
Thank you

register.txtHi

I've attached the register dump file from CCS

Thank you

Hi MB,

It looks like you have shared DSP registers. I was actually asking for the Pinmux registers for VIN2A and VIN6A. The pinmux registers are part of the control module.

Rgds,

Brijesh

Hi

I've checked all register box as like attached picture

Is there other way to get the information for pinmux register?

Thank you