On Tue, Nov 22, 2016 at 1:57 PM, Dennis Lee Bieber
<[email protected]> wrote:
> On Tue, 22 Nov 2016 11:01:04 -0600, Robert Nelson
> <[email protected]> declaimed the
> following:
>
>         <SNIP>
>
>>
>>usr0 - turn on - on boot starting
>>usr1 - turn on - starting scan of mmc0 (microSD)
>>
>>/uEnv.txt (boot) *default use for comparability with old images..
>>usr2 - turn on - found /uEnv.txt
>>usr3 - turn on - running u-boot cmd: uenvcmd
>>
>         <snip>
>         So if I understand the description from Mr. Watts, his board is never
> finding anything after looking at the non-installed SD card.
>
>>/boot/uEnv.txt  *default set by "eMMC flasher"
>>usr2 - turn on - found /boot/uEnv.txt
>>usr3 - turn on - running u-boot cmd: uname_boot
>>
>>usr3 - turn off
>>usr2 - turn off
>>usr1 - turn off
>>Starting Scan off mmc1 (eMMC)
>>
>         Either mine boots too fast too tell, or it follows a different 
> sequence
> <G>... This implies that after the scan of SD card it drops back to usr0
> on, usr1 off, and then should go usr2 on, usr3 on... But I don't see it
> when booting without an SD card -- appeared to cycle to all 4 on, then jump
> to off/on/off/on (0/1/2/3), before normal activity (heartbeat, eMMC, cpu
> flickers)
>
>         In either case, it would seem that the problem board is never finding
> /a/ boot configuration file when booting from eMMC. Since the problem board
> also seems to never be recognized by the Mac OS even when booting from SD
> card, I have no further ideas... either a debug serial adapter, or USB
> keyboard/mouse and HDMI cable to a TV, to try examining the eMMC contents
> after booting from SD card.

A serial cable would help. ;)

>
>>/uEnv.txt (boot) *default use for comparability with old images..
>>usr2 - turn on - found /uEnv.txt
>>usr3 - turn on - running u-boot cmd: uenvcmd
>>
>>/boot.scr (for debian)
>>usr2 - turn on - found /boot.scr
>>usr3 - turn on - running u-boot cmd: bootscript
>>
>>/boot/boot.scr (for debian)
>>usr2 - turn on - found /boot/boot.scr
>>usr3 - turn on - running u-boot cmd: bootscript
>>
>>/boot/uEnv.txt  *default set by "eMMC flasher"
>>usr2 - turn on - found /boot/uEnv.txt
>>usr3 - turn on - running u-boot cmd: uname_boot
>>
>>aka... it doesn't actually tell you much, unless it get's stuck..
>>
>
>         HEH... Especially when my eMMC (running Wheezy
> debian@beaglebone:/$ uname -a
> Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 2016 armv7l
> GNU/Linux ) doesn't seem to have /uEnv.txt, /boot.scr, or /boot/boot.scr,
> just /boot/uEnv.txt -- SDcard image does have /uEnv.txt though... You've
> actually got me wondering how mine even boots...

the first three are optional:

http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

the first one /uEnv.txt allows us to support the really really old
angstrom version of u-boot.. If you look very close at your /uEnv.txt
so you'll see actually reading /boot/uEnv.txt .;)

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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYihqLvqyDzC1t3Ukr2Jb4U7_LrCyFrJPns%2Bv%3D7TeA6Kcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to