与ds90ub954-Q1EVM解串器连接失败

zhiwu jiang

Prodigy 110 points

Part Number: SK-TDA4VM
Other Parts Discussed in Thread: DS90UB954-Q1EVM, , DS90UB954-Q1

sdk: ti-processor-sdk-linux-j7-evm-08_06_01_02

连接SK-TDA4VM与ds90ub954-Q1EVM：

使用ds90ub954-Q1EVM的J26连接到SK-TDA4VM的J24，ds90ub954-Q1EVM的J26已经填充零欧姆电阻，连接情况如下图：

并在sk-tda4vm的/run/media/mmcblk0p1/uEnv.txt文件中添加如下dtbo：

name_overlays=k3-j721e-fpdlink-sk-fusion.dtbo

重启发现问题：

1 年多前

0 Gary Lu 1 年多前

TI__Mastermind 27060 points

确认一下通信协议的配置是否正确，波特率、数据位和停止位等参数

0 zhiwu jiang 1 年多前回复 Gary Lu

Prodigy 110 points

你好，可以说得清楚一点吗？在哪里配置呢？

0 Defu Liu 1 年多前回复 Gary Lu

Prodigy 90 points

你好，我也遇到了这个问题，能详细说一下解决方法吗谢谢

0 Gary Lu 1 年多前

TI__Mastermind 27060 points

您是如何上电ds90ub954-Q1EVM的？

您能试试这个顺序吗?(先上电ds90ub954-Q1EVM，再上电SK板)

0 zhiwu jiang 1 年多前回复 Gary Lu

Prodigy 110 points

您好，我们是按照您所说这个顺序上电的，还是不行。

我们使用的是SK板的CSI2-EXP接口连接ds90ub954-Q1EVM，添加的是k3-j721e-fpdlink-sk-fusion.dtbo，请问设备树中有需要修改的地方吗？

下面是k3-j721e-fpdlink-sk-fusion.dts

// SPDX-License-Identifier: GPL-2.0
/*
 * Copyright (C) 2021 Texas Instruments Incorporated - http://www.ti.com/
 */

/dts-v1/;
/plugin/;

/ {
	fragment@101 {
		target-path = "/";

		__overlay__ {
			clk_fusion_25M_fixed: fixed-clock-25M {
				compatible = "fixed-clock";
				#clock-cells = <0>;
				clock-frequency = <25000000>;
			};
		};
	};
};

&main_i2c3 {
	#address-cells = <1>;
	#size-cells = <0>;

	i2c-switch@70 {
		compatible = "nxp,pca9543";
		#address-cells = <1>;
		#size-cells = <0>;
		reg = <0x70>;

		cam0_i2c: i2c@0 {
			#address-cells = <1>;
			#size-cells = <0>;
			reg = <0>;

			ds90ub960_0: deser@3d {
				compatible = "ti,ds90ub960-q1";

				reg-names = "main", "ser0", "ser1", "ser2", "ser3";
				reg       = <0x3d>, <0x44>, <0x45>, <0x46>, <0x47>;

				clocks = <&clk_fusion_25M_fixed>;

				i2c-alias-pool = /bits/ 16 <0x4a 0x4b 0x4c 0x4d 0x4e 0x4f>;

				data-rate = <1600000000>;

				#clock-cells = <0>;

				ds90ub960_0_ports: ports {
					#address-cells = <1>;
					#size-cells = <0>;

					/* CSI-2 */
					port@4 {
						reg = <4>;
						ds90ub960_0_csi_out: endpoint {
							clock-lanes = <0>;
							data-lanes = <1 2 3 4>;
							remote-endpoint = <&csi2_phy0>;
						};
					};
				};

				ds90ub960_0_atr: i2c-atr {
					#address-cells = <1>;
					#size-cells = <0>;
				};
			};

			ds90ub960_1: deser@36 {
				compatible = "ti,ds90ub960-q1";

				reg-names = "main", "ser0", "ser1", "ser2", "ser3";
				reg       = <0x36>, <0x54>, <0x55>, <0x56>, <0x57>;

				clocks = <&clk_fusion_25M_fixed>;

				i2c-alias-pool = /bits/ 16 <0x5a 0x5b 0x5c 0x5d 0x5e 0x5f>;

				data-rate = <1600000000>;

				#clock-cells = <0>;

				ds90ub960_1_ports: ports {
					#address-cells = <1>;
					#size-cells = <0>;

					/* CSI-2 */
					port@4 {
						reg = <4>;
						ds90ub960_1_csi_out: endpoint {
							clock-lanes = <0>;
							data-lanes = <1 2 3 4>;
							remote-endpoint = <&csi2_phy1>;
						};
					};
				};

				ds90ub960_1_atr: i2c-atr {
					#address-cells = <1>;
					#size-cells = <0>;
				};
			};
		};
	};
};

&csi0_port0 {
	status = "okay";

	csi2_phy0: endpoint {
		remote-endpoint = <&ds90ub960_0_csi_out>;
		clock-lanes = <0>;
		data-lanes = <1 2 3 4>;
	};
};

&csi1_port0 {
	status = "okay";

	csi2_phy1: endpoint {
		remote-endpoint = <&ds90ub960_1_csi_out>;
		clock-lanes = <0>;
		data-lanes = <1 2 3 4>;
	};
};