[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[salahgafoor]

Hi all,

I've two beaglebone black revC boards with debian 7.9, kernel 3.8 and 
debian 9.3,kernel 4.9 respectively.

I tried to power up these two boards using VDD pins on a board having some 
another interfaces like LCD etc,

But, only first board is booting up(debian 7.9). For second board, only 
power led is glowing.

Please help me on how to debug this

On Thursday, 1 August 2013 03:18:54 UTC+5:30, duckhunt...@gmail.com wrote:
>
> Hi guys,
>
> we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
> Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
> The Beagle Bone is placed in a case and we have connected it to a DC power 
> supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
> in our power supply, the BeagleBone powers on (Power LED is on), but 
> nothing more happens (none of the other four LEDs is on). If we are now 
> removing the power supply and putting it in again, the BBB starts normally. 
> I guess the power supply is strong enough: 5A@5V.
>
> Thanks for your help in advance.
>
> Regards,
> duckhunter
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/baed1d11-f2fb-4832-83a9-f103e898f223%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Christopher Stack]

That makes sense, and is definitely what you would want if you are starting
from scratch.

Just figured I'd pass along that I did 1700 power cycles last night and no
failures occurred!

Thanks again for the help,

Chris

On Thu, Oct 8, 2015 at 6:08 PM, William Hermans  wrote:

> *The only reason i clear out the mbr in the directions, is just to help*
>> * guarantee the user doesn't run into random*
>> * complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)*
>>
>> * and it helps make sure they have a good state of the microSD...*
>>
>
> I'd also like to add that occasionally, and potentially semi, but not
> completely related. Sometimes you get an error message at boot instructing
> the user to to run fsck. I've found that simply running fsck when it asks
> does away with this "boot complaint" afterwords. i.e. the Problem has been
> fixed. Usually, this only happens after one does something like re-sizing
> the partition using fdisk when the disk is live. It does work, but the
> system temporarily gets confused by the existing partition table, until
> after fsck is run.
>
> On Thu, Oct 8, 2015 at 2:41 PM, Robert Nelson 
> wrote:
>
>> On Thu, Oct 8, 2015 at 4:35 PM, Christopher Stack 
>> wrote:
>> > Don't worry I had already made a backup img so continually messing
>> things up
>> > wasn't really an issue. Just takes a few minutes to download the img
>> back to
>> > the sd.
>> >
>> > It is similar to what is on both Robert's and your blogs, so I'm not
>> sure
>> > why it got messed up when I tried recreating the partition table as
>> well.
>> >
>> > Regardless:
>> >
>> > I skipped this step: Erase partition table/labels on microSD card and it
>> > appeared the base uboot directly from Roberts guide worked properly.
>> Then I
>> > added the patch from here
>> > http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue and
>> > repeated the procedure. On power up while holding 'a' on the keyboard
>> the
>> > boot process continued as desired. So knock on wood I think I got the
>> > bootloader replaced and the new patch worked.
>> >
>> > Thank you both for your help and Miki for the patch!
>> >
>> > Before I'm content is there any issue from not cleaning out the MBR?
>> Like if
>> > the img after the last patch is a different size then Robert's img file?
>> >
>> > Intending to run reboot tests overnight to make sure the patch clears
>> up the
>> > issue. Although if the "random" noise on the rx line spells out stop I'm
>> > going to be a little spooked.
>>
>> The only reason i clear out the mbr in the directions, is just to help
>> guarantee the user doesn't run into random
>> complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)
>>
>> and it helps make sure they have a good state of the microSD...
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://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/d/optout.
>>
>
> --
> 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/aXv6An1xfqI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Christopher Stack]

Don't worry I had already made a backup img so continually messing things
up wasn't really an issue. Just takes a few minutes to download the img
back to the sd.

It is similar to what is on both Robert's and your blogs, so I'm not sure
why it got messed up when I tried recreating the partition table as well.

Regardless:

I skipped this step: Erase partition table/labels on microSD card and it
appeared the base uboot directly from Roberts guide worked properly. Then I
added the patch from here
http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue and
repeated the procedure. On power up while holding 'a' on the keyboard the
boot process continued as desired. So knock on wood I think I got the
bootloader replaced and the new patch worked.

Thank you both for your help and Miki for the patch!

Before I'm content is there any issue from not cleaning out the MBR? Like
if the img after the last patch is a different size then Robert's img file?

Intending to run reboot tests overnight to make sure the patch clears up
the issue. Although if the "random" noise on the rx line spells out stop
I'm going to be a little spooked.

Thanks,

Chris

On Thu, Oct 8, 2015 at 5:30 PM, William Hermans  wrote:

>
>> *Read everything below before half fast attempting such procedure *
>>
>>
>>
>> *If I understand what you're asking here, yes it is possible. I've
>> experimented with this personally. I talk about what I've done here in a
>> blog post.
>> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/
>> *
>>
>>
>>
>>
>> *So here is the idea. First you would want to backup the MBR liek this: $
>> sudo dd if=/dev/sdb of=/home/william/mbr-sdb.bak bs=1M count=1*
>>
> *Second You write the wanted MLO / uboot.img file into the first 512k of
> the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked
> to already ?*
>
>
>
> Before attempting the second step here. You would need to use tar to
> backup the rootfs as well. Because in effect you do have to wipe out the
> partition table. but it can be restored.
>
> *That *should* leave the partition table intact. But in case it fails, you
>> can put the whole partition table, plus original MLO, and uboot.image back
>> on the sdcard like so.*
>>
>> *$ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1*
>>
>>
>
> **OR**
> *It would probably be safer / easier to just dd the whole block device
> into an image file stored in a safe place*
>
>
> On Thu, Oct 8, 2015 at 2:20 PM, William Hermans  wrote:
>
>> Sorry not finished and accidentally hit "send". But if you need more
>> information on the steps. I can test, and duplicate exact step in order for
>> you to do the same - In a safe way.
>>
>> On Thu, Oct 8, 2015 at 2:19 PM, William Hermans 
>> wrote:
>>
>>> *Sorry that this is probably a dumb question, but is it possible to not
 blow*
 * away the partition table since I just want to swap the MLO and
 u-boot.img?*
>>>
>>>
>>> *Read everything below before half fast attempting such procedure*
>>>
>>> If I understand what you're asking here, yes it is possible. I've
>>> experimented with this personally. I talk about what I've done here in a
>>> blog post.
>>> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/
>>>
>>> So here is the idea.
>>>
>>> First you would want to backup the MBR liek this: $ sudo dd if=/dev/sdb
>>> of=/home/william/mbr-sdb.bak bs=1M count=1
>>>
>>> Second You write the wanted MLO / uboot.img file into the first 512k of
>>> the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked
>>> to already ?
>>>
>>> That *should* leave the partition table intact. But in case it fails,
>>> you can put the whole partition table, plus original MLO, and uboot.image
>>> back on the sdcard like so.
>>>
>>> $ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1
>>>
>>> *OR*
>>>
>>> It would probably be safer / easier to just dd the whole block device
>>> into an image file stored in a safe place.
>>>
>>> Actually, the whole process is very similar to the exact steps I've laid
> out in my blog post. Except that instead of resizing the partition smaller.
> You create the partition size however large you want it, and then untar the
> rootfs backup to that.
>
> The whole process is pretty complex, so if you have any questions or
> doubts. Ask prior to attempting such a procedure. As there are  ways to at
> minimum get back to where you started if things go wrong. Mainly, start off
> with "dd-ing" the whole top level block device.
>
> --
> 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
> 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

>
> *Sorry that this is probably a dumb question, but is it possible to not
> blow*
> * away the partition table since I just want to swap the MLO and
> u-boot.img?*


*Read everything below before half fast attempting such procedure*

If I understand what you're asking here, yes it is possible. I've
experimented with this personally. I talk about what I've done here in a
blog post.
http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/

So here is the idea.

First you would want to backup the MBR liek this: $ sudo dd if=/dev/sdb of=/
home/william/mbr-sdb.bak bs=1M count=1

Second You write the wanted MLO / uboot.img file into the first 512k of the
MBR. As demonstrated on Roberts eewiki guide - Which I think you linked to
already ?

That *should* leave the partition table intact. But in case it fails, you
can put the whole partition table, plus original MLO, and uboot.image back
on the sdcard like so.

$ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1

*OR*

It would probably be safer / easier to just dd the whole block device into
an image file stored in a safe place.

On Thu, Oct 8, 2015 at 1:57 PM, Robert Nelson 
wrote:

> On Thu, Oct 8, 2015 at 3:37 PM, Christopher Stack 
> wrote:
> > Sorry that this is probably a dumb question, but is it possible to not
> blow
> > away the partition table since I just want to swap the MLO and
> u-boot.img?
>
> Using dd, just re-write them to the microSD...  The partition table is
> safe at another location..
>
> >
> > I'm just running the standard image on a Beagle Bone Black that does not
> > have an eMMC or hdmi chip. I assumed it was busy because I was trying to
> > reprogram the disk while on an OS that was using the disk?
> >
> > This was the error:
> >
> >
> >
> >  Checking that no-one is using this disk right now ...
> > BLKRRPART: Device or resource busy
> >
> >
> >
> >
> >
> >
> > After adding the force option it said:
> >
> >
> >
> >
> > Checking that no-one is using this disk right now ...
> > BLKRRPART: Device or resource busy
> >
> > This disk is currently in use - repartitioning is probably a bad idea.
> > Umount all file systems, and swapoff all swap partitions on this disk.
> > Use the --no-reread flag to suppress this check.
> >
> > Disk /dev/mmcblk0: 121008 cylinders, 4 heads, 16 sectors/track
> >
> > sfdisk: ERROR: sector 3069576189 does not have an msdos signature
> >  /dev/mmcblk0: unrecognized partition table type
> > Old situation:
> > No partitions found
> > New situation:
> > Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
> >
> >Device Boot Start   EndMiB#blocks   Id  System
> > /dev/mmcblk0p1   * 1   3780   37803870720   83  Linux
> > /dev/mmcblk0p2 0  -  0  00  Empty
> > /dev/mmcblk0p3 0  -  0  00  Empty
> > /dev/mmcblk0p4 0  -  0  00  Empty
> > Successfully wrote the new partition table
>
> ah, sfdisk is just noisly, it worked ...
>
> > Re-reading the partition table ...
> > BLKRRPART: Device or resource busy
>
> later versions don't show this extra stuff...
>
> >
> >
> >
> >
> >
> > I have the  serial output after the last test, but not from the test
> where I
> > did not recreate the partition table.
> >
> >
> >
> >
> > U-Boot 2015.10-rc2-1-g5879130-dirty (Oct 09 2015 - 15:52:49 +)
> >
> >Watchdog enabled
> > I2C:   ready
> > DRAM:  512 MiB
> > Reset Source: Global external warm reset has occurred.
> > Reset Source: Power-on reset has occurred.
> > MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> > Using default environment
> >
> > Net:not set. Validating first E-fuse MAC
> > cpsw
> > Hit any key to stop autoboot:  0
> > gpio: pin 53 (gpio 53) value is 1
> > switch to partitions #0, OK
> > mmc0 is current device
> > gpio: pin 54 (gpio 54) value is 1
> > Checking for: /uEnv.txt ...
> > Checking for: /boot.scr ...
> > Checking for: /boot/boot.scr ...
> > Checking for: /boot/uEnv.txt ...
> > ** Invalid partition 2 **
> > ** Invalid partition 3 **
> > ** Invalid partition 4 **
> > ** Invalid partition 5 **
> > ** Invalid partition 6 **
> > ** Invalid partition 7 **
>
> This looks fine, based on where you stopped...  it was searching for
> the microSD card...
>
> Regards,
>
> --
> Robert Nelson
> https://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/d/optout.
>

-- 
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 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

Sorry not finished and accidentally hit "send". But if you need more
information on the steps. I can test, and duplicate exact step in order for
you to do the same - In a safe way.

On Thu, Oct 8, 2015 at 2:19 PM, William Hermans  wrote:

> *Sorry that this is probably a dumb question, but is it possible to not
>> blow*
>> * away the partition table since I just want to swap the MLO and
>> u-boot.img?*
>
>
> *Read everything below before half fast attempting such procedure*
>
> If I understand what you're asking here, yes it is possible. I've
> experimented with this personally. I talk about what I've done here in a
> blog post.
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/
>
> So here is the idea.
>
> First you would want to backup the MBR liek this: $ sudo dd if=/dev/sdb of
> =/home/william/mbr-sdb.bak bs=1M count=1
>
> Second You write the wanted MLO / uboot.img file into the first 512k of
> the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked
> to already ?
>
> That *should* leave the partition table intact. But in case it fails, you
> can put the whole partition table, plus original MLO, and uboot.image back
> on the sdcard like so.
>
> $ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1
>
> *OR*
>
> It would probably be safer / easier to just dd the whole block device into
> an image file stored in a safe place.
>
> On Thu, Oct 8, 2015 at 1:57 PM, Robert Nelson 
> wrote:
>
>> On Thu, Oct 8, 2015 at 3:37 PM, Christopher Stack 
>> wrote:
>> > Sorry that this is probably a dumb question, but is it possible to not
>> blow
>> > away the partition table since I just want to swap the MLO and
>> u-boot.img?
>>
>> Using dd, just re-write them to the microSD...  The partition table is
>> safe at another location..
>>
>> >
>> > I'm just running the standard image on a Beagle Bone Black that does not
>> > have an eMMC or hdmi chip. I assumed it was busy because I was trying to
>> > reprogram the disk while on an OS that was using the disk?
>> >
>> > This was the error:
>> >
>> >
>> >
>> >  Checking that no-one is using this disk right now ...
>> > BLKRRPART: Device or resource busy
>> >
>> >
>> >
>> >
>> >
>> >
>> > After adding the force option it said:
>> >
>> >
>> >
>> >
>> > Checking that no-one is using this disk right now ...
>> > BLKRRPART: Device or resource busy
>> >
>> > This disk is currently in use - repartitioning is probably a bad idea.
>> > Umount all file systems, and swapoff all swap partitions on this disk.
>> > Use the --no-reread flag to suppress this check.
>> >
>> > Disk /dev/mmcblk0: 121008 cylinders, 4 heads, 16 sectors/track
>> >
>> > sfdisk: ERROR: sector 3069576189 does not have an msdos signature
>> >  /dev/mmcblk0: unrecognized partition table type
>> > Old situation:
>> > No partitions found
>> > New situation:
>> > Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from
>> 0
>> >
>> >Device Boot Start   EndMiB#blocks   Id  System
>> > /dev/mmcblk0p1   * 1   3780   37803870720   83  Linux
>> > /dev/mmcblk0p2 0  -  0  00  Empty
>> > /dev/mmcblk0p3 0  -  0  00  Empty
>> > /dev/mmcblk0p4 0  -  0  00  Empty
>> > Successfully wrote the new partition table
>>
>> ah, sfdisk is just noisly, it worked ...
>>
>> > Re-reading the partition table ...
>> > BLKRRPART: Device or resource busy
>>
>> later versions don't show this extra stuff...
>>
>> >
>> >
>> >
>> >
>> >
>> > I have the  serial output after the last test, but not from the test
>> where I
>> > did not recreate the partition table.
>> >
>> >
>> >
>> >
>> > U-Boot 2015.10-rc2-1-g5879130-dirty (Oct 09 2015 - 15:52:49 +)
>> >
>> >Watchdog enabled
>> > I2C:   ready
>> > DRAM:  512 MiB
>> > Reset Source: Global external warm reset has occurred.
>> > Reset Source: Power-on reset has occurred.
>> > MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> > Using default environment
>> >
>> > Net:not set. Validating first E-fuse MAC
>> > cpsw
>> > Hit any key to stop autoboot:  0
>> > gpio: pin 53 (gpio 53) value is 1
>> > switch to partitions #0, OK
>> > mmc0 is current device
>> > gpio: pin 54 (gpio 54) value is 1
>> > Checking for: /uEnv.txt ...
>> > Checking for: /boot.scr ...
>> > Checking for: /boot/boot.scr ...
>> > Checking for: /boot/uEnv.txt ...
>> > ** Invalid partition 2 **
>> > ** Invalid partition 3 **
>> > ** Invalid partition 4 **
>> > ** Invalid partition 5 **
>> > ** Invalid partition 6 **
>> > ** Invalid partition 7 **
>>
>> This looks fine, based on where you stopped...  it was searching for
>> the microSD card...
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://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.
>> 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

I've found that 2 LEDs, or any number of LEDS on, and stuck on after a boot
is a uEnv.txt configuration error. Anyway you can show us your uEnv.txt
file contents ?

Also it would be good to get the output from the serial debug port.

On Thu, Oct 8, 2015 at 1:25 PM, Robert Nelson 
wrote:

> On Thu, Oct 8, 2015 at 3:06 PM, Christopher Stack 
> wrote:
> > Let me know if I need to put this in a new thread, or if someone wants to
> > take off the group entirely.
> >
> > I followed the directions here:
> >
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
> .
> > Specifically this section: Bootloader: U-Boot and the bootloader portion
> of
> > Setup microSD card.
> >
> > After following those directions the Beagle Bone fails to boot, leaving 2
> > LEDS on and messages on UART0 saying that there is no partition table.
> >
> > I see the next step in Setup microSD card is creating the partition
> table,
> > but that doesn't seem to be working it complains that the device is
> > currently busy. I'd prefer not to blow away the operating system if
> that's
> > possible? Just to see what happened I forced the sfdisk command and it
> > seemed to create 4 partitions, only one of which had a size which seems
> > right to me. When i rebooted though I get an error that says bad device
> mmc
> > 1.
>
> busy? odd as you just blew out the partition table in the step before...
>
> I'm guessing... Virtual Machine???
>
> or an evil auto-mounter...
>
> Regards,
>
> --
> Robert Nelson
> https://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/d/optout.
>

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Thu, Oct 8, 2015 at 3:37 PM, Christopher Stack  wrote:
> Sorry that this is probably a dumb question, but is it possible to not blow
> away the partition table since I just want to swap the MLO and u-boot.img?

Using dd, just re-write them to the microSD...  The partition table is
safe at another location..

