mmcinit --> "No MMC Card found"
240 views
Skip to first unread message
TreibAir
Jun 29, 2009, 9:53:11 AM6/29/09
to Beagle Board
Hi everybody,
I just tried to get my new Beagleboard to work. Following the
instructions in http://elinux.org/BeagleBoardUbuntu I have built
myself an SD card with Ubuntu but using the mmcinit command in U-Boot
leads to the error message "No MMC card found". I also tried a card
which came with the board with the same results. Is there a
possibility that the card slot is defective or is it a software issue?
Thanks in advance!
I just tried to get my new Beagleboard to work. Following the
instructions in http://elinux.org/BeagleBoardUbuntu I have built
myself an SD card with Ubuntu but using the mmcinit command in U-Boot
leads to the error message "No MMC card found". I also tried a card
which came with the board with the same results. Is there a
possibility that the card slot is defective or is it a software issue?
Thanks in advance!
Robert Nelson
Jun 29, 2009, 7:35:45 PM6/29/09
to beagl...@googlegroups.com
Hello,
I've seen this happen before, usually it's a corrupt file system on the mmc card
Check your card with : "sudo fdisk -l" are the partitions listed correctly?
Next, when you rebuild the mmc card, use the 'sync' command to flush
the kernel buffers to ensure everything is written the mmc card.
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Michael Evans
Jun 29, 2009, 8:06:25 PM6/29/09
to beagl...@googlegroups.com
If you spend a lot of time ejecting and inserting SD cards you'll soon come across the "sync" is asynchronous <i>feature</i> of linux. Suffice to say its very annoying and at times leads to corrupt filesystems even after you've sync'ed a couple of times and waited for a couple of seconds...
I'm old skool and always thought that the "eject" command was only for CD-ROMs... turns out its for pendrives and SD cards too....
So... don't "sudo sync" but rather "sudo eject something" where something is either the mount point, the partition dev file (e.g. /dev/sdd2) or the actual device (e.g. /dev/sdd). When the "eject" command returns the drive can be removed immediately without fear of corruption... :)
> Date: Mon, 29 Jun 2009 18:35:45 -0500
> Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
> From: robert...@gmail.com
> To: beagl...@googlegroups.com
I'm old skool and always thought that the "eject" command was only for CD-ROMs... turns out its for pendrives and SD cards too....
So... don't "sudo sync" but rather "sudo eject something" where something is either the mount point, the partition dev file (e.g. /dev/sdd2) or the actual device (e.g. /dev/sdd). When the "eject" command returns the drive can be removed immediately without fear of corruption... :)
> Date: Mon, 29 Jun 2009 18:35:45 -0500
> Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
> From: robert...@gmail.com
> To: beagl...@googlegroups.com
> Upgrade to Internet Explorer 8 Optimised for MSN. Download Now
TreibAir
Jun 30, 2009, 5:49:58 AM6/30/09
to Beagle Board
I have attatched the messages from my beagle below. I am wondering why
I get the messages "Loading u-boot.bin from nand" even if I have
pressed the USER button. Should the Beagle in this case not at least
try to read the MMC card? I have also run the fsinfo command which
leads to an error message (see below).
My partitions look correct:
Gerät boot. Anfang Ende Blöcke Id System
/dev/sde1 * 1 6 48163+ b W95 FAT32
/dev/sde2 7 489 3879697+ 83 Linux
________________________________________________________
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand
U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31)
I2C: ready
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 256 MB
NAND: 256 MiB
MUSB: using high speed
In: serial usbtty
Out: serial usbtty
Err: serial usbtty
Board revision C
Serial #0bba00030000000004013f790301e01b
Hit any key to stop autoboot: 10 9 8 0
OMAP3 beagleboard.org # mmcinit
No MMC card found
OMAP3 beagleboard.org # fsinfo
### filesystem type is JFFS2
Scanning JFFS2 FS: read_nand_cached: error reading nand off
0xffffe00 size 8192 bytes
done.
Compression: NONE
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: ZERO
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: RTIME
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: RUBINMIPS
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: COPY
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: DYNRUBIN
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: ZLIB
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
OMAP3 beagleboard.org # printenv
bootdelay=10
baudrate=115200
loadaddr=0x80200000
rdaddr=0x81600000
console=ttyS2,115200n8
optargs=
mmcargs=setenv bootargs console=${console} ${optargs} root=/dev/
mmcblk0p2 rw rootfstype=ext3 rootwait
ramargs=setenv bootargs console=${console} ${optargs} root=/dev/ram0
rw ramdisk_size=32768 initrd=${rdaddr},32M
ubifsargs=setenv bootargs console=${console} ${optargs}
root=ubi0:beagleroot ubi.mtd=4 rw rootfstype=ubifs
jffs2args=setenv bootargs console=${console} ${optargs} root=/dev/
mtdblock4 rw rootfstype=jffs2
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; autoscr ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage.bin
loadramdisk=fatload mmc 0 ${rdaddr} ramdisk.gz
ramboot=echo Booting from ramdisk.gz ...; run ramargs; bootm $
{loadaddr}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run jffs2args; nand read $
{loadaddr} 280000 400000; bootm ${loadaddr}
usbtty=cdc_acm
stdout=serial,usbtty
stdin=serial,usbtty
stderr=serial,usbtty
serial=0bba00030000000004013f790301e01b
bootargs=console=ttyS2,115200n8 ramdisk size=8192 root=/dev/ram0 rw
rootfstype=ext2 initrd=0x81600000,8M nohz=Off
bootcmd=mmcinit; fatload mmc 0 0x80300000 uImage;fatload mmc 0
0x81600000 rd-ext2.bin;bootm 0x80300000
Environment size: 1310/131068 bytes
OMAP3 beagleboard.org #
I get the messages "Loading u-boot.bin from nand" even if I have
pressed the USER button. Should the Beagle in this case not at least
try to read the MMC card? I have also run the fsinfo command which
leads to an error message (see below).
My partitions look correct:
Gerät boot. Anfang Ende Blöcke Id System
/dev/sde1 * 1 6 48163+ b W95 FAT32
/dev/sde2 7 489 3879697+ 83 Linux
________________________________________________________
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand
U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31)
I2C: ready
OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
DRAM: 256 MB
NAND: 256 MiB
MUSB: using high speed
In: serial usbtty
Out: serial usbtty
Err: serial usbtty
Board revision C
Serial #0bba00030000000004013f790301e01b
Hit any key to stop autoboot: 10 9 8 0
OMAP3 beagleboard.org # mmcinit
No MMC card found
OMAP3 beagleboard.org # fsinfo
### filesystem type is JFFS2
Scanning JFFS2 FS: read_nand_cached: error reading nand off
0xffffe00 size 8192 bytes
done.
Compression: NONE
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: ZERO
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: RTIME
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: RUBINMIPS
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: COPY
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: DYNRUBIN
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
Compression: ZLIB
" frag count: 0"
" compressed sum: 0"
" uncompressed sum: 0"
OMAP3 beagleboard.org # printenv
bootdelay=10
baudrate=115200
loadaddr=0x80200000
rdaddr=0x81600000
console=ttyS2,115200n8
optargs=
mmcargs=setenv bootargs console=${console} ${optargs} root=/dev/
mmcblk0p2 rw rootfstype=ext3 rootwait
ramargs=setenv bootargs console=${console} ${optargs} root=/dev/ram0
rw ramdisk_size=32768 initrd=${rdaddr},32M
ubifsargs=setenv bootargs console=${console} ${optargs}
root=ubi0:beagleroot ubi.mtd=4 rw rootfstype=ubifs
jffs2args=setenv bootargs console=${console} ${optargs} root=/dev/
mtdblock4 rw rootfstype=jffs2
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; autoscr ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage.bin
loadramdisk=fatload mmc 0 ${rdaddr} ramdisk.gz
ramboot=echo Booting from ramdisk.gz ...; run ramargs; bootm $
{loadaddr}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run jffs2args; nand read $
{loadaddr} 280000 400000; bootm ${loadaddr}
usbtty=cdc_acm
stdout=serial,usbtty
stdin=serial,usbtty
stderr=serial,usbtty
serial=0bba00030000000004013f790301e01b
bootargs=console=ttyS2,115200n8 ramdisk size=8192 root=/dev/ram0 rw
rootfstype=ext2 initrd=0x81600000,8M nohz=Off
bootcmd=mmcinit; fatload mmc 0 0x80300000 uImage;fatload mmc 0
0x81600000 rd-ext2.bin;bootm 0x80300000
Environment size: 1310/131068 bytes
OMAP3 beagleboard.org #
Michael Evans
Jun 30, 2009, 6:14:08 AM6/30/09
to beagl...@googlegroups.com
Holding the USER button changes where the bootrom tried to find X-Loader. The boot order is normally NAND,USB,SERIAL,MMC and with USER pressed it becomes USB,SERIAL,MMC,NAND... if the first three options don't work out then the bootrom will eventually boot from NAND again.
Its worth pointing out that this is where X-Loader is loaded from. X-Loader could be compiled to use NAND rather than MMC so its worth checking you've got the right version on your SD card.
This is what I get:
$ sudo fdisk -l /dev/sdd
Disk /dev/sdd: 2032 MB, 2032664576 bytes
255 heads, 63 sectors/track, 247 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 14 112423+ c W95 FAT32 (LBA)
/dev/sdd2 15 247 1871572+ 83 Linux
Your first parition has an ID of 'b' rather than 'c'. You might also need to change the drive's geometry, see: http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat
> Date: Tue, 30 Jun 2009 02:49:58 -0700
Its worth pointing out that this is where X-Loader is loaded from. X-Loader could be compiled to use NAND rather than MMC so its worth checking you've got the right version on your SD card.
This is what I get:
$ sudo fdisk -l /dev/sdd
Disk /dev/sdd: 2032 MB, 2032664576 bytes
255 heads, 63 sectors/track, 247 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 14 112423+ c W95 FAT32 (LBA)
/dev/sdd2 15 247 1871572+ 83 Linux
Your first parition has an ID of 'b' rather than 'c'. You might also need to change the drive's geometry, see: http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat
> Date: Tue, 30 Jun 2009 02:49:58 -0700
> Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
TreibAir
Jun 30, 2009, 7:39:37 AM6/30/09
to Beagle Board
Ok, I have rebuilt the Card according to your guide, it now looks like
this:
Platte /dev/sde: 4029 MByte, 4029677568 Byte
255 Köpfe, 63 Sektoren/Spuren, 489 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x0008f324
Gerät boot. Anfang Ende Blöcke Id System
/dev/sde1 * 1 51 409626 c W95 FAT32
(LBA)
/dev/sde2 52 489 3518235 83 Linux
I've used MLO, uImage.bin and u-boot.bin from
http://code.google.com/p/beagleboard/downloads/list but still get the
"No mmc card found" message when I enter mmcinit and the board skips
straigt to booting from nand.
On 30 Jun., 12:14, Michael Evans <horse_d...@hotmail.com> wrote:
> Holding the USER button changes where the bootrom tried to find X-Loader. The boot order is normally NAND,USB,SERIAL,MMC and with USER pressed it becomes USB,SERIAL,MMC,NAND... if the first three options don't work out then the bootrom will eventually boot from NAND again.
>
> Its worth pointing out that this is where X-Loader is loaded from. X-Loader could be compiled to use NAND rather than MMC so its worth checking you've got the right version on your SD card.
>
> This is what I get:
>
> $ sudo fdisk -l /dev/sdd
> Disk /dev/sdd: 2032 MB, 2032664576 bytes
> 255 heads, 63 sectors/track, 247 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x00000000
>
> Device Boot Start End Blocks Id System
> /dev/sdd1 * 1 14 112423+ c W95 FAT32 (LBA)
> /dev/sdd2 15 247 1871572+ 83 Linux
>
> Your first parition has an ID of 'b' rather than 'c'. You might also need to change the drive's geometry, see:http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat
>
>
>
>
>
> > Date: Tue, 30 Jun 2009 02:49:58 -0700
> > Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
> > From: treib...@gmx.net
> _________________________________________________________________
> With Windows Live, you can organise, edit, and share your photos.http://clk.atdmt.com/UKM/go/134665338/direct/01/
this:
Platte /dev/sde: 4029 MByte, 4029677568 Byte
255 Köpfe, 63 Sektoren/Spuren, 489 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x0008f324
Gerät boot. Anfang Ende Blöcke Id System
(LBA)
/dev/sde2 52 489 3518235 83 Linux
I've used MLO, uImage.bin and u-boot.bin from
http://code.google.com/p/beagleboard/downloads/list but still get the
"No mmc card found" message when I enter mmcinit and the board skips
straigt to booting from nand.
On 30 Jun., 12:14, Michael Evans <horse_d...@hotmail.com> wrote:
> Holding the USER button changes where the bootrom tried to find X-Loader. The boot order is normally NAND,USB,SERIAL,MMC and with USER pressed it becomes USB,SERIAL,MMC,NAND... if the first three options don't work out then the bootrom will eventually boot from NAND again.
>
> Its worth pointing out that this is where X-Loader is loaded from. X-Loader could be compiled to use NAND rather than MMC so its worth checking you've got the right version on your SD card.
>
> This is what I get:
>
> $ sudo fdisk -l /dev/sdd
> Disk /dev/sdd: 2032 MB, 2032664576 bytes
> 255 heads, 63 sectors/track, 247 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x00000000
>
> Device Boot Start End Blocks Id System
> /dev/sdd1 * 1 14 112423+ c W95 FAT32 (LBA)
> /dev/sdd2 15 247 1871572+ 83 Linux
>
> Your first parition has an ID of 'b' rather than 'c'. You might also need to change the drive's geometry, see:http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat
>
>
>
>
>
> > Date: Tue, 30 Jun 2009 02:49:58 -0700
> > Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
> With Windows Live, you can organise, edit, and share your photos.http://clk.atdmt.com/UKM/go/134665338/direct/01/
Michael Evans
Jun 30, 2009, 8:28:11 AM6/30/09
to beagl...@googlegroups.com
Hmm... either the SD connector is broken (seems a lot of that around at the moment :) or the SD card simply isn't compatible with the BeagleBoard... Your 8Gb card should be fine... provided its SDHC and not SDXC (I've been happily using a 16Gb SHDC card)
I'd have to assume the connector is broken.
> Date: Tue, 30 Jun 2009 04:39:37 -0700
I'd have to assume the connector is broken.
> Date: Tue, 30 Jun 2009 04:39:37 -0700
> Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
Michael Evans
Jun 30, 2009, 8:39:00 AM6/30/09
to beagl...@googlegroups.com
Hang on... misread your output... you've got a 4Gb card...
Its a bit hot here today so brain has gone to mush...
Is your first parition around 400Mb...? That might be a problem for the bootrom... Most people have a primary partition of 50Mb which is usually ample, perhaps it being so large is the problem...???? (I think the Google code instructions should say +50M for the partition size rather than 50 cyclinders...!!)
From: horse...@hotmail.com
To: beagl...@googlegroups.com
Its a bit hot here today so brain has gone to mush...
Is your first parition around 400Mb...? That might be a problem for the bootrom... Most people have a primary partition of 50Mb which is usually ample, perhaps it being so large is the problem...???? (I think the Google code instructions should say +50M for the partition size rather than 50 cyclinders...!!)
From: horse...@hotmail.com
To: beagl...@googlegroups.com
Subject: [beagleboard] Re: mmcinit --> "No MMC Card found"
Date: Tue, 30 Jun 2009 13:28:11 +0100
Dan Poirot
Jun 30, 2009, 8:56:10 AM6/30/09
to beagl...@googlegroups.com
Go get the ESC demo image from beagleboard.org
dd() from the image to the card
Give it a try and report back...
- dan
On 6/30/09, Michael Evans <horse...@hotmail.com> wrote:
>
> Hang on... misread your output... you've got a 4Gb card...
> Its a bit hot here today so brain has gone to mush...
>
> Is your first parition around 400Mb...? That might be a problem for the
> bootrom... Most people have a primary partition of 50Mb which is usually
> ample, perhaps it being so large is the problem...???? (I think the Google
> code instructions should say +50M for the partition size rather than 50
> cyclinders...!!)
>
dd() from the image to the card
Give it a try and report back...
- dan
On 6/30/09, Michael Evans <horse...@hotmail.com> wrote:
>
> Hang on... misread your output... you've got a 4Gb card...
> Its a bit hot here today so brain has gone to mush...
>
> Is your first parition around 400Mb...? That might be a problem for the
> bootrom... Most people have a primary partition of 50Mb which is usually
> ample, perhaps it being so large is the problem...???? (I think the Google
> code instructions should say +50M for the partition size rather than 50
> cyclinders...!!)
>
Robert Nelson
Jun 30, 2009, 9:43:49 AM6/30/09
to beagl...@googlegroups.com
On Tue, Jun 30, 2009 at 7:39 AM, Michael Evans<horse...@hotmail.com> wrote:
> Hang on... misread your output... you've got a 4Gb card...
> Its a bit hot here today so brain has gone to mush...
>
> Is your first parition around 400Mb...? That might be a problem for the
> bootrom... Most people have a primary partition of 50Mb which is usually
> ample, perhaps it being so large is the problem...???? (I think the Google
> code instructions should say +50M for the partition size rather than 50
> cyclinders...!!)
> Hang on... misread your output... you've got a 4Gb card...
> Its a bit hot here today so brain has gone to mush...
>
> Is your first parition around 400Mb...? That might be a problem for the
> bootrom... Most people have a primary partition of 50Mb which is usually
> ample, perhaps it being so large is the problem...???? (I think the Google
> code instructions should say +50M for the partition size rather than 50
> cyclinders...!!)
I was thinking the same thing, however using a 400Mb partition on my
4Gb Transcend card works just fine on my beagle b5 with U-Boot
2009.3/2009.6-rc2... X-loader 1.4.2...
Disk /dev/sdd: 4029 MB, 4029677568 bytes
255 heads, 63 sectors/track, 489 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ba161
Device Boot Start End Blocks Id System
/dev/sdd1 1 51 409626 b W95 FAT32
Reply all
Reply to author
Forward
0 new messages