On Sun, Jan 5, 2014 at 4:33 PM, Brian Piccioni <nairb1...@gmail.com> wrote: > Hello and thank you in advance for the help. > > I know that, in general, this topic has been addressed before. I looked > through all the posts, followed whatever methods, etc., were suggested but I > can't get it to work (it being cloning my eMMC on one BBB to another BBB). > > I live in rural Canada and downloading costs me $10/gb so I am cautious > about downloading stuff unless i have to, etc.. > > My 'source' system is Ubuntu 13.04 (GNU/Linux 3.8.13-bone21 armv7l). > Initially my target was an 'out of the box' BBB. > > I booted the 'source' system from an Anstrom 'bootable' microSD, mounted a > USB drive, in the USB directory I executed > > dd if=/dev/mmcblk1 of=BeagleBoneBlack-eMMC-image-Jan52014.img bs=10M > > The command completed with no errors and a reassuring amount of data copied > (1.9gb) > > Then I booted the 'destination' system from an Anstrom 'bootable' microSD, > mounted my USB drive, and in the USB directory executed > > dd if=BeagleBoneBlack-eMMC-image-Jan52014.img of=/dev/mmcblk1 bs=10M > > Again, the command completed with no errors and a reassuring amount of data > copied (1.9gb) > > > Unfortunately, when I boot the destination machine, nothing much happens > except a flashing LED. I can't SSH into the board and it doesn't even show > up on my network.
well get a usb-serial adapter and it'll tell you why it can't boot... > > Figuring there was something Ubuntu related I flashed the destination BBB > with Ubuntu 12.4, which I had around. It worked fine, however, when I > repeated the above procedure (including booting Angstrom off microSD) I got > the same result. > > > I wonder if there is something wrong with my eMMC partion table on the > source BBB (even though it works fine). When I execute fdisk -l I get the > following (note the doesn't contain a valid partition table reports) > > Disk /dev/mmcblk1: 1920 MB, 1920991232 bytes > 255 heads, 63 sectors/track, 233 cylinders, total 3751936 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Device Boot Start End Blocks Id System > /dev/mmcblk1p1 * 63 144584 72261 c W95 FAT32 (LBA) > /dev/mmcblk1p2 144585 3743144 1799280 83 Linux > > Disk /dev/mmcblk1boot1: 1 MB, 1048576 bytes > 4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/mmcblk1boot1 doesn't contain a valid partition table > > Disk /dev/mmcblk1boot0: 1 MB, 1048576 bytes > 4 heads, 16 sectors/track, 32 cylinders, total 2048 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/mmcblk1boot0 doesn't contain a valid partition table ignore the "/dev/mmcblk1bootX" they are not used in this system.. > I would be very grateful if somebody could tell me what I am doing wrong. your debugging blind, grab a usb-serial adapter and you can easily see what's wrong.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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.
