2008-10-31 03:29:35     SPI MMC problem

Document created by Aaronwu Employee on Aug 14, 2013
Version 1Show Document
  • View in full screen mode

2008-10-31 03:29:35     SPI MMC problem

Yi Li (CHINA)

Message: 64481   

 

Question from a developer:

 

 

 

"We have encountered an issue with MMC driver under uCLinux of 2008r1-rc1 version.  Attached is detail information. Please check it and give us some advice.

 

Thank you very much."

 

--------------

 

Detail info:

 

操作和错误说明

 

内核的配置按bmp图片显示的配置的

 

root:/> mount  –t msdos  –o  sync  /dev/spi_mmc  /tmp

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc: unknown partition table//这句话不应该出现吧

 

root:/> cd tmp

root:/tmp> ls

d.pdf //这个文件是一个5M大小的pdf文件

 

root:/tmp> cp d.pdf /root/

root:/tmp> cd

root:/> ls

bin    dev    home   lib    proc   sbin   tmp    var

d.pdf  etc    init   mnt    root   sys    usr

 

root:/> tftp -l d. pdf

root:/> tftp -l  d.pdf  -p  192.168.1.102//传出去的文件大部分正确,但也有不对的地方,有时候文件也打不开,说是pdf文件已破坏

 

root:/> cp  etc/rc  /tmp //拷贝rc文件到MMC卡下面

root:/> cd tmp

root:/tmp> ls

d.pdf  rc

 

root:/tmp> cat rc//查看rc文件,文件正确

hostname blackfin

mount -t proc proc /proc

mount -t ramfs ramfs /var

mount -t sysfs sysfs /sys

mount -t devpts devpts /dev/pts

[ -d /proc/bus/usb ] && mount -t usbfs usbfs /proc/bus/usb

[ -d /sys/kernel/debug ] && mount -t debugfs debugfs /sys/kernel/debug

[ -d /proc/sys/fs/binfmt_misc ] && mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc

[ -d /sys/kernel/security ] && mount -t securityfs securityfs /sys/kernel/security

grep -qs nfsd /proc/filesystems && mount -t nfsd nfsd /proc/fs/nfsd

if [ -e /bin/mdev ] ; then

          echo /bin/mdev 2>/dev/null > /proc/sys/kernel/hotplug

          /bin/mdev -s 2> /dev/null

fi

mkdir /var/tmp /var/log /var/run /var/lock

#dhcpcd &

ifconfig eth0 192.168.1.76 up

#ifconfig lo 127.0.0.1

inetd &

#cat /etc/issue

#cat /etc/motd

#insmod /bin/ads1256.ko

#mount /dev/hda1 /tmp

#chmod 755 /bin/sample

#/bin/sample&

#modprobe g_file_storage file=/dev/mmc1

 

root:/tmp>

 

重启

 

root:/> PHY: 0:01 - Link is Up - 100/Full

 

 

 

root:/>

 

root:/> mount  -t  msdos  -o  sync  /dev/spi_mmc  / tmp

 

New MMC/SD card found: 488 MB(511967232 bytes)

 

spi_mmc: unknown partition table

 

//有时候可能mount不上

 

root:/> cd tmp

 

root:/tmp> ls//查看MMC的文件

 

ls: ./bflt: No such file or directory//多余了一些东西

 

ls: ./步w眂?s.

?: No such file or directory//多余了一些东西

 

d.pdf  rc////多余了一些东西

 

root:/tmp>

 

root:/tmp>

 

root:/tmp> cat rc//小文件的内容是正确的

 

hostname blackfin

 

mount -t proc proc /proc

 

mount -t ramfs ramfs /var

 

mount -t sysfs sysfs /sys

 

mount -t devpts devpts /dev/pts

 

[ -d /proc/bus/usb ] && mount -t usbfs usbfs /proc/bus/usb

 

[ -d /sys/kernel/debug ] && mount -t debugfs debugfs /sys/kernel/debug

 

[ -d /proc/sys/fs/binfmt_misc ] && mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc

 

