BBB - Booting to Ubuntu (Question about user/boot button)

I was trying to follow this guide: http://www.armhf.com/index.php/boards/beaglebone-black/

and I seem to be having some problems booting into the board. Angstrom works, of course, but the user/boot button (little raised white/black square?) seems to not budge at all. It’s on the opposite end of the full-sized USB. Did I read the schematics wrong? Do I need to hold down the button at all anymore?

Did you look at the pictures?

http://circuitco.com/support/index.php?title=BeagleBoneBlack

Gerald

These buttons are very stiff, i nearly felt like i was going to press the board in half first time I used them.

Right on the money. The buttons were alarmingly stiff during the first attempt(s). I managed to press the button and the screen looks like it's working to a degree. I have some gabled or otherwise squashed text up the upper portion of the screen. Instead of saying 1080p, it's a weird 500something format on my big screen. I've been searching through some of the posts, but haven't had a chance to look up all of them. Good news is the button works.

It is normal for the buttons to be a little stiff when first use. They will loosen up with use.

Gerald


BeagleBone uboot followed http://eewiki.net/display/linuxonarm/BeagleBone



U-Boot# boot
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
304 bytes read in 7 ms (42 KiB/s)
Importing environment from mmc …
gpio: pin 55 (gpio 55) value is 1
Card did not respond to voltage select!
mmc1(part 0) is current device
Card did not respond to voltage select |

Well "1" is the eMMC... on the beaglebone black... so yeah...

Does this make sense?

Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
302 bytes read in 4 ms (73.2 KiB/s)
Importing environment from mmc ...
gpio: pin 55 (gpio 55) value is 1

uenvcmd was not defined in uEnv.txt ...
trying eMMC (BeagleBone Black) ...

mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
mmc1(part 0) is current device
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!

patch:
https://github.com/eewiki/u-boot-patches/commit/3165b9c404d996f23ce9daff97a8991e7a9663fd

and added this line to the wiki page:
[As v3.2.x/v3.8.x are too vastly different kernels (board file vs
device tree) you need to uncomment one of the "uenvcmd" variables
shown in the uEnv.txt boot script, otherwise it will not boot the
kernel image.]

Your Welcome..

My system now has a blinking light and appears to be running OK except


I have a Serial login issue. I never get a login prompt


I followed http://eewiki.net/display/linuxonarm/BeagleBone


I have a BB white and I built the 3.8 kernel. Googling around I found this link from this group.
His output of where he is loosing the console is the identical to mine


https://groups.google.com/forum/?fromgroups#!search/Beagle$20Bone$20No$20login$20prompt/beagleboard/7yeTytu9AfA/FUMDruCPTtYJ





Is this fix suggested above correct?


— On Sat, 6/1/13, Robert Nelson robertcnelson@gmail.com wrote:


> Well “1” is the eMMC… on the beaglebone black… so yeah…
>
> Does this make sense?
>
> patch:
> https://github.com/eewiki/u-boot-patches/commit/3165b9c404d996f23ce9daff97a8991e7a9663fd
>
> and added this line to the wiki page:
> [As v3.2.x/v3.8.x are too vastly different kernels (board file vs
> device tree) you need to uncomment one of the “uenvcmd” variables
> shown in the uEnv.txt boot script, otherwise it will not boot the
> kernel image.]
>
> Your Welcome…
>
> –




|

What 'fix'? it's the exact same setting for the serial port "ttyO0"
that's already on the wiki page..

Regards,

Mark.... "Yet Again" I have no idea where you 'wandered' in the wiki
directions.. So here you go, figure it out, as I really won't be back
to debug anything till early next week..

Line by Line on my console:
http://pastebin.com/pPApkeUB

