Re: ARMADA espressobin SATA drive detection failure

From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "Pali Rohár" <pali@kernel.org>
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 04:56:50 +0000	[thread overview]
Message-ID: <20220812045650.nzisin52zfbbwhsq@shindev> (raw)
In-Reply-To: <20220810103654.w3yurhdeulgyepbb@shindev>

On Aug 10, 2022 / 19:36, Shin'ichiro Kawasaki wrote:
> On Aug 09, 2022 / 11:42, Pali Rohár wrote:
> > Hello Shinichiro!
> 
> [...]
> 
> > Sorry for late reply. At the time when you sent this message I had
> > issues with office station and was waiting for repairing support. And
> > after that I forgot about this email.
> > 
> > Now I have looked at it. For testing purposes I took Espressobin V5
> > board and some random SATA disk (some Samsung SSD). I installed latest
> > firmwares (secure-firmware, ARM trusted-firmware and U-Boot) on
> > Espressobin's SPI-NOR and Linux kernel version 5.18.16 on SD card.
> > 
> > Disk is successfully detected in U-Boot as:
> 
> Hello Pali! Thank you for looking into this. So, there should be something
> different between your system and my system.
> 
> > Could you please check if you still have these issues with the 5.18.16
> > kernel version (IIRC it should be the latest 5.18 release)?
> > 
> > And could you please check if your disk is working fine in U-Boot?
> 
> Yes, I will check these points. Let me have several days to work on them.

Hello Pali, I've tried the latest 5.18.x kernel and disk detection by U-boot.
Unfortunately, the issue is still observed with the kernel v5.18.16. When I
connect my SSD to the board, it prints out the message "ata1: SATA link down
(SStatus 101 SControl 300)", and the SSD is not detected as a sd device.

From U-Boot, my SSD is detected. "scsi scan" command shows the SSD vendor name
"SanDisk". I was able to look in ext4 filesystem on the SSD from U-Boot. So it
looks ok from U-Boot to access the SSD.

  Marvell>> scsi scan
  scanning bus for devices...
  Target spinup took 0 ms.
  AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
  flags: ncq led only pmp fbss pio slum part sxs 
    Device 0: (0:0) Vendor: ATA Prod.: SanDisk SDSSDA24 Rev: U210
              Type: Hard Disk
              Capacity: 228936.5 MB = 223.5 GB (468862128 x 512)
  Marvell>> scsi info
  Device 0: (0:0) Vendor: ATA Prod.: SanDisk SDSSDA24 Rev: U210
              Type: Hard Disk
              Capacity: 228936.5 MB = 223.5 GB (468862128 x 512)
  Marvell>> ext4ls scsi 0 /
  <DIR>       4096 .
  <DIR>       4096 ..
  <DIR>      16384 lost+found
                 4 bar
  Marvell>>

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
-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy