Hi Dennis,
{That's alright, I am just glad I am getting help from you that's all as I
have given up on the documents in the forum already}
As my BBB isn't booting anymore, my PC isn't able to read the contents of
BBB anymore. (As usual, as soon as I power my BBB, the USR0 and USR1 get
lit and stay like that forever)
Well, actually this is what is happenening, if I had to denote the lit LED
as [x] and turned off LED as [], and the USR0 to USR3 LEDs as [] [] [] []
, then this is the pattern I am getting :
[] [] [] [] --> [x] [] [] [] --> [x] [x] [] [] --> [x] [x] [x] [] --> []
[] [] [] --> [x] [] [] [] --> [x] [x] [] [] (and it stays like this
forever)
Basically the first three LEDs light up for a fraction of a second, and
then everything goes blank and the first two LEDs stay lit forever.
I couldn't find what's wrong in the uEnv.txt of the debian image that I am
trying to flash on the BBB.
I am no longer flashing or trying to boot from unofficial images.
Earlier I had flashed the following image :
BBB-eMMC-flasher-ubuntu-16.04.1-console-armhf-2016-09-09-2gb.img (from
https://rcn-ee.com/rootfs/2016-09-09/flasher/BBB-eMMC-flasher-ubuntu-16.04.1-console-armhf-2016-09-09-2gb.img.xz)---
after which the problem of only 2 LEDs lighting started.
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.
I am attaching the uEnv.txt file along with this reply just for further
clarification. But as a quick reference I found this part interesting :
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
and as Hermans mentioned, it might have something to do with this.
On Tuesday, 20 September 2016 03:46:08 UTC+5:30, Dennis Lee Bieber wrote:
>
> On Mon, 19 Sep 2016 08:55:42 -0700 (PDT), Viswadeep Sarangi
> <deepu...@gmail.com <javascript:>> declaimed the
> following:
>
> >
> >But when I started the BBB after flashing. Only the first two LEDs
> flashed
> >and stayed lit ( USR0 and USR1). But nothing else happened. It's been
> like
>
> USR1 is defined to be SD card access, and USR3 is the eMMC.
>
> But where in the OS those get controlled I can't say... nor if any
> of
> the third-party OS releases don't bother installing the handlers for the
> LEDs.
>
> >Any idea what might be happening and how I can fix it ?
>
> My first suggestion would be to revert to a 2GB compatible
> official
> image first -- which would be this old one:
>
> https://debian.beagleboard.org/images/BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
>
>
> If the BBB won't run that after flashing (and removing the SD
> card) you
> have some significant problem. Actually, I'd suggest first booting an SD
> card with
> https://debian.beagleboard.org/images/bone-debian-7.5-2014-05-14-2gb.img.xz
> just to make sure the BBB runs with that OS, period... THEN flash the eMMC
> and check that it still runs.
>
> IF you get the unit to run with the 2GB flasher image above...
> THEN try
> your third party OS on the SD card in a NON-flasher mode; ensure that OS
> works before flashing it to the eMMC... And make sure it does fit
> (depending on how "GB" is being computed -- you may still be running over:
> decimal 2GB is only binary 1.86GB).
> --
> 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
https://groups.google.com/d/msgid/beagleboard/385d7c5e-a293-4db8-a3b4-f4234fb19555%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
##Video: Uncomment to override:
##see:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt
#kms_force_mode=video=HDMI-A-1:1024x768@60e
##Enable systemd
systemd=quiet init=/lib/systemd/systemd
##BeagleBone Cape Overrides
##BeagleBone Black:
##Disable HDMI/eMMC
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
##Disable HDMI
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
##Audio Cape (needs HDMI Audio disabled)
#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI
#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02
##Example
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
##WIP: v3.14+ capes..
#cape=ttyO1
#cape=
##note: the eMMC flasher script relies on the next line
mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext4 rootwait fixrtc
##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
console=ttyO0,115200n8
kernel_file=zImage
initrd_file=initrd.img
loadaddr=0x82000000
initrd_addr=0x88080000
fdtaddr=0x88000000
initrd_high=0xffffffff
fdt_high=0xffffffff
loadkernel=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${kernel_file}
loadinitrd=load mmc ${mmcdev}:${mmcpart} ${initrd_addr} ${initrd_file}; setenv
initrd_size ${filesize}
loadfdt=load mmc ${mmcdev}:${mmcpart} ${fdtaddr} /dtbs/${fdtfile}
loadfiles=run loadkernel; run loadinitrd; run loadfdt
mmcargs=setenv bootargs console=tty0 console=${console} ${optargs}
${cape_disable} ${cape_enable} ${kms_force_mode} root=${mmcroot}
rootfstype=${mmcrootfstype} ${systemd}
uenvcmd=run loadfiles; run mmcargs; bootz ${loadaddr}
${initrd_addr}:${initrd_size} ${fdtaddr}
#
