Carlos Mateo | 1 Oct 2002 10:48
Picon
Picon
Favicon

Newbie with DOC2000

I am trying to access a DOC2000, but I failed so far.
I am using kernel 2.4.4.  I have recompiled it with
DOC support (M-Sys DOC200, Direct char device access
to MTD devices, FTL support, NTFL support and write
support for NTFL).
The kernel boots fine, but I am not able to do
anything with the DOC (fdisk, mke2fs...).

Any hints on what I should do?

Thank you
--
Carlos Mateo
cmateo <at> indra.es

_______________________________________________________________
Yahoo! Messenger
Nueva versión: Webcam, voz, y mucho más ¡Gratis! 
Descárgalo ya desde http://messenger.yahoo.es

Michael Palme | 1 Oct 2002 14:05
Favicon

Interesting MTD (jffs2) problem - magic bitmask not found

hello...

i've posted this on linux-arm mailing list, but i think its also 
interesting for this list...

i run 2.4.18-rmk7 with mtd from cvs (mid september).
problem as follows:
# cat /proc/mtd
   dev:    size   erasesize  name
   mtd0: 00040000 00040000 "blob"
   mtd1: 00040000 00040000 "parm"
   mtd2: 00100000 00040000 "krnl"
   mtd3: 00400000 00040000 "rd"
   mtd4: 00100000 00040000 "krnl2"
   mtd5: 00400000 00040000 "rd2"
   mtd6: 01580000 00040000 "jffs2"
# mtd_debug info /dev/mtd6
   mtd.type = MTD_NORFLASH
   mtd.flags = MTD_CAP_NORFLASH
   mtd.size = 22544384 (21M)
   mtd.erasesize = 262144 (256K)
   mtd.oobblock = 0
   mtd.oobsize = 0
   mtd.ecctype = MTD_ECC_NONE
   regions = 0
# cd /root
# ls temp
   temp1  temp2
# mkfs.jffs2 -r temp -e 262144 -o jffs2img
# eraseall /dev/mtd6
(Continue reading)

Sriram Neelakandan Iyer | 1 Oct 2002 15:12
Picon
Favicon

MTD copy on JFFS2

hi list,
i have 2 jffs2 partitions(over mtd) used for storing
config files.
I need to copy all the files from one partition to
another, and the destination mtd partition is larger
than the source mtd partition.(i cannot mount the
second partition as jffs2 before the data is copied)

As of now i run mkfs.jffs2 over the source jffs2
directory and copy to ramfs and then erase the
destination partition and i do a mtd-write over the
destination partition.

But mkfs.jffs2 needs libz and both of them occupy
about 87K of space.

So i plan to do a plain mtd-copy ,i.e 
1. first unmount source jffs2,
2. read over the source mtd-char-device and 
3. dump it back to the second mtd-partition. 

Will jffs2 be able to mount the second partition
without trouble?  (or) must i do a mkfs.jffs2 always
to have a jffs2 mountable partition.

regards
sriram.

__________________________________________________
Do you Yahoo!?
(Continue reading)

Michael Palme | 1 Oct 2002 17:23
Favicon

Re: jffs2 problem - magic bitmask not found

hello again :-)

after lots of time playing around that thing put me really into madness...

but could be i am doing something wrong!?
please verify:

i want to use jffs2 on my strongarmboard with 32Mb Intel strata flash.
so i think things to do to get a working jffs2 partition are as follows:

* built kernel with mtd and jffs2 support (i have done this ... kernel 
2.4.18-rmk7 with patched in mtd-cvs)

* built mtd-utils (successfully done -- crossbuilt for running on arm 
native)

