When I then let it boot into WB from the SD card, Media Toolbox could not see (any devices on) the sii3114ide.device. A PCIscan showed three new devices:

Device #3:
  Vendor:           0x2000 (Smart Link Ltd.)
  Device:           0x0000 (Unknown)
  Class code:       0x000000
  RevisionID:       0x00
  Interrupt:        Line 0x00, Pin 0x00
  Subsystem Vendor: 0x0000
  Subsystem ID:     0x0000

Device #4:
  Vendor:           0x104C (Texas Instruments)
  Device:           0x8231 (Unknown)
  Class code:       0x060400
  RevisionID:       0x03
  Interrupt:        Line 0xFF, Pin 0x00
  Subsystem Vendor: 0x0000
  Subsystem ID:     0x0000

Device #5:
  Vendor:           0x1095 (Silicon Image, Inc.)
  Device:           0x3114 (SiI 3114 [SATALink/SATARaid] Serial ATA Controller)
  Class code:       0x010400
  RevisionID:       0x02
  Interrupt:        Line 0x00, Pin 0x01
  Subsystem Vendor: 0x1095
  Subsystem ID:     0x7114
  Resource range #0 (IO)
    Base address:     0x00002000
    Physical address: 0x00002000
    Size:             0x00000008
  Resource range #1 (IO)
    Base address:     0x00002008
    Physical address: 0x00002008
    Size:             0x00000008
  Resource range #2 (IO)
    Base address:     0x00002010
    Physical address: 0x00002010
    Size:             0x00000008
  Resource range #3 (IO)
    Base address:     0x00002018
    Physical address: 0x00002018
    Size:             0x00000008
  Resource range #4 (IO)
    Base address:     0x00002020
    Physical address: 0x00002020
    Size:             0x00000010

An "idetool -l sii3114ide.device" says "*** Error opening device sii3114ide.device / unit 0" and the same for all 16 units.

"idetool -b" prints a dump of hex bytes which is useless to me, but part of it does look like it finds a controller which makes some sense to it:

----------SiI3114 PCI IDE Configuration--------------------
PCI Revision          : $2
PCI Class code        : $2
PCI Cacheline size    : $1
IDE0 prim IO base     : $00002000
IDE0 alt. IO base     : $0000200A
IDE1 prim IO  base    : $00002010
IDE1 alt. IO Revision : $0000201A
Busmater cntr. IO base: $00002020
Mem. mapped reg. base : $C0000000

So although the card is somewhat visible from both UBoot and AmigaOS, I have no idea if it could be made to actually work. I suspect both UBoot and the sii3114 driver need some sort of update to enable them to work with the known chip in an unknown context - or whatever .

Anybody more informed about the technicalities is welcome to chime in (where's Olegil when we need him? ).

Hans wrote:
Quote:

nbache wrote:
I had some time today to make my first tests with the Exsys EX-3506 card in the Sam460ex. I first tried simply switching the UBoot setting from Sata2 to PCIe and putting the HD cable on the first internal port of the card and booting from "SATA 3114 HD" (or whatever that setting is called, can't check it ATM).

No luck. So it seems UBoot/FLB cannot use devices on the card as boot sources.

Did you also change the jumper on the motherboard for switching between Sata2 and PCIe? You have to change both the UBoot setting, and the jumper.

mr2 wrote:
@ChrisH

He wrote :


...there is a PCIe SATA card that should work. Some Sam460 owner should test it ;)

...but yes, this card he linked surprisingly has Sil 3114 chip. Now im confused...

1. there are no PCIe SATA cards with chipsets currently supported by OS4.1, so i'll have to use up the PCI slot for that purpose.

Deniil wrote:

Quote:

Someone (apparently) once wrote an OS3 utility which saved the contents of RAM to disk, and allowed you to restore on next boot. This would of course be AWESOME for OS4, but probably not going to happen.

And it worked?