Antwort: Re: Antwort: 8xxrom wierdness, 2nd

Antwort: Re: Antwort: 8xxrom wierdness, 2nd

[Ruedi.Hofer]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 971 bytes --]

Hi Magnus

I see now why it doesn't crash anymore: 

You've put the line check_fs(); (disk.c; 151) into comments. ;-)


Cheers, Ruedi


BTW: 

- Do you have experience with the sandisk pc cards?

- I formatted the pc card on a win95 box. That should work, right?
  (At least the boot device list should mention something)

____________________________________________________________________



I just tried your 8xxrom. It seems to work a bit better than the Bossek original  ;-)

It generates the following output:

8xxROM 0.3.0

compiletime options:
board: ADS DRAM_25MHZ
disk: DISK_ATA PCMCIABUG

cpu: XPC860xxZPnnA3 at 25 MHz: 4Kbyte icache 4Kbyte dcache

<warning: cpu core has silicon bugs, check the errata>

board: ADS rev A - warning, read errata
flash: 2 Mbytes, delay 90 ns
dram: EDO, 4 Mbyte, 70 ns, OK
pcmcia: 5V and 3V
pcsr = 0x0070fe70

ATA disk: 'SunDisk SDP'.

Boot device list:Card Not Ready 0x0

disk: No disk found.

>

Do you have any ideas?

Ruedi

Re: Antwort: Re: Antwort: 8xxrom wierdness, 2nd

[Magnus Damm]

> - Do you have experience with the sandisk pc cards?

Not with pc cards.
But my compact-flash cards with converter works.
I've got cf-cards from Sandisk, Viking and Mitsubishi.
I posted about the wierd Viking card a few weeks ago...

If anyone out there wants support for a certain ATA-card
feel free to send them to me and I will make sure it works! =)

If I were you would I have a look at the data-sheet for the 
pc-card and verify that the ata registers are mapped at the right
positions...

SanDisk has got pretty nice CF manuals and I guess that their pc-card
documentation is good too.
 
> - I formatted the pc card on a win95 box. That should work, right?
>   (At least the boot device list should mention something)

It should work.
 
>> ATA disk: 'SunDisk SDP'.
> 
> Boot device list:Card Not Ready 0x0

It is good that it is able to parse the cis and find out
that it is a ATA disk.

It probably fails when it should send a identify command.

You might need some spinup time if it is a mechanical drive.

Cheers /

magnus

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/