cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Explorer
Explorer
866 Views
Registered: ‎09-06-2019

SATA link connection issues

Hi I'm trying to bring up a sata link (SATA0, GT Lane 2) using a 125MHz reference clock but am having issues with the link establishing. All tools are in 2019.1.

Here is a snippet of the boot message:

 

[    2.408498] ahci-ceva fd0c0000.ahci: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    2.417457] ahci-ceva fd0c0000.ahci: flags: 64bit ncq sntf pm clo only pmp fbs pio slum part ccc sds apst
[    2.428256] scsi host0: ahci-ceva
[    2.431783] scsi host1: ahci-ceva
[    2.435187] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 39
[    2.443105] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 39
[    2.451597] zynqmp_pll_disable() clock disable failed for apll_int, ret = -13
[    2.459921] macb ff0d0000.ethernet: Not enabling partial store and forward
[    2.467329] libphy: MACB_mii_bus: probed
[    2.471238] mdio_bus ff0d0000.ethernet-ffffffff: Loop over the child nodes and register a phy_device for each phy
[    2.481500] mdio_bus ff0d0000.ethernet-ffffffff: address found. scan phy phy at address 0
[    2.489680] mdio_bus ff0d0000.ethernet-ffffffff: This child node is a phy node of mdio
[    2.500831] mdio_bus ff0d0000.ethernet-ffffffff: address found. scan phy phy at address 1
[    2.509019] mdio_bus ff0d0000.ethernet-ffffffff: This child node is a phy node of mdio
[    2.519817] mdio_bus ff0d0000.ethernet-ffffffff: address found. scan phy phy at address 2
[    2.528000] mdio_bus ff0d0000.ethernet-ffffffff: This child node is a phy node of mdio
[    2.535974] mdio_bus ff0d0000.ethernet-ffffffff: MDIO device at address 2 is missing.
[    2.543799] mdio_bus ff0d0000.ethernet-ffffffff: address found. scan phy phy at address 3
[    2.551969] mdio_bus ff0d0000.ethernet-ffffffff: This child node is a phy node of mdio
[    2.559939] mdio_bus ff0d0000.ethernet-ffffffff: MDIO device at address 3 is missing.
[    2.568348] TI DP83867 ff0d0000.ethernet-ffffffff:00: attached PHY driver [TI DP83867] (mii_bus:phy_addr=ff0d0000.ethernet-ffffffff:00, irq=POLL)
[    2.581382] macb ff0d0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0d0000 irq 30 (00:0a:35:00:00:02)
[    2.591595] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[    2.598148] xilinx-axipmon fd0b0000.perf-monitor: Probed Xilinx APM
[    2.604636] xilinx-axipmon fd490000.perf-monitor: Probed Xilinx APM
[    2.611118] xilinx-axipmon ffa10000.perf-monitor: Probed Xilinx APM
[    2.617801] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 32
[    2.624141] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 33
[    2.630564] zynqmp_gpd_attach_dev() domain12 request failed for node 40: -13
[    2.637607] sdhci-arasan ff170000.mmc: failed to add to PM domain domain12: -13
[    2.644917] sdhci-arasan: probe of ff170000.mmc failed with error -13
[    2.653477] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-07-14 04:50:38 UTC (16779038)
[    2.662177] of_cfs_init
[    2.664657] of_cfs_init: OK
[    2.668277] zynqmp_clk_gate_is_enabled() clock get state failed for gtgref0_ref, ret = -22
[    2.676552] zynqmp_clk_gate_disable() clock disable failed for gtgref0_ref, ret = -22
[    2.684750] ALSA device list:
[    2.687709]   No soundcards found.
[    2.769534] ata2: SATA link down (SStatus 0 SControl 330)
[    4.661358] ata1: SATA link down (SStatus 1 SControl 330)
[    6.891388] ata1: SATA link down (SStatus 1 SControl 330)
[    9.119333] ata1: SATA link down (SStatus 1 SControl 330)
[   11.347333] ata1: SATA link down (SStatus 1 SControl 330)
[   13.575333] ata1: SATA link down (SStatus 1 SControl 330)
[   13.580729] ata1: EH pending after 5 tries, giving up
[   13.585901] Freeing unused kernel memory: 512K

 

