![]() ![]() |
Sep 6 2005, 08:45 AM
Post
#1
|
|
|
Group: Members Posts: 577 Joined: 17-March 04 Member No.: 2,365 |
Hello
Just to let you know the MMC has been soldered into the simpad, and the driver is being developped. Currently some basic tests (like powering on and off leds from a kernel module) work fine. Attention - the picture on my website has the MMC card drawn backwards. it should read "Top view" instead of "bottom view". I'll fix the picture. Guylhem |
|
|
|
Sep 6 2005, 10:43 AM
Post
#2
|
|
|
Group: Members Posts: 6 Joined: 21-August 05 Member No.: 7,914 |
Very good work Guylhem!
|
|
|
|
Sep 7 2005, 02:54 AM
Post
#3
|
|
|
Group: Members Posts: 577 Joined: 17-March 04 Member No.: 2,365 |
BTW before killing my bluetooth chip (my own fault) I could get reliably speed up to 230 400 kbit/s.
I will release my custom 2.4.25 (backported bluetooth stack, custom mmc driver, support for 128 Mb) as soon as the mmc driver works.... it *almost* does. |
|
|
|
Sep 7 2005, 06:33 AM
Post
#4
|
|
|
Group: Members Posts: 5 Joined: 13-October 04 Member No.: 4,981 |
Does anyone know where to get those MD35 DECT module flatcable and/or connectors Guylhem is talking about in his Creating a "beautiful" Bluetooth module for the Siemens Simpad SL4?
|
|
|
|
Sep 7 2005, 07:01 AM
Post
#5
|
|
|
Group: Members Posts: 699 Joined: 26-February 04 From: near Munich, Germany Member No.: 2,043 |
QUOTE(laurens @ Sep 7 2005, 03:33 PM) Does anyone know where to get those MD35 DECT module flatcable and/or connectors Guylhem is talking about in his Creating a "beautiful" Bluetooth module for the Siemens Simpad SL4? I don't know about the MD35, but for the MD32 or 34 try: http://www.tis-gmbh.de/md32-34.html?&L=1-- hns |
|
|
|
Sep 7 2005, 07:26 AM
Post
#6
|
|
|
Group: Members Posts: 535 Joined: 7-March 04 Member No.: 2,195 |
Why would one need a cable if flying leads could easily be soldered?
Any technical details on what "almost working" means in this context? -albertr |
|
|
|
Sep 8 2005, 12:52 AM
Post
#7
|
|
|
Group: Members Posts: 577 Joined: 17-March 04 Member No.: 2,365 |
I don't know why I needed a cable - maybe to make a pretty module that can easily be plucked out of the simpad for improvement, so that everytime I had to solder/unsolder stuff on it, I could do that easily without risking frying the simpad motherboard :-)
Regarding the "almost working" : # insmod simpad-mmc.o mmc: GPIO init mmc: initialising MMC GPIO_SD_CS dir: 1 alt: 0 GPIO_SD_DI dir: 1 alt: 0 GPIO_SD_DO dir: 0 alt: 0 GPIO_SD_CS dir: 1 alt: 0 mmc: card init 1/2 mmc: card init 2/2 mmc: card init 3/3 Size = 249856, hardsectsize = 512, sectors = 499712 Partition check: mmc/disc0/disc: p1 # cat /etc/fstab|grep mmcroot@simpad:~# cat /etc/fstab |grep mmc /dev/mmc/disc0/part1 /mnt/mmc ext2 defaults,sync,noatime 0 0 # mount /mnt/mmc # df Filesystem 1k-blocks Used Available Use% Mounted on /dev/root 24320 20440 3880 84% / tmpfs 61868 36 61832 0% /var /dev/mtdblock/2 8192 6492 1700 79% /home /dev/hda1 125034 45654 79380 37% /mnt/cf /dev/mmc/disc0/part1 241949 20 229437 0% /mnt/mmc Sweet- 256 Mb in R/W on my simpad ! Along with my 128 Mb of RAM and internal bluetooth, it makes it a nice machine - the ultimate Zaurus once I get my Sandisk wifi+128 Mb CF working inside ! Currently merging home and root on the mtdblock - I will put Qtopia, my home and everything else (/opt) on mmc instead... The driver only needs to be powersaving aware to be complete. (ie when receiving a apm suspend signal, finish its operation, and reinit the card on resume) Anyway for now, and after some tests, I consider it a 99% success. The remaining 1% (powersaving) will be fixed when necessary. The files will soon be available on my website. Guylhem |
|
|
|
Sep 8 2005, 02:40 AM
Post
#8
|
|
|
Group: Members Posts: 577 Joined: 17-March 04 Member No.: 2,365 |
|
|
|
|
Sep 8 2005, 03:33 AM
Post
#9
|
|
|
Group: Members Posts: 7 Joined: 25-August 05 Member No.: 7,947 |
This is very interesting, indeed. I'm wondering what read/write performance you did achieve on the mmc...
|
|
|
|
Sep 8 2005, 05:04 AM
Post
#10
|
|
|
Group: Members Posts: 577 Joined: 17-March 04 Member No.: 2,365 |
What do you want me to run to test it ? some timed dd ? give me a command line and I'll test it.
|
|
|
|
Sep 8 2005, 05:40 AM
Post
#11
|
|
|
Group: Members Posts: 7 Joined: 25-August 05 Member No.: 7,947 |
How about this:
date ; dd bs=4096 count=10000 if=/dev/zero of=/mnt/mmc/test ; sync ; date This will write 40MB to the MMC and flush the cache. Then reboot to clean the cache and reread the file: date ; cat /mnt/mmc/test > /dev/null ; date |
|
|
|
Sep 8 2005, 07:06 AM
Post
#12
|
|
|
Group: Members Posts: 535 Joined: 7-March 04 Member No.: 2,195 |
Thanks for clarification, but I would like to see the output of `ls -la /mnt/mmc` at least
What particular brand of card do you use? It would be interesting to see tests of reading/writing from/to MMC simultaneously with high I/O activity of CF card to see if there's any timing problems under stress conditions. Someting like mounting NFS/SAMBA volume over CF wired/wireless link, and then do something like this: cd /mnt/nfs; tar cvf - . | (cd /mnt/mmc; tar xvpf - ) and then compare MD5 sums, of course... -albertr |
|
|
|
Sep 8 2005, 10:13 AM
Post
#13
|
|
|
Group: Members Posts: 577 Joined: 17-March 04 Member No.: 2,365 |
root@simpad:/mnt/mmc# date ; dd bs=256k count=64 if=/dev/zero of=/mnt/mmc/test ;sync; date
Thu Sep 8 17:15:19 UTC 2005 64+0 records in 64+0 records out Thu Sep 8 17:17:19 UTC 2005 root@simpad:/mnt/mmc# root@simpad:/mnt/mmc# root@simpad:/mnt/mmc# ls -l test -rw-r--r-- 1 root root 16777216 Sep 8 17:15 test (reboot) root@simpad:/mnt/mmc# date ; cat /mnt/mmc/test > /dev/null ; date Thu Sep 8 17:13:23 UTC 2005 Thu Sep 8 17:15:22 UTC 2005 16384/120=136 ko/s in read, same in write. Not so bad. Regarding corruption, don't worry. I've put binaries- they haven't been corrupted :-) |
|
|
|
Sep 8 2005, 03:20 PM
Post
#14
|
|
|
Group: Members Posts: 535 Joined: 7-March 04 Member No.: 2,195 |
Sounds promising.... So, you haven't experienced any problems? How long are you using it? I'll try to give it a shot when time permits, being very busy lately.
-albertr |
|
|
|
Sep 17 2005, 02:18 PM
Post
#15
|
|
|
Group: Members Posts: 535 Joined: 7-March 04 Member No.: 2,195 |
I've soldered a SD/MMC socket to Simpad and was trying to use guylhem's driver. Unfortunately, I'm having problems with 32MB MMC card that I have.
Sometimes I'm getting the following error messages: CODE mmc: GPIO init mmc: initialising MMC GPIO_SD_CS dir: 1 alt: 0 GPIO_SD_DI dir: 1 alt: 0 GPIO_SD_DO dir: 0 alt: 0 GPIO_SD_CS dir: 1 alt: 0 mmc: card init 1/2 mmc: card init 255 error GPIO_SD_CS dir: 1 alt: 0 GPIO_SD_DI dir: 1 alt: 0 GPIO_SD_DO dir: 0 alt: 0 GPIO_SD_CS dir: 1 alt: 0 mmc: card init 1/2 mmc: card init 255 error mmc: error 1 in mmc_card_init mmc: error -1 in mmc_init Sometimes it gets alittle bit further, but I still get errors: CODE mmc: GPIO init mmc: initialising MMC GPIO_SD_CS dir: 1 alt: 0 GPIO_SD_DI dir: 1 alt: 0 GPIO_SD_DO dir: 0 alt: 0 GPIO_SD_CS dir: 1 alt: 0 mmc: card init 1/2 mmc: card init 2/2 mmc: card init 3/3 Size = 31360, hardsectsize = 512, sectors = 62720 Partition check: mmca:end_request: I/O error, dev 79:00 (mmc), sector 0 end_request: I/O error, dev 79:00 (mmc), sector 2 end_request: I/O error, dev 79:00 (mmc), sector 4 end_request: I/O error, dev 79:00 (mmc), sector 6 end_request: I/O error, dev 79:00 (mmc), sector 0 end_request: I/O error, dev 79:00 (mmc), sector 2 end_request: I/O error, dev 79:00 (mmc), sector 4 end_request: I/O error, dev 79:00 (mmc), sector 6 unable to read partition table Either way, so far I was not able to do anything useful with this card on Simpad. The card has a single primary partition type 6 that is formated FAT16. It works fine in my cell phone, notebook and two different Zauruses. It looks it's able to read card's physical parameters sometimes, so wiring must be correct. Any idea what could be wrong? I'll try to find some old Sandisk 128MB SD card that I have somewhere and give it a try too. -albertr |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 24th May 2013 - 04:47 AM |