[ -d /sys/kernel/security ] && mount -t securityfs securityfs /sys/kernel/security

 

grep -qs nfsd /proc/filesystems && mount -t nfsd nfsd /proc/fs/nfsd

 

if [ -e /bin/mdev ] ; then

 

          echo /bin/mdev 2>/dev/null > /proc/sys/kernel/hotplug

 

          /bin/mdev -s 2> /dev/null

 

fi

 

mkdir /var/tmp /var/log /var/run /var/lock

 

#dhcpcd &

 

ifconfig eth0 192.168.1.76 up

 

#ifconfig lo 127.0.0.1

 

inetd &

 

#cat /etc/issue

 

#cat /etc/motd

 

#insmod /bin/ads1256.ko

 

#mount /dev/hda1 /tmp

 

#chmod 755 /bin/sample

 

#/bin/sample&

 

#modprobe g_file_storage file=/dev/mmc1

 

 

 

 

 

root:/tmp>

 

root:/tmp>

 

root:/tmp> ls

 

ls: ./bflt: No such file or directory

 

ls: ./步w眂?s.

?: No such file or directory

 

d.pdf  rc

 

root:/tmp> cp d.pdf  /root/   //将d.pdf拷贝到根目录下,就出现下面的错误

 

FAT: Filesystem panic (dev spi_mmc)

 

    fat_get_cluster: invalid cluster chain (i_pos 7939)

 

    File system has been set read-only

 

FAT: Filesystem panic (dev spi_mmc)

 

    fat_get_cluster: invalid cluster chain (i_pos 7939)

 

FAT: Filesystem panic (dev spi_mmc)

 

    fat_get_cluster: invalid cluster chain (i_pos 7939)

 

FAT: Filesystem panic (dev spi_mmc)

 

fat_get_cluster: invalid cluster chain (i_pos 7939)

 

 

 

然后再重启的话,要么mount不上,要么mount上了但没有文件了,用笔记本打开卡上也没有内容了,或者说格式不正确,要求格式化

 

 

 

小文件的读写一般没有问题,大文件出现问题比较多

 

 

QuoteReplyEditDelete

 

 

2008-10-31 03:33:34     Re: SPI MMC problem

Yi Li (CHINA)

Message: 64482   

 

For the error: "unkown partition table", please run "mkdosfs /dev/spi_mmc" or using "fdisk" to create partitions.

 

Please refer to:  docs.blackfin.uclinux.org/doku.php?id=linux-kernel:drivers:spi_mmc

QuoteReplyEditDelete

 

 

2008-11-02 04:46:27     SPI MMC new problem

lm g (CHINA)

Message: 64598   

 

I have do

 

mkdosfs /dev/spi_mmc

 

mount -t msdos -o sync /dev/spi_mmc /tmp  (sometimes  I must mount more than one time)

 

cp a.pdf  /tmp (this file is 5MB)

 

occur this err

 

FAT: Filesystem panic (dev spi_mmc)

    fat_get_cluster: detected the cluster chain loop (i_pos 7856)

    File system has been set read-only

cp: write error: Input/output error

QuoteReplyEditDelete

 

 

2008-11-02 21:45:13     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 64610   

 

What is your platform ?(BF537?) Are there any other SPI devices on the same SPI bus?

 

If you copy files with smaller size, e.g, 1MB, will there be error message?

QuoteReplyEditDelete

 

 

2008-11-02 22:40:55     Re: SPI MMC new problem

Li Dong (CHINA)

Message: 64611   

 

Platform is BF536.

 

There is no problem with small files.

QuoteReplyEditDelete

 

 

2008-11-02 22:42:08     Re: SPI MMC new problem

Li Dong (CHINA)

Message: 64612   

 

Also no other devices attached to SPI bus.

QuoteReplyEditDelete

 

 

2008-11-02 22:56:12     Re: SPI MMC new problem

lm g (CHINA)

Message: 64613   

 

BF537

 

root:~> mkdosfs /dev/spi_mmc

mkdosfs 2.10 (22 Sep 2003)

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc: unknown partition table   / /this err