>
> I'm just running the standard image on a Beagle Bone Black that does not
> have an eMMC or hdmi chip. I assumed it was busy because I was trying to
> reprogram the disk while on an OS that was using the disk?
>
> This was the error:
>
>
>
>  Checking that no-one is using this disk right now ...
> BLKRRPART: Device or resource busy
>
>
>
>
>
>
> After adding the force option it said:
>
>
>
>
> Checking that no-one is using this disk right now ...
> BLKRRPART: Device or resource busy
>
> This disk is currently in use - repartitioning is probably a bad idea.
> Umount all file systems, and swapoff all swap partitions on this disk.
> Use the --no-reread flag to suppress this check.
>
> Disk /dev/mmcblk0: 121008 cylinders, 4 heads, 16 sectors/track
>
> sfdisk: ERROR: sector 3069576189 does not have an msdos signature
>  /dev/mmcblk0: unrecognized partition table type
> Old situation:
> No partitions found
> New situation:
> Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0
>
>Device Boot Start   EndMiB#blocks   Id  System
> /dev/mmcblk0p1   * 1   3780   37803870720   83  Linux
> /dev/mmcblk0p2 0  -  0  00  Empty
> /dev/mmcblk0p3 0  -  0  00  Empty
> /dev/mmcblk0p4 0  -  0  00  Empty
> Successfully wrote the new partition table

ah, sfdisk is just noisly, it worked ...

> Re-reading the partition table ...
> BLKRRPART: Device or resource busy

later versions don't show this extra stuff...

>
>
>
>
>
> I have the  serial output after the last test, but not from the test where I
> did not recreate the partition table.
>
>
>
>
> U-Boot 2015.10-rc2-1-g5879130-dirty (Oct 09 2015 - 15:52:49 +)
>
>Watchdog enabled
> I2C:   ready
> DRAM:  512 MiB
> Reset Source: Global external warm reset has occurred.
> Reset Source: Power-on reset has occurred.
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Net:not set. Validating first E-fuse MAC
> cpsw
> Hit any key to stop autoboot:  0
> gpio: pin 53 (gpio 53) value is 1
> switch to partitions #0, OK
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> Checking for: /uEnv.txt ...
> Checking for: /boot.scr ...
> Checking for: /boot/boot.scr ...
> Checking for: /boot/uEnv.txt ...
> ** Invalid partition 2 **
> ** Invalid partition 3 **
> ** Invalid partition 4 **
> ** Invalid partition 5 **
> ** Invalid partition 6 **
> ** Invalid partition 7 **

This looks fine, based on where you stopped...  it was searching for
the microSD card...

Regards,

-- 
Robert Nelson
https://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/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Christopher Stack]

Sorry that this is probably a dumb question, but is it possible to not blow
away the partition table since I just want to swap the MLO and u-boot.img?

I'm just running the standard image on a Beagle Bone Black that does not
have an eMMC or hdmi chip. I assumed it was busy because I was trying to
reprogram the disk while on an OS that was using the disk?

This was the error:



 Checking that no-one is using this disk right now ...
BLKRRPART: Device or resource busy






After adding the force option it said:




Checking that no-one is using this disk right now ...
BLKRRPART: Device or resource busy

This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.

Disk /dev/mmcblk0: 121008 cylinders, 4 heads, 16 sectors/track

sfdisk: ERROR: sector 3069576189 does not have an msdos signature
 /dev/mmcblk0: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   EndMiB#blocks   Id  System
/dev/mmcblk0p1   * 1   3780   37803870720   83  Linux
/dev/mmcblk0p2 0  -  0  00  Empty
/dev/mmcblk0p3 0  -  0  00  Empty
/dev/mmcblk0p4 0  -  0  00  Empty
Successfully wrote the new partition table

Re-reading the partition table ...
BLKRRPART: Device or resource busy





I have the  serial output after the last test, but not from the test where
I did not recreate the partition table.




U-Boot 2015.10-rc2-1-g5879130-dirty (Oct 09 2015 - 15:52:49 +)

   Watchdog enabled
I2C:   ready
DRAM:  512 MiB
Reset Source: Global external warm reset has occurred.
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net:not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 2 **
** Invalid partition 3 **
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
Card did not respond to voltage select!
gpio: pin 54 (gpio 54) value is 1
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /uEnv.txt ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot.scr ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot/boot.scr ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Checking for: /boot/uEnv.txt ...
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **
Card did not respond to voltage select!
** Bad device mmc 1 **

FAILSAFE: U-Boot UMS (USB Mass Storage) enabled, media now available over
the usb slave port ...
Card did not respond to voltage select!
** Bad device mmc 1 **


Which uEnv.txt would you like? The only modifications I made from stock
were to disable the eMMC and hdmi.

Thanks,

Chris

On Thu, Oct 8, 2015 at 4:29 PM, William Hermans  wrote:

> I've found that 2 LEDs, or any number of LEDS on, and stuck on after a
> boot is a uEnv.txt configuration error. Anyway you can show us your
> uEnv.txt file contents ?
>
> Also it would be good to get the output from the serial debug port.
>
> On Thu, Oct 8, 2015 at 1:25 PM, Robert Nelson 
> wrote:
>
>> On Thu, Oct 8, 2015 at 3:06 PM, Christopher Stack 
>> wrote:
>> > Let me know if I need to put this in a new thread, or if someone wants
>> to
>> > take off the group entirely.
>> >
>> > I followed the directions here:
>> >
>> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
>> .
>> > Specifically this section: Bootloader: U-Boot and the bootloader
>> portion of
>> > Setup microSD card.
>> >
>> > After following those directions the Beagle Bone fails to boot, leaving
>> 2
>> > LEDS on and messages on UART0 saying that there is no partition table.
>> >
>> > I see the next step in Setup microSD card is creating the partition
>> table,
>> > but that doesn't seem to be working it complains that the device is
>> > currently busy. I'd prefer not to blow away the operating system if
>> that's
>> > possible? Just to see what 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

>
>
> *Read everything below before half fast attempting such procedure *
>
>
>
> *If I understand what you're asking here, yes it is possible. I've
> experimented with this personally. I talk about what I've done here in a
> blog post.
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/
> *
>
>
>
>
> *So here is the idea. First you would want to backup the MBR liek this: $
> sudo dd if=/dev/sdb of=/home/william/mbr-sdb.bak bs=1M count=1*
>
*Second You write the wanted MLO / uboot.img file into the first 512k of
the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked
to already ?*



Before attempting the second step here. You would need to use tar to backup
the rootfs as well. Because in effect you do have to wipe out the partition
table. but it can be restored.

*That *should* leave the partition table intact. But in case it fails, you
> can put the whole partition table, plus original MLO, and uboot.image back
> on the sdcard like so.*
>
> *$ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1*
>
>

**OR**
*It would probably be safer / easier to just dd the whole block device into
an image file stored in a safe place*


On Thu, Oct 8, 2015 at 2:20 PM, William Hermans  wrote:

> Sorry not finished and accidentally hit "send". But if you need more
> information on the steps. I can test, and duplicate exact step in order for
> you to do the same - In a safe way.
>
> On Thu, Oct 8, 2015 at 2:19 PM, William Hermans  wrote:
>
>> *Sorry that this is probably a dumb question, but is it possible to not
>>> blow*
>>> * away the partition table since I just want to swap the MLO and
>>> u-boot.img?*
>>
>>
>> *Read everything below before half fast attempting such procedure*
>>
>> If I understand what you're asking here, yes it is possible. I've
>> experimented with this personally. I talk about what I've done here in a
>> blog post.
>> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/
>>
>> So here is the idea.
>>
>> First you would want to backup the MBR liek this: $ sudo dd if=/dev/sdb
>> of=/home/william/mbr-sdb.bak bs=1M count=1
>>
>> Second You write the wanted MLO / uboot.img file into the first 512k of
>> the MBR. As demonstrated on Roberts eewiki guide - Which I think you linked
>> to already ?
>>
>> That *should* leave the partition table intact. But in case it fails, you
>> can put the whole partition table, plus original MLO, and uboot.image back
>> on the sdcard like so.
>>
>> $ sudo dd if=/home/william/mbr-sdb.bak of=/dev/sdb bs=1M count=1
>>
>> *OR*
>>
>> It would probably be safer / easier to just dd the whole block device
>> into an image file stored in a safe place.
>>
>> Actually, the whole process is very similar to the exact steps I've laid
out in my blog post. Except that instead of resizing the partition smaller.
You create the partition size however large you want it, and then untar the
rootfs backup to that.

The whole process is pretty complex, so if you have any questions or
doubts. Ask prior to attempting such a procedure. As there are  ways to at
minimum get back to where you started if things go wrong. Mainly, start off
with "dd-ing" the whole top level block device.

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

>
> *The only reason i clear out the mbr in the directions, is just to help*
> * guarantee the user doesn't run into random*
> * complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)*
>
> * and it helps make sure they have a good state of the microSD...*
>

I'd also like to add that occasionally, and potentially semi, but not
completely related. Sometimes you get an error message at boot instructing
the user to to run fsck. I've found that simply running fsck when it asks
does away with this "boot complaint" afterwords. i.e. the Problem has been
fixed. Usually, this only happens after one does something like re-sizing
the partition using fdisk when the disk is live. It does work, but the
system temporarily gets confused by the existing partition table, until
after fsck is run.

On Thu, Oct 8, 2015 at 2:41 PM, Robert Nelson 
wrote:

> On Thu, Oct 8, 2015 at 4:35 PM, Christopher Stack 
> wrote:
> > Don't worry I had already made a backup img so continually messing
> things up
> > wasn't really an issue. Just takes a few minutes to download the img
> back to
> > the sd.
> >
> > It is similar to what is on both Robert's and your blogs, so I'm not sure
> > why it got messed up when I tried recreating the partition table as well.
> >
> > Regardless:
> >
> > I skipped this step: Erase partition table/labels on microSD card and it
> > appeared the base uboot directly from Roberts guide worked properly.
> Then I
> > added the patch from here
> > http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue and
> > repeated the procedure. On power up while holding 'a' on the keyboard the
> > boot process continued as desired. So knock on wood I think I got the
> > bootloader replaced and the new patch worked.
> >
> > Thank you both for your help and Miki for the patch!
> >
> > Before I'm content is there any issue from not cleaning out the MBR?
> Like if
> > the img after the last patch is a different size then Robert's img file?
> >
> > Intending to run reboot tests overnight to make sure the patch clears up
> the
> > issue. Although if the "random" noise on the rx line spells out stop I'm
> > going to be a little spooked.
>
> The only reason i clear out the mbr in the directions, is just to help
> guarantee the user doesn't run into random
> complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)
>
> and it helps make sure they have a good state of the microSD...
>
> Regards,
>
> --
> Robert Nelson
> https://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/d/optout.
>

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Thu, Oct 8, 2015 at 3:06 PM, Christopher Stack  wrote:
> Let me know if I need to put this in a new thread, or if someone wants to
> take off the group entirely.
>
> I followed the directions here:
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
> Specifically this section: Bootloader: U-Boot and the bootloader portion of
> Setup microSD card.
>
> After following those directions the Beagle Bone fails to boot, leaving 2
> LEDS on and messages on UART0 saying that there is no partition table.
>
> I see the next step in Setup microSD card is creating the partition table,
> but that doesn't seem to be working it complains that the device is
> currently busy. I'd prefer not to blow away the operating system if that's
> possible? Just to see what happened I forced the sfdisk command and it
> seemed to create 4 partitions, only one of which had a size which seems
> right to me. When i rebooted though I get an error that says bad device mmc
> 1.

busy? odd as you just blew out the partition table in the step before...

I'm guessing... Virtual Machine???

or an evil auto-mounter...

Regards,

-- 
Robert Nelson
https://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/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Thu, Oct 8, 2015 at 4:35 PM, Christopher Stack  wrote:
> Don't worry I had already made a backup img so continually messing things up
> wasn't really an issue. Just takes a few minutes to download the img back to
> the sd.
>
> It is similar to what is on both Robert's and your blogs, so I'm not sure
> why it got messed up when I tried recreating the partition table as well.
>
> Regardless:
>
> I skipped this step: Erase partition table/labels on microSD card and it
> appeared the base uboot directly from Roberts guide worked properly. Then I
> added the patch from here
> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue and
> repeated the procedure. On power up while holding 'a' on the keyboard the
> boot process continued as desired. So knock on wood I think I got the
> bootloader replaced and the new patch worked.
>
> Thank you both for your help and Miki for the patch!
>
> Before I'm content is there any issue from not cleaning out the MBR? Like if
> the img after the last patch is a different size then Robert's img file?
>
> Intending to run reboot tests overnight to make sure the patch clears up the
> issue. Although if the "random" noise on the rx line spells out stop I'm
> going to be a little spooked.

The only reason i clear out the mbr in the directions, is just to help
guarantee the user doesn't run into random
complaints/warnings/annoyances in later "mkfs.ext4" tools. ;)

and it helps make sure they have a good state of the microSD...

Regards,

-- 
Robert Nelson
https://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/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Christopher Stack]

Let me know if I need to put this in a new thread, or if someone wants to
take off the group entirely.

I followed the directions here:
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
Specifically this section: Bootloader: U-Boot and the bootloader
portion of Setup
microSD card.

After following those directions the Beagle Bone fails to boot, leaving 2
LEDS on and messages on UART0 saying that there is no partition table.

I see the next step in Setup microSD card is creating the partition table,
but that doesn't seem to be working it complains that the device is
currently busy. I'd prefer not to blow away the operating system if that's
possible? Just to see what happened I forced the sfdisk command and it
seemed to create 4 partitions, only one of which had a size which seems
right to me. When i rebooted though I get an error that says bad device mmc
1.

Any ideas?

Thanks,

Chris

On Tue, Oct 6, 2015 at 8:34 PM, William Hermans  wrote:

> For more information you can read my blog post here:
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/
>
> It's briefly covered in the "Advanced usage of tar" section.
>
> On Tue, Oct 6, 2015 at 5:31 PM, William Hermans  wrote:
>
>> *However I can't find a FAT partition on my sd-card.. Is this something
>>> that changed when switching from Angstrom to Debian? Searching for
>>> u-boot.img and MLO and only found them in the u-boot backup folder so I
>>> assume that's not what I need to change. *
>>
>>
>> This has been in effect since around kernel 3.8.13-bone47 on Wheezy.
>> Since partition, with MLO, and u-boot.img being located in the first 1M of
>> the partition.
>>
>> On Tue, Oct 6, 2015 at 3:24 PM,  wrote:
>>
>>> I also am experiencing this issue. I'm trying to avoid a hardware
>>> modification so I was trying to follow Mikkel's post:
>>> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue.
>>> However I can't find a FAT partition on my sd-card.. Is this something that
>>> changed when switching from Angstrom to Debian? Searching for u-boot.img
>>> and MLO and only found them in the u-boot backup folder so I assume that's
>>> not what I need to change.
>>>
>>> I'm running the Debian image from 03-01-2015. Using the newer images did
>>> not increase reliability by much.
>>>
>>> Thanks,
>>>
>>> Chris
>>>
>>> On Saturday, October 3, 2015 at 6:54:51 AM UTC-4, Mikkel Kirkgaard
>>> Nielsen wrote:



 On 3. okt. 2015 00.29.26 CEST, Robert Nelson 
 wrote:
 >On Fri, Oct 2, 2015 at 5:23 PM, Brian Adams 
 wrote:
 >we are still experiencing a 4.5% boot failure rate
 >For a board that "stops" what happens when you plug in a usb-usart,
 >are you really in u-boot?
 >(u-boot prompt should echo back on the first enter)

 Characters on uart0 was clearly, without any doubt, what interrupted
 the boot when I did my testing last winter (that was the unmodified uboot);
 http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue

 I checked numerous times with a serial connection that uboot was indeed
 waiting for commands on uart0 in this condition.

 As for the cause, I still have a suspicion towards the circuitry design
 around the buffer U15 and its OE and _OE (discussed in
 http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause).
 But I guess nobody wants to waste time analyzing this issue on a stale
 design such as the BB.

 >One reason i can't lock down u-boot by default, CircuitCo's tester
 >expect to take over u-boot to program the eeprom as part of their
 >tester machines..

 And that is indeed a valid argument for keeping the feature. Changing
 stuff in factory is non-trivial.
 But still you would probably be able to identify the one character that
 their testers actually do use to stop boot and only react to that one. That
 would lower possibility by 2^8 (if all chars are still valid in current
 uboot).
 Or future CircuitCo production image uboots could be built from a
 branch/fork/patchset that stops on one char as now. This would allow the
 proper "wait for string" solution to be implemented in the default uboot.
 People doing their own builds like Brian would then actually build a uboot
 that doesn't intendedly ruin boot stability.

 It is really disheartening to know that people are still fighting this
 problem even though a solution is well-known and has been for such a long
 time.

 Mikkel
 --
 Sendt fra min Android telefon med K-9 Mail. Undskyld hvis jeg er lidt
 kortfattet.

>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[cstack89]

I also am experiencing this issue. I'm trying to avoid a hardware 
modification so I was trying to follow Mikkel's 
post: http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue. 
However I can't find a FAT partition on my sd-card.. Is this something that 
changed when switching from Angstrom to Debian? Searching for u-boot.img 
and MLO and only found them in the u-boot backup folder so I assume that's 
not what I need to change. 

I'm running the Debian image from 03-01-2015. Using the newer images did 
not increase reliability by much.

Thanks,

Chris

On Saturday, October 3, 2015 at 6:54:51 AM UTC-4, Mikkel Kirkgaard Nielsen 
wrote:
>
>
>
> On 3. okt. 2015 00.29.26 CEST, Robert Nelson  > wrote: 
> >On Fri, Oct 2, 2015 at 5:23 PM, Brian Adams  > wrote: 
> >we are still experiencing a 4.5% boot failure rate 
> >For a board that "stops" what happens when you plug in a usb-usart, 
> >are you really in u-boot? 
> >(u-boot prompt should echo back on the first enter) 
>
> Characters on uart0 was clearly, without any doubt, what interrupted the 
> boot when I did my testing last winter (that was the unmodified uboot); 
> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue 
>
> I checked numerous times with a serial connection that uboot was indeed 
> waiting for commands on uart0 in this condition. 
>
> As for the cause, I still have a suspicion towards the circuitry design 
> around the buffer U15 and its OE and _OE (discussed in 
> http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause).
>  
> But I guess nobody wants to waste time analyzing this issue on a stale 
> design such as the BB. 
>
> >One reason i can't lock down u-boot by default, CircuitCo's tester 
> >expect to take over u-boot to program the eeprom as part of their 
> >tester machines.. 
>
> And that is indeed a valid argument for keeping the feature. Changing 
> stuff in factory is non-trivial. 
> But still you would probably be able to identify the one character that 
> their testers actually do use to stop boot and only react to that one. That 
> would lower possibility by 2^8 (if all chars are still valid in current 
> uboot). 
> Or future CircuitCo production image uboots could be built from a 
> branch/fork/patchset that stops on one char as now. This would allow the 
> proper "wait for string" solution to be implemented in the default uboot. 
> People doing their own builds like Brian would then actually build a uboot 
> that doesn't intendedly ruin boot stability. 
>
> It is really disheartening to know that people are still fighting this 
> problem even though a solution is well-known and has been for such a long 
> time. 
>
> Mikkel 
> -- 
> Sendt fra min Android telefon med K-9 Mail. Undskyld hvis jeg er lidt 
> kortfattet. 
>

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

