BeagleBone Black fails to Boot for micro SD card

[Stephen Bates]

Hello,

I have recently bought a BeagleBone Black Rev C but it fails to boot from the micro SD card, I have uploaded the latest image to a micro SD card which I have then placed in my BeagleBone Black and connected it to the PC via connector P4. The device can initially be contacted using Putty however when I press and hold S2 and press and release S3 and then release S2 the board turns off and fails to restart/reboot, all the LEDs are off including power. The device will restart using the old image if I press S3.

Can anyone help?

Regards

Stephen

[Dennis Lee Bieber]

On Thu, 24 May 2018 07:07:48 -0700 (PDT), Stephen Bates
<stephen....@gmail.com> declaimed the
following:

>I have recently bought a BeagleBone Black Rev C but it fails to boot from
>the micro SD card, I have uploaded the latest image to a micro SD card

What image is on the eMMC to begin with?

>which I have then placed in my BeagleBone Black and connected it to the PC
>via connector P4. The device can initially be contacted using Putty however
>when I press and hold S2 and press and release S3 and then release S2 the

For quite some time now (Jessie and Stretch; I think the last Wheezy
also) the boards will boot from SD card /without/ having to hold the
alt-boot button. Just insert the SD card and apply power. The only trick
may be if one has a uBoot in eMMC that doesn't do uBoot device tree, but
are booting an SD card that expected uBoot to load the device tree -- that
may need the alt-boot button (and I think that is more reliable if held
when power is connected -- rather than using power or reset buttons.


--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/

[Chris Green]

Dennis Lee Bieber <wlf...@ix.netcom.com> wrote:
> On Thu, 24 May 2018 07:07:48 -0700 (PDT), Stephen Bates
> <stephen....@gmail.com> declaimed the
> following:
>
> >I have recently bought a BeagleBone Black Rev C but it fails to boot from
> >the micro SD card, I have uploaded the latest image to a micro SD card
>
> What image is on the eMMC to begin with?
>

That is *exactly* the question one shouldn't have to ask!

There needs to be a reliable/easy way to install an OS onto the eMMC
*without* making any assumptions as to what was there previously.

--
Chris Green
·

[stephen bates]

Hello Dennis

The eMMC image is Debian 8.4 Jessie and that boots ok, however when I log in and type "fdisk -l" the response from the memory locations, including the microSD card, is permission denied I have attached a jpeg to illustrate this. 

This suggests either an error with the hardware or this image. 

I've tried booting by applying power with the S2 pressed and then releasing it. The power comes on but the devices does no boot up.

Not sure what else to try

Regards

Stephen

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/KZtuqDNSMUw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f88egdl40gsdiskut1pmbr3falib5gbrlb%404ax.com.
For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Fri, May 25, 2018, 6:37 AM stephen bates <stephen....@gmail.com> wrote:

Hello Dennis

The eMMC image is Debian 8.4 Jessie and that boots ok, however when I log in and type "fdisk -l" the response from the memory locations, including the microSD card, is permission denied I have attached a jpeg to illustrate this. 

This suggests either an error with the hardware or this image. 

Nope just a user misunderstanding error.

The user 'debian' is a normal user, not 'root'. If you'd like to call fdisk and get a response you need to use 'sudo' to utilize root permissions.

Regards,

[Dennis Lee Bieber]

On Fri, 25 May 2018 10:53:10 +0100, stephen bates
<stephen....@gmail.com> declaimed the
following:

>Hello Dennis
>
>The eMMC image is Debian 8.4 Jessie and that boots ok, however when I log
>in and type "fdisk -l" the response from the memory locations, including
>the microSD card, is permission denied I have attached a jpeg to illustrate
>this.

WHY a 300kB full-screen image when cut&pasting the PuTTY /text/ would
only be around 1-2kB, and would allow one to cut&paste snippets back for
testing... Or, at the least, just capture the active window, not the entire
screen. {It is summer, and my DSL is flaky -- I'm lucky to be getting over
1Mbps on a peak 1.5Mbps service}

>This suggests either an error with the hardware or this image.
>

Nothing I see wrong there... As responded to elsewhere, the "debian"
login does not have root privileges, and fdisk is a privileged utility.

-=-=-=-=-
debian@beaglebone:~$ uname -a
Linux beaglebone 4.9.78-ti-r94 #1 SMP PREEMPT Fri Jan 26 21:26:24 UTC 2018
armv7l GNU/Linux
debian@beaglebone:~$ fdisk -l
fdisk: cannot open /dev/mmcblk1: Permission denied
fdisk: cannot open /dev/mmcblk1boot1: Permission denied
fdisk: cannot open /dev/mmcblk1boot0: Permission denied
debian@beaglebone:~$ sudo fdisk -l
[sudo] password for debian:
Disk /dev/mmcblk1: 3.7 GiB, 3925868544 bytes, 7667712 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
Disklabel type: dos
Disk identifier: 0xe8c7fdfb

Device Boot Start End Sectors Size Id Type
/dev/mmcblk1p1 * 8192 7667711 7659520 3.7G 83 Linux


Disk /dev/mmcblk1boot1: 1 MiB, 1048576 bytes, 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 /dev/mmcblk1boot0: 1 MiB, 1048576 bytes, 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

debian@beaglebone:~$ #insert SD card

debian@beaglebone:~$ sudo fdisk -l
Disk /dev/mmcblk1: 3.7 GiB, 3925868544 bytes, 7667712 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
Disklabel type: dos
Disk identifier: 0xe8c7fdfb

Device Boot Start End Sectors Size Id Type
/dev/mmcblk1p1 * 8192 7667711 7659520 3.7G 83 Linux


Disk /dev/mmcblk1boot1: 1 MiB, 1048576 bytes, 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 /dev/mmcblk1boot0: 1 MiB, 1048576 bytes, 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 /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 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
Disklabel type: dos
Disk identifier: 0xca52207f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 15523839 15515648 7.4G 83 Linux
debian@beaglebone:~$
-=-=-=-=-

>I've tried booting by applying power with the S2 pressed and then releasing
>it. The power comes on but the devices does no boot up.
>

So try without pushing S2...

-=-=-=-=-
debian@beaglebone:~$ #SD card still inserted

debian@beaglebone:~$ sudo reboot
-=-=-=-=-

(after USB down/up sounds, restart session in PuTTY)

-=-=-=-=-
login as: debian
Debian GNU/Linux 8

BeagleBoard.org Debian Image 2017-03-19

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

deb...@192.168.7.2's password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun May 13 10:41:46 2018 from 192.168.2.109
debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.54-ti-r93 #1 SMP Fri Mar 17 13:08:22 UTC 2017 armv7l
GNU/Linux
debian@beaglebone:~$ sudo fdisk -l
[sudo] password for debian:

Disk /dev/mmcblk0: 7.4 GiB, 7948206080 bytes, 15523840 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
Disklabel type: dos
Disk identifier: 0xca52207f

Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 15523839 15515648 7.4G 83 Linux

Disk /dev/mmcblk1: 3.7 GiB, 3925868544 bytes, 7667712 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
Disklabel type: dos
Disk identifier: 0xe8c7fdfb

Device Boot Start End Sectors Size Id Type
/dev/mmcblk1p1 * 8192 7667711 7659520 3.7G 83 Linux
-=-=-=-=-

If you have a valid image on the SD card, Jessie should be new enough
to automatically boot from the SD card (I haven't had to hold down the
alt-boot button since Wheezy).

Your original post did not specify /which/ "latest image" you obtained,
and you state you "uploaded" it to the SD card. That could be interpreted
to mean you just copied the .img.xz file to the SD card -- that will not
work! You need to use a program that block copies the contents of the file
onto the blocks of the SD card (I believe the current Windows recommended
is etcher, though I've not had problems with Win32DiskImager (which also
supports making an image file from an SD card, etcher can on write to
cards).

-=-=-=-=-
debian@beaglebone:~$ sudo mkdir /media/emmc
debian@beaglebone:~$ sudo mount /dev/mmcblk1p1 /media/emmc
debian@beaglebone:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 10240 0 10240 0% /dev
tmpfs 99956 2924 97032 3% /run
/dev/mmcblk0p1 7570776 3178052 4033720 45% /
tmpfs 249888 4 249884 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 249888 0 249888 0% /sys/fs/cgroup
tmpfs 49980 0 49980 0% /run/user/1000
/dev/mmcblk1p1 3704040 2930100 566068 84% /media/emmc
debian@beaglebone:~$
-=-=-=-=-

(shutdown, remove SD card, press power button, restart session, reinsert SD
card)

-=-=-=-=-
debian@beaglebone:~$ sudo mkdir /media/SD
[sudo] password for debian:
debian@beaglebone:~$ sudo mount /dev/mmcblk0p1 /media/SD
debian@beaglebone:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 219512 0 219512 0% /dev
tmpfs 49576 5180 44396 11% /run
/dev/mmcblk1p1 3704040 2930308 565860 84% /
tmpfs 247876 0 247876 0% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 247876 0 247876 0% /sys/fs/cgroup
tmpfs 49572 4 49568 1% /run/user/1000
/dev/mmcblk0p1 7570776 3178036 4033736 45% /media/SD
debian@beaglebone:~$ ls /media/SD
bbb-uEnv.txt boot etc ID.txt lost+found mnt opt root sbin
sys usr
bin dev home lib media nfs-uEnv.txt proc run srv
tmp var
debian@beaglebone:~$
-=-=-=-=-

Note that the SD card has a Jessie image on it, while I've flashed the
eMMC with a Stretch image. I tend to keep one SD card with a "last
generation" image, with a second SD card holding the current generation
(it's the one used for flashing, after booting the BBB off the new eMMC
image, I remount the flasher image and "de-flasher" it, followed by
expanding the file system to use the entire card).