FPDLink3 ev and question

Hi Lynn,

Can you specify which FPD-Link III part numbers are on your boards?

Thanks,

Ryan

AIDA APPS

Thanks, Ryan!

The Part No. on serielizer board is DS90UB913,   the part on Deserielizer is DS90UB914. i need run my camera sensor at 74MHz pixel clock, sensor slave address is 0x20. senor part No. is Aptina MT9M024.

the demo kits for DS90UB913 and DS90UB914 is Rev2.

Hi Lynn,

The user guide, found here, contains a quick setup section. It sounds like you need 12-bit high-speed mode with external PCLK, set by the mode switches. These are discussed on page5 and page7 of the user guide.

The board schematics and layouts are also contained in the user guide. Let me know if you have more questions or run into trouble with the setup.

Regards,

Ryan

AIDA APPS

i have this document and looked it already. it doesn't specify about the command and setup clearly. i'm able to get link and i can see video transferred with connecting I2C directly from Sensor( and serializer) to my base board (deserializer). i could see it's not right resolution or data format or sychronization problem. i really need the detail information about  setting  pixel clock(74MHz around), 12 bit data, Aptina MT9M024 sensor and go through this quick. 

Lynn, can you please share a block diagram of your system?  Also, how are you converting HiSPi data?  Are you using the SN65LVDS324 for this function?

Best regards,
RE

Thanks, RossE!

No, i don't use SN65LVDS324. i have Ti DS90UB913Q/DS90UB914Q demo kit Rev2.0. i connect this demo kit in between Aptina kit that one side is the camera with Aptina sensor MT9M024 and one side with Aptina demo2x. the data format will be the raw data. i know that someone in Ti has gone through Aptina sensor with Ti demo kit, but i don't know what control board was used. anyway some one in Ti should know that what need to be done to get it correctly.

Best,

Lynn

Hi Lynn,

Based on your description it sounds like you receive the picture OK if you bypass the I2C bridge FPD3 link between the 913/914 by connecting the I2C interfaces directly. Could you tell me the status of the following registers in the deserializer (914)?

1. 0x03'h
2. 0x05'h
3. 0x08'h
4. 0x09'h

Thanks, Ryan!

default register value

0x03 h: 0xE9

0x05 h: 0x00

0x08 h: 0x00

0x09 h: 0x00

i'm able to send the new value to them through Devware after i  get  the devware launched through additional I2C wires conneting to image sensor directly when i set to 10 bit mode on deserializer side. this is not what our final design goal. also i could see video wasn't good because of video resolution or data format or synchronization.

the big problem is that when i set to deserializer to12bits high speed mode(12 bits, 74Mhz around) that what we need run, even i used addition wires for I2C, i could see from Devware GUI showing all the frames dropped, which meant major data transfer not right.

i could read back the mode state from deserializer, it showed set to 12 bit high frequency selection.

i heard someone in Ti has gone through your kit with Aptina camera. i need know what control board that was using on Ti side, if setting to 12 bit high frequency.

Best Regards,

Lynn

Hi Lynn,

Dropped frames makes it sound like you could have a link issue. Is the LOCK pin reading a constant logic high during operation? The eval boards should have a Lock LED, as well as a Lock Latch LED that will light up if Lock status is lost during operation. Be sure to reset the latch circuit first and then monitor it for coincidence with the dropped frames.

Could you tell me what kind of cable you are using to connect between the serializer and deserializer? If possible, a picture and/or block diagram of your setup would be immensely helpful.

Thanks,

Ryan

Hi, Ryan,

i'm using DS90UB913 and DS90UB914 ev board from Ti to do the evaluation. we are using Aptina demo2x base board for controller and MT9M024 for camera sensor. we inserted your demo kit in between for serializer and de serializer. we had difficulty to get good video. without extra  I2C wires connecting from Ser to Deser, nothing can be read from Deser side. with extra  I2C wires connecting from Ser to Deser, the bad quality can be seen. 

our final design goal is to design camera with your DS90UB913, then use your DS90UB914 to convert serial data back to parallel. since we couldn't get good results, we can't move forward to final design,

i'm looking expertise support for your demo working with Aptina demo2x kit.

Thanks,

Lynn

your kit is using rosenbarger connector and cable.

Hi Lynn,

Did you ensure that your board mode switch were set to external PCLK (on the 913 serializer board), and 12-bit high-frequency mode (on the 914 deserializer board). I think the default factory settings are 10-bit high-frequency mode, which would not work (or work poorly) with your imager.

Can you take a close up picture of each board (both the serializer and deserializer)? If you don't want to post it on the open forum, please send to me at ryan (dot) bailey (at) ti (dot) com.

Best Regards,

Ryan

SVA APPS

Thanks, Ryan!

all the set up OK and checked already. when set to 10-bit mode, with extra direct I2C connection, i'm able to see the bad quality video; everything else kept the same, just change to 12-bit mode, nothing could be displayed. i spent a lot of time on that, verified almost everything except each single component, but i did see some component populate or not on the board is different from your document. not sure if hardware configuration issue or not.

without extra direct I2C connection between Ser and DeSer, Aptina Devware couldn't start due to no sensor found( this is because of sensor no reponse).

the problem is how to make your demo kit to work with Aptina demo kit demo2x(base board for control, header board is camera image).

i've got some bat file for running your kit with Aptina, but it's till not working yet. i really need the support for how to make it work with Aptina kit. because my final proposal for our camera design will be image sensor plus your serializer 913. if we can't see your demo kit working well, then we can't move to final design.

Hi Lynn,

Can you email me directly at:

ryan (dot) bailey (at) ti (dot) com

I think there may be some customer-specific historical context here that I can't post on the open forum. Also, I'd like to bring some of my colleagues into the conversation as well so the email approach would be easier.