Once in the kernel I attempt to scan for devices (as presented here https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842339/SATA

 

 # echo "- - -" > /sys/class/scsi_host/host0/scan
[ 1050.237467] ata1: SATA link down (SStatus 1 SControl 330)
[ 1052.465455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1054.693456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1056.921455] ata1: SATA link down (SStatus 1 SControl 330)
# [ 1059.149455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1061.377451] ata1: SATA link down (SStatus 1 SControl 330)
[ 1063.605455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1065.833455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1068.061455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1070.289455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1072.517455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1074.745456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1076.973459] ata1: SATA link down (SStatus 1 SControl 330)
[ 1079.201455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1081.429455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1083.657455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1085.885463] ata1: SATA link down (SStatus 1 SControl 330)
[ 1088.113455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1090.341455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1092.569455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1094.797456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1097.025456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1099.253456] ata1: SATA link down (SStatus 1 SControl 330)
echo "- - -" > /sys/class/scsi_host/host1/scan
[ 1100.011660] ata2: SATA link down (SStatus 0 SControl 330)
# [ 1101.481456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1103.713455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1105.941456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1108.169455] ata1: SATA link down (SStatus 1 SControl 330)
[ 1110.397456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1112.625456] ata1: SATA link down (SStatus 1 SControl 330)
[ 1114.853456] ata1: SATA link down (SStatus 1 SControl 330)

But as you can see no links are ever established.

 

This is my current ahci device tree node in (dts and dtsi entries). Here is my system-user entry:

 

&sata {
	status = "okay";
	ceva,p0-cominit-params = <0x18401828>;
	ceva,p0-comwake-params = <0x614080e>;
	ceva,p0-burst-params = <0x13084a06>;
	ceva,p0-retry-params = <0x96a43ffc>;
	ceva,p1-cominit-params = <0x18401828>;
	ceva,p1-comwake-params = <0x614080e>;
	ceva,p1-burst-params = <0x13084a06>;
	ceva,p1-retry-params = <0x96a43ffc>;
	ceva,broken-gen2;
};

&serdes {
	status = "okay";
};

and default tree configuration generated by my hdf:

		sata: ahci@fd0c0000 {
			compatible = "ceva,ahci-1v84";
			status = "disabled";
			reg = <0x0 0xfd0c0000 0x0 0x2000>;
			interrupt-parent = <&gic>;
			interrupts = <0 133 4>;
			power-domains = <&zynqmp_firmware 28>;
			#stream-id-cells = <4>;
		/*	iommus = <&smmu 0x4c0>, <&smmu 0x4c1>,
				 <&smmu 0x4c2>, <&smmu 0x4c3>;*/
		};

Could anyone provide some guidance into resolving this issue? Thanks in advance!

 

0 Kudos
5 Replies
Highlighted
Explorer
Explorer
849 Views
Registered: ‎09-06-2019

I should also mention that this port is connected and attempting to establish a link with a port multiplier

0 Kudos
Highlighted
Explorer
Explorer
729 Views
Registered: ‎09-26-2014

Hello.

I have the same problem. Were you able to resolve it?

0 Kudos
Highlighted
Explorer
Explorer
667 Views
Registered: ‎09-06-2019

no unfortunately not though it may be a signal integrity issue on our board

0 Kudos
Highlighted
Explorer
Explorer
606 Views
Registered: ‎09-26-2014

&sata {
ceva,p0-burst-params = /bits/ 8 <0x13 0x08 0x4A 0x06>;
ceva,p0-cominit-params = /bits/ 8 <0x18 0x40 0x18 0x28>;
ceva,p0-comwake-params = /bits/ 8 <0x06 0x14 0x08 0x0E>;
ceva,p0-retry-params = /bits/ 16 <0x96A4 0x3FFC>;
ceva,p1-burst-params = /bits/ 8 <0x13 0x08 0x4A 0x06>;
ceva,p1-cominit-params = /bits/ 8 <0x18 0x40 0x18 0x28>;
ceva,p1-comwake-params = /bits/ 8 <0x06 0x14 0x08 0x0E>;
ceva,p1-retry-params = /bits/ 16 <0x96A4 0x3FFC>;
status = "okay";
xlnx,tz-nonsecure-sata0 = <0x0>;
xlnx,tz-nonsecure-sata1 = <0x0>;
phy-names = "sata-phy";
phys = <&lane0 1 0 3 150000000>;
};

&serdes {
status = "okay";
};

In my board, i have problem with not soldering connector. 

Now, with these lines in system-user.dtsi, SATA is detected.

Highlighted
Explorer
Explorer
563 Views
Registered: ‎09-06-2019

We are believe our SATA issues are also related to hardware. Using a different target board with the same image we were able to detect the media. 

0 Kudos