>
> *However I can't find a FAT partition on my sd-card.. Is this something
> that changed when switching from Angstrom to Debian? Searching for
> u-boot.img and MLO and only found them in the u-boot backup folder so I
> assume that's not what I need to change. *


This has been in effect since around kernel 3.8.13-bone47 on Wheezy. Since
partition, with MLO, and u-boot.img being located in the first 1M of the
partition.

On Tue, Oct 6, 2015 at 3:24 PM,  wrote:

> I also am experiencing this issue. I'm trying to avoid a hardware
> modification so I was trying to follow Mikkel's post:
> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue.
> However I can't find a FAT partition on my sd-card.. Is this something that
> changed when switching from Angstrom to Debian? Searching for u-boot.img
> and MLO and only found them in the u-boot backup folder so I assume that's
> not what I need to change.
>
> I'm running the Debian image from 03-01-2015. Using the newer images did
> not increase reliability by much.
>
> Thanks,
>
> Chris
>
> On Saturday, October 3, 2015 at 6:54:51 AM UTC-4, Mikkel Kirkgaard Nielsen
> wrote:
>>
>>
>>
>> On 3. okt. 2015 00.29.26 CEST, Robert Nelson 
>> wrote:
>> >On Fri, Oct 2, 2015 at 5:23 PM, Brian Adams  wrote:
>> >we are still experiencing a 4.5% boot failure rate
>> >For a board that "stops" what happens when you plug in a usb-usart,
>> >are you really in u-boot?
>> >(u-boot prompt should echo back on the first enter)
>>
>> Characters on uart0 was clearly, without any doubt, what interrupted the
>> boot when I did my testing last winter (that was the unmodified uboot);
>> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue
>>
>> I checked numerous times with a serial connection that uboot was indeed
>> waiting for commands on uart0 in this condition.
>>
>> As for the cause, I still have a suspicion towards the circuitry design
>> around the buffer U15 and its OE and _OE (discussed in
>> http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause).
>> But I guess nobody wants to waste time analyzing this issue on a stale
>> design such as the BB.
>>
>> >One reason i can't lock down u-boot by default, CircuitCo's tester
>> >expect to take over u-boot to program the eeprom as part of their
>> >tester machines..
>>
>> And that is indeed a valid argument for keeping the feature. Changing
>> stuff in factory is non-trivial.
>> But still you would probably be able to identify the one character that
>> their testers actually do use to stop boot and only react to that one. That
>> would lower possibility by 2^8 (if all chars are still valid in current
>> uboot).
>> Or future CircuitCo production image uboots could be built from a
>> branch/fork/patchset that stops on one char as now. This would allow the
>> proper "wait for string" solution to be implemented in the default uboot.
>> People doing their own builds like Brian would then actually build a uboot
>> that doesn't intendedly ruin boot stability.
>>
>> It is really disheartening to know that people are still fighting this
>> problem even though a solution is well-known and has been for such a long
>> time.
>>
>> Mikkel
>> --
>> Sendt fra min Android telefon med K-9 Mail. Undskyld hvis jeg er lidt
>> kortfattet.
>>
> --
> 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.
>

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

For more information you can read my blog post here:
http://www.embeddedhobbyist.com/2015/09/beaglebone-black-working-with-debianlinux-images/

It's briefly covered in the "Advanced usage of tar" section.

On Tue, Oct 6, 2015 at 5:31 PM, William Hermans  wrote:

> *However I can't find a FAT partition on my sd-card.. Is this something
>> that changed when switching from Angstrom to Debian? Searching for
>> u-boot.img and MLO and only found them in the u-boot backup folder so I
>> assume that's not what I need to change. *
>
>
> This has been in effect since around kernel 3.8.13-bone47 on Wheezy. Since
> partition, with MLO, and u-boot.img being located in the first 1M of the
> partition.
>
> On Tue, Oct 6, 2015 at 3:24 PM,  wrote:
>
>> I also am experiencing this issue. I'm trying to avoid a hardware
>> modification so I was trying to follow Mikkel's post:
>> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue.
>> However I can't find a FAT partition on my sd-card.. Is this something that
>> changed when switching from Angstrom to Debian? Searching for u-boot.img
>> and MLO and only found them in the u-boot backup folder so I assume that's
>> not what I need to change.
>>
>> I'm running the Debian image from 03-01-2015. Using the newer images did
>> not increase reliability by much.
>>
>> Thanks,
>>
>> Chris
>>
>> On Saturday, October 3, 2015 at 6:54:51 AM UTC-4, Mikkel Kirkgaard
>> Nielsen wrote:
>>>
>>>
>>>
>>> On 3. okt. 2015 00.29.26 CEST, Robert Nelson 
>>> wrote:
>>> >On Fri, Oct 2, 2015 at 5:23 PM, Brian Adams  wrote:
>>> >we are still experiencing a 4.5% boot failure rate
>>> >For a board that "stops" what happens when you plug in a usb-usart,
>>> >are you really in u-boot?
>>> >(u-boot prompt should echo back on the first enter)
>>>
>>> Characters on uart0 was clearly, without any doubt, what interrupted the
>>> boot when I did my testing last winter (that was the unmodified uboot);
>>> http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue
>>>
>>> I checked numerous times with a serial connection that uboot was indeed
>>> waiting for commands on uart0 in this condition.
>>>
>>> As for the cause, I still have a suspicion towards the circuitry design
>>> around the buffer U15 and its OE and _OE (discussed in
>>> http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause).
>>> But I guess nobody wants to waste time analyzing this issue on a stale
>>> design such as the BB.
>>>
>>> >One reason i can't lock down u-boot by default, CircuitCo's tester
>>> >expect to take over u-boot to program the eeprom as part of their
>>> >tester machines..
>>>
>>> And that is indeed a valid argument for keeping the feature. Changing
>>> stuff in factory is non-trivial.
>>> But still you would probably be able to identify the one character that
>>> their testers actually do use to stop boot and only react to that one. That
>>> would lower possibility by 2^8 (if all chars are still valid in current
>>> uboot).
>>> Or future CircuitCo production image uboots could be built from a
>>> branch/fork/patchset that stops on one char as now. This would allow the
>>> proper "wait for string" solution to be implemented in the default uboot.
>>> People doing their own builds like Brian would then actually build a uboot
>>> that doesn't intendedly ruin boot stability.
>>>
>>> It is really disheartening to know that people are still fighting this
>>> problem even though a solution is well-known and has been for such a long
>>> time.
>>>
>>> Mikkel
>>> --
>>> Sendt fra min Android telefon med K-9 Mail. Undskyld hvis jeg er lidt
>>> kortfattet.
>>>
>> --
>> 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.
>>
>
>

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Mikkel Kirkgaard Nielsen]

On 3. okt. 2015 00.29.26 CEST, Robert Nelson  wrote:
>On Fri, Oct 2, 2015 at 5:23 PM, Brian Adams  wrote:
>we are still experiencing a 4.5% boot failure rate
>For a board that "stops" what happens when you plug in a usb-usart,
>are you really in u-boot?
>(u-boot prompt should echo back on the first enter)

Characters on uart0 was clearly, without any doubt, what interrupted the boot 
when I did my testing last winter (that was the unmodified uboot); 
http://www.mikini.dk/index.php/category/beaglebone-black/boot-issue

I checked numerous times with a serial connection that uboot was indeed waiting 
for commands on uart0 in this condition.

As for the cause, I still have a suspicion towards the circuitry design around 
the buffer U15 and its OE and _OE (discussed in 
http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause).
 But I guess nobody wants to waste time analyzing this issue on a stale design 
such as the BB. 

>One reason i can't lock down u-boot by default, CircuitCo's tester
>expect to take over u-boot to program the eeprom as part of their
>tester machines..

And that is indeed a valid argument for keeping the feature. Changing stuff in 
factory is non-trivial.
But still you would probably be able to identify the one character that their 
testers actually do use to stop boot and only react to that one. That would 
lower possibility by 2^8 (if all chars are still valid in current uboot).
Or future CircuitCo production image uboots could be built from a 
branch/fork/patchset that stops on one char as now. This would allow the proper 
"wait for string" solution to be implemented in the default uboot. People doing 
their own builds like Brian would then actually build a uboot that doesn't 
intendedly ruin boot stability.

It is really disheartening to know that people are still fighting this problem 
even though a solution is well-known and has been for such a long time. 

Mikkel
-- 
Sendt fra min Android telefon med K-9 Mail. Undskyld hvis jeg er lidt 
kortfattet.

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Brian Adams]

We are building our images using the omap-image-builder scripts.  Looks 
like everything is current (u_boot_release="v2015.10-rc3") yet we are still 
experiencing a 4.5% boot failure rate where we have a single power light 
and no other leds lit. Do I understand correctly that the uboot software 
fix that checks for any key press essentially reduces the failure rate 
because the random noise on the uart would have to be in the range of a 
real key-code to stop the boot sequence? And if that is right, that while 
reduced, there is still a range of noise that can abort the boot sequence?

On Tuesday, August 11, 2015 at 7:13:14 AM UTC-7, RobertCNelson wrote:
>
> On Mon, Aug 10, 2015 at 10:18 PM,   wrote: 
> > Hi, 
> > 
> > Robert, in place of 2015-07-17 image, I see 2015-07-28 image. In any 
> way, 
> > how it is fixed? 
>
> Just weekly build snapshots, look at the log for major changes: 
>
> https://github.com/RobertCNelson/omap-image-builder/commits/master 
>
> >I just tried to flash it to my BBB and I still can go into 
> > u-boot pressing any single key. Shouldn't it be some key sequence like 
> > "uboot"? 
>
> It's just a single key over the usart... 
>
> If it's not working, you more then likely have a version in eMMC not from 
> me 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://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/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gedas]

Here are my instructions how to solve boot issue on eMMC (see one warning 
which I get below):

All commands should be run on BBB as root or add sudo.

Checkout and patch u-boot as described 
here: 
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
Do not build yet.


```
nano configs/am335x_boneblack_defconfig
```
Add these lines to the end of the file:
```
CONFIG_AUTOBOOT_KEYED=y
CONFIG_AUTOBOOT_PROMPT=Autobooting in %d seconds, enter \stop\ to stop\n
CONFIG_AUTOBOOT_STOP_STR=stop
CONFIG_AUTOBOOT_DELAY_STR=delay
```
Then compile u-boot running these commands:
```
make ARCH=arm CROSS_COMPILE=${CC} distclean
make ARCH=arm CROSS_COMPILE=${CC} am335x_boneblack_defconfig
make ARCH=arm CROSS_COMPILE=${CC}
```
Now you should have u-boot.img and MLO files compiled.
Write them to eMMC boot calling these commands:
```
dd if=MLO of=/dev/mmcblk0 count=1 seek=1 conv=notrunc bs=128k
dd if=u-boot.img of=/dev/mmcblk0 count=2 seek=1 conv=notrunc bs=384k
```
Done. Try to restart. If you have serial connection, check if you will see 
message when BBB starts Autobooting in 1 seconds, enter stop to stop

Warning: After applying this I see warning when u-boot starts *** Warning 
- bad CRC, using default environment. By this warning description here 
(http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment) 
seems like it's not critical or even important, but still, maybe someone 
has an idea how to solve it?

Thanks.

Gedas

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Andrew Glen]

But my scripts can flick a switch:)


On 12 August 2015 at 08:34, William Hermans yyrk...@gmail.com wrote:

 Isn't that why the boot switch exists ?

 On Tue, Aug 11, 2015 at 12:13 PM, Andrew Glen andrewtaneg...@gmail.com
 wrote:

 The system checks for MLO on the eMMC before the sd card. If you have
 updated u-boot/MLO on the sd card, but the 'as shipped' files are still
 present on the eMMC, your new files will have no effect.
 To get rid of the files on the eMMC you don't need to refashion it. Just
 boot the BBB, mount the eMMC partition, and delete MLO/u-boot.
 On the next boot it will be using your updated boot loader files on the
 sd card.

 On Tuesday, 11 August 2015, Gedas fzr...@gmail.com wrote:

 Hi,

 Just to make it clear. As I see there is no way to update u-boot without
 reflashing eMMC. Am I right?

 Thanks in advance for an answer.

 Regards,
 Gediminas

 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 --
 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.


 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

 *But my scripts can flick a switch:)*


Point I was making is that I'm not sure it is wise to instruct people to
remove the first or second stage bootloader from the eMMC. This typically
leads to more problems than it solves . . .

On Tue, Aug 11, 2015 at 2:40 PM, Andrew Glen andrewtaneg...@gmail.com
wrote:

 But my scripts can flick a switch:)


 On 12 August 2015 at 08:34, William Hermans yyrk...@gmail.com wrote:

 Isn't that why the boot switch exists ?

 On Tue, Aug 11, 2015 at 12:13 PM, Andrew Glen andrewtaneg...@gmail.com
 wrote:

 The system checks for MLO on the eMMC before the sd card. If you have
 updated u-boot/MLO on the sd card, but the 'as shipped' files are still
 present on the eMMC, your new files will have no effect.
 To get rid of the files on the eMMC you don't need to refashion it. Just
 boot the BBB, mount the eMMC partition, and delete MLO/u-boot.
 On the next boot it will be using your updated boot loader files on the
 sd card.

 On Tuesday, 11 August 2015, Gedas fzr...@gmail.com wrote:

 Hi,

 Just to make it clear. As I see there is no way to update u-boot
 without reflashing eMMC. Am I right?

 Thanks in advance for an answer.

 Regards,
 Gediminas

 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 --
 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.


 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


 --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gedas]

Hi,

Just to make it clear. As I see there is no way to update u-boot without 
reflashing eMMC. Am I right?

Thanks in advance for an answer.

Regards,
Gediminas

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[gg]

Hi,

Robert, in place of 2015-07-17 image, I see 2015-07-28 image. In any way, 
how it is fixed? I just tried to flash it to my BBB and I still can go into 
u-boot pressing any single key. Shouldn't it be some key sequence like 
uboot?

Thanks,
Gediminas

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gediminas Guoba]

Yes, it's single key. Thanks
On Aug 11, 2015 17:13, Robert Nelson robertcnel...@gmail.com wrote:

 On Mon, Aug 10, 2015 at 10:18 PM,  g...@drivr.com wrote:
  Hi,
 
  Robert, in place of 2015-07-17 image, I see 2015-07-28 image. In any way,
  how it is fixed?

 Just weekly build snapshots, look at the log for major changes:

 https://github.com/RobertCNelson/omap-image-builder/commits/master

 I just tried to flash it to my BBB and I still can go into
  u-boot pressing any single key. Shouldn't it be some key sequence like
  uboot?

 It's just a single key over the usart...

 If it's not working, you more then likely have a version in eMMC not from
 me

 Regards,

 --
 Robert Nelson
 https://rcn-ee.com/

 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Mon, Aug 10, 2015 at 10:18 PM,  g...@drivr.com wrote:
 Hi,

 Robert, in place of 2015-07-17 image, I see 2015-07-28 image. In any way,
 how it is fixed?

Just weekly build snapshots, look at the log for major changes:

https://github.com/RobertCNelson/omap-image-builder/commits/master

I just tried to flash it to my BBB and I still can go into
 u-boot pressing any single key. Shouldn't it be some key sequence like
 uboot?

It's just a single key over the usart...

If it's not working, you more then likely have a version in eMMC not from me

Regards,

-- 
Robert Nelson
https://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/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Tue, Aug 11, 2015 at 10:00 AM, Gediminas Guoba g...@drivr.com wrote:
 Yes, it's single key. Thanks

Oh, i should mention, we can't change this from a single key, as
CircuitCo's testing equipment relies on this feature.

Regards,

-- 
Robert Nelson
https://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/d/optout.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Andrew Glen]

The system checks for MLO on the eMMC before the sd card. If you have
updated u-boot/MLO on the sd card, but the 'as shipped' files are still
present on the eMMC, your new files will have no effect.
To get rid of the files on the eMMC you don't need to refashion it. Just
boot the BBB, mount the eMMC partition, and delete MLO/u-boot.
On the next boot it will be using your updated boot loader files on the sd
card.

On Tuesday, 11 August 2015, Gedas fzr...@gmail.com wrote:

 Hi,

 Just to make it clear. As I see there is no way to update u-boot without
 reflashing eMMC. Am I right?

 Thanks in advance for an answer.

 Regards,
 Gediminas

 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com
 javascript:_e(%7B%7D,'cvml','beagleboard%2bunsubscr...@googlegroups.com');
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[William Hermans]

Isn't that why the boot switch exists ?

On Tue, Aug 11, 2015 at 12:13 PM, Andrew Glen andrewtaneg...@gmail.com
wrote:

 The system checks for MLO on the eMMC before the sd card. If you have
 updated u-boot/MLO on the sd card, but the 'as shipped' files are still
 present on the eMMC, your new files will have no effect.
 To get rid of the files on the eMMC you don't need to refashion it. Just
 boot the BBB, mount the eMMC partition, and delete MLO/u-boot.
 On the next boot it will be using your updated boot loader files on the sd
 card.

 On Tuesday, 11 August 2015, Gedas fzr...@gmail.com wrote:

 Hi,

 Just to make it clear. As I see there is no way to update u-boot without
 reflashing eMMC. Am I right?

 Thanks in advance for an answer.

 Regards,
 Gediminas

 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Mon, Jul 27, 2015 at 4:05 AM,  speednpo...@gmail.com wrote:
 Problem still exist on Revision C


 why BBB team do not recompile officially the uboot whit the solution ?

yawn 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-07-17_Release_Notes

Regards,

