On Thursday, October 31, 2013 2:10:24 PM UTC-7, Jason Kridner wrote:
> > - I followed your instructions (8GB µSD, FAT32 formatted)
> > o If I press no button, the BBB boots on the eMMC
>
> This tells me that the bootloader you flashed onto the eMMC doesn't
> properly work with the uEnv.txt put onto the uSD card as part of following
> my instructions.
>
I've no idea what bootloader the Debian image flashed to my eMMC (as a lot
of people, I know nothing about Angström, and the first thing I did was to
put Debian into my device, a much more common distrib, because I just want
a cheap linux server to do some stuff at home).
I'm kind of a noob using the BBB, sorry about that (I'm using a RPi for
quite a while now, but I'm not considering myself as a power user --
despite managing some linux servers and having a master in embedded
systems, I'm a web developer and I love high level programming). What I
mean but all that is: something that could look obvious to you isn't for
95% of the people reading your guides, the 95% that aren't doing BBB
related stuff for a living.
But well, if I could boot onto the µSD using the boot button that would be
ever more fine to me (I could leave the µSD into the BBB and boot on it
when I want to backup my distrib).
> > o If I press the “boot” button while plugging the power, the BBB just
> > doesn’t boot (stays in a “powered off” state, with only the LED near the
> > power plug on)
>
> This means that the uSD card FAT partition isn't marked as bootable.
> You can do that with 'fdisk' from your BeagleBone running Debian in all
> likelihood.
>
Huge thanks for the step by step :)
I think it would be way easier for everybody (including you ^^) if you made
a .img image of the card (maybe in different sizes?) -- this would
eliminate any possible mistake in the process.
As most people, I'm using Windows and formatting a card doesn't mark the
partition as bootable, so following your base instructions just doesn't
work.
I've found that my µSD is in /dev/mmcblk0 (I tried /dev/mmcblk1 at first
and it bricked my BBB, I had to flash it again -- not a big deal)
root@arm:~# cat /proc/partitions
major minor #blocks name
179 0 7822336 mmcblk0
179 1 7818240 mmcblk0p1
179 8 1875968 mmcblk1
179 9 72261 mmcblk1p1
179 10 1799280 mmcblk1p2
179 24 1024 mmcblk1boot1
179 16 1024 mmcblk1boot0
The card is now bootable:
root@arm:~# fdisk /dev/mmcblk0
Command (m for help): p
Disk /dev/mmcblk0: 8010 MB, 8010072064 bytes
214 heads, 8 sectors/track, 9138 cylinders, total 15644672 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/mmcblk0p1 * 8192 15644671 7818240 b W95 FAT32
It was still booting to the eMMC by default, so I powered it on while
having the boot button but -- no matter if I pressed the button for 4
seconds or until LEDs are on - it somewhat booted, but the USR0 was
directly steady on. So I tried to reboot it (using the "reset" button) and
it's now correctly writing the image to the SD. I don't really know how the
"boot" button works, but considering this behaviour I would say it disables
the eMMC while pressed, isn't?
So my "create image process" is: power the BBB on with the boot button
pressed for like 5s, and once the USR0 is steady on, press the reset button
and then wait 10min for USR0 to be steady on again.
Again, thank you a lot for your help. I really like the BBB, the only think
I don't like is how difficult it is to make an image of the eMMC and your
method is a huge step into making it simple.
> root@beaglebone:~# fdisk /dev/mmcblk1
> Welcome to fdisk (util-linux 2.23.1).
>
> Changes will remain in memory only, until you decide to write them.
> Be careful before using the write command.
>
>
> Command (m for help): a
> Partition number (1,2, default 2): 1
>
> Command (m for help): p
>
> Disk /dev/mmcblk1: 3904 MB, 3904897024 bytes, 7626752 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 label type: dos
> Disk identifier: 0x00000000
>
> Device Boot Start End Blocks Id System
> /dev/mmcblk1p1 * 2048 133119 65536 e W95 FAT16
> (LBA)
> /dev/mmcblk1p2 133120 7626751 3746816 83 Linux
>
> >
> > The BBB is brand new, so maybe they changed something.
>
> Who's "they"? It is possible CircuitCo switched the bootloader image on
> the eMMC, but it sounds more like you did that above.
Yeah, I thought maybe CircuitCo changed something in the bootloading or
something, but it definitively doesn't seems to be the issue here.
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