root:~> mount -t msdos -o sync /dev/spi_mmc /mnt

root:~> cd mnt

root:/mnt> ls

ls: ./?.h竓: No such file or directory

ls: ./? : No such file or directory

ls: ./|竓: No such file or directory

ls: ./).€        : No such file or directory

ls: ./ : No such file or directory

ls: ./@?: No such file or directory

ls: ./\筯. : No such file or directory

ls: ./€筯: No such file or directory

ls: ./?.韫h: No such file or directory

root:/mnt>           //No such file or directory

 

 

root:~> tftp 192.168.1.102

tftp> get b.pdf                                                        //b.pdf    1MB

Received 1049121 bytes in 1.2 seconds

tftp> q

root:~> cp b.pdf /mnt/

FAT: Filesystem panic (dev spi_mmc)

    fat_get_cluster: invalid cluster chain (i_pos 7856)

    File system has been set read-only

FAT: Filesystem panic (dev spi_mmc)

    fat_free: invalid cluster chain (i_pos 7856)

cp: write error: Input/output error

root:~> ls -l b.pdf

-rw-r--r--    1 root     root      1048788 Jan  2 11:01 b.pdf

root:~>

 

root:~> cd mnt/

root:/mnt> ls

ls: ./?.h竓: No such file or directory

ls: ./? : No such file or directory

ls: ./|竓: No such file or directory

ls: ./).€        : No such file or directory

ls: ./ : No such file or directory

ls: ./@?: No such file or directory

ls: ./\筯. : No such file or directory

ls: ./€筯: No such file or directory

ls: ./?.韫h: No such file or directory

b.pdf

 

 

root:/mnt>

 

only 1MB has the same err, and reboot

 

root:~> mount -t msdos -o sync /dev/spi_mmc /mnt

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc:

root:~> cd mnt

root:/mnt> ls //can mount on ; but there is no file

 

if before reboot ,do

 

umount /mnt          and  reboot

 

root:~> mount -t msdos -o sync /dev/spi_mmc /mnt

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc: unknown partition table

mount: mounting /dev/spi_mmc on /mnt failed

root:~> mount -t msdos -o sync /dev/spi_mmc /mnt

mount: mounting /dev/spi_mmc on /mnt failed

root:~> mount -t msdos -o sync /dev/spi_mmc /mnt

mount: mounting /dev/spi_mmc on /mnt failed

root:~>   / / mount   failed

 

if

 

 

 

 

QuoteReplyEditDelete

 

 

2008-11-04 08:20:13     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 64660   

 

BF537

 

root:~> mkdosfs /dev/spi_mmc

mkdosfs 2.10 (22 Sep 2003)

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc: unknown partition table   / /this err

 

---

 

First of all, you will need to fix this error "spi_mmc: unknown partition table" , before you mount and use the card. Could  you try to create a partition (e.g, /dev/spi_mmc1) using fdisk, then "mkdosfs /dev/spi_mmc1" and see what happens?

 

-Yi

 

 

QuoteReplyEditDelete

 

 

2008-11-04 08:27:45     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 64661   

 

Also no other devices attached to SPI bus.

 

---

 

Please try to disable SPI DMA when using the spi_mmc driver. I found using PIO mode is more stable than DMA mode. Also, is your spi_mmc driver using SPI framework (select CONFIG_SPI_MMC_FRAMEWORK_DRIVER) or it access SPI bus directly(select CONFIG_SPI_MMC_BFIN_PIO_SPI)? If using the framework, you can disable DMA by define:

 

static struct bfin5xx_spi_chip spi_mmc_chip_info = {

    .enable_dma = 0,

    .bits_per_word = 8,

};

 

-Yi

QuoteReplyEditDelete

 

 

2008-11-05 04:10:49     Re: SPI MMC new problem

lm g (CHINA)

Message: 64681   

 

1,no other devices attached to SPI bus

 

2.we are using the framework,and disable DMA by define in where?

 

static struct bfin5xx_spi_chip spi_mmc_chip_info = {

