Sorry, After flashing the BBB the ID.txt contains:
*CLoud9 GNOME Image 2013.09.04* and not *CLoud9 GNOME Image 2013.06.20* as I wrongly wrote in my previous post. BR Marco On Thursday, September 26, 2013 11:13:12 AM UTC+2, basi...@gmail.com wrote: > > Hi Gerald, > > thanks for your reply! > I followed your suggestion using the latest firmware. > After flashing the BBB I see now that the ID.txt files shows: > > *CLoud9 GNOME Image 2013.06.20* > root@beaglebone:~# more /etc/version > > Angstrom v2012.12 > root@beaglebone:~# > > root@beaglebone:~# uname -a > Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l > GNU/Linux > > I repartitioned my microSD as before (UENV and SD) and created the > uEnv.txt in primary FAT32 partition (UENV ) as above. > > If I insert the microSD into the BBB, the microSD is detected and the two > partitions are automatically mounted under /media > > root@beaglebone:/# cd /media/ > root@beaglebone:/media# ls > BEAGLEBONE SD UENV card cf hdd mmc1 net ram realroot union > root@beaglebone:/media# more UENV/uEnv.txt > mmcdev=1 > bootpart=1:2 > mmcroot=/dev/mmcblk1p2 ro > optargs=quiet > root@beaglebone:/media# > > The problem is when I reboot the BBB with the microSD already in. > I still receive the same error message as before (I attach the complete > console output *BBBlog.txt*): > > SD/MMC found on device 0 > reading uEnv.txt > 66 bytes read in 3 ms (21.5 KiB/s) > Loaded environment from uEnv.txt > Importing environment from mmc ... > gpio: pin 55 (gpio 55) value is 1 > mmc_send_cmd : timeout: No status update > **Bad partition specification mmc 1:2 > U-Boot# > I thought (and hoped) the problem was due to the missing of CR-LF at the > end of the uEnv.txt as I read in other posts, but it is not :( > > What I really don't get is why and how I did manage few days ago to boot > the BBB with the microSD in, just after following the instructions in > http://circuitco.com/support/index.php?title=MicroSD_As_Extra_Storage > > But I can't know achieve the same result. > (I had to re-flash the BBB from scratch because I did later on other > mistakes ... I'm learning :) ) > > Clearly this **Bad partition specification mmc *1:2* error message is > related to the following settings in the uEnv.txt > mmcdev=1 > bootpart=*1:2* > > But why now suddenly doesn't it accept 1:2 while it did it few days ago? > > Thanks in advance for any help/saggestion. > > Marco > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
