So I got my 8gb flash, and resized original boards partition to be smaller 
than second board.  So now the problem is I have flashed new board, and it 
will not boot up.  I can mount and view both partitions correctly, and 
everything looks ok, but I only get "CCC" when trying to boot and viewing 
with FTDI cable.   Any ideas?

Disk /dev/mmcblk1: 3867 MB, 3867148288 bytes
                                  
4 heads, 16 sectors/track, 118016 cylinders, total 7553024 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   *        2048      198655       98304    e  W95 FAT16 (LBA)
  
/dev/mmcblk1p2          198656     7571455     3686400   83  Linux



On Tuesday, December 2, 2014 at 11:20:13 PM UTC-5, Graham wrote:
>
> I think you will have two problems.
>
> First, you can not put a 4GB file on a 4 GB card, because there must also 
> be room for the 
> Linux OS, and depending on the version, this can be another 1 GB, or more.
>
> Second problem is that when you install a 2 GB image on a 4 GB card, the 
> partition as
> installed is typically about 2 GB, and the rest of the card can not be 
> used, until you
> expand the partition to the full size of the card.
>
> So, for working with the 4 GB eMMC version of the Beaglebone Black, you 
> must use
> at least an 8 GB card.  I use 16 GB, so that there is room for about three 
> images
> that are not compressed.  You can not go larger than 32 GB at this time.
>
> --- Graham
>
> ==
>
> On Tuesday, December 2, 2014 5:57:16 PM UTC-6, br...@forceconstant.com 
> wrote:
>>
>> So in that other thread, it was instructed to use the same dd command "dd 
>> if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M" to 
>> create image, so why would mine only end up 2GB instead of 4GB?  I cannot 
>> follow those instructions exactly, as I only have a 4GB SD card, so maybe 
>> this is the problem since the eMMC is 4GB also.
>>
>> On Tuesday, December 2, 2014 5:22:47 PM UTC-5, janszyma...@gmail.com 
>> wrote:
>>>
>>> there is another thread here *Duplicate BeagleBone black setup* 
>>> <https://groups.google.com/forum/embed/?place=forum/beagleboard&showsearch=true&showpopout=true&showtabs=true&hideforumtitle=true&parenturl=http%3A%2F%2Fwww.beagleboard.org%2FCommunity%2FForums#%21category-topic/beagleboard/beaglebone-black/hKuAggxij40>
>>>  dated 
>>> Nov 28, where you will find a solution to your problem.
>>> Good luck.
>>> Jan
>>>
>>> On Wednesday, December 3, 2014 6:32:08 AM UTC+11, 
>>> br...@forceconstant.com wrote:
>>>
>>>> I am trying to clone an existing BBB, so my first try is using the 
>>>> scripts on http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents 
>>>> .  So first thing I notice is the .img file created was only 2GB, whereas 
>>>> this is a newer BBB that has 4GB eMMC.  So when I updated script to write 
>>>> the img to new BBB, it no longer boots from eMMC.  i would like to make 
>>>> exact copies including uENV.txt, etc.  Does anyone know why this is not 
>>>> working?
>>>>
>>>> The read command script is 
>>>>
>>>> #!/bin/sh
>>>> echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
>>>> dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img 
>>>> bs=10M 
>>>> sync
>>>> echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigge
>>>>
>>>

-- 
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/d/optout.

Reply via email to