This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to enable vin1b, vin3a, vin4a on TDA2xx

Hi,

I want to add 3 more channels on TDA2xx.

Following table shows relatived ball numbers and its function:

Ball Number Ball name
AD3 vin1b_d0
AD2 vin1b_d1
AE6 vin1b_d2
AE2 vin1b_d3
AE1 vin1b_d4
AE5 vin1b_d5
AE3 vin1b_d6
AF1 vin1b_d7
AH7 vin1b_clk1
AD9 vin1b_hsync1
AF9 vin1b_vsync1
B7 vin3a_d0
B8 vin3a_d1
A7 vin3a_d2
A8 vin3a_d3
C9 vin3a_d4
A9 vin3a_d5
B9 vin3a_d6
A10 vin3a_d7
P1 vin3a_clk0
C11 vin3a_hsync0
E11 vin3a_vsync0
B14 vin4a_d0
J14 vin4a_d1
G13 vin4a_d2
J11 vin4a_d3
E12 vin4a_d4
F13 vin4a_d5
C12 vin4a_d6
D12 vin4a_d7
B26 vin4a_clk1
E21 vin4a_hsync1
F20 vin4a_vsync1

Can anyone tell me how to enable vin1b, vin3a, vin4a based on the table?

Such as modifications of dra7-evm-infoadas, dra7-evm-vision, and mux_data.h.

Thanks,

Kevin Tsai

  • Hi Kevin,

    VIN experts can comment here. However, I did a quick test based on your table:

    1. Looks like you got a conflict for vin3a. You are trying to configure data signals in IOSET4, but you got your clock set on P1 which is in IOSET1?
    2. For vin4a you probably meant clk0/sync0 not clk1/sync1?

    Thanks,
    Alex

  • Hi Kevin,

    I have forwarded your question to the VIP experts.
    Meanwhile can you tell what is the version of the software that you use?

    Regards,
    Yordan
  • Hello,

    There are three parts of this answer:
    To enable the devices in Linux kernel (which is used only by vision DTB), you just need to add device tree nodes in the dra7-evm-vision.dtb
    For infoadas DTB, actually all VIP instances are deleted from kernel (coz linux doesn't control them), so nothing needs to be done.

    To enable the pinmuxes, you need to add entries to the bootloader mux_data.h For this, please refer TRM to find out the right muxmodes for the pads/balls you have selected. (Solve the conflicts first).

    In case you have some board muxes (which I assume you don't have), you should modify the dra7-eve-vision.dtb to add the boardmux related info in the corresponding sensor nodes.
    I am assuming that you have added additional sensors & serdes nodes (which connect to the new video interfaces) in the dra7-evm.dtsi file.

    I hope this helps.

    Regards,
    NIkhil D
  • Nikhil Devshatwar said:
    To enable the pinmuxes, you need to add entries to the bootloader mux_data.h For this, please refer TRM to find out the right muxmodes for the pads/balls you have selected. (Solve the conflicts first).

    To add some additional advice, you may also refer the the device Pad Configuration Tool (PCT) for complete list of iosets and registers. It's even easier to spot errors there and see what setting you want to apply. 

    Thanks,

    Alex

  • Hi Alex,

    1. vin3a clk should be B11
    2. Yes, vin4a -> vin4a_vsync0 , vin4a_hsync0 & vin4a_clk0

    Thanks for your correction.

    Kevin
  • Hi Yordan,

    We use VSDK v2.10. A15 OS is Linux.

    Thanks,
    Kevin
  • Hi NIkhil,

    You mentioned about dra7-evm.dtsi, but I cannot find any file named as dra7-evm.dtsi.
    Do you mean dra7.dtsi / dra7xx-vision(ov1063x).dtsi / dra7xx-vision(ov490).dtsi or all of them?

    Thanks,
    Kevin
  • Hi Kevin,

    Sorry for the typo. I mean "arch/arm/boot/dts/dra7xx-vision.dtsi" file to update the serdes and camera sensor related device tree nodes.

    Regards,
    Nikhil D