-- 
Robert Nelson
https://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/d/optout.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[speednpower]

Problem still exist on Revision C

Why the BBB team do not recompile ufficially the uboot whit the solution ?


-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[speednpower]

 Problem still exist on Revision C


why BBB team do not recompile officially the uboot whit the solution ?

 

 

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[martin . zoller]

Hi,
Just as a +1 to Andrew's findings:
I have done a simple test with two BBBs to verify the presence and fix of 
the boot issue. The BBB under test had pins 1 and 5 of its UART0 port 
connected to an FTDI converter cable, which was plugged into the second 
BBB's USB port. The system reset pin (P9_10) of the BBB under test was 
wired to a GPIO pin on the other BBB. I then ran a shell script that pulled 
the reset pin high whenever Starting kernel ... was being printed on the 
serial console, and counted the number of resets. After some cycles the 
board would enter the U-Boot console and get stuck there. In three attempts 
with an A6A board, it took 3, 64 and 37 resets respectively for the board 
to get stuck. On a rev. C board, the problem occurred after 24, 31 and 3 
resets. The U-Boot version used for these tests is fairly old (U-Boot SPL 
2013.04-rc1-14237-g90639fe-dirty (Apr 13 2013 - 13:57:11) / U-Boot 2013.04 
(Apr 23 2013 - 18:26:39))

I then copied the fixed u-boot provided by Guglielmo 
(https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg) to the board's 
eMMC. When repeating the test, I now got past 1000 cycles on both BBBs 
(rev. A6A and rev. C) without a single boot failure.

In summary, this software fix is still highly useful.
Thank you Andrew and Guglielmo for your work!

Martin


On Monday, November 3, 2014 at 10:34:02 PM UTC+1, AndrewTaneGlen wrote:

 Hi Shu,

 I think I answered this in an earlier post, cut/pasted below:

 Rather than making any hardware mods I decided to reconfigured u-boot to 
 look for a specific key sequence before entering the u-boot console. To do 
 this I firstly downloaded and rebuilt u-boot following instructions here: 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#
 BeagleBoneBlack-Bootloader:U-Boot. (Testing with the default config 
 produced the same 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding the 
 following:

 #define CONFIG_AUTOBOOT_KEYED 1 
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the 
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate 
 however. This is when I learned that the boot files on the eMMC flash are 
 still loading before jumping to the files on the sd card I am using. So 
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output of 
 uart0 to detect whether the device had successfully booted or had become 
 stuck in u-boot, and then left it cycling power. We were then able to get 
 many hundreds of consecutive successful boots - we only stopped the test 
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with 
 disabling booting from the eMMC. (we could have simply reconfigured u-boot 
 on the eMMC in the same way, but disabling it drops a few seconds off the 
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen

 On 4 November 2014 10:12, Shu Liu shu...@vensi.com javascript: wrote:

 Mikkel,

 You don't have to remove the whole U15. You can just give a 3.3V pull-up 
 to the 4th PIN on the J1 connector. Then the board will not be stuck at the 
 UBOOT anymore.

 My question is how to fix it from software perspective? In u-Boot source, 
 how can we make sure it is not stuck? 

 If anyone can answer my question, i would really appreciate it. 

 Regards,
 Shu

 On Friday, October 31, 2014 12:19:11 PM UTC-5, mi...@mikini.dk wrote:


 On October 16th 2014 21.26.23 UTC+2 Gerald wrote:

 Is the power LED shutoff too?
 Gerald


 Hi Gerald.

 I'm also affected by the OP's issue of periodic failing boots on BBB (I 
 got all REV Bs).

 My experience has always been with the power led lighting up and the 
 system stuck without booting. Pressing the reset switch takes the system 
 out of this locked up state, but neither boot switch or power switch has 
 any effect. 

 I am very interested in your input on the successful experiences put 
 forward by Andrew and Marcus in May, about modifying uboot to remedy noise 
 input on UART0_RXD (pin E15 of AM3358).

 I have done some tests today documenting the basic issue and some 
 followup experiments investigating this specific cause, and I would 
 appreciate if you could take a look and comment on the resulting 
 speculations. You can find the details here; http://www.mikini.dk/index.
 php/2014/10/beaglebone-black-periodic-boot-failure-
 establishing-failure-rate-and-possible-cause.

 Executive summary; removing U15 (SN74LVC2G241: UART0 powerdown 
 isolation) seems to remedy the boot issue on a CircuitCo-produced BBB in my 
 possession.

 Although my result is inconclusive, as I was careless enough to rush 
 myself into omitting a pre-modification test, verifying the failure rate of 
 the unmodified BBB.


 Thanks in advance for your 

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Chandu D]

i have the same problem, could you tell me the how to get the device back ..
thank

On Thursday, 1 August 2013 03:18:54 UTC+5:30, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Mikkel Kirkgaard Nielsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Chu.

On 2014-11-05 11:47, Mikkel Kirkgaard Nielsen wrote:
 As my modification also solves the issue, your assumption about
 your fix (a high level at J4.1/B_UART0_RX (U15.2/1A)) is not true.

Sorry, J1.4 is the correct pin.
I've now done tests with a stronger pulldown (1k in parallel with R165=
990 ohm) and a short directly to DGND/VDD_3V3B (I'll post details later,
find them at http://www.mikini.dk/index.php/category/beaglebone-black).

These tests confirm that B_UART0_RX can't be pulled down/up, to prevent
the failure to occur. But forming a stable voltage on the input using a
voltage divider (also using 0 ohm= short circuit!) does solve the
problem. That is; whether we form a stable 0.58V or a stable 3.3V on
B_UART0_RX the system will always boot.

Does anybody have definite confirmation (by scope measurements) that
U15.6 (1Y) really is flickering during early power? It would be exiting
to do some experiments showing how it is affected by the U15.3 (1A)
input. I think that is the core of this issue.

 We removed the R165 which is the pull down resistor on the 
 UART0_RX line. The UART0_RX is around 1.4V and sometimes
 floating. We also checked the device tree. The internal pull up
 of the UART0_RX is turned on.

[UART0_RX on 1.4V or floating]
 Peculiar, as it should never float.

I haven't been able to replicate that measurement. I got 3V3 on
UART0_RX (the one without B_, on the cpu side), except in early power
up. I see the voltage flickering shortly just after power is applied,
and in the same instance that kernel is loaded (USR0-USR3 leds starts
lighting up) there also some activity.

Are you sure that you actually did measure on U15.6? It isn't easy to
place the probes right on those small pads.

 We do not know why the UART0_RX is not getting 3.3V, can you 
 please check the voltage on both UART0_TX and UART0_RX when U15
 is removed?
 I'll definitely look into this tomorrow. Including taking this 
 measurement.

Here they are, I see nothing unexpected here when things are static. I
also checked the U15 supply, which seems to be ok.

* BBB measurements on terminals of removed U15

** Device Under Test:
   Modified Beaglebone Black produced by CircuitCo (PCB REV B6, serial
   007142901445, marked beaglebone+ beagle logo and
   beagleboard.org).
   Modified by removing U15 (uart0 buffer chip: SN74LVC2G241) and its
   decoupling capacitor C155.

** Equipment
*** Multimeter
Brymen Elma BM515CF MOBILE LOGGER, MFG.#: 063391676.

*** Power Supply Unit
Huawei HW-050200E3W, output 5V 2A, USB A-connector. Danish plug.
Sourced from Huawei E589 mobile wifi.

*** Power Cable
20 cm no-name USB A male connector to USB Mini-B male connector.

** Procedure
   Apply power to BBB through USB Mini-B connector.
   Use multimeter to measure voltage levels on exposed U15 terminals
   and related supply lines to check possible supply voltage drop.
   COM probe fixed at DGND on decoupling capacitor (terminal C155.DGND
   farthest from PCB edge).

** Measurements
   C155.VDD_3V3B: 3.352V (terminal nearest to PCB edge)

   U15.1: _1OE  = 0V
   U15.2: 1A= 0V
   U15.3: 2Y= floating (flickering +-0.000,50V)
   U15.4: GND   = 0V
   U15.5: 2A = UART0_RX = 3.335V
   U15.6: 1Y = UART0_TX = 3.195V
   U15.7: 2OE   = 3.352V
   U15.8: VCC   = 3.352V

   J1.1  = DGND = 0.000,02 V
   P2.20 = GND5 = 0.000,02 V
   FB4.1 = VDD_3V3B = 3.351 V


 Regads,
Even more regads,
- -- 
Mikkel
  ,= ,-_-. =.
 ((_/)o o(\_))
  `-'(. .)`-'
  \_/

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUW47fAAoJEJ2luFWzaTSanH0H+gKv5DcQ/9NeX0vuf+9eIE3r
6mNho8sKbpWtx6uGcLRZzxEBLbU0NWnq/ePzhCzbWq7c/nEyXlYwtoa7hagJl7VT
OGaqjxxvt3Ti/iVTLp1rtiCm97Uyi0DzOKxuM8SwFTQDXTjWdmp/2ArApJqETZUD
PkpBABtfvFFWenks5rEpUYvQlI+a3SGL6nBHDmYdfD1bLExlM3ceKZ/rlCiIuHQa
8+Gj8BnoSfXO7FYk/3zUX13bBxEne2tdFgNtkOsqZK8/ut8G72jsrQwi2HmA1i1j
77CcoyTKUUeVwThcqx544pWDCvYx4FuAJz7dqIuTp3eNjHDN0JHcjNdemaL6O1M=
=LasS
-END PGP SIGNATURE-

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Shu Liu]

 Mikkil,


Thanks for you detailed answer. 

   U15.1: _1OE  = 0V 
   U15.2: 1A= 0V 
   U15.3: 2Y= floating (flickering +-0.000,50V) 
   U15.4: GND   = 0V 
   U15.5: 2A = UART0_RX = 3.335V 
   U15.6: 1Y = UART0_TX = 3.195V 
   U15.7: 2OE   = 3.352V 
   U15.8: VCC   = 3.352V 

Based on the voltages that when U15 is removed, the UART0_RX is at its 
proper voltage level (3V3) that is defined in the device tree.

The strange thing is that when U15 is there, the UART0_RX is not getting 
3V3.  _1OE is low and 2OE is high. Then the voltage on the j4.4 should be 
the same as UART0_RX. But J4.4 is not 3.3V (it was 1.4 on my board) even 
when R165 is removed, therefore, UART0_RX is not 3.3V.
 
How did you get the 0.58V on J4.4 using 1K resistor?  I do not why 0.58V 
works.

To my understanding, the default idle state should be high on both TX and 
RX lines for UART0. 

Regards,
Shu

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Mikkel Kirkgaard Nielsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi there Shu et al.

On 2014-11-03 22:12, Shu Liu wrote:
 You don't have to remove the whole U15. You can just give a 3.3V
 pull-up to the 4th PIN on the J1 connector. Then the board will not
 be stuck at the UBOOT anymore.

Really?
My first hunch after reading Andrew and Marcus' posts was also that
the RX line just needed to be tied down. But after seeing that R165
already does this, my suspicion was that it might be caused by the
SN74LVC2G241 doing some hiccups on the CPU during early power because
of OE and _OE being constantly active.

This is contradicted of your above experience, or at least also makes
the noise dependent on the 241's 1A input, which agreed does also seem
plausible. Inserting a pull up as you suggest, however does make
this and R165 a voltage divider keeping the B_UART0_RX input on ~1.4V
(at least when 3V3 and DGND has stabilized). Have you tried if the
uart0 port is functional after this modification?

Inspired by your input I've now done more tests which confirms your
experiences. Find them here;
http://www.mikini.dk/index.php/2014/11/beaglebone-black-periodic-boot-failure-fixing-b_uart0_rx-with-voltage-divider

Funny thing though, I tried increasing the pull down done by R165
(100k-45k), that didn't alleviate the problem as I kind-of expected.
Could the issue be that DGND and/or 3V3 actually isn't stable in
periods where the 241 has power and is gating 1A through to 1Y?

 My question is how to fix it from software perspective? In u-Boot 
 source, how can we make sure it is not stuck?

I've yet only skimmed the posts about the software fix, as I prefer
understanding the problem fully before settling on a fix.

I regard issues like this as a hardware flaw, and it needs to be fixed
in hardware. There might be software workarounds that can mend the
symptoms on already existing boards, but that is part 2 for me so I'm
not there, yet.

One suggestion could be that the uart driver/uboot itself flushes the
uart fifo during initialization, so that uboot only reacts on input
made during the execution of the code that checks for interactivity.
My guess is that the fifo gets filled with characters generated from
noise early during power up, and it just sits there until uboot comes
around yanking it out and interpreting it. I haven't looked at the
uboot code yet, so this is pure speculation.

Regards,
- -- 
Mikkel
  ,= ,-_-. =.
 ((_/)o o(\_))
  `-'(. .)`-'
  \_/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUWLpWAAoJEJ2luFWzaTSaMEIIALOoGbABZn5F8Vbi9FQI92P/
I8PFMNp06ybldLHDORJpWpXRnOjIm2Ix5xSFKH5loyUqatoTjeg9ASfAB8m0AeKl
JcD/c8lkzC8Z91Ygm7vZtx6SC/09VXuWSd6x6mWvzf1tI9NmCaMReGMalvrLN58X
CxfFriqliE9qouI3kOHIJp8FVAmyMFnzxOukgIpU56LV8xTOWwNIot7Q4dK9GXIg
Twv+VPzKtSfW5mqKZKP6fhHqGmifWYcV19VI5onue0/rpBrPQM6w4NoJFOcRjTVA
ijAuWiDTsgh5/949VOHJl5ansB9KqMn8DJe/2cBrCREUgBSB1B3yKxNa1kzDP2I=
=SB8K
-END PGP SIGNATURE-

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Shu Liu]

Mikkel,

You can give a 3.3v directly or use a small resistor to make the voltage on 
the 4th pin of J1 higher than 3V. That should work. We rebooted a board 
over hundreds of time by using an app on Linux. It did not fail a single 
time. 

We found this accidently by using serial cable and the board never fails to 
boot when the cable is connected. The serial cable gives the 3.3v to the 
4th pin which is the UART0_RX.

We tried to figure out what cause the problem and found a weird thing. We 
measured the UART3_RX(D16), UART3_TX(D15), UART4_RX(pin11 on header P9) and 
UART4_TX(pin13 on header P9). They are all 3.3V and they are in UART mode. 
We removed the R165 which is the pull down resistor on the UART0_RX line. 
The UART0_RX is around 1.4V and sometimes floating. We also checked the 
device tree. The internal pull up of the UART0_RX is turned on.

uart0_pins: pinmux_uart0_pins {
pinctrl-single,pins = 
0x170 (PIN_INPUT_PULLUP | MUX_MODE0) /* uart0_rxd.uart0_rxd */ 

We do not know why the UART0_RX is not getting 3.3V, can you please check 
the voltage on both UART0_TX and UART0_RX when U15 is removed?

Again, If somebody can tell me how to fix it in uboot or from software 
perspective, I would really appreciate it. 

Regards,
Shu

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Mikkel Kirkgaard Nielsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Chu,

On 2014-11-04 21:40, Shu Liu wrote:
 You can give a 3.3v directly or use a small resistor to make the 
 voltage on the 4th pin of J1 higher than 3V. That should work. We 
 rebooted a

Well, that is interesting, as it isn't consistent with my findings. I
guess you missed that I use a 82k5 ohms resistor as pull up. That's
where the 3,3V*(100k/(100k+82,5k)= 1.81V level on B_UART0_RX/J4.1 is
from (which I misstated as the 82k2's voltage drop of 1.4V in previous
post).

This is close to, but not surpassing, the high level voltage of U15
which is 2V at 3.3V VCC (datasheet p. 3), thus it will interpret my
B_UART0_RX as a low level. As my modification also solves the issue,
your assumption about your fix (a high level at J4.1/B_UART0_RX
(U15.2/1A)) is not true.

 board over hundreds of time by using an app on Linux. It did not
 fail a single time.

Nice, thought about doing something like that too while manually
plug/unplugging ;). Is that application available somewhere? It would be
nice to fully automate the test to really hammer this issue.
How do you notify the application of successful boot? Another BBB and
some IO's?

 We found this accidently by using serial cable and the board never 
 fails

No-one can plan for good stuff, it just shows up. Nice find, I remember
having read your posting about it somewhere.

 We measured the UART3_RX(D16), UART3_TX(D15), UART4_RX(pin11 on 
 header P9) and UART4_TX(pin13 on header P9). They are all 3.3V and 
 they are in UART mode.

Pins configurable for UART3 is used for MMC/MII, so I guess it is UART1
on TX;D15/P9.24 and RX;D16/P9.26 you have measured?

 We removed the R165 which is the pull down resistor on the UART0_RX
 line. The UART0_RX is around 1.4V and sometimes floating. We also
 checked the device tree. The internal pull up of the UART0_RX is
 turned on.

Peculiar, as it should never float.

 We do not know why the UART0_RX is not getting 3.3V, can you please
  check the voltage on both UART0_TX and UART0_RX when U15 is
 removed?

I'll definitely look into this tomorrow. Including taking this
measurement.

 Again, If somebody can tell me how to fix it in uboot or from 
 software perspective, I would really appreciate it.

Got hints or pointers on bulding uboot for BBB? There's a lot of
different how-tos/blogs out there.

Regads,
- -- 
Mikkel
  ,= ,-_-. =.
 ((_/)o o(\_))
  `-'(. .)`-'
  \_/

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUWY+ZAAoJEJ2luFWzaTSaM34H/1SOSvouAWoFQcngSqhuw6Z0
TjLhyZpfNmhRc4/Ykh4Wn4iW1oPL4WXYXJ35ePY5TAt69eQbuvDGhkpN2FMz/Seb
n1tbz4jz1fhXS1UYFT9ogJ4KuzE1YdQe4+GeTThEfsHCglTJGGuKSYVA4A/0uw0k
wRb7URXZYZ2JKAklPu+349UCJc+7oNBWtLiFV6CV/psuLq25wpwcmoq5qYnepOVK
BtKG+clu3IIXKlT+lzQb043KdAnCWOnKbs434robS1HUAQyuUBxrDz5+yu+2RW2B
LX2jfDXFHRjQ5dxR/WRdbk2MGJdlBkynV78vvYKi7IOWP9mSwQMm7sdGTIvIhNE=
=m/NP
-END PGP SIGNATURE-

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Shu Liu]

Mikkel,