    .enable_dma = 0,

    .bits_per_word = 8,

};

 

 

 

 

 

3.

root:~> fdisk /dev/mmc

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc:tion1

partition 1 0

unknown partition table

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

 

 

The number of cylinders for this disk is set to 2016.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

 

Command (m for help): m

Command action

   a   toggle a bootable flag

   b   edit bsd disklabel

   c   toggle the dos compatibility flag

   d   delete a partition

   l   list known partition types

   m   print this menu

   n   add a new partition

   o   create a new empty DOS partition table

   p   print the partition table

   q   quit without saving changes

   s   create a new empty Sun disklabel

   t   change a partition's system id

   u   change display/entry units

   v   verify the partition table

   w   write table to disk and exit

   x   extra functionality (experts only)

 

Command (m for help): o

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

 

 

The number of cylinders for this disk is set to 2016.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

   (e.g., DOS FDISK, OS/2 FDISK)

 

Command (m for help): w

The partition table has been altered!

 

Calling ioctl() to re-read partition table.

spi_mmc:tion1

partition 1 0

unknown partition table

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc:tion1

partition 1 0

unknown partition table

 

WARNING: If you have created or modified any DOS 6.x

partitions, please see the fdisk manual page for additional

information.

Syncing disks.

root:~>

root:~> mount -t msdos -o sync /dev/spi_mmc /mnt

New MMC/SD card found: 488 MB(511967232 bytes)

spi_mmc:tion1

partition 1 0

unknown partition table

mount: mounting /dev/mmc on /mnt failed

root:~>

