sample_embedding_folder2/0680584.txt

Ticket Name: Linux/TDA2EX17EVM: BT656 For TDA2Ex

Query Text:
Part Number: TDA2EX17EVM Tool/software: Linux Dear Sirs: We use latest Processor SDK Vision. We want to make sure the BT656 is really working on TDA2 so we did the following test: 1. We use J6E Board with a VAYU VISION board with the OV10635 sensor 2. When using BT601 with OV 1063x setting setting 0x4700 and 0x4708 inside the PSDK, the code working fine. 3. When using BT656 with OV 1063x setting setting 0x4700 and 0x4708 inside the PSDK and modify the related OV video setting to be a)pInstPrm->videoIfMode = SYSTEM_VIFM_SCH_ES; b)pPortCfg->syncType = SYSTEM_VIP_SYNC_TYPE_EMB_SINGLE_422_YUV; and other setting remain same as before i.e. pInstPrm->videoIfWidth = SYSTEM_VIFW_8BIT; pInprms->dataFormat = SYSTEM_DF_YUV422P; pInprms->scanFormat = SYSTEM_SF_PROGRESSIVE; ... Please refer to PROCESSOR_SDK_VISION_03_02_00_00\vision_sdk\apps\src\hlos\common\chains_common.c where captureSrc == CHAINS_CAPTURE_SRC_OV10635 The above OV BT656 setting is working in our DM81xx board, but not in J6 Entry. Do you have any idea to know what could be the problem to no VIDEO input in BT656 mode? Regards, /ckhsu

Responses:
Forgot to said, the above setting we set the pixelClk to RISING, and we also test on the FALLING and both not working. And we also use another J6Entry board and attach a TVP5158 to it, with setting BT656 on it, no matter what setting on 1CH/4CH, interlace, 8 bit, none of them work in BT656 mode. Please let me know what could be my problem. Regards, /ckhsu

Hi hsu, Can you please VIP register? I am interested in in mode and data size register.. As the config looks correct, but can you also check the board muxes are set correctly.. Regards, Brijesh

Since OV 10635 is 10 bits output in VISION board, to prevent the BT656 signal from OV is in fact from D9 to D2, we also create a H/W connector to make OV D9 to D2 is connected to D7 to D0 in J6E board. However the result is still the same. We will post the register values later after we dump it. Regards, /ckhsu

The problem is solved. This problem is only in PSDK Linux version but not in BIOS version.