You don't have to remove the whole U15. You can just give a 3.3V pull-up to 
the 4th PIN on the J1 connector. Then the board will not be stuck at the 
UBOOT anymore.

My question is how to fix it from software perspective? In u-Boot source, 
how can we make sure it is not stuck? 

If anyone can answer my question, i would really appreciate it. 

Regards,
Shu

On Friday, October 31, 2014 12:19:11 PM UTC-5, mi...@mikini.dk wrote:


 On October 16th 2014 21.26.23 UTC+2 Gerald wrote:

 Is the power LED shutoff too?
 Gerald


 Hi Gerald.

 I'm also affected by the OP's issue of periodic failing boots on BBB (I 
 got all REV Bs).

 My experience has always been with the power led lighting up and the 
 system stuck without booting. Pressing the reset switch takes the system 
 out of this locked up state, but neither boot switch or power switch has 
 any effect. 

 I am very interested in your input on the successful experiences put 
 forward by Andrew and Marcus in May, about modifying uboot to remedy noise 
 input on UART0_RXD (pin E15 of AM3358).

 I have done some tests today documenting the basic issue and some followup 
 experiments investigating this specific cause, and I would appreciate if 
 you could take a look and comment on the resulting speculations. You can 
 find the details here; 
 http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause
 .

 Executive summary; removing U15 (SN74LVC2G241: UART0 powerdown isolation) 
 seems to remedy the boot issue on a CircuitCo-produced BBB in my possession.

 Although my result is inconclusive, as I was careless enough to rush 
 myself into omitting a pre-modification test, verifying the failure rate of 
 the unmodified BBB.


 Thanks in advance for your help, and for my Beagle puppies ;).
 Mikkel 


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Andrew Glen]

Hi Shu,

I think I answered this in an earlier post, cut/pasted below:

Rather than making any hardware mods I decided to reconfigured u-boot to
look for a specific key sequence before entering the u-boot console. To do
this I firstly downloaded and rebuilt u-boot following instructions here:
http://eewiki.net/display/linuxonarm/BeagleBone+Black#
BeagleBoneBlack-Bootloader:U-Boot. (Testing with the default config
produced the same 'failure' rate)
I then modified '/include/config.h' in the u-boot source files, adding the
following:

#define CONFIG_AUTOBOOT_KEYED 1
#define CONFIG_AUTOBOOT_DELAY_STR uboot

This now forces a user to enter the string 'uboot' before entering the
u-boot console, otherwise the device will boot up normally.

Rebuilding with this configuration still gave the same failure rate
however. This is when I learned that the boot files on the eMMC flash are
still loading before jumping to the files on the sd card I am using. So
upon deleting the MLO file on the eMMC flash I had more luck.

We setup a programmable power supply and a script looking at the output of
uart0 to detect whether the device had successfully booted or had become
stuck in u-boot, and then left it cycling power. We were then able to get
many hundreds of consecutive successful boots - we only stopped the test
because we decided it would probably never fail.

So in the end it all came down to spurious data on uart0 - along with
disabling booting from the eMMC. (we could have simply reconfigured u-boot
on the eMMC in the same way, but disabling it drops a few seconds off the
boot time).


Thanks for all your help Gerald (and duckhunter).

Regards,
Andrew Glen

On 4 November 2014 10:12, Shu Liu shu@vensi.com wrote:

 Mikkel,

 You don't have to remove the whole U15. You can just give a 3.3V pull-up
 to the 4th PIN on the J1 connector. Then the board will not be stuck at the
 UBOOT anymore.

 My question is how to fix it from software perspective? In u-Boot source,
 how can we make sure it is not stuck?

 If anyone can answer my question, i would really appreciate it.

 Regards,
 Shu

 On Friday, October 31, 2014 12:19:11 PM UTC-5, mi...@mikini.dk wrote:


 On October 16th 2014 21.26.23 UTC+2 Gerald wrote:

 Is the power LED shutoff too?
 Gerald


 Hi Gerald.

 I'm also affected by the OP's issue of periodic failing boots on BBB (I
 got all REV Bs).

 My experience has always been with the power led lighting up and the
 system stuck without booting. Pressing the reset switch takes the system
 out of this locked up state, but neither boot switch or power switch has
 any effect.

 I am very interested in your input on the successful experiences put
 forward by Andrew and Marcus in May, about modifying uboot to remedy noise
 input on UART0_RXD (pin E15 of AM3358).

 I have done some tests today documenting the basic issue and some
 followup experiments investigating this specific cause, and I would
 appreciate if you could take a look and comment on the resulting
 speculations. You can find the details here; http://www.mikini.dk/index.
 php/2014/10/beaglebone-black-periodic-boot-failure-
 establishing-failure-rate-and-possible-cause.

 Executive summary; removing U15 (SN74LVC2G241: UART0 powerdown isolation)
 seems to remedy the boot issue on a CircuitCo-produced BBB in my possession.

 Although my result is inconclusive, as I was careless enough to rush
 myself into omitting a pre-modification test, verifying the failure rate of
 the unmodified BBB.


 Thanks in advance for your help, and for my Beagle puppies ;).
 Mikkel

  --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Shu Liu]

Andrew,

I tried that already. The file ../include/config.h is automatically 
generated when recompiling. I added the two lines which I marked red below. 
After I recompiled the uboot source again, the new generated config.h file 
replaces the old one that i modified and does not have the two lines. 

My question is that have the two lines got recompiled into the u-boot.img? 
Or am I missing something here?

/* Automatically generated - do not edit */
#define CONFIG_SERIAL11
#define CONFIG_CONS_INDEX1
#define CONFIG_NAND1
#define CONFIG_SYS_ARCH  arm
#define CONFIG_SYS_CPU   armv7
#define CONFIG_SYS_BOARD am335x
#define CONFIG_SYS_VENDOR ti
#define CONFIG_SYS_SOCam33xx
#define CONFIG_BOARDDIR board/ti/am335x
#define CONFIG_AUTOBOOT_KEYED 1
#define CONFIG_AUTOBOOT_DELAY_STR uboot
#include config_cmd_defaults.h
#include config_defaults.h
#include configs/am335x_evm.h
#include asm/config.h
#include config_fallbacks.h
#include config_uncmd_spl.h

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[miki]

On October 16th 2014 21.26.23 UTC+2 Gerald wrote:

 Is the power LED shutoff too?
 Gerald


Hi Gerald.

I'm also affected by the OP's issue of periodic failing boots on BBB (I got 
all REV Bs).

My experience has always been with the power led lighting up and the system 
stuck without booting. Pressing the reset switch takes the system out of 
this locked up state, but neither boot switch or power switch has any 
effect. 

I am very interested in your input on the successful experiences put 
forward by Andrew and Marcus in May, about modifying uboot to remedy noise 
input on UART0_RXD (pin E15 of AM3358).

I have done some tests today documenting the basic issue and some followup 
experiments investigating this specific cause, and I would appreciate if 
you could take a look and comment on the resulting speculations. You can 
find the details here; 
http://www.mikini.dk/index.php/2014/10/beaglebone-black-periodic-boot-failure-establishing-failure-rate-and-possible-cause.

Executive summary; removing U15 (SN74LVC2G241: UART0 powerdown isolation) 
seems to remedy the boot issue on a CircuitCo-produced BBB in my possession.

Although my result is inconclusive, as I was careless enough to rush myself 
into omitting a pre-modification test, verifying the failure rate of the 
unmodified BBB.


Thanks in advance for your help, and for my Beagle puppies ;).
Mikkel 

-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[DEEPAK KESWANI]

Hello everybody,

I am facing the same problem...in my BBB all led are completely shut 
downi am trying to build new os then trying to boot my bbb form my sd 
card but i am not able to do it...please help me regarding it to how to 
boot my sd card from BBB...

On Thursday, August 1, 2013 3:18:54 AM UTC+5:30, duckhunt...@gmail.com 
wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Is the power LED shutoff too?

Gerald


On Thu, Oct 16, 2014 at 2:22 PM, DEEPAK KESWANI deepakkeswan...@gmail.com
wrote:

 Hello everybody,

 I am facing the same problem...in my BBB all led are completely shut
 downi am trying to build new os then trying to boot my bbb form my sd
 card but i am not able to do it...please help me regarding it to how to
 boot my sd card from BBB...


 On Thursday, August 1, 2013 3:18:54 AM UTC+5:30, duckhunt...@gmail.com
 wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card).
 The Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging
 in our power supply, the BeagleBone powers on (Power LED is on), but
 nothing more happens (none of the other four LEDs is on). If we are now
 removing the power supply and putting it in again, the BBB starts normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[vagom15]

That's it, I was using the boot pins, the System Reference Manual says that 
I can use this pins after Reset signal, how can I do this?

Valdir

