[U-Boot] Problem w/ SATA/IDE on Kirkwood _88F6281_ board:

Problem w/ SATA/IDE on Kirkwood 88F6281 board:
I've got U-Boot 2011.12 working well on a 8192 Kirkwood board, _except_ for a nagging SATA problem. Currently, it loads and executes U-Boot fine, it boots fine from a USB drive, but I'm unable to get the SATA port to function correctly. Any insight from Albert, Prafulla or anyone else who recognizes this problem, would be greatly appreciated.
It will detect an known-good-SATA-drive with known-good-ext2-partitions and list its specs, but there are some errors:
U-Boot 2011.12 (Apr 01 2012 - 15:55:54) Cloud Engines-Pogoplug v4
SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 Pogov4> ide reset
Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: TOSHIBA MK1655GSX Firm: FG010D Ser#: X9AHTNGQT Type: Hard Disk Supports 48-bit addressing Capacity: 152627.8 MB = 149.0 GB (312581808 x 512) Error (no IRQ) dev 0 blk 16: status 0x7f No Powersaving mode 7F Error (no IRQ) dev 0 blk 0: status 0x7f Device 1: not available Pogov4> ext2ls ide 0:1 / ** Bad partition - ide 0:1 ** Pogov4> ------------------------------------
With #define DEBUG enabled in common/cmd_ide.c, I see the following: ------------------------------------ Pogov4> ide reset
Reset IDE: Bus 0: ide_outb (dev= 0, port= 0x118, val= 0xe0) : @ 0xf1082118 ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x50 OK Bus 1: ide_outb (dev= 1, port= 0x118, val= 0xf0) : @ 0xf1082118 ide_inb (dev= 1, port= 0x11c) : @ 0xf108211c -> 0x50 OK Device 0: ide_outb (dev= 0, port= 0x118, val= 0xe0) : @ 0xf1082118 ide_outb (dev= 0, port= 0x11c, val= 0xec) : @ 0xf108211c ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0xd0 ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x58 in input data base for read is f1082100 Model: ?�?�?�?�?�?� Firm: ?�?�?�?� Ser#: ?�?�?��?�?�?� Type: Hard Disk Supports 48-bit addressing Capacity: 524263.9 MB = 511.9 GB (1073692671 x 512) ide_read dev 0 start 10, blocks 1 buffer at 7FBB230 ide_outb (dev= 0, port= 0x118, val= 0xe0) : @ 0xf1082118 ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x58 ide_outb (dev= 0, port= 0x11c, val= 0xe5) : @ 0xf108211c ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0xd8 ... ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0xd8 ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f No Powersaving mode 7F ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f ide_outb (dev= 0, port= 0x108, val= 0x01) : @ 0xf1082108 ide_outb (dev= 0, port= 0x10c, val= 0x10) : @ 0xf108210c ide_outb (dev= 0, port= 0x110, val= 0x00) : @ 0xf1082110 ide_outb (dev= 0, port= 0x114, val= 0x00) : @ 0xf1082114 ide_outb (dev= 0, port= 0x118, val= 0xe0) : @ 0xf1082118 ide_outb (dev= 0, port= 0x11c, val= 0x20) : @ 0xf108211c ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f Error (no IRQ) dev 0 blk 16: status 0x7f ide_read dev 0 start 0, blocks 1 buffer at 7E30C30 ide_outb (dev= 0, port= 0x118, val= 0xe0) : @ 0xf1082118 ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f ide_outb (dev= 0, port= 0x11c, val= 0xe5) : @ 0xf108211c ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x80 ... ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x80 ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f No Powersaving mode 7F ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f ide_outb (dev= 0, port= 0x108, val= 0x01) : @ 0xf1082108 ide_outb (dev= 0, port= 0x10c, val= 0x00) : @ 0xf108210c ide_outb (dev= 0, port= 0x110, val= 0x00) : @ 0xf1082110 ide_outb (dev= 0, port= 0x114, val= 0x00) : @ 0xf1082114 ide_outb (dev= 0, port= 0x118, val= 0xe0) : @ 0xf1082118 ide_outb (dev= 0, port= 0x11c, val= 0x20) : @ 0xf108211c ide_inb (dev= 0, port= 0x11c) : @ 0xf108211c -> 0x7f Error (no IRQ) dev 0 blk 0: status 0x7f Device 1: ide_outb (dev= 1, port= 0x118, val= 0xf0) : @ 0xf1082118 ide_outb (dev= 1, port= 0x11c, val= 0xec) : @ 0xf108211c ide_inb (dev= 1, port= 0x11c) : @ 0xf108211c -> 0x7f not available ------------------------------------
Ideas, anyone?

On Sun, Apr 1, 2012 at 4:24 PM, David Purdy david.c.purdy@gmail.com wrote:
Problem w/ SATA/IDE on Kirkwood 88F6281 board:
To clarify, this is actually a _6192_ board. I double-checked, there are no 6192 boards in include/configs/ .
The contents in arch/arm/arch-kirkwood/ certainly suggest that the 6192 is supported.

-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot- bounces@lists.denx.de] On Behalf Of David Purdy Sent: 02 April 2012 07:31 To: u-boot@lists.denx.de Subject: Re: [U-Boot] Problem w/ SATA/IDE on Kirkwood _88F6281_ board:
On Sun, Apr 1, 2012 at 4:24 PM, David Purdy david.c.purdy@gmail.com wrote:
Problem w/ SATA/IDE on Kirkwood 88F6281 board:
To clarify, this is actually a _6192_ board. I double-checked, there are no 6192 boards in include/configs/ .
The contents in arch/arm/arch-kirkwood/ certainly suggest that the 6192 is supported.
Hi David 6192 is supported for basic boot operation, no peripherals were tested on this platform.
Regards.. Prafulla . . .