* create partitions on flash (i have done this via commmand line 
partition table parsing -- CONFIG_CMDLINE="root=/dev/ram0 
mtdparts=sa1100:256k(blob),256k(parm),1M(krnl),4M(rd),1M(krnl2),4M(rd2),-(jffs2)")

* erase the jffs2 partition (done via "eraseall /dev/mtd6" -- also tried 
to delete it via jtag, so im sure theres no crap in after erasing...)

* verify things ("cat /proc/mtd" and "mtd_debug info /dev/mtd6" -- okay, 
everything as expected)

* create a jffs2 image (done via "mkfs.jffs2 -r foo -o jffs2.img -p -e 
262144"  -- image contains only a dummy file and is very small)

* copy the image to the mtd partition ("cp jffs2.img /dev/mtd6")
(Continue reading)

Mark Meade | 1 Oct 2002 17:47

Re: Newbie with DOC2000

Carlos,

What does your system log say?  Run dmesg and see if the DoC was detected 
correctly, and if the nftl driver found any partitions.

Also check your /dev entries for nftla: nftla should be 93,0; /dev/nftla1 
should be 93,1.. etc.

Mark

Carlos Mateo wrote:
> I am trying to access a DOC2000, but I failed so far.
> I am using kernel 2.4.4.  I have recompiled it with
> DOC support (M-Sys DOC200, Direct char device access
> to MTD devices, FTL support, NTFL support and write
> support for NTFL).
> The kernel boots fine, but I am not able to do
> anything with the DOC (fdisk, mke2fs...).
>
> Any hints on what I should do?
>
> Thank you

Joakim Tjernlund | 1 Oct 2002 17:56
Picon

RE: jffs2 problem - magic bitmask not found

> 
> hello again :-)
> 
> after lots of time playing around that thing put me really into madness...
> 
> but could be i am doing something wrong!?
> please verify:
> 
> i want to use jffs2 on my strongarmboard with 32Mb Intel strata flash.
> so i think things to do to get a working jffs2 partition are as follows:
> 
> * built kernel with mtd and jffs2 support (i have done this ... kernel 
> 2.4.18-rmk7 with patched in mtd-cvs)
> 
> * built mtd-utils (successfully done -- crossbuilt for running on arm 
> native)
> 
> * create partitions on flash (i have done this via commmand line 
> partition table parsing -- CONFIG_CMDLINE="root=/dev/ram0 
> mtdparts=sa1100:256k(blob),256k(parm),1M(krnl),4M(rd),1M(krnl2),4M(rd2),-(jffs2)")
> 
> * erase the jffs2 partition (done via "eraseall /dev/mtd6" -- also tried 
> to delete it via jtag, so im sure theres no crap in after erasing...)
> 
> * verify things ("cat /proc/mtd" and "mtd_debug info /dev/mtd6" -- okay, 
> everything as expected)
> 
> * create a jffs2 image (done via "mkfs.jffs2 -r foo -o jffs2.img -p -e 
> 262144"  -- image contains only a dummy file and is very small)
> 
(Continue reading)

Geoffrey Espin | 1 Oct 2002 21:03

cfi_probe on arm940T (linux-2.4.6pre0 uclinux)

I can't seem to identify a TE28F160B3 (x1 Sharp 16Mbit (2M byte))
on my arm940 (mmu-less) system.  This is 2.4.6pre0/uclinux kernel.
Separately, I'm trying to upgrade to 2.4.19... but that's different
challenge.)  I added a little debugging to my sa1100-flash.c derived
map.  The same problem exist if I use physmap.c.

  ...
  conexant_write16: 0x400000
  conexant_write16: 0x405555         <<<<<<<<---------------
  Unable to handle kernel NULL pointer dereference at virtual address 0000003f
  fault-common.c(98): start_code=0xe1a00000, start_stack=0xe1a00000)
  Internal error: Oops: ffffffff

CFI options:

    CONFIG_MTD_PHYSMAP=y
    CONFIG_MTD_PHYSMAP_START=400000
    CONFIG_MTD_PHYSMAP_LEN=200000
    CONFIG_MTD_PHYSMAP_BUSWIDTH=2

    CONFIG_MTD_CFI=y
    CONFIG_MTD_CFI_ADV_OPTIONS=y
    CONFIG_MTD_CFI_NOSWAP=y
    CONFIG_MTD_CFI_GEOMETRY=y
    CONFIG_MTD_CFI_B2=y
    CONFIG_MTD_CFI_I1=y
    CONFIG_MTD_CFI_INTELEXT=y

I've tried this with the Data Cache enable/disabled.  The kernel
has fixup/abort handler code for bad alignment CONFIG_ALIGNMENT_TRAP
(Continue reading)

Chris Morrow | 2 Oct 2002 00:09

Memory management problem?

I'm running into a problem where the linux kernel is running
out of memory and starts killing processes in an attempt to
recover. The environment is as follows.

A CDB89712 based system with 16 Meg. sdram and 16 meg CFI flash.
Linux-2.4.19-rmk1 with linux-2.4.19-pre10-shared-zlib patch.

First, on another system I create a number of files with random
contents and calculate their md5sums as follows;

#!/bin/sh

rm randFile*

numFiles=40
blockSize=1024
blocksPerFile=100

proc createFiles () {
	numFiles=$1
	blockSize=$2
	blockPerFile=$3
	fileSize=$(($blocksPerFile * $blockSize))
	while [ $numFiles -gt 0 ]; do
     		echo "creating file $numFiles"
     		dd if=/dev/urandom of=randFile.$numFiles \
			bs=$blockSize count=$blocksPerFile
     		let $((numFiles--))
		done
}
(Continue reading)

David Woodhouse | 2 Oct 2002 01:32
Favicon

Re: Memory management problem?

cmorrow <at> YottaYotta.com said:
> A CDB89712 based system with 16 Meg. sdram and 16 meg CFI flash.
> Linux-2.4.19-rmk1 with linux-2.4.19-pre10-shared-zlib patch. 

cmorrow <at> YottaYotta.com said:
>  There are some "deflateInit failed" warning messages during
> the run.

You shouldn't see that if you're actually using the shared zlib patch.

--
dwmw2

Piotr Trojanek | 2 Oct 2002 15:37
Picon

Re: Memory management problem?

there are two issues about out of memory:
1) you get malloc() with null
2) kernel decides to kill something

1: this should be checked in program code
2: look in /usr/src/linux/mm/oom.c

On Tue, Oct 01, 2002 at 04:09:47PM -0600, Chris Morrow wrote:
> 
> I'm running into a problem where the linux kernel is running
> out of memory and starts killing processes in an attempt to
> recover. The environment is as follows.
> 
> A CDB89712 based system with 16 Meg. sdram and 16 meg CFI flash.
> Linux-2.4.19-rmk1 with linux-2.4.19-pre10-shared-zlib patch.
> 
> First, on another system I create a number of files with random
> contents and calculate their md5sums as follows;
> 
> #!/bin/sh
> 
> rm randFile*
> 
> numFiles=40
> blockSize=1024
> blocksPerFile=100
> 
> proc createFiles () {
> 	numFiles=$1
> 	blockSize=$2
(Continue reading)


Gmane