Em terça-feira, 26 de agosto de 2014 17h11min52s UTC-3, Gerald escreveu:

 Are the I/O lines the boot pins? Check the System Reference Manual for 
 more information.

 Gerald



 On Tue, Aug 26, 2014 at 3:54 AM, vag...@gmail.com javascript: wrote:

 Hi, I don't know if my issue is the same described here, my BBB never 
 boots with something connected to I/O lines, if I disconnect, boots BBB and 
 then reconnected I/Os everything works fine.

 Em segunda-feira, 28 de outubro de 2013 19h18min20s UTC-2, AndrewTaneGlen 
 escreveu:

 RESOLVED:

 Upon investigating the u-boot output we found we were facing the same 
 problem reported earlier in this thread by duckhunter: u-boot was detecting 
 spurious data on uart0 and entering the u-boot console on about 1/20 
 power-ups.

 Rather than making any hardware mods I decided to reconfigured u-boot to 
 look for a specific key sequence before entering the u-boot console. To do 
 this I firstly downloaded and rebuilt u-boot following instructions here: 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-
 Bootloader:U-Boot. (Testing with the default config produced the same 
 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding 
 the following:

 #define CONFIG_AUTOBOOT_KEYED 1 
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the 
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate 
 however. This is when I learned that the boot files on the eMMC flash are 
 still loading before jumping to the files on the sd card I am using. So 
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output 
 of uart0 to detect whether the device had successfully booted or had become 
 stuck in u-boot, and then left it cycling power. We were then able to get 
 many hundreds of consecutive successful boots - we only stopped the test 
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with 
 disabling booting from the eMMC. (we could have simply reconfigured u-boot 
 on the eMMC in the same way, but disabling it drops a few seconds off the 
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen.

 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald wrote:

 That is correct. The power button is only good for shutting it down 
 with power attached and turning it back on with power still attached.

 UBoot uses the UART0 debug port on the header, J1, on the board.

 Gerald




 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 When it fails to boot after connecting 5V, a short press of the power 
 switch has no effect. The kernel has not booted, so the button press 
 event 
 is going nowhere.

 From this failure mode, pressing and holding the power switch until 
 the power led goes off and then releasing it causes the device to boot - 
 as 
 does a short press of the reset switch. This is what has led me to the 
 conclusion that the only way to guarantee the device boots after applying 
 power is to control the reset signal with a watchdog circuit triggered 
 off 
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure 
 mode. Do you know if any of the uarts available on P9 are configured by 
 default for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do 
 it just power cycles. Pressing the button once let's the Linux kernel 
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com
  wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and 
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, 
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the 
 device failed to boot (the heartbeat led failed to come on) on the 14th 
 try, and continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user 
 interaction and with a power supply that can come on and go off 
 randomly 
 (it functions as a wifi client I connect to and control/monitor with an 
 ipad), so unfortunately I don't have the ability to manually press the 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[John Syn]

From:  vago...@gmail.com
Reply-To:  beagleboard@googlegroups.com beagleboard@googlegroups.com
Date:  Thursday, August 28, 2014 at 6:00 PM
To:  beagleboard@googlegroups.com beagleboard@googlegroups.com
Subject:  Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start.
Only Power LED is on

 That's it, I was using the boot pins, the System Reference Manual says that I
 can use this pins after Reset signal, how can I do this?
If you power your board from the 3V3B rail or use this power rail to enable
power on your own board, then you should be OK. If you power your board
before the 3V3B pin is powered, you will damage the processor and you will
most likely have a boot problem.

Regards,
John
 
 Valdir
 
 Em terça-feira, 26 de agosto de 2014 17h11min52s UTC-3, Gerald  escreveu:
 Are the I/O lines the boot pins? Check the System Reference Manual for more
 information.
 
 Gerald
 
 
 
 On Tue, Aug 26, 2014 at 3:54 AM,  vag...@gmail.com javascript:  wrote:
 Hi, I don't know if my issue is the same described here, my BBB never boots
 with something connected to I/O lines, if I disconnect, boots BBB and then
 reconnected I/Os everything works fine.
 
 Em segunda-feira, 28 de outubro de 2013 19h18min20s UTC-2, AndrewTaneGlen
 escreveu:
 RESOLVED:
 
 Upon investigating the u-boot output we found we were facing the same
 problem reported earlier in this thread by duckhunter: u-boot was detecting
 spurious data on uart0 and entering the u-boot console on about 1/20
 power-ups.
 
 Rather than making any hardware mods I decided to reconfigured u-boot to
 look for a specific key sequence before entering the u-boot console. To do
 this I firstly downloaded and rebuilt u-boot following instructions here:
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootl
 oader:U-Boot 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Boot
 loader:U-Boot . (Testing with the default config produced the same
 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding the
 following:
 
 #define CONFIG_AUTOBOOT_KEYED 1
 #define CONFIG_AUTOBOOT_DELAY_STR uboot
 
 This now forces a user to enter the string 'uboot' before entering the
 u-boot console, otherwise the device will boot up normally.
 
 Rebuilding with this configuration still gave the same failure rate
 however. This is when I learned that the boot files on the eMMC flash are
 still loading before jumping to the files on the sd card I am using. So
 upon deleting the MLO file on the eMMC flash I had more luck.
 
 We setup a programmable power supply and a script looking at the output of
 uart0 to detect whether the device had successfully booted or had become
 stuck in u-boot, and then left it cycling power. We were then able to get
 many hundreds of consecutive successful boots - we only stopped the test
 because we decided it would probably never fail.
 
 So in the end it all came down to spurious data on uart0 - along with
 disabling booting from the eMMC. (we could have simply reconfigured u-boot
 on the eMMC in the same way, but disabling it drops a few seconds off the
 boot time).
 
 
 Thanks for all your help Gerald (and duckhunter).
 
 Regards,
 Andrew Glen.
 
 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald  wrote:
 That is correct. The power button is only good for shutting it down with
 power attached and turning it back on with power still attached.
 
 UBoot uses the UART0 debug port on the header, J1, on the board.
 
 Gerald
 
 
 
 
 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com
 wrote:
 When it fails to boot after connecting 5V, a short press of the power
 switch has no effect. The kernel has not booted, so the button press
 event is going nowhere.
 
 From this failure mode, pressing and holding the power switch until the
 power led goes off and then releasing it causes the device to boot - as
 does a short press of the reset switch. This is what has led me to the
 conclusion that the only way to guarantee the device boots after applying
 power is to control the reset signal with a watchdog circuit triggered
 off a transition of the heart-beat signal (or something similar).
 
 I'm wondering if it possibly is getting to u-boot under this failure
 mode. Do you know if any of the uarts available on P9 are configured by
 default for u-boot?
 
 Cheers,
 Andrew.
 
 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald  wrote:
 You must just press the power button once. Not hold it. If you do it
 just power cycles. Pressing the button once let's the Linux kernel
 shutdown after a 60 second time out.
 
 Try it again using the power button as it was intended.
 
 Gerald
 
 
 
 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com
 wrote:
 Hi Gerald, thank you for your response.
 
 I tried the following (Using a new BBB with no SD card inserted, and
 nothing else connected to it at all):
 
 Firstly, plug in 5V barrel connector (connected to regulated 5V

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[vagom15]

Hi, I don't know if my issue is the same described here, my BBB never boots 
with something connected to I/O lines, if I disconnect, boots BBB and then 
reconnected I/Os everything works fine.

Em segunda-feira, 28 de outubro de 2013 19h18min20s UTC-2, AndrewTaneGlen 
escreveu:

 RESOLVED:

 Upon investigating the u-boot output we found we were facing the same 
 problem reported earlier in this thread by duckhunter: u-boot was detecting 
 spurious data on uart0 and entering the u-boot console on about 1/20 
 power-ups.

 Rather than making any hardware mods I decided to reconfigured u-boot to 
 look for a specific key sequence before entering the u-boot console. To do 
 this I firstly downloaded and rebuilt u-boot following instructions here: 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
  
 (Testing with the default config produced the same 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding the 
 following:

 #define CONFIG_AUTOBOOT_KEYED 1 
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the 
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate 
 however. This is when I learned that the boot files on the eMMC flash are 
 still loading before jumping to the files on the sd card I am using. So 
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output of 
 uart0 to detect whether the device had successfully booted or had become 
 stuck in u-boot, and then left it cycling power. We were then able to get 
 many hundreds of consecutive successful boots - we only stopped the test 
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with 
 disabling booting from the eMMC. (we could have simply reconfigured u-boot 
 on the eMMC in the same way, but disabling it drops a few seconds off the 
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen.

 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald wrote:

 That is correct. The power button is only good for shutting it down with 
 power attached and turning it back on with power still attached.

 UBoot uses the UART0 debug port on the header, J1, on the board.

 Gerald




 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 When it fails to boot after connecting 5V, a short press of the power 
 switch has no effect. The kernel has not booted, so the button press event 
 is going nowhere.

 From this failure mode, pressing and holding the power switch until the 
 power led goes off and then releasing it causes the device to boot - as 
 does a short press of the reset switch. This is what has led me to the 
 conclusion that the only way to guarantee the device boots after applying 
 power is to control the reset signal with a watchdog circuit triggered off 
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure 
 mode. Do you know if any of the uarts available on P9 are configured by 
 default for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do 
 it just power cycles. Pressing the button once let's the Linux kernel 
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and 
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, 
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device 
 failed to boot (the heartbeat led failed to come on) on the 14th try, and 
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction 
 and with a power supply that can come on and go off randomly (it 
 functions 
 as a wifi client I connect to and control/monitor with an ipad), so 
 unfortunately I don't have the ability to manually press the power or 
 reset 
 buttons to ensure the device always comes on when power is applied (at 
 least as I intend to use it).

 What I will do, as a kind of nuclear option, is reassign the 
 heart-beat led to a spare gpio on P9, and implement a basic watchdog 
 circuit that will pull the 'SYS_RESETn' low for a couple of hundred 
 milliseconds if it doesn't see a change in state of the heart-beat signal 
 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Are the I/O lines the boot pins? Check the System Reference Manual for more
information.

Gerald



On Tue, Aug 26, 2014 at 3:54 AM, vago...@gmail.com wrote:

 Hi, I don't know if my issue is the same described here, my BBB never
 boots with something connected to I/O lines, if I disconnect, boots BBB and
 then reconnected I/Os everything works fine.

 Em segunda-feira, 28 de outubro de 2013 19h18min20s UTC-2, AndrewTaneGlen
 escreveu:

 RESOLVED:

 Upon investigating the u-boot output we found we were facing the same
 problem reported earlier in this thread by duckhunter: u-boot was detecting
 spurious data on uart0 and entering the u-boot console on about 1/20
 power-ups.

 Rather than making any hardware mods I decided to reconfigured u-boot to
 look for a specific key sequence before entering the u-boot console. To do
 this I firstly downloaded and rebuilt u-boot following instructions here:
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-
 Bootloader:U-Boot. (Testing with the default config produced the same
 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding
 the following:

 #define CONFIG_AUTOBOOT_KEYED 1
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate
 however. This is when I learned that the boot files on the eMMC flash are
 still loading before jumping to the files on the sd card I am using. So
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output
 of uart0 to detect whether the device had successfully booted or had become
 stuck in u-boot, and then left it cycling power. We were then able to get
 many hundreds of consecutive successful boots - we only stopped the test
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with
 disabling booting from the eMMC. (we could have simply reconfigured u-boot
 on the eMMC in the same way, but disabling it drops a few seconds off the
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen.

 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald wrote:

 That is correct. The power button is only good for shutting it down with
 power attached and turning it back on with power still attached.

 UBoot uses the UART0 debug port on the header, J1, on the board.

 Gerald




 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com
 wrote:

 When it fails to boot after connecting 5V, a short press of the power
 switch has no effect. The kernel has not booted, so the button press event
 is going nowhere.

 From this failure mode, pressing and holding the power switch until the
 power led goes off and then releasing it causes the device to boot - as
 does a short press of the reset switch. This is what has led me to the
 conclusion that the only way to guarantee the device boots after applying
 power is to control the reset signal with a watchdog circuit triggered off
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure
 mode. Do you know if any of the uarts available on P9 are configured by
 default for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do
 it just power cycles. Pressing the button once let's the Linux kernel
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com
 wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V,
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device
 failed to boot (the heartbeat led failed to come on) on the 14th try, and
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user
 interaction and with a power supply that can come on and go off randomly
 (it functions as a wifi client I connect to and control/monitor with an
 ipad), so unfortunately I don't have the ability to manually press the
 power or reset buttons to ensure the device always comes on when power is
 applied (at least as I intend to use it).

 What I will do, as a kind of nuclear option, is reassign the
 heart-beat led to a spare gpio on P9, and implement a basic watchdog
 circuit that will pull the 

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[verster . cornel]

From Andrew's answer:

If I hard-ground uart0, will that solve the problem?

Thanks in advance
Cornel

On Wednesday, 31 July 2013 23:48:54 UTC+2, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[verster . cornel]

Hello Andrew
@AndrewTaneGlen

Thank you so much for this post! I'm having the exact same problem, and am 
in need of getting the golden 100% boot ratio :)
I've been using linux for about a year, but am still not trusted with the 
building of kernels and modules. I had a look at the link that you posted, 
but am still not trusted with what is going on exactly.
Will it be possible for you to give me some more details on exactly what we 
are doing by rebuilding u-boot and what the steps are in doing so?
Also, any additional steps required (deleting the MLO file from the eMMC - 
what it is and what the implications are).

Or refer me to somewhere where I can learn more on these topics.

Kind regards
Cornel Verster

On Monday, 28 October 2013 23:18:20 UTC+2, AndrewTaneGlen wrote:

 RESOLVED:

 Upon investigating the u-boot output we found we were facing the same 
 problem reported earlier in this thread by duckhunter: u-boot was detecting 
 spurious data on uart0 and entering the u-boot console on about 1/20 
 power-ups.

 Rather than making any hardware mods I decided to reconfigured u-boot to 
 look for a specific key sequence before entering the u-boot console. To do 
 this I firstly downloaded and rebuilt u-boot following instructions here: 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
  
 (Testing with the default config produced the same 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding the 
 following:

 #define CONFIG_AUTOBOOT_KEYED 1 
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the 
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate 
 however. This is when I learned that the boot files on the eMMC flash are 
 still loading before jumping to the files on the sd card I am using. So 
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output of 
 uart0 to detect whether the device had successfully booted or had become 
 stuck in u-boot, and then left it cycling power. We were then able to get 
 many hundreds of consecutive successful boots - we only stopped the test 
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with 
 disabling booting from the eMMC. (we could have simply reconfigured u-boot 
 on the eMMC in the same way, but disabling it drops a few seconds off the 
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen.

 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald wrote:

 That is correct. The power button is only good for shutting it down with 
 power attached and turning it back on with power still attached.

 UBoot uses the UART0 debug port on the header, J1, on the board.

 Gerald




 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 When it fails to boot after connecting 5V, a short press of the power 
 switch has no effect. The kernel has not booted, so the button press event 
 is going nowhere.

 From this failure mode, pressing and holding the power switch until the 
 power led goes off and then releasing it causes the device to boot - as 
 does a short press of the reset switch. This is what has led me to the 
 conclusion that the only way to guarantee the device boots after applying 
 power is to control the reset signal with a watchdog circuit triggered off 
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure 
 mode. Do you know if any of the uarts available on P9 are configured by 
 default for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do 
 it just power cycles. Pressing the button once let's the Linux kernel 
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and 
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, 
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device 
 failed to boot (the heartbeat led failed to come on) on the 14th try, and 
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction 
 and with a power supply that can come on and go off randomly (it 
 functions 
 as a wifi client I connect to 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[verster . cornel]

Hello Andrew

Thank you so much for this post! I'm having the exact same problem, and am 
in need of getting the golden 100% boot ratio :)
I've been using linux for about a year, but am still not trusted with the 
building of kernels and modules. I had a look at the link that you posted, 
but am still not trusted with what is going on exactly.
Will it be possible for you to give me some more details on exactly what we 
are doing by rebuilding u-boot and what the steps are in doing so?
Also, any additional steps required (deleting the MLO file from the eMMC - 
what it is and what the implications are).

Or refer me to somewhere where I can learn more on these topics.

Kind regards
Cornel Verster

On Monday, 28 October 2013 23:18:20 UTC+2, AndrewTaneGlen wrote:

 RESOLVED:

 Upon investigating the u-boot output we found we were facing the same 
 problem reported earlier in this thread by duckhunter: u-boot was detecting 
 spurious data on uart0 and entering the u-boot console on about 1/20 
 power-ups.

 Rather than making any hardware mods I decided to reconfigured u-boot to 
 look for a specific key sequence before entering the u-boot console. To do 
 this I firstly downloaded and rebuilt u-boot following instructions here: 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
  
 (Testing with the default config produced the same 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding the 
 following:

 #define CONFIG_AUTOBOOT_KEYED 1 
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the 
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate 
 however. This is when I learned that the boot files on the eMMC flash are 
 still loading before jumping to the files on the sd card I am using. So 
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output of 
 uart0 to detect whether the device had successfully booted or had become 
 stuck in u-boot, and then left it cycling power. We were then able to get 
 many hundreds of consecutive successful boots - we only stopped the test 
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with 
 disabling booting from the eMMC. (we could have simply reconfigured u-boot 
 on the eMMC in the same way, but disabling it drops a few seconds off the 
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen.

 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald wrote:

 That is correct. The power button is only good for shutting it down with 
 power attached and turning it back on with power still attached.

 UBoot uses the UART0 debug port on the header, J1, on the board.

 Gerald




 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 When it fails to boot after connecting 5V, a short press of the power 
 switch has no effect. The kernel has not booted, so the button press event 
 is going nowhere.

 From this failure mode, pressing and holding the power switch until the 
 power led goes off and then releasing it causes the device to boot - as 
 does a short press of the reset switch. This is what has led me to the 
 conclusion that the only way to guarantee the device boots after applying 
 power is to control the reset signal with a watchdog circuit triggered off 
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure 
 mode. Do you know if any of the uarts available on P9 are configured by 
 default for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do 
 it just power cycles. Pressing the button once let's the Linux kernel 
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and 
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, 
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device 
 failed to boot (the heartbeat led failed to come on) on the 14th try, and 
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction 
 and with a power supply that can come on and go off randomly (it 
 functions 
 as a wifi client I connect to and 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[verster . cornel]

Hello Andrew

Thank you so much for this post! I'm having the exact same problem, and am 
in need of getting the golden 100% boot ratio :)
I've been using linux for about a year, but am still not trusted with the 
building of kernels and modules. I had a look at the link that you posted, 
but am still not trusted with what is going on exactly.
Will it be possible for you to give me more detail about what exactly we 
are doing by rebuilding the u-boot and the neccessary steps?
Also, about any other steps that need to be taken (deleting the MLO file on 
the eMMC - what is it and what are the effects of deleting it).

Or refer me to somewhere where I can learn more?

Kind Regards
Cornel Verster

On Monday, 28 October 2013 23:18:20 UTC+2, AndrewTaneGlen wrote:

 RESOLVED:

 Upon investigating the u-boot output we found we were facing the same 
 problem reported earlier in this thread by duckhunter: u-boot was detecting 
 spurious data on uart0 and entering the u-boot console on about 1/20 
 power-ups.

 Rather than making any hardware mods I decided to reconfigured u-boot to 
 look for a specific key sequence before entering the u-boot console. To do 
 this I firstly downloaded and rebuilt u-boot following instructions here: 
 http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
  
 (Testing with the default config produced the same 'failure' rate)
 I then modified '/include/config.h' in the u-boot source files, adding the 
 following:

 #define CONFIG_AUTOBOOT_KEYED 1 
 #define CONFIG_AUTOBOOT_DELAY_STR uboot

 This now forces a user to enter the string 'uboot' before entering the 
 u-boot console, otherwise the device will boot up normally.

 Rebuilding with this configuration still gave the same failure rate 
 however. This is when I learned that the boot files on the eMMC flash are 
 still loading before jumping to the files on the sd card I am using. So 
 upon deleting the MLO file on the eMMC flash I had more luck.

 We setup a programmable power supply and a script looking at the output of 
 uart0 to detect whether the device had successfully booted or had become 
 stuck in u-boot, and then left it cycling power. We were then able to get 
 many hundreds of consecutive successful boots - we only stopped the test 
 because we decided it would probably never fail.

 So in the end it all came down to spurious data on uart0 - along with 
 disabling booting from the eMMC. (we could have simply reconfigured u-boot 
 on the eMMC in the same way, but disabling it drops a few seconds off the 
 boot time).


 Thanks for all your help Gerald (and duckhunter).

 Regards,
 Andrew Glen.

 On Friday, 25 October 2013 10:00:44 UTC+13, Gerald wrote:

 That is correct. The power button is only good for shutting it down with 
 power attached and turning it back on with power still attached.

 UBoot uses the UART0 debug port on the header, J1, on the board.

 Gerald




 On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 When it fails to boot after connecting 5V, a short press of the power 
 switch has no effect. The kernel has not booted, so the button press event 
 is going nowhere.

 From this failure mode, pressing and holding the power switch until the 
 power led goes off and then releasing it causes the device to boot - as 
 does a short press of the reset switch. This is what has led me to the 
 conclusion that the only way to guarantee the device boots after applying 
 power is to control the reset signal with a watchdog circuit triggered off 
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure 
 mode. Do you know if any of the uarts available on P9 are configured by 
 default for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do 
 it just power cycles. Pressing the button once let's the Linux kernel 
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.com 
 wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and 
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, 
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device 
 failed to boot (the heartbeat led failed to come on) on the 14th try, and 
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction 
 and with a power supply that can come on and go off randomly (it 
 functions 
 as a wifi client I connect to and 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[makem86]

Problem still exist on Revision B. The solution proposed by AndreTaneGlen 
by recompiling
to make it look for a sequence works like a charm. I've mended all my BBB 
from revision
A5 to B with this fix and they have since then never failed to boot.

Just to be clear, this is how I edited the u-boot source to make it work:

u-boot/include/configs/am335x_evm.h:


#define CONFIG_AUTOBOOT_PROMPT Type delay in %d seconds to get to 
U-boot-prompt\n, bootdelay
#define CONFIG_AUTOBOOT_DELAY_STR delay

u-boot/include/configs/ti_armv7_common.h:

 #define CONFIG_BOOTDELAY 3



Best regards,
Marcus

On Monday, May 5, 2014 5:06:37 PM UTC+2, Gerald wrote:

 What revision are these boards? You may want to check here:


 http://www.elinux.org/Beagleboard:BeagleBoneBlack#Board_Revisions_and_Changes

 Gerald



 On Mon, May 5, 2014 at 9:47 AM, to...@maaiveld.nl javascript: wrote:

 Hi,

 Thanks a lot to all of you guys for this effort...

 I have been stuck for weeks with 50+ beagle's that wouldn't reboot (or 
 startup) 1/10 times...
 It is driving me crazy...

 Do I really assume correctly that all that is needed to fix this is 
 replace the two files? 
 No flashing or otherwise enabling the changes?

 I'm testing with one of them now and sofar it's coming back every time, 
 but I have no idea how to really check if the changes did stick
 (they're all in a remote location)

 Thanks, Tony


 On Wednesday, April 23, 2014 5:36:11 PM UTC+2, gagu...@stratia.net wrote:

 Hello,
 Basing on the correct answer of Andrew Glen,I attach the link of the 
 compiled files to avoid the boot problem, you just need to replace the 
 original files MLO and u-boot.img on eMMC and SD card, sorry for my bad 
 english, regards:

 https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg

 El miércoles, 31 de julio de 2013 16:48:54 UTC-5, 
 duckhunt...@gmail.comescribió:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts 
 normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  -- 
 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...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Guillermo A.]

Hello,

Shared files in the dropbox works for me in beaglebone black rev the A6,
the only changes I made was in u-boot/include/config.h in lines:

#define CONFIG_AUTOBOOT_KEYED 1
#define CONFIG_AUTOBOOT_DELAY_STR uboot

Regards


On Sun, May 18, 2014 at 4:50 PM, make...@gmail.com wrote:

 Problem still exist on Revision B. The solution proposed by AndreTaneGlen
 by recompiling
 to make it look for a sequence works like a charm. I've mended all my BBB
 from revision
 A5 to B with this fix and they have since then never failed to boot.

 Just to be clear, this is how I edited the u-boot source to make it work:

 u-boot/include/configs/am335x_evm.h:


 #define CONFIG_AUTOBOOT_PROMPT Type delay in %d seconds to get to 
 U-boot-prompt\n, bootdelay
 #define CONFIG_AUTOBOOT_DELAY_STR delay

 u-boot/include/configs/ti_armv7_common.h:

  #define CONFIG_BOOTDELAY 3



 Best regards,
 Marcus

 On Monday, May 5, 2014 5:06:37 PM UTC+2, Gerald wrote:

 What revision are these boards? You may want to check here:

 http://www.elinux.org/Beagleboard:BeagleBoneBlack#
 Board_Revisions_and_Changes

 Gerald



 On Mon, May 5, 2014 at 9:47 AM, to...@maaiveld.nl wrote:

 Hi,

 Thanks a lot to all of you guys for this effort...

 I have been stuck for weeks with 50+ beagle's that wouldn't reboot (or
 startup) 1/10 times...
 It is driving me crazy...

 Do I really assume correctly that all that is needed to fix this is
 replace the two files?
 No flashing or otherwise enabling the changes?

 I'm testing with one of them now and sofar it's coming back every time,
 but I have no idea how to really check if the changes did stick
 (they're all in a remote location)

 Thanks, Tony


 On Wednesday, April 23, 2014 5:36:11 PM UTC+2, gagu...@stratia.netwrote:

 Hello,
 Basing on the correct answer of Andrew Glen,I attach the link of the
 compiled files to avoid the boot problem, you just need to replace the
 original files MLO and u-boot.img on eMMC and SD card, sorry for my bad
 english, regards:

 https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg

 El miércoles, 31 de julio de 2013 16:48:54 UTC-5, 
 duckhunt...@gmail.comescribió:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using
 Ubuntu Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD
 Card). The Beagle Bone is placed in a case and we have connected it to a 
 DC
 power supply. Sometimes (I would say every 5 to 10 times), when we are
 plugging in our power supply, the BeagleBone powers on (Power LED is on),
 but nothing more happens (none of the other four LEDs is on). If we are 
 now
 removing the power supply and putting it in again, the BBB starts 
 normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  --
 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...@googlegroups.com.

 For more options, visit https://groups.google.com/d/optout.




-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[tony]

Hi,

Thanks a lot to all of you guys for this effort...

I have been stuck for weeks with 50+ beagle's that wouldn't reboot (or 
startup) 1/10 times...
It is driving me crazy...

Do I really assume correctly that all that is needed to fix this is replace 
the two files? 
No flashing or otherwise enabling the changes?

I'm testing with one of them now and sofar it's coming back every time, but 
I have no idea how to really check if the changes did stick
(they're all in a remote location)

Thanks, Tony

On Wednesday, April 23, 2014 5:36:11 PM UTC+2, gagu...@stratia.net wrote:

 Hello,
 Basing on the correct answer of Andrew Glen,I attach the link of the 
 compiled files to avoid the boot problem, you just need to replace the 
 original files MLO and u-boot.img on eMMC and SD card, sorry for my bad 
 english, regards:

 https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg

 El miércoles, 31 de julio de 2013 16:48:54 UTC-5, 
 duckhunt...@gmail.comescribió:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter



-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

What revision are these boards? You may want to check here:

http://www.elinux.org/Beagleboard:BeagleBoneBlack#Board_Revisions_and_Changes

Gerald



On Mon, May 5, 2014 at 9:47 AM, t...@maaiveld.nl wrote:

 Hi,

 Thanks a lot to all of you guys for this effort...

 I have been stuck for weeks with 50+ beagle's that wouldn't reboot (or
 startup) 1/10 times...
 It is driving me crazy...

 Do I really assume correctly that all that is needed to fix this is
 replace the two files?
 No flashing or otherwise enabling the changes?

 I'm testing with one of them now and sofar it's coming back every time,
 but I have no idea how to really check if the changes did stick
 (they're all in a remote location)

 Thanks, Tony


 On Wednesday, April 23, 2014 5:36:11 PM UTC+2, gagu...@stratia.net wrote:

 Hello,
 Basing on the correct answer of Andrew Glen,I attach the link of the
 compiled files to avoid the boot problem, you just need to replace the
 original files MLO and u-boot.img on eMMC and SD card, sorry for my bad
 english, regards:

 https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg

 El miércoles, 31 de julio de 2013 16:48:54 UTC-5, 
 duckhunt...@gmail.comescribió:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card).
 The Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging
 in our power supply, the BeagleBone powers on (Power LED is on), but
 nothing more happens (none of the other four LEDs is on). If we are now
 removing the power supply and putting it in again, the BBB starts normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  --
 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.


-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Guillermo A.]

Hi,

I flash the eMMC of BEAGLEBONE BLACK with debian
(BBB-eMMC-flasher-debian-7.4-2014-04-14-2gb.img.xz) and then I replace 2
files MLO and u-boot.img , also in the microSD remplaze files, it is
noteworthy that the microSD is loaded ubuntu 13.04

Regards


On Mon, May 5, 2014 at 9:47 AM, t...@maaiveld.nl wrote:

 Hi,

 Thanks a lot to all of you guys for this effort...

 I have been stuck for weeks with 50+ beagle's that wouldn't reboot (or
 startup) 1/10 times...
 It is driving me crazy...

 Do I really assume correctly that all that is needed to fix this is
 replace the two files?
 No flashing or otherwise enabling the changes?

 I'm testing with one of them now and sofar it's coming back every time,
 but I have no idea how to really check if the changes did stick
 (they're all in a remote location)

 Thanks, Tony

 On Wednesday, April 23, 2014 5:36:11 PM UTC+2, gagu...@stratia.net wrote:

 Hello,
 Basing on the correct answer of Andrew Glen,I attach the link of the
 compiled files to avoid the boot problem, you just need to replace the
 original files MLO and u-boot.img on eMMC and SD card, sorry for my bad
 english, regards:

 https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg

 El miércoles, 31 de julio de 2013 16:48:54 UTC-5, 
 duckhunt...@gmail.comescribió:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card).
 The Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging
 in our power supply, the BeagleBone powers on (Power LED is on), but
 nothing more happens (none of the other four LEDs is on). If we are now
 removing the power supply and putting it in again, the BBB starts normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter



-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Andrew Glen]

I was also driven crazy by the issue initially, but after fixing it I
have seen zero issues relating to the boot sequence getting stuck.

The problem my solution refers to is noise on the uart causing u-boot
to enter its terminal. Like when you boot up a PC and press F12 (or
some other key) to enter the bios menu, u-boot looks for any input on
the uart to break out of the boot sequence and enter the 'u-boot
menu'.

The fix involves two steps. Firstly, u-boot can be recompiled to look
for a specific character sequence (instead of any input) before
entering the u-boot terminal. The files Guillermo linked to are for
this effect. This solves the problem of random noise causing the boot
sequence to stop at u-boot, unless some miracle the random noise
spells out your specific character sequence, which I for one am happy
to allow for as a possible corner case.

Secondly, the boot sequence of the processor looks at the eMMC first
for an MLO file to boot with. So by deleting the MLO file on the eMMC
you stop the processor trying to boot from there. By simply copying
the same boot files to the eMMC you'll also solve the problem, I just
thought it better to have nothing there.

Regards,
Andrew.



On 6 May 2014 02:47,  t...@maaiveld.nl wrote:
 Hi,

 Thanks a lot to all of you guys for this effort...

 I have been stuck for weeks with 50+ beagle's that wouldn't reboot (or
 startup) 1/10 times...
 It is driving me crazy...

 Do I really assume correctly that all that is needed to fix this is replace
 the two files?
 No flashing or otherwise enabling the changes?

 I'm testing with one of them now and sofar it's coming back every time, but
 I have no idea how to really check if the changes did stick
 (they're all in a remote location)

 Thanks, Tony


 On Wednesday, April 23, 2014 5:36:11 PM UTC+2, gagu...@stratia.net wrote:

 Hello,
 Basing on the correct answer of Andrew Glen,I attach the link of the
 compiled files to avoid the boot problem, you just need to replace the
 original files MLO and u-boot.img on eMMC and SD card, sorry for my bad
 english, regards:

 https://www.dropbox.com/sh/98xacnk466xfpza/uTlii1hrsg

 El miércoles, 31 de julio de 2013 16:48:54 UTC-5, duckhunt...@gmail.com
 escribió:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). The
 Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging in
 our power supply, the BeagleBone powers on (Power LED is on), but nothing
 more happens (none of the other four LEDs is on). If we are now removing the
 power supply and putting it in again, the BBB starts normally. I guess the
 power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

 --
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[rob . lemon]

Just adding to the list.

I am seeing this on hard boot 1/20 

on SHUTDOWN -r I am getting even more frequent failures, closer to 1/10. 

On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Check the support Wiki under changes. This was fixed on a later revision.

Gerald



On Thu, Apr 17, 2014 at 2:58 PM, rob.le...@gmail.com wrote:

 Just adding to the list.

 I am seeing this on hard boot 1/20

 on SHUTDOWN -r I am getting even more frequent failures, closer to 1/10.

 On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card).
 The Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging
 in our power supply, the BeagleBone powers on (Power LED is on), but
 nothing more happens (none of the other four LEDs is on). If we are now
 removing the power supply and putting it in again, the BBB starts normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[moonsurveyor]

Even SHUTDOWN -r not always work!


On Friday, January 24, 2014 12:16:48 PM UTC+1, Dave Holden wrote:

 Just another data point.  I'm running an A5C and about 1/8 times when I 
 restart with a watchdog timer it won't restart.  I have to hit the HW reset 
 button to restart it.  Even then I've noticed it sometimes doesn't restart. 
  

 Kind of nullifies the value of the watchdog, I'm bummed.  Guess I'll hook 
 my Wemo up to the power supply.  :) 


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Dave Holden]

Just another data point.  I'm running an A5C and about 1/8 times when I 
restart with a watchdog timer it won't restart.  I have to hit the HW reset 
button to restart it.  Even then I've noticed it sometimes doesn't restart. 
 

Kind of nullifies the value of the watchdog, I'm bummed.  Guess I'll hook 
my Wemo up to the power supply.  :) 

-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Andreas Tauböck]

 I hava a similar problem, just it almost everytime does not boot. I have 
1.2A and nothing connected, just uSD card inserted. Also tried to flash the 
eMMC or boot from uSD, no success. And when it boots one of a hundret tries 
and i do not diconnect the power source an just reboot in shell, it is the 
same again.

Can anybody please help me?

Am Mittwoch, 31. Juli 2013 23:48:54 UTC+2 schrieb duckhunt...@gmail.com:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Not sure what your issue is. You may need to request and RMA and get it
looked at to see if there is a HW issue. 1 time out of 100 seems to
indicate there could be an issue in the HW.

Gerald



On Wed, Jan 8, 2014 at 9:17 AM, Andreas Tauböck
andreas.taubo...@gmail.comwrote:

  I hava a similar problem, just it almost everytime does not boot. I have
 1.2A and nothing connected, just uSD card inserted. Also tried to flash the
 eMMC or boot from uSD, no success. And when it boots one of a hundret tries
 and i do not diconnect the power source an just reboot in shell, it is the
 same again.

 Can anybody please help me?

 Am Mittwoch, 31. Juli 2013 23:48:54 UTC+2 schrieb duckhunt...@gmail.com:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card).
 The Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging
 in our power supply, the BeagleBone powers on (Power LED is on), but
 nothing more happens (none of the other four LEDs is on). If we are now
 removing the power supply and putting it in again, the BBB starts normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[llindor . acticonseils]

Hi Gerald,
Last measurements were performed with an A6 revision board. We don't think the 
3V3 power up update fix this issue.
We will try the bootloader solution described by AndrewTaneGlen.

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gary Hoffman]

Thanks. That worked.

Gary

Sent from my iPhone

 On Dec 29, 2013, at 12:27 PM, Gerald Coley ger...@beagleboard.org wrote:
 
 Yes, there is hope. You cannot brick the board if you can create a bootable 
 SD card to reflash from.
 
 http://elinux.org/Beagleboard:Updating_The_Software
 
 Gerald
 
 
 
 On Sat, Dec 28, 2013 at 10:29 PM, gbhoff...@gmail.com wrote:
 My A6 version just bricked probably due to my ineptitude in creating a 
 bootable SD card. I only get a power light when powered by either brick or 
 USB. The serial debug interface just says CCC continuously.
 
 This may be a different issue than reported in this thread, but the results 
 are the same: no boot.
 
 Is there hope?
 
 Gary
 -- 
 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.
 
 -- 
 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/aXv6An1xfqI/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 beagleboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[gbhoffman]

My A6 version just bricked probably due to my ineptitude in creating a 
bootable SD card. I only get a power light when powered by either brick or 
USB. The serial debug interface just says CCC continuously.

This may be a different issue than reported in this thread, but the results 
are the same: no boot.

Is there hope?

Gary

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Yes, there is hope. You cannot brick the board if you can create a bootable
SD card to reflash from.

http://elinux.org/Beagleboard:Updating_The_Software

Gerald



On Sat, Dec 28, 2013 at 10:29 PM, gbhoff...@gmail.com wrote:

 My A6 version just bricked probably due to my ineptitude in creating a
 bootable SD card. I only get a power light when powered by either brick or
 USB. The serial debug interface just says CCC continuously.

 This may be a different issue than reported in this thread, but the
 results are the same: no boot.

 Is there hope?

 Gary

 --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[pcamargo]

Can you post step by step instruction how to compile a new uboot and replace 
the old uboot in the BBB internal storage?

We tried the steps on the link you provided and got a new uboot.img and tried 
coping it to boot partition /media/beaglebone but it corrupted the obit 
partition.

We appreciate any help you can provide.

Pedro

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

It is the big white label on the expansion header. There are pictures of it
in the System Reference Manual.

Gerald


On Sat, Dec 21, 2013 at 5:03 PM, Hitesh Kalra hiteshka...@gmail.com wrote:

 quick question: How do I find out the hw rev version of my beagle bone
 black? i can't seem to locate it visually on the board itself..


 On Friday, December 20, 2013 5:06:12 AM UTC-8, Gerald wrote:

 It is called Rev A6A.

 http://www.elinux.org/Beagleboard:BeagleBoneBlack#
 Board_Revisions_and_Changes


 Gerald



 On Fri, Dec 20, 2013 at 6:58 AM, llindor.ac...@gmail.com wrote:

 Hi Gerald,
 We encountered exactly the same issue described above with several
 BeagleBone revision A5C.
 Do you plan to fix it in the next hardware board revision? Or must we
 systematically update the bootloader with the patch from Andrew Glen?
 Many thanks
 Regards,

 Ludovic

 --
 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...@googlegroups.com.

 For more options, visit https://groups.google.com/groups/opt_out.


  --
 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.


-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[moonsurveyor]

Hi i had the same problem.

My solution is to plug the barrel connector first and then plug the adaptor 
into the wall socket.
The it boots always.




On Wednesday, July 31, 2013 11:48:54 PM UTC+2, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

It is called Rev A6A.

http://www.elinux.org/Beagleboard:BeagleBoneBlack#Board_Revisions_and_Changes


Gerald



On Fri, Dec 20, 2013 at 6:58 AM, llindor.acticonse...@gmail.com wrote:

 Hi Gerald,
 We encountered exactly the same issue described above with several
 BeagleBone revision A5C.
 Do you plan to fix it in the next hardware board revision? Or must we
 systematically update the bootloader with the patch from Andrew Glen?
 Many thanks
 Regards,

 Ludovic

 --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[llindor . acticonseils]

Thanks Gerald.

You changed C24 to a 2.2uF capacitor to improve the reset signal but we don't 
think that fix the issue.
We made some measurements around UART0 and we are convinced that u-boot detects 
spurious data during start up. Find below 2 ocilloscope screenshots (CH1 :  PIN 
3-J1   B_UART0_TX, CH2 :  PIN 4-J1 B_UART0_RX).
http://hpics.li/9d7742f
http://hpics.li/956957a
RX signal looks noisy when TX signal changes. Maybe a coupling issue?

Regards,

Ludovic

-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Could be. That issue we have not seen. The one we did see was addressed by
the capacitor change. I will look at this for a later revision, assuming we
can duplicate it. But it won't be in the next revision for sure.

Gerald



On Fri, Dec 20, 2013 at 10:26 AM, llindor.acticonse...@gmail.com wrote:

 Thanks Gerald.

 You changed C24 to a 2.2uF capacitor to improve the reset signal but we
 don't think that fix the issue.
 We made some measurements around UART0 and we are convinced that u-boot
 detects spurious data during start up. Find below 2 ocilloscope screenshots
 (CH1 :  PIN 3-J1   B_UART0_TX, CH2 :  PIN 4-J1 B_UART0_RX).
 http://hpics.li/9d7742f
 http://hpics.li/956957a
 RX signal looks noisy when TX signal changes. Maybe a coupling issue?

 Regards,

 Ludovic

 --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

Get one of the latest version and try it. There was a change made back on
Rev A6 that tied the 3V3B power up to the 3V3A. The 3V3B rail was coming up
before the 3V3A rail. That may help this issue.

Gerald


On Fri, Dec 20, 2013 at 10:32 AM, Gerald Coley ger...@beagleboard.orgwrote:

 Could be. That issue we have not seen. The one we did see was addressed by
 the capacitor change. I will look at this for a later revision, assuming we
 can duplicate it. But it won't be in the next revision for sure.

 Gerald



 On Fri, Dec 20, 2013 at 10:26 AM, llindor.acticonse...@gmail.com wrote:

 Thanks Gerald.

 You changed C24 to a 2.2uF capacitor to improve the reset signal but we
 don't think that fix the issue.
 We made some measurements around UART0 and we are convinced that u-boot
 detects spurious data during start up. Find below 2 ocilloscope screenshots
 (CH1 :  PIN 3-J1   B_UART0_TX, CH2 :  PIN 4-J1 B_UART0_RX).
 http://hpics.li/9d7742f
 http://hpics.li/956957a
 RX signal looks noisy when TX signal changes. Maybe a coupling issue?

 Regards,

 Ludovic

 --
 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.




-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

I don't see that fix as being the issue you are seeing. But, when they
are available, you can certainly give it a try.

The reset button is a warm reset button. It is not the power on reset for
the board.

I suggest that you use the power button as it is intended and use it to
power off the board and then power on the board. See what sort of results
you get in that use case.

Gerald


On Wed, Oct 23, 2013 at 9:41 PM, AndrewTaneGlen andrewtaneg...@gmail.comwrote:

 Hello All,

 I am also having this problem - with a bench top power supply set to 5V
 and 5A, plugging into the barrel connector with no SD card inserted, so
 running the default Angstrom image from flash, the device will fail to boot
 at least 1 in 20 tries. A similar failure rate was observed on my two other
 boards.

 I noticed a new board revision has been a released - the A6. The list of
 revisions included a reference to fixing a random glitch in the
 SYS_RESETn signal. Could this possibly address the problem I have been
 seeing - I would be more than happy to buy more boards if this is the case.

 Regardless of the new release, I have tried various experiments to find a
 100% reliable way of making the A5C board boot, as follows:

 1) Hold reset button, connect power, release reset button after ~1 second.

 2) Connect power, press and hold reset button, then release after ~1
 second.

 3) Hold Power button, connect power, wait till power led goes off, then
 release power button.

 All of these also failed at varying rates, but all showing at least one
 failure out of 40 tries - which is unfortunate as I am building a custom
 cape that will have access to the reset and power signals, so I there was
 some sure fire way of making it boot this would have been fairly easy to
 include in my design.

 Any further info would be greatly appreciated.


 Regards,
 Andrew.


 On Saturday, 28 September 2013 10:04:06 UTC+12, gmbe...@gmail.com wrote:

 Same problem here, its showing up in 2 ways. The Beagle Board Black has a
 power control IC that is sensitive to 5 volt rise time and has frozen up
 under short brownout situations..in fact, I can freeze it up at will by
 dropping out 5 V for about 100mS, it will lock up with 3.3 volts turned off
 even though the 5 volt input is good. Removing the 5 volt input for more
 than 1 second restores normal 3.3 Volt power and all is good. The other
 way..I'm still investigating, it refuses to boot about 1 in 20 tries for
 reasons that are so far unknown. In this instance I have power supply
 monitoring instruments all over this board, and the power supply controller
 is working even when the lockup occurs. So I'm mainly interested in the
 situation where the blue lights are on but the board is not booting. We are
 running a port of Debian Linux.


 On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.comwrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card).
 The Beagle Bone is placed in a case and we have connected it to a DC power
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging
 in our power supply, the BeagleBone powers on (Power LED is on), but
 nothing more happens (none of the other four LEDs is on). If we are now
 removing the power supply and putting it in again, the BBB starts normally.
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter

  --
 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.