-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot- bounces@lists.denx.de] On Behalf Of David Purdy Sent: 02 April 2012 02:54 To: u-boot@lists.denx.de Subject: [U-Boot] Problem w/ SATA/IDE on Kirkwood _88F6281_ board:
Problem w/ SATA/IDE on Kirkwood 88F6281 board:
I've got U-Boot 2011.12 working well on a 8192 Kirkwood board, _except_ for a nagging SATA problem. Currently, it loads and executes U-Boot fine, it boots fine from a USB drive, but I'm unable to get the SATA port to function correctly. Any insight from Albert, Prafulla or anyone else who recognizes this problem, would be greatly appreciated.
I remember there was some delay issue on SATA, since processor in this platform is running at lower clock, (may be) this could be one of parameter to be considered. May be Albert can have some more inside on this.
Regards.. Prafulla . . .

On Mon, Apr 2, 2012 at 12:11 AM, Prafulla Wadaskar prafulla@marvell.com wrote:
I remember there was some delay issue on SATA, since processor in this
platform is running at lower clock, (may be) this could be one of parameter to be considered.
May be Albert can have some more inside on this.
Regards.. Prafulla . . .
Hi Prafulla and hopefully Albert,
1 possibility ruled out, 1 tiny piece improved, 1 major problem still there, & few questions...
0. Latest code in git shows the same behavior... that isn't the issue...
1. Adjusting some of the timings in drivers/block/mvsata_ide.c has allowed me to apparently solve a _small_ fraction of the problem. I can now get it to consistently/reliably honor the 'ide reset' command. (before this timing adjustment, I would frequently see: .................................. Pogov4> ide reset
Reset IDE: ide_preinit failed `````````````````````````````````` ... so this is one minor part of it that no longer seems a problem.
2. The two 'no IRQ' errors that I see here still persist: .................................. Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: TOSHIBA MK1655GSX Firm: FG010D Ser#: X9AHTNGQT Type: Hard Disk Supports 48-bit addressing Capacity: 152627.8 MB = 149.0 GB (312581808 x 512) Error (no IRQ) dev 0 blk 16: status 0x7f No Powersaving mode 7F Error (no IRQ) dev 0 blk 0: status 0x7f Device 1: not available `````````````````````````````````` These apparently come from common/cmd_ide.c . The offsets shown in the DEBUG output look to me to be the correct ones, referencing the Marvell docs.
I can't find a meaning for 'status 0x7f', though.
Again, any ideas or hints of what to examine would be appreciated.
3. Prafulla, could a problem w/ my kwbimage.cfg file cause timing problems? Could the incorrect SoC identification (showing as a 6281 instead of a 6192) cause a problem due to some registers being misread somehow?
Regards and thanks,
Dave

________________________________ From: David Purdy [mailto:david.c.purdy@gmail.com] Sent: 03 April 2012 10:40 To: Prafulla Wadaskar; u-boot@lists.denx.de; albert.u.boot@aribaud.net Subject: Problem w/ SATA/IDE on Kirkwood _88F6281_ board:
On Mon, Apr 2, 2012 at 12:11 AM, Prafulla Wadaskar <prafulla@marvell.commailto:prafulla@marvell.com> wrote:
I remember there was some delay issue on SATA, since processor in this platform is running at lower clock, (may be) this could be one of parameter to be considered. May be Albert can have some more inside on this.
Regards.. Prafulla . . .
Hi Prafulla and hopefully Albert,
1 possibility ruled out, 1 tiny piece improved, 1 major problem still there, & few questions...
0. Latest code in git shows the same behavior... that isn't the issue...
1. Adjusting some of the timings in drivers/block/mvsata_ide.c has allowed me to apparently solve a _small_ fraction of the problem. I can now get it to consistently/reliably honor the 'ide reset' command. (before this timing adjustment, I would frequently see: .................................. Pogov4> ide reset
Reset IDE: ide_preinit failed `````````````````````````````````` ... so this is one minor part of it that no longer seems a problem.
2. The two 'no IRQ' errors that I see here still persist: .................................. Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: TOSHIBA MK1655GSX Firm: FG010D Ser#: X9AHTNGQT Type: Hard Disk Supports 48-bit addressing Capacity: 152627.8 MB = 149.0 GB (312581808 x 512) Error (no IRQ) dev 0 blk 16: status 0x7f No Powersaving mode 7F Error (no IRQ) dev 0 blk 0: status 0x7f Device 1: not available `````````````````````````````````` These apparently come from common/cmd_ide.c . The offsets shown in the DEBUG output look to me to be the correct ones, referencing the Marvell docs.
I can't find a meaning for 'status 0x7f', though.
Again, any ideas or hints of what to examine would be appreciated.
3. Prafulla, could a problem w/ my kwbimage.cfg file cause timing problems? Could the incorrect SoC identification (showing as a 6281 instead of a 6192) cause a problem due to some registers being misread somehow? [Prafulla] : I don't think so, only TCLK is being configured to 166Mhz instead of 200, kwbimage.cfg does system configuration before boot, so whatever you do in this file are equally important. But specific to this problem, I am bit away from peripheral sata :( Regards.. Prafulla . . .
Regards and thanks,
Dave
participants (2)
-
David Purdy
-
Prafulla Wadaskar