Re: Problem with DiskOnChipMillenium

Re: Problem with DiskOnChipMillenium

[Sanal Kumar]

Hi Mark,


Thanks for your reply.
I have tried as you said . But it is giving exactly
the same error as before any other ideas.

TIA

Best Regrads
Ssanal


--- Mark Meade <mark@lakeshoremicro.com> wrote:
> Try using the following options:
> 
> # Memory Technology Devices (MTD)
> CONFIG_MTD=y
> CONFIG_MTD_DEBUG=y
> CONFIG_MTD_CHAR=y
> CONFIG_NFTL=y
> CONFIG_NFTL_RW=y
> 
> # Disk-On-Chip Device Drivers
> CONFIG_MTD_DOC2000=y
> CONFIG_MTD_DOCPROBE=y
> 
> (turn off CONFIG_MTD_DOC2001, and
> CONFIG_MTD_DOCPROBE ADDRESS).
> 
> Sanal Kumar wrote:
> > I am working on an Assabet like board(SA1110).
> > but when I enable mtd device(M-systems Millenium)I
> am
> > able to see the driver recognizing the Millenium
chip.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: Problem with DiskOnChipMillenium

[Mark Meade]

Sanal Kumar wrote:
> Thanks for your reply.
> I have tried as you said . But it is giving exactly
> the same error as before any other ideas.

Sorry, I've never seen those type of error messages before.

It may be worth a try to completely reformat the DiskOnChip using the 
M-Systems DOS utilities:

http://www.m-sys.com/content/download/OSSupport2.asp?id=8&pid=2

Whenever my DoC had problems, the DFORMAT utility was usually able to get it 
back to a known state.

Unless you're using newer code from the MTD CVS archives, you'll want to use 
version 4.2 of the utilities.

These instructions show how to install the Grub bootloader on a DoC, but 
there is some general information about using DFORMAT and installing a Linux 
filesystem:

http://www.lakeshoremicro.com/diskonchip-grub-howto.html

I hope this helps.

Mark

Problem with DiskOnChipMillenium

[Sanal Kumar]

Hi all,

I am working on an Assabet like board(SA1110).
but when I enable mtd device(M-systems Millenium)I am
able to see the driver recognizing the Millenium chip.

After booting I have added following links 

mknod /dev/nftla b 93 0
mknod /dev/nftla1 b 93 1
mknod /dev/nftla2 b 93 2
mknod /dev/nftla3 b 93 3

and 

mknod /dev/mtd0 c 90 0
mknod /dev/mtd1 c 90 1
mknod /dev/mtd2 c 90 2
mknod /dev/mtd3 c 90 3

and in bootup I am getting some errors like
out-of-line wait
_DoC_WaitReady called for out-of-line wait
.
.

_DoC_WaitReady called for out-of-line wait
Could not find valid boot record
Could not mount NFTL device

and using nftl_format I tried to format the diskon
chip But I get an error like the following

NFTL_open
ENODEV: thisNFTL = 0, minor = 23808, ip = c94ac4c0, fp
= c965caa0
NFTL_open
ENODEV: thisNFTL = 0, minor = 23809, ip = c94ac6e0, fp
= c965ca20

The only thing I could do was 

 dd if=XXXX of=/dev/mtd0 

What all things I need to so to make a linux filesysem
on Disk On Chip.

I am adding part of my .config here.

# 
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
# CONFIG_MTD_BOOTLDR_PARTS is not set
# CONFIG_MTD_AFS_PARTS is not set

# 
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
# CONFIG_MTD_BLOCK is not set
# CONFIG_MTD_BLOCK_RO is not set
# CONFIG_FTL is not set
CONFIG_NFTL=y
CONFIG_NFTL_RW=y

# 
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
# CONFIG_MTD_GEN_PROBE is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set

#
# Mapping drivers for chip access
#

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_MTDRAM is not set
# CONFIG_MTD_BLKMTD is not set

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC1000 is not set
CONFIG_MTD_DOC2000=y
CONFIG_MTD_DOC2001=y
CONFIG_MTD_DOCPROBE=y
# CONFIG_MTD_DOCPROBE_ADVANCED is not set
CONFIG_MTD_DOCPROBE_ADDRESS=0
# CONFIG_MTD_DOCPROBE_HIGH is not set
# CONFIG_MTD_DOCPROBE_55AA is not set

#
# NAND Flash Device Drivers
#
# CONFIG_MTD_NAND is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set



TIA
Best Regards
Sanal.



__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: Problem with DiskOnChipMillenium

[Mark Meade]

Try using the following options:

# Memory Technology Devices (MTD)
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_CHAR=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y

# Disk-On-Chip Device Drivers
CONFIG_MTD_DOC2000=y
CONFIG_MTD_DOCPROBE=y

(turn off CONFIG_MTD_DOC2001, and CONFIG_MTD_DOCPROBE ADDRESS).

Sanal Kumar wrote:
> I am working on an Assabet like board(SA1110).
> but when I enable mtd device(M-systems Millenium)I am
> able to see the driver recognizing the Millenium chip.