-- 
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.

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[AndrewTaneGlen]

Hi Gerald, thank you for your response.

I tried the following (Using a new BBB with no SD card inserted, and 
nothing else connected to it at all):

Firstly, plug in 5V barrel connector (connected to regulated 5V, measured 
with good multimeter as 5.0001V), then:

1) Wait to see he heartbeat led (D2) come on.

2) Press and hold the power key until the power led (D1) goes off.

3) Release the power key

Repeating this process (with 5V connected the entire time) the device 
failed to boot (the heartbeat led failed to come on) on the 14th try, and 
continues to do so about 1/20.

I'm using the BBB in a location away from any regular user interaction and 
with a power supply that can come on and go off randomly (it functions as a 
wifi client I connect to and control/monitor with an ipad), so 
unfortunately I don't have the ability to manually press the power or reset 
buttons to ensure the device always comes on when power is applied (at 
least as I intend to use it).

What I will do, as a kind of nuclear option, is reassign the heart-beat led 
to a spare gpio on P9, and implement a basic watchdog circuit that will 
pull the 'SYS_RESETn' low for a couple of hundred milliseconds if it 
doesn't see a change in state of the heart-beat signal within about 10 
seconds. This should give a 100% guarantee that (as long as the hardware is 
ok) the kernel will eventually get booted whenever power is applied.