root:~> mount -t msdos -o sync /dev/mmc /mnt [J

mount: mounting /dev/mmc on /mnt failed

root:~>

root:~> mount -t msdos -o sync /dev/mmc /mnt [J

mount: mounting /dev/mmc on /mnt failed

 

 

root:~> //mount   failed

QuoteReplyEditDelete

 

 

2008-11-06 02:58:13     Re: SPI MMC new problem

Wei Jiang (CHINA)

Message: 64733   

 

I think you can try the "SPI framework driver" not "SPI bus directly".

QuoteReplyEditDelete

 

 

2008-11-09 20:35:30     Re: SPI MMC new problem

lm g (CHINA)

Message: 64892   

 

yes,we are using SPI framework driver

QuoteReplyEditDelete

 

 

2008-11-10 05:00:02     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 64919   

 

> 2.we are using the framework,and disable DMA by define in where?

 

> static struct bfin5xx_spi_chip spi_mmc_chip_info = {

>    .enable_dma = 0,

>    .bits_per_word = 8,

> };

 

Please change it in your board file, e.g, I am using BF537-stamp, so I changed in arch/blackfin/mach-bf537/boards/stamp.c

 

3.

>root:~> fdisk /dev/mmc

 

>Command (m for help): w

>The partition table has been altered!

 

>Calling ioctl() to re-read partition table.

>spi_mmc:tion1

>partition 1 0

  >unknown partition table

 

This looks strange. Could you please try again with another SD/mmc card ?

 

 

QuoteReplyEditDelete

 

 

2008-11-12 03:31:35     Re: SPI MMC new problem

lm g (CHINA)

Message: 65079   

 

we try again with a new card(SD),and change     . enable_dma = 0, in kernel

 

 

It's better than last MMc card,It can write  4M file,and only can write  4145152  bytes

 

 

 

test program is  wr

 

int main(void)

{

  int           i;

  char          buf[256]={0};

 

  for(i=0;i<256;i++)

  buf[1]=i;

 

  system("mkdosfs /dev/spi_mmc");

  sleep(2);

 

  system("mount -t msdos -o sync /dev/mmc /mnt");

  sleep(2);

 

  fp = fopen("/mnt/wrdata","a+");

 

  while(1)

  {

      fwrite(buf,256,1,fp);  

  }

 

  printf("close...\n");

  fclose(fp);

  return 0;

}

 

 

 

 

 

wr&

43

root:~> mkdosfs 2.10 (22 Sep 2003)

New MMC/SD card found: 961 MB(1007681536 bytes)

spi_mmc:tion1

 

partition 1 1

 

 

root:~> free

              total         used         free       shared      buffers

  Mem:        21748         4648        17100            0          108

root:~> ls -l mnt

-rwxr-xr-x    1 root     root       355072 Jan  2 14:53 wrdata

root:~>

root:~> ls -l mnt

root:~> free

              total         used         free       shared      buffers

  Mem:        21748         4952        16796            0          108

root:~>

root:~> free

              total         used         free       shared      buffers

  Mem:        21748         5052        16696            0          108

root:~>

root:~> ls -l mnt

-rwxr-xr-x    1 root     root       934144 Jan  2 14:54 wrdata

root:~>

root:~> ls -l mnt

-rwxr-xr-x    1 root     root      1030912 Jan  2 14:54 wrdata

root:~>

root:~> ls -l mnt

root:~> ls -l mnt

root:~> free

              total         used         free       shared      buffers

  Mem:        21748         6492        15256            0          108

root:~>

root:~> free

              total         used         free       shared      buffers

  Mem:        21748         6560        15188            0          108

root:~>

root:~> free [J

root:~> free [J

root:~> ls -l mnt [J

-rwxr-xr-x    1 root     root      2391808 Jan  2 14:54 wrdata

root:~>

root:~> ls -l mnt [J

-rwxr-xr-x    1 root     root      2614528 Jan  2 14:54 wrdata

root:~>

root:~> ls -l mnt [J

-rwxr-xr-x    1 root     root      3934464 Jan  2 14:55 wrdata

root:~>

root:~> ls -l mnt [J

-rwxr-xr-x    1 root     root      4096256 Jan  2 14:55 wrdata

root:~> Hardware Trace:

0 Target : <0x0000492c> { _dump_stack + 0x0 }

   Source : <0x0007f0e6> { ___blk_put_request + 0x76 }

1 Target : <0x0007f0e6> { ___blk_put_request + 0x76 }

   Source : <0x0007f0b4> { ___blk_put_request + 0x44 }

2 Target : <0x0007f0a4> { ___blk_put_request + 0x34 }

   Source : <0x0007f09a> { ___blk_put_request + 0x2a }

3 Target : <0x0007f096> { ___blk_put_request + 0x26 }

   Source : <0x0007d0ce> { _elv_completed_request + 0x2a }

4 Target : <0x0007d0c0> { _elv_completed_request + 0x1c }

   Source : <0x0007d0b4> { _elv_completed_request + 0x10 }

5 Target : <0x0007d0a4> { _elv_completed_request + 0x0 }

   Source : <0x0007f092> { ___blk_put_request + 0x22 }

6 Target : <0x0007f070> { ___blk_put_request + 0x0 }

   Source : <0x0007f1e0> { _end_that_request_last + 0xa8 }

7 Target : <0x0007f1c4> { _end_that_request_last + 0x8c }

   Source : <0x0007dcc0> { _disk_round_stats + 0x24 }

8 Target : <0x0007dcc0> { _disk_round_stats + 0x24 }

   Source : <0x0007dcae> { _disk_round_stats + 0x12 }

9 Target : <0x0007dc9c> { _disk_round_stats + 0x0 }

   Source : <0x0007f1c0> { _end_that_request_last + 0x88 }

10 Target : <0x0007f17e> { _end_that_request_last + 0x46 }

   Source : <0x0007f164> { _end_that_request_last + 0x2c }

11 Target : <0x0007f138> { _end_that_request_last + 0x0 }

   Source : <0x000b550e> { _spi_mmc_transfer_worker + 0x18a }

12 Target : <0x000b550a> { _spi_mmc_transfer_worker + 0x186 }

   Source : <0x0007c96c> { _elv_dequeue_request + 0x24 }

13 Target : <0x0007c96a> { _elv_dequeue_request + 0x22 }

   Source : <0x0007c95e> { _elv_dequeue_request + 0x16 }

14 Target : <0x0007c948> { _elv_dequeue_request + 0x0 }

   Source : <0x000b5506> { _spi_mmc_transfer_worker + 0x182 }

15 Target : <0x000b5502> { _spi_mmc_transfer_worker + 0x17e }

   Source : <0x0009212c> { _add_timer_randomness + 0x120 }

Stack from 0165fee4:

        00092126 0007f0ea 00388f04 00010404 000b5460 00000000 00000000 000b5512

        00388f04 00000001 0014a374 01654784 0162e668 0000001f 0162e678 00385600

        00000001 000b5384 0001b256 016526f4 0162e660 0162e668 0000ffff 0162e678

        0017803c 0165e000 0165e000 00178394 00000000 00000000 0001bb0e 0162e670

        0162e660 0001ba0c 0162e668 0165ff98 00000000 00104174 00000000 00000000

        00000001 00000000 00000000 00010000 00000000 00000000 01634040 0000a7d8

Call Trace:

[<00100100>] _unix_seq_open+0x58/0x6c

[<0001e0ce>] _kthread+0xd6/0xec

[<0001dff8>] _kthread+0x0/0xec

[<00001946>] _kernel_thread_helper+0x6/0xc

 

kernel BUG at block/ll_rw_blk.c:2675!

Kernel panic - not syncing: BUG!

 

 

 

It's err , and  reboot ...

 

 

mount -t msdos -o sync /dev/mmc /mnt

root:~>

root:~>

root:~> mount -t msdos -o sync /dev/mmc /mnt

New MMC/SD card found: 961 MB(1007681536 bytes)

spi_mmc:tion1

 

partition 1 1

root:~> cd mnt

root:/mnt> ls -l

-rwxr-xr-x    1 root     root      4145152 Jan  1  1980 wrdata

root:/mnt>

 

 

 

1. we try many times , and can only  write  4145152  in  wrdata  every time

 

 

 

2. root:~> free

                      total         used         free       shared      buffers

  Mem:        21748         4648        17100            0          108

 

 

root:~> free

                       total         used         free       shared      buffers

  Mem:        21748         6560        15188            0          108

 

used  is always  incleassing   when card is writting

 

 

QuoteReplyEditDelete

 

 

2008-11-12 06:44:03     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 65147   

 

1. For the kernel panic, I will have a test myself. But on my BF537-STAMP, I can write file upto 8MB:

 

ls /mnt

 

-rwxr-xr-x    1 root     root      8778496 Jan  1 00:48 wrdata

 

 

Maybe it is related to total memory?

 

root:/mnt> free

              total         used         free       shared      buffers

  Mem:        55272        23048        32224            0          296

 

 

2. For the memory issue, if looking at /proc/meminfo, you can find the increased memory are all "Caches", that is pagecache - But the unused pagecache will be finally be reclaimed by kernel (you mean read document about /proc/sys/vm/dirtry_*).

 

-Yi

QuoteReplyEditDelete

 

 

2008-11-12 22:24:12     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 65176   

 

Sorry, I cannot reproduce the kernel panic you met. I run your test until my SD card is filled with the data, without error.

 

-Yi

QuoteReplyEditDelete

 

 

2008-11-13 22:40:08     Re: SPI MMC new problem

lm g (CHINA)

Message: 65261   

 

I'm sorry , It'S our  err

 

now ,we copy a new 2008R1 kernel ,and use DMA , It's no problem  for read or write

 

but

 

root:/> cat /proc/spi_mmc

Driver build date: Nov 14 2008

SCLK: 20000 KHz

SPISEL1 as chip select

Driver: SPI Framework master

Total errors: 0

 

SD card :

         Capacity: 1007681536 B

         Name: N/A   ?

         Rev: 9.15

         Date: 2005/7

         Serial: 0xf45456 (16012374)

         CSD ver.: 0

         CCC supported: 5f5

         Mult. block writes works: YES

last block:      340992

users:   1

Performance for last 100 transfers

         Mean read throughput:   15 kB/s

         Mean write throughput:  104 kB/s

 

 

 

write speed  only  104 kB/s

 

do you have some methreads  to make speed fastly?

 

                                                                                                                                                  

QuoteReplyEditDelete

 

 

2008-11-14 05:09:42     Re: SPI MMC new problem

Yi Li (CHINA)

Message: 65284   

 

What is your expected R/W speed? I did not do performance tuning on this spi mmc driver before ( and we plan to). Could you do some test on you side to find out where is the bottleneck? SPI framework? spi mmc driver? Or SD card?

 

-Yi

QuoteReplyEditDelete

 

 

2008-11-26 22:23:38     new problem for adsl pppd

lm g (CHINA)

Message: 65877   

 

now ,we stop sd card

 

and  do another things for pppd

 

in kernel  uClinux-dist.R1.1-RC3 ,I use

 

pppd pty '/bin/pppoe' user 2007111111111

 

can get the adsl IP ,/etc/ppp/chap-secrets   like                  user   *     password

 

but  in kernel  uClinux-dist-2008R1-RC8,it's  ppp-2.4.4

 

use the same way ,can't get the adsl IP

 

Is it have some change for uClinux-dist.R1.1-RC3?

 

or some files to  refer to for uClinux-dist-2008R1-RC8

QuoteReplyEditDelete

 

 

2008-11-27 04:27:40     Re: new problem for adsl pppd

Yi Li (CHINA)

Message: 65899   

 

Please open another post for the pppd topic. Please list detail steps to reproduce your issue.

 

For the spi/mmc, thanks for contribution from one of our uses, we can use the mainline mmc_spi driver now, code will be checked into svn trunk this week.

 

-Yi

QuoteReplyEditDelete

 

 

2009-02-03 23:05:48     Re: new problem for adsl pppd

lm g (CHINA)

Message: 68807   

 

    we used1G SD card at  2.6.22.18-ADI-2008R1-svn, and we can read or write;

 

    but we use 8 G SD card ,it is't can  read or write, I want to known how to let  2.6.22.18-ADI-2008R1-svn to support  8 G SD card; or it's support  8 G SD card

 

1G SD card

 

New MMC/SD card found: 961 MB(1007681536 bytes)

spi_mmc:

 

8 G SD card

 

mount: mounting /dev/spi_mmc on /tmp failed

QuoteReplyEditDelete

 

 

2009-02-03 23:08:53     Re: new problem for adsl pppd

Yi Li (CHINA)

Message: 68808   

 

You will have to back port mmc_spi.c driver and spi_bfin5xx.c driver to 2008R1. SDHC is supported by kernel mmc stack. The old spi_mmc driver in 2008R1 does not support SDHC.

 

-Yi

QuoteReplyEditDelete

 

 

2009-02-03 23:30:41     Re: new problem for adsl pppd

lm g (CHINA)

Message: 68809   

 

yes, 8G SD is SDHC;

 

now how can i do to support 8G SDHC ?

QuoteReplyEditDelete

 

 

2009-02-04 00:45:38     Re: new problem for adsl pppd

lm g (CHINA)

Message: 68810   

 

SDHC is supported by kernel mmc stack

 

how can i do to let for kernel mmc stack?

QuoteReplyEditDelete

 

 

2009-02-04 04:53:36     Re: new problem for adsl pppd

Yi Li (CHINA)

Message: 68844   

 

lm,

 

> how can i do to let for kernel mmc stack?

 

Use the mmc_spi driver (drivers/mmc/host/mmc_spi.c).

 

-Yi

QuoteReplyEditDelete

 

 

2009-03-04 21:53:11     problem for spi_mmc

lm g (CHINA)

Message: 70392   

 

do you have new spi_mmc driver for2.6.22.18-ADI-2008R1-svn?and where to download?

 

                                                                                                                        Thank's

QuoteReplyEditDelete

 

 

2009-03-05 03:09:01     Re: problem for spi_mmc

Bill Xie (CHINA)

Message: 70413   

 

blackfin.uclinux.org/gf/project/uclinux-dist/frs/

Attachments

    Outcomes