Hi Dennis,

I finally got the Board working !!!

Right now, it's booting from the uSD card. The OS in the eMMC is still 
causing problems though, but at least it's working somehow now. 
I downloaded the image 
from https://beagleboard.org/latest-images

I am powering the BBB using the USB, but have connected the USB to a cell 
phone charger of 5 V - 2 Amps

I am glad that it's working now, and I can look into the eMMC issue in 
detail at my convenience. I needed this to setup a Python script to run 
periodically every day and I can do that now. 

Thanks a lot, Dennis, but at least guiding me till this point. 


On Tuesday, 20 September 2016 18:44:00 UTC+5:30, Dennis Lee Bieber wrote:
> On Tue, 20 Sep 2016 02:39:50 -0700 (PDT), Viswadeep Sarangi 
> <deepu...@gmail.com <javascript:>> declaimed the 
> following: 
> > 
> >Right now, I have installed the following image onto my uSD card : 
> >
> https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
> > --- but the BBB doesn't boot from it anymore (even after pressing the S2 
> >button) and still shows the top 2 LEDs lit forever. 
> > 
>         Try the version that does not have "flasher" in the name, just to 
> see 
> if the system can boot from a plain SD card image. 
>         When booting a flasher image, the LEDs normally do a 0-3 fill 
> sequence 
> at the start of flashing, then to some pattern that may vary with the 
> image 
> before going to a solid all on at the end (Molloy's website says a 
> side-to-side sweep while flashing). 
>         You seem to be seeing the first phase of a flasher start. 
>         Hmm -- how are you powering the unit? A USB connection may not be 
> providing enough power to sustain eMMC flashing. 
> > 
> >loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile} 
> > 
>         Other than the fact that I don't know where the environment 
> variables 
> are defined... mmcdev, mmcpart, and fdtfile are not defined in uEnv.txt; 
> the first two define the flash device and partition, and the last 
> specifies 
> the device tree file. 
>         The contents do show that it expects the kernel image to be: 
> zImage 
> and initrd to be: initrd.img 
> so those match the directory content. 
> -- 
>         Wulfraed                 Dennis Lee Bieber         AF6VN 
>     wlf...@ix.netcom.com <javascript:>    HTTP://wlfraed.home.netcom.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.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to