Spaces:
Sleeping
Sleeping
Ticket Name: Linux/TDA2: TDA2x Pin Muxing for Linux | |
Query Text: | |
Part Number: TDA2 Other Parts Discussed in Thread: DRA742 Tool/software: Linux Hello every one, I am trying to connect a custom camera board to TDA2x board. How can I change the pin muxing for linux ? I want to connect the cameras in vin1a,vin2a,vin6a and vin1b port. How can i do the pinmuxing for the same ? Regards, Renjith | |
Responses: | |
Hello, One way to do so is to use the pinmux tool: https://dev.ti.com/pinmux/ . You can then dump register setting to a file and use that configuration in the SDK driver (I believe it's a .dts file actually). thanks, Alex | |
Hi Alex, Thank you very much for your quick reply. I want to know one more thing , Can i use PDK for developing the same ? or PDK is only for RTOS ? Regards, Renjith | |
Renjith Mohan said: I want to know one more thing , Can i use PDK for developing the same ? or PDK is only for RTOS ? Let me ping PDK experts as this is slightly out of my expertise. They will reply here soon. thanks, Alex | |
Helllo, TI recommends to perform all the pinmux from u-boot first stage (MLO) You should describe the required pinmux settings in the board/ti/dra7xx/mux_data.h If you are using vision SDK, you are already using PDK for basic drivers. When running with Linux, some devices are controlled from A15 Linux while other are controlled from M4 RTOS. In this case, pinmux is controllled by A15 u-boot. PDK code for pinmux should not be used since it runs on M4. Regards, Nikhil D | |
Hello Nikhil, Thank you verymuch for your valuable reply.. I am working on Vision SDK in DRA74x EVM REV H.0 board, which all are the PDK drivers working with Linux ? In my case i want to connect 4 cameras , Can i use the serializer & deserializer drivers in PDK ? Do i need to configure all the things in linux ? What all are the things controlled by A15 U-boot ? Regards, Renjith | |
Hii Nikhil, Could you Help me on this ? Actually my use case is connect four camera with TDA2xx in Linux , VisionSDK version 3.04. CAM1 -> VIN1A 8bit mode. CAM2-> VIN2A 8bit mode. CAM3 -> VIN6A 8bit mode. CAM4 -> VIN1B 8bit mode. I have already tried everything within my knowledge.But dont work for me. I Set the pimux changes as in file attached. What all are the changes need to do in SDK side and Kernel Side ? Could u help to solve this problem.. 6840.pin_mux.pdf | |
Hi, For the camera capture, you can use the PDK drivers, it should work well. None of the cameras are controlled by Linux/Uboot so there isn't any conflict. I assume, If you are using TI EVM, then all the cameras are connected to i2c5. In this case, PDK drivers will also control the i2c ONLY pinmux and boardmux is setup by the u-boot first stage. Apart from that, everythin is controlled by PDK drivers. Regards, Nikhil D | |
I reviewed your pinmux document. You should describe the required pinmux settings in the board/ti/dra7xx/mux_data.h There are macros to describe the PAD registers and muxmodes. Nikhil D | |
Hi Nikhil , I am using DRA74x EVM REV H.0 board. I configured values for "dra74x_core_padconf_array, dra742_es2_0_iodelay_cfg_array" in the board/ti/dra7xx/mux_data.h But i couldn't find delay values for "dra742_es1_1_iodelay_cfg_array" in TRM/DataSheet etc. Where can i get these ioDelay values ? Regards, Renjith | |
Hi, You can find the iodelay values from the data sheet. Also, you can utilize the python tool which generates the iodelay values for the pad config that is done already. https://git.ti.com/glsdk/iodelay-config I hope this is helpful Regards, Nikhil D | |
Hi Nikhil, I have some more doubts regarding this, pin muxing done in board/ti/dra7xx/mux_data.h file. Where i can set the instances/port for VIP as per the requirement ? I want to change the SerDes config (linux) , Can i follow the "Video Driver Porting Guide for TDA2xx, TDA2Ex and TDA3xx" ? It would be greateful if you share an example ( how to set vin1b port instance/capture) . Regards, Renjith | |
Hi Ranjit, I would suggest to close this thread and open another for VIP camera configuration. The appropriate owner shall respond on that. Regards, Nikhil D | |