Ask for some guidance...
Vipin Malik
vipin at embeddedlinuxworks.com
Tue Jul 24 23:12:27 EDT 2001
At 08:32 PM 7/24/2001 +0200, olea at hispafuentes.com wrote:
>Our problem is that Linux can't see the IDE device.
>
>Since the machine is designed and built by a third company (other than
>our client) we don't have any information about the implementation.
>
>We have investigated the machine and we have some suppositions:
>
> - the bios doesn't look modified to access the flash ide disk;
> - there isn't any Samsung flash controler chip in the board;
> - the board has some chips looking as programmable roms;
> - it's looks that this chips are a firmware for doing the FTL.
It's not trivial to do FTL inside some "prom's". Depending on how large
(rather small) they are, they may be doing just chip decoding.
Most of the times IDE disk's are emulated under a "special" BIOS that
translate the BIOS IDE int (int 13?) into read/writes of the Flash sectors.
What BIOS is it using? I know that General Software's Embedded BIOS
supports that functionality.
There is not much that you can do re. accessing this disk under Linux as
Linux does not use the BIOS for IDE disk access.
>Our questions are:
>
> - How can we probe that there is a firmware doing the FTL and
>which firmware is it?
Simple (!), use "Debug" under DOS, to trace into the BIOS IDE interrupt and
see that it does.
> - Do you think we could access to the flash disk using MTD?
That's probably the most sensible approach in my mind- though you would not
access the flash _disk_, rather just the flash under MTD, which would show
up as a char and block device on which you could then mount JFFS2 and then
access it like a regular file system through Linux, including booting from it.
Vipin
More information about the linux-mtd
mailing list