Re: ARMADA espressobin SATA drive detection failure

From: "Pali Rohár" <pali@kernel.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
	"kabel@kernel.org" <kabel@kernel.org>,
	Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: ARMADA espressobin SATA drive detection failure
Date: Fri, 12 Aug 2022 14:44:07 +0200	[thread overview]
Message-ID: <20220812124407.pdjjxpsf6pddsmsr@pali> (raw)
In-Reply-To: <20220812120028.xcnvr3ocxmmkioqi@shindev>

On Friday 12 August 2022 12:00:28 Shinichiro Kawasaki wrote:
> On Aug 12, 2022 / 10:20, Pali Rohár wrote:
> > On Friday 12 August 2022 04:56:50 Shinichiro Kawasaki wrote:
> 
> [...]
> 
> > > I noticed one difference between your system and mine: U-Boot version.
> > > On my system, it has rather old version now:
> > > 
> > >   Marvell>> version
> > >   U-Boot 2017.03-armada-17.10.2-g14aeedc (Jun 01 2018 - 15:39:10 +0800)
> > >   aarch64-linux-gnu-gcc (Linaro GCC 5.2-2015.11-2) 5.2.1 20151005
> > >   GNU ld (GNU Binutils) 2.25.0 Linaro 2015_10
> > > 
> > > Do you think it's worth trying the latest U-boot?
> > > 
> > > -- 
> > > Shin'ichiro Kawasaki
> > 
> > Yes, please update firmwares to the latests versions. Or at least try to
> > boot new U-Boot via UART (without replacing existing version) and check
> > for differences.
> > 
> > Building documentations:
> > https://trustedfirmware-a.readthedocs.io/en/latest/plat/marvell/armada/build.html
> > https://source.denx.de/u-boot/u-boot/-/blob/v2022.07/doc/README.marvell
> > 
> > UART booting documentation is currently waiting for review:
> > https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/16198
> 
> Thanks for the good references. I've managed to build U-Boot for UART booting (I
> use fedora, then needed to identify Fedora packages corresponding to guided apt
> packages. I also needed to fix a build failure in A3700-utils-marvell.)
> 
> I modified board jumper pins to UART mode and downloaded the built U-Boot using
> mox-imager. The downloaded U-Boot showed the new version and detected my SSD:
> 
>   => version
>   U-Boot 2022.10-rc2-00049-g157861e6af (Aug 12 2022 - 18:10:21 +0900)
> 
>   aarch64-linux-gnu-gcc (GCC) 12.1.1 20220507 (Red Hat Cross 12.1.1-1)
>   GNU ld version 2.37-7.fc36
>   => scsi scan
>   scanning bus for devices...
>     Device 0: (0:0) Vendor: ATA Prod.: SanDisk SDSSDA24 Rev: U210
>               Type: Hard Disk
>               Capacity: 228936.5 MB = 223.5 GB (468862128 x 512)
> 
> However, after booting Linux kernel v5.18.16 from the U-Boot, still the error
> message "ata1: SATA link down (SStatus 0 SControl 300)" is printed.
> This may indicate that the error is not related U-Boot.
> 
> Now I'm not sure what's the key difference between your system and mine. If
> there is anything I can do next, please let me know.
> 
> -- 
> Shin'ichiro Kawasaki

Probably this is SSD disk specific. I will try to prepare some kernel
changes to test if it changes something.

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy