Quote:
dmsg doesn't show any event on card insertion.
No device node is created either.
Do I need to create the device node manually?
Something like "mknod /dev/mmcblock0 b 254 0" ?

1.you can check whether the mmc driver configed in the kernel,i think if it configed there should have some info about it.
2.in the .config you should config the following
file system -->
pseudo filesystem-->
/proc file system support choose
/proc/kcore support choose
sysfs file system support choose
/dev file system support choose
auto mount at boot not choose
3. fdisk /dev/mmcblock0
4. mx31# mount -t vfat /dev/mmcblock0p1 /mnt/

Hi,

I am also having problems with my SanDisk TransFlash card. I have enabled MMC/SD drivers, /proc, sysfs file system support and I am getting the following error:

MXCMMC: CMD: opcode: 18 <6>arg: 0x00000000 <6>flags: 0x00000035
[ 54.700000] mxcmci_request:status: <6>CARD_BUS_CLK_RUN |<6>SDIO_INT_ACTIVE |<6>XBUF_EMPTY |<6>YBUF_EMPTY |<6>
[ 54.710000] mxcmci_start_clock:status: <6>mxcmci_irq:status: <6>RESP_CRC_ERR |<6>BUF_READ_RDY |<6>END_CMD_RESP |<6>SDIO_I>[ 51.720000] MXCMMC: cmd crc error
[ 54.730000] CARD_BUS_CLK_RUN |<6>SDIO_INT_ACTIVE |<6>XBUF_EMPTY |<6>YBUF_EMPTY |<6>
[ 54.740000] mxcmci_start_clock:status: <6>BUF_READ_RDY |<6>CARD_BUS_CLK_RUN |<6>SDIO_INT_ACTIVE |<6>BUF_OVFL |<6>XBUF_FUL>[ 51.750000] mmcblk0: error 2 sending read/write command
[ 52.750000] end_request: I/O error, dev mmcblk0, sector 0
[ 51.750000] Buffer I/O error on device mmcblk0, logical block 0
[ 54.770000] MXCMMC: CMD: opcode: 18 <6>arg: 0x00000000 <6>flags: 0x00000035
[ 54.770000] mxcmci_request:status: <6>BUF_READ_RDY |<6>SDIO_INT_ACTIVE |<6>BUF_OVFL |<6>XBUF_FULL |<6>YBUF_FULL |<6>
[ 54.780000] mxcmci_start_clock:status: <6>SDIO_INT_ACTIVE |<6>XBUF_EMPTY |<6>YBUF_EMPTY |<6>
[ 54.790000] mxcmci_start_clock:status: <6>BUF_READ_RDY |<6>CARD_BUS_CLK_RUN |<6>SDIO_INT_ACTIVE |<6>BUF_OVFL |<6>XBUF_FUL>

And the kernel hangs there.

If I try to mount after bootup, it doesnt mount.

mx31# cat /proc/devices
Block devices:
...
254 mmc
mx31# mknod /dev/mmcblock0 b 254 0
mx31# fdisk /dev/mmcblock0
Unable to open /dev/mmcblock0
mx31# mount -t vfat /dev/mmcblock0 /mnt/
mount: Mounting /dev/mmcblock0 on /mnt/ failed: No such device or address

Is this a problem with the disk since it says CRC error?

Thanks

I am not able to mount the SD/MMC card after the system boots. If the card is inserted at the time of boot up the card works just fine. But when I insert the card later(after bootup) I dont see a mmcblk created. And the interrupt routine itself is not called. Has anybody faced this problem. Any pointers would be really great.

Similar problem for me as well:

mx31# mount -t vfat /dev/mmcblock0 /mnt/sd
udevsend[1268]: main: error getting socket: Address family not supported by protocol
mount: Mounting /dev/mmcblock0 on /mnt/sd failed: Invalid argument

I have tried booting with the card in and then I don't have to do mknod, but it won't mount. I have tried an old 32MB card and a newer 2GB one. When I stick the card in I get these warnings:

mx31# [ 52.880000] mmc0: host does not support reading read-only switch. assuming write-enable.
[ 54.940000] mmcblk0: mmc0:b368 D0507 29888KiB
[ 54.940000] mmcblk0:udevsend[1362]: main: error getting socket: Address family not supported by protoco
l
p1
udevsend[1389]: main: error getting socket: Address family not supported by protocol
udevsend[1391]: main: error getting socket: Address family not supported by protocol


I hope the solution is out there.

someone more familiar with the patches will have to comment on what's in the code, but I know the two switches built into the sd socket are wired up differently on the ads board and the lpd board. ads board used their fpga and lpd board uses processor gpio. if the patches don't set up and point to these gpio it might explain why it works when the card is in prior to booting.

change the GPIO1_1 to GPIO1_6 in mx31lite_gpio.c for sdhc (1).

This will solve the problem of autodetection of sd card after linux has booted.

How are you getting fdisk, do you have to configure busybox to add this or is it in another ltib package?

fdisk is already there in my busybox rootfs. I am using imx31_ads_20070128-rel3-ltib.iso and by default it is there in /sbin.

Your changes worked for detection of the card, but mmcblk doesnt get created and there are no error messages either. It still works when i have card inserted prior to booting.