There is a TI part, the TPS382x that is nearly perfect for this task, but 
has a non-configurable delay time of 1.6s - I'll try to find something like 
this.

Cheers,
Andrew.



On Friday, 25 October 2013 02:01:51 UTC+13, Gerald wrote:

 I don't see that fix as being the issue you are seeing. But, when they 
 are available, you can certainly give it a try.

 The reset button is a warm reset button. It is not the power on reset for 
 the board.

 I suggest that you use the power button as it is intended and use it to 
 power off the board and then power on the board. See what sort of results 
 you get in that use case.

 Gerald


 On Wed, Oct 23, 2013 at 9:41 PM, AndrewTaneGlen 
 andrewt...@gmail.comjavascript:
  wrote:

 Hello All,

 I am also having this problem - with a bench top power supply set to 5V 
 and 5A, plugging into the barrel connector with no SD card inserted, so 
 running the default Angstrom image from flash, the device will fail to boot 
 at least 1 in 20 tries. A similar failure rate was observed on my two other 
 boards.

 I noticed a new board revision has been a released - the A6. The list of 
 revisions included a reference to fixing a random glitch in the 
 SYS_RESETn signal. Could this possibly address the problem I have been 
 seeing - I would be more than happy to buy more boards if this is the case.

 Regardless of the new release, I have tried various experiments to find a 
 100% reliable way of making the A5C board boot, as follows:

 1) Hold reset button, connect power, release reset button after ~1 second.

 2) Connect power, press and hold reset button, then release after ~1 
 second.

 3) Hold Power button, connect power, wait till power led goes off, then 
 release power button.

 All of these also failed at varying rates, but all showing at least one 
 failure out of 40 tries - which is unfortunate as I am building a custom 
 cape that will have access to the reset and power signals, so I there was 
 some sure fire way of making it boot this would have been fairly easy to 
 include in my design.

 Any further info would be greatly appreciated.


 Regards,
 Andrew.


 On Saturday, 28 September 2013 10:04:06 UTC+12, gmbe...@gmail.com wrote:

 Same problem here, its showing up in 2 ways. The Beagle Board Black has 
 a power control IC that is sensitive to 5 volt rise time and has frozen up 
 under short brownout situations..in fact, I can freeze it up at will by 
 dropping out 5 V for about 100mS, it will lock up with 3.3 volts turned off 
 even though the 5 volt input is good. Removing the 5 volt input for more 
 than 1 second restores normal 3.3 Volt power and all is good. The other 
 way..I'm still investigating, it refuses to boot about 1 in 20 tries for 
 reasons that are so far unknown. In this instance I have power supply 
 monitoring instruments all over this board, and the power supply controller 
 is working even when the lockup occurs. So I'm mainly interested in the 
 situation where the blue lights are on but the board is not booting. We are 
 running a port of Debian Linux.


 On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.comwrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

You must just press the power button once. Not hold it. If you do
it just power cycles. Pressing the button once let's the Linux kernel
shutdown after a 60 second time out.

Try it again using the power button as it was intended.

Gerald



On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewtaneg...@gmail.comwrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, measured
 with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device
 failed to boot (the heartbeat led failed to come on) on the 14th try, and
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction and
 with a power supply that can come on and go off randomly (it functions as a
 wifi client I connect to and control/monitor with an ipad), so
 unfortunately I don't have the ability to manually press the power or reset
 buttons to ensure the device always comes on when power is applied (at
 least as I intend to use it).

 What I will do, as a kind of nuclear option, is reassign the heart-beat
 led to a spare gpio on P9, and implement a basic watchdog circuit that will
 pull the 'SYS_RESETn' low for a couple of hundred milliseconds if it
 doesn't see a change in state of the heart-beat signal within about 10
 seconds. This should give a 100% guarantee that (as long as the hardware is
 ok) the kernel will eventually get booted whenever power is applied.

 There is a TI part, the TPS382x that is nearly perfect for this task, but
 has a non-configurable delay time of 1.6s - I'll try to find something like
 this.

 Cheers,
 Andrew.




 On Friday, 25 October 2013 02:01:51 UTC+13, Gerald wrote:

 I don't see that fix as being the issue you are seeing. But, when they
 are available, you can certainly give it a try.

 The reset button is a warm reset button. It is not the power on reset for
 the board.

 I suggest that you use the power button as it is intended and use it to
 power off the board and then power on the board. See what sort of results
 you get in that use case.

 Gerald


 On Wed, Oct 23, 2013 at 9:41 PM, AndrewTaneGlen andrewt...@gmail.comwrote:

 Hello All,

 I am also having this problem - with a bench top power supply set to 5V
 and 5A, plugging into the barrel connector with no SD card inserted, so
 running the default Angstrom image from flash, the device will fail to boot
 at least 1 in 20 tries. A similar failure rate was observed on my two other
 boards.

 I noticed a new board revision has been a released - the A6. The list of
 revisions included a reference to fixing a random glitch in the
 SYS_RESETn signal. Could this possibly address the problem I have been
 seeing - I would be more than happy to buy more boards if this is the case.

 Regardless of the new release, I have tried various experiments to find
 a 100% reliable way of making the A5C board boot, as follows:

 1) Hold reset button, connect power, release reset button after ~1
 second.

 2) Connect power, press and hold reset button, then release after ~1
 second.

 3) Hold Power button, connect power, wait till power led goes off, then
 release power button.

 All of these also failed at varying rates, but all showing at least one
 failure out of 40 tries - which is unfortunate as I am building a custom
 cape that will have access to the reset and power signals, so I there was
 some sure fire way of making it boot this would have been fairly easy to
 include in my design.

 Any further info would be greatly appreciated.


 Regards,
 Andrew.


 On Saturday, 28 September 2013 10:04:06 UTC+12, gmbe...@gmail.com wrote:

 Same problem here, its showing up in 2 ways. The Beagle Board Black has
 a power control IC that is sensitive to 5 volt rise time and has frozen up
 under short brownout situations..in fact, I can freeze it up at will by
 dropping out 5 V for about 100mS, it will lock up with 3.3 volts turned off
 even though the 5 volt input is good. Removing the 5 volt input for more
 than 1 second restores normal 3.3 Volt power and all is good. The other
 way..I'm still investigating, it refuses to boot about 1 in 20 tries for
 reasons that are so far unknown. In this instance I have power supply
 monitoring instruments all over this board, and the power supply controller
 is working even when the lockup occurs. So I'm mainly interested in the
 situation where the blue lights are on but the board is not booting. We are
 running a port of Debian Linux.


 On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.comwrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using
 Ubuntu Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[AndrewTaneGlen]

When it fails to boot after connecting 5V, a short press of the power 
switch has no effect. The kernel has not booted, so the button press event 
is going nowhere.

From this failure mode, pressing and holding the power switch until the 
power led goes off and then releasing it causes the device to boot - as 
does a short press of the reset switch. This is what has led me to the 
conclusion that the only way to guarantee the device boots after applying 
power is to control the reset signal with a watchdog circuit triggered off 
a transition of the heart-beat signal (or something similar).

I'm wondering if it possibly is getting to u-boot under this failure mode. 
Do you know if any of the uarts available on P9 are configured by default 
for u-boot?

Cheers,
Andrew.

On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do 
 it just power cycles. Pressing the button once let's the Linux kernel 
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen 
 andrewt...@gmail.comjavascript:
  wrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and 
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V, measured 
 with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device 
 failed to boot (the heartbeat led failed to come on) on the 14th try, and 
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction 
 and with a power supply that can come on and go off randomly (it functions 
 as a wifi client I connect to and control/monitor with an ipad), so 
 unfortunately I don't have the ability to manually press the power or reset 
 buttons to ensure the device always comes on when power is applied (at 
 least as I intend to use it).

 What I will do, as a kind of nuclear option, is reassign the heart-beat 
 led to a spare gpio on P9, and implement a basic watchdog circuit that will 
 pull the 'SYS_RESETn' low for a couple of hundred milliseconds if it 
 doesn't see a change in state of the heart-beat signal within about 10 
 seconds. This should give a 100% guarantee that (as long as the hardware is 
 ok) the kernel will eventually get booted whenever power is applied.

 There is a TI part, the TPS382x that is nearly perfect for this task, but 
 has a non-configurable delay time of 1.6s - I'll try to find something like 
 this.

 Cheers,
 Andrew.




 On Friday, 25 October 2013 02:01:51 UTC+13, Gerald wrote:

 I don't see that fix as being the issue you are seeing. But, when they 
 are available, you can certainly give it a try.

 The reset button is a warm reset button. It is not the power on reset 
 for the board.

 I suggest that you use the power button as it is intended and use it to 
 power off the board and then power on the board. See what sort of results 
 you get in that use case.

 Gerald


 On Wed, Oct 23, 2013 at 9:41 PM, AndrewTaneGlen andrewt...@gmail.comwrote:

 Hello All,

 I am also having this problem - with a bench top power supply set to 5V 
 and 5A, plugging into the barrel connector with no SD card inserted, so 
 running the default Angstrom image from flash, the device will fail to 
 boot 
 at least 1 in 20 tries. A similar failure rate was observed on my two 
 other 
 boards.

 I noticed a new board revision has been a released - the A6. The list 
 of revisions included a reference to fixing a random glitch in the 
 SYS_RESETn signal. Could this possibly address the problem I have been 
 seeing - I would be more than happy to buy more boards if this is the case.

 Regardless of the new release, I have tried various experiments to find 
 a 100% reliable way of making the A5C board boot, as follows:

 1) Hold reset button, connect power, release reset button after ~1 
 second.

 2) Connect power, press and hold reset button, then release after ~1 
 second.

 3) Hold Power button, connect power, wait till power led goes off, then 
 release power button.

 All of these also failed at varying rates, but all showing at least one 
 failure out of 40 tries - which is unfortunate as I am building a custom 
 cape that will have access to the reset and power signals, so I there was 
 some sure fire way of making it boot this would have been fairly easy to 
 include in my design.

 Any further info would be greatly appreciated.


 Regards,
 Andrew.


 On Saturday, 28 September 2013 10:04:06 UTC+12, gmbe...@gmail.comwrote:

 Same problem here, its showing up in 2 ways. The Beagle Board Black 
 has a power control IC that is sensitive to 5 volt rise time and has 
 frozen 
 up under short 

Re: [beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[Gerald Coley]

That is correct. The power button is only good for shutting it down with
power attached and turning it back on with power still attached.

UBoot uses the UART0 debug port on the header, J1, on the board.

Gerald




On Thu, Oct 24, 2013 at 3:57 PM, AndrewTaneGlen andrewtaneg...@gmail.comwrote:

 When it fails to boot after connecting 5V, a short press of the power
 switch has no effect. The kernel has not booted, so the button press event
 is going nowhere.

 From this failure mode, pressing and holding the power switch until the
 power led goes off and then releasing it causes the device to boot - as
 does a short press of the reset switch. This is what has led me to the
 conclusion that the only way to guarantee the device boots after applying
 power is to control the reset signal with a watchdog circuit triggered off
 a transition of the heart-beat signal (or something similar).

 I'm wondering if it possibly is getting to u-boot under this failure mode.
 Do you know if any of the uarts available on P9 are configured by default
 for u-boot?

 Cheers,
 Andrew.

 On Friday, 25 October 2013 09:14:18 UTC+13, Gerald wrote:

 You must just press the power button once. Not hold it. If you do
 it just power cycles. Pressing the button once let's the Linux kernel
 shutdown after a 60 second time out.

 Try it again using the power button as it was intended.

 Gerald



 On Thu, Oct 24, 2013 at 3:05 PM, AndrewTaneGlen andrewt...@gmail.comwrote:

 Hi Gerald, thank you for your response.

 I tried the following (Using a new BBB with no SD card inserted, and
 nothing else connected to it at all):

 Firstly, plug in 5V barrel connector (connected to regulated 5V,
 measured with good multimeter as 5.0001V), then:

 1) Wait to see he heartbeat led (D2) come on.

 2) Press and hold the power key until the power led (D1) goes off.

 3) Release the power key

 Repeating this process (with 5V connected the entire time) the device
 failed to boot (the heartbeat led failed to come on) on the 14th try, and
 continues to do so about 1/20.

 I'm using the BBB in a location away from any regular user interaction
 and with a power supply that can come on and go off randomly (it functions
 as a wifi client I connect to and control/monitor with an ipad), so
 unfortunately I don't have the ability to manually press the power or reset
 buttons to ensure the device always comes on when power is applied (at
 least as I intend to use it).

 What I will do, as a kind of nuclear option, is reassign the heart-beat
 led to a spare gpio on P9, and implement a basic watchdog circuit that will
 pull the 'SYS_RESETn' low for a couple of hundred milliseconds if it
 doesn't see a change in state of the heart-beat signal within about 10
 seconds. This should give a 100% guarantee that (as long as the hardware is
 ok) the kernel will eventually get booted whenever power is applied.

 There is a TI part, the TPS382x that is nearly perfect for this task,
 but has a non-configurable delay time of 1.6s - I'll try to find something
 like this.

 Cheers,
 Andrew.




 On Friday, 25 October 2013 02:01:51 UTC+13, Gerald wrote:

 I don't see that fix as being the issue you are seeing. But, when they
 are available, you can certainly give it a try.

 The reset button is a warm reset button. It is not the power on reset
 for the board.

 I suggest that you use the power button as it is intended and use it to
 power off the board and then power on the board. See what sort of results
 you get in that use case.

 Gerald


 On Wed, Oct 23, 2013 at 9:41 PM, AndrewTaneGlen 
 andrewt...@gmail.comwrote:

 Hello All,

 I am also having this problem - with a bench top power supply set to
 5V and 5A, plugging into the barrel connector with no SD card inserted, so
 running the default Angstrom image from flash, the device will fail to 
 boot
 at least 1 in 20 tries. A similar failure rate was observed on my two 
 other
 boards.

 I noticed a new board revision has been a released - the A6. The list
 of revisions included a reference to fixing a random glitch in the
 SYS_RESETn signal. Could this possibly address the problem I have been
 seeing - I would be more than happy to buy more boards if this is the 
 case.

 Regardless of the new release, I have tried various experiments to
 find a 100% reliable way of making the A5C board boot, as follows:

 1) Hold reset button, connect power, release reset button after ~1
 second.

 2) Connect power, press and hold reset button, then release after ~1
 second.

 3) Hold Power button, connect power, wait till power led goes off,
 then release power button.

 All of these also failed at varying rates, but all showing at least
 one failure out of 40 tries - which is unfortunate as I am building a
 custom cape that will have access to the reset and power signals, so I
 there was some sure fire way of making it boot this would have been fairly
 easy to include in my design.

 Any further info would be greatly appreciated.


 

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[AndrewTaneGlen]

Hello All,

I am also having this problem - with a bench top power supply set to 5V and 
5A, plugging into the barrel connector with no SD card inserted, so running 
the default Angstrom image from flash, the device will fail to boot at 
least 1 in 20 tries. A similar failure rate was observed on my two other 
boards.

I noticed a new board revision has been a released - the A6. The list of 
revisions included a reference to fixing a random glitch in the SYS_RESETn 
signal. Could this possibly address the problem I have been seeing - I 
would be more than happy to buy more boards if this is the case.

Regardless of the new release, I have tried various experiments to find a 
100% reliable way of making the A5C board boot, as follows:

1) Hold reset button, connect power, release reset button after ~1 second.

2) Connect power, press and hold reset button, then release after ~1 second.

3) Hold Power button, connect power, wait till power led goes off, then 
release power button.

All of these also failed at varying rates, but all showing at least one 
failure out of 40 tries - which is unfortunate as I am building a custom 
cape that will have access to the reset and power signals, so I there was 
some sure fire way of making it boot this would have been fairly easy to 
include in my design.

Any further info would be greatly appreciated.


Regards,
Andrew.

On Saturday, 28 September 2013 10:04:06 UTC+12, gmbe...@gmail.com wrote:

 Same problem here, its showing up in 2 ways. The Beagle Board Black has a 
 power control IC that is sensitive to 5 volt rise time and has frozen up 
 under short brownout situations..in fact, I can freeze it up at will by 
 dropping out 5 V for about 100mS, it will lock up with 3.3 volts turned off 
 even though the 5 volt input is good. Removing the 5 volt input for more 
 than 1 second restores normal 3.3 Volt power and all is good. The other 
 way..I'm still investigating, it refuses to boot about 1 in 20 tries for 
 reasons that are so far unknown. In this instance I have power supply 
 monitoring instruments all over this board, and the power supply controller 
 is working even when the lockup occurs. So I'm mainly interested in the 
 situation where the blue lights are on but the board is not booting. We are 
 running a port of Debian Linux.


 On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter



-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[gmbeagler]

On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.

[beagleboard] Re: BeagleBone Black doesn't sometimes start. Only Power LED is on

[gmbeagler]

Same problem here, its showing up in 2 ways. The Beagle Board Black has a 
power control IC that is sensitive to 5 volt rise time and has frozen up 
under short brownout situations..in fact, I can freeze it up at will by 
dropping out 5 V for about 100mS, it will lock up with 3.3 volts turned off 
even though the 5 volt input is good. Removing the 5 volt input for more 
than 1 second restores normal 3.3 Volt power and all is good. The other 
way..I'm still investigating, it refuses to boot about 1 in 20 tries for 
reasons that are so far unknown. In this instance I have power supply 
monitoring instruments all over this board, and the power supply controller 
is working even when the lockup occurs. So I'm mainly interested in the 
situation where the blue lights are on but the board is not booting. We are 
running a port of Debian Linux.


On Wednesday, July 31, 2013 5:48:54 PM UTC-4, duckhunt...@gmail.com wrote:

 Hi guys,

 we have a problem with our Beagle Bone Black (A5C). We are using Ubuntu 
 Raring 13.04 armhf v3.8.13-bone21 (2013-06-14) on the eMMC (no SD Card). 
 The Beagle Bone is placed in a case and we have connected it to a DC power 
 supply. Sometimes (I would say every 5 to 10 times), when we are plugging 
 in our power supply, the BeagleBone powers on (Power LED is on), but 
 nothing more happens (none of the other four LEDs is on). If we are now 
 removing the power supply and putting it in again, the BBB starts normally. 
 I guess the power supply is strong enough: 5A@5V.

 Thanks for your help in advance.

 Regards,
 duckhunter


-- 
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.