BeagleBone (white) perfectly happy booting with 3.8 (although it
really doesn't like that early proto dvi adapter..)
http://pastebin.com/T5cqn9Jn

Regards,


Robert
Looking at your boot log the serial login part is the only part missing in my output



I am asking what could cause this? It would seem to me the serial.conf is could be the only thing wrong I can do retry it again.


My question IS:


Are there any other things in this very short and well written wiki that if done incorrectly that could cause no serial login.???






Have a safe trip




1. * Starting web server apache2 e[80G apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName


I DONT SEE BELOW
1. e[74G[ OK ]

1.
1. Ubuntu 13.04 arm ttyO0

1.
1. arm login: ubuntu


— On Sun, 6/2/13, Robert Nelson robertcnelson@gmail.com wrote:


> From: Robert Nelson robertcnelson@gmail.com
> Subject: Re: [beagleboard] http://eewiki.net/display/linuxonarm/BeagleBone Serial login issue
> To: beagleboard@googlegroups.com
> Date: Sunday, June 2, 2013, 6:09 PM
>
> On Sun, Jun 2, 2013 at 5:27 PM, Robert Nelson robertcnelson@gmail.com wrote:
> > On Sun, Jun 2, 2013 at 5:23 PM, Mark Lazarewicz lazarman@yahoo.com wrote:
> >>
> >> My system now has a blinking light and appears to be running OK except
> >>
> >> I have a Serial login issue. I never get a login prompt
> >>
> >> I followed http://eewiki.net/display/linuxonarm/BeagleBone
> >>
> >> I have a BB white and I built the 3.8 kernel. Googling around I found this
> >> link from this group.
> >> His output of where he is loosing the console is the identical to mine
> >>
> >>
> >> https://groups.google.com/forum/?fromgroups#!search/Beagle$20Bone$20No$20login$20prompt/beagleboard/7yeTytu9AfA/FUMDruCPTtYJ
> >>
> >>
> >> Is this fix suggested above correct?
> >
> > What ‘fix’? it’s the exact same setting for the serial port “ttyO0”
> > that’s already on the wiki page…
>
> Mark… “Yet Again” I have no idea where you ‘wandered’ in the wiki
> directions… So here you go, figure it out, as I really won’t be back
> to debug anything till early next week…
>
> Line by Line on my console:
> http://pastebin.com/pPApkeUB
>
> BeagleBone (white) perfectly happy booting with 3.8 (although it
> really doesn’t like that early proto dvi adapter…)
> http://pastebin.com/T5cqn9Jn




|

"if" the network cable is not plugged in (and eth0 is defined in
/etc/network/interfaces), there could be a 2 minute delay as 'upstart'
is trying to get an IP 'before' giving login access. But after those
2 minutes, the login prompt will appear..

Regards,

Another thing to look for... are the LED's still blinking? If not,
the board probably locked up due to lack of power.. (just noticed that
today)

Regards,

Hi Robert. Thanks!
The LED are blinking similar to what they do for Angstrom . I am in the process of finding a proper ethernet cable and the instructions to try to get in/set ip address over ethernet to ensure its REALLY alive


I did somehow miss this step, Appears like this is done once correct?
Upgrade distro “device-tree-compiler” package

:~$ /usr/local/bin/dtc -v





This gave me hope that a complete retry from scrach would work for ME I just have not had the time ,
I did have time to try the missed step so my enviroment is proper below and I got an error git was blocked


I just fixed this now


Is missing that step this a possible problem that would cause my symptoms? I will try a complete from scratch tonight. can I just use ./rebuild.sh?




l__ue, 6/4/13, Robert Nelson robertcnelson@gmail.com__ wrote:




> From: Robert Nelson robertcnelson@gmail.com
> Subject: Re: [beagleboard] http://eewiki.net/display/linuxonarm/BeagleBone Serial login issue
> To: beagleboard@googlegroups.com
> Date: Tuesday, June 4, 2013, 12:08 AM
>
> On Sun, Jun 2, 2013 at 7:52 PM, Robert Nelson robertcnelson@gmail.com wrote:
> > On Sun, Jun 2, 2013 at 6:38 PM, Mark Lazarewicz lazarman@yahoo.com wrote:
> >>
> >> Robert
> >> Looking at your boot log the serial login part is the only part missing in
> >> my output
> >>
> >>
> >> I am asking what could cause this? It would seem to me the serial.conf is
> >> could be the only thing wrong I can do retry it again.
> >>
> >> My question IS:
> >>
> >> Are there any other things in this very short and well written wiki that
> >> if done incorrectly that could cause no serial login.???
> >
> > “if” the network cable is not plugged in (and eth0 is defined in
> > /etc/network/interfaces), there could be a 2 minute delay as ‘upstart’
> > is trying to get an IP ‘before’ giving login access. But after those
> > 2 minutes, the login prompt will appear…
>
> Another thing to look for… are the LED’s still blinking? If not,
> the board probably locked up due to lack of power… (just noticed that
> today)
>
> 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+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.


|

Hi Robert. Thanks!
The LED are blinking similar to what they do for Angstrom . I am in the process of finding a proper ethernet cable and the instructions to try to get in/set ip address over ethernet to ensure its REALLY alive


I did somehow miss this step, Appears like this is done once correct?
Upgrade distro “device-tree-compiler” package

:~$ /usr/local/bin/dtc -v

“/usr/local/bin/” is used to not interfere with the debian package in “/usr/bin”