Thanks Dennis, I appreciate your help / thoughts... Hmmm... to summarise where I'm at : I have a BBB (Rev C / 4GB) with an external 2A PSU and 2 x 4GB uSD Cards. On Card-1- I have a 4GB FLASHER image (Debian 8.6-lxqt-4gb-armhf-2016-11-06-4gb.img). To me this is an image that will effect an eMMC AUTOMATICALLY upon boot - i.e. it already has the uEnv.txt file modified to effect the flash, meaning I don't need to gain access to the BBB to modify the file myself. On Card-2- I have a 'non-flasher' image of Debian 8 (Debian-8.6-lxqt-4gb-armhf-2016-10-30-4gb.img)
So, Powered UP : Brand new out-of-the-box BBB (no uSD card inserted, boot from eMMC with supplied 2014 Debian Distro) ;-) correct power up as per the UserLEDs :-) the unit presented itself to the network (Network-ove-USB cable) on 192.168.7.2 :-) I could ssh in via Terminal (Mac) :-) I could browse to it via 192.168.7.2 from Safari and Chrome. Updated the Image from the supplied 2014 Debian Distro to the 2016 8.6 Debian Distro :-) All went well, Cylon lights -> all four UsrLEDs ON. a simple 'cat' of the ID.txt file indicated the new Distro Powered DOWN... and my problems began... Power UP : Debian 8.6 with no card inserted : *;-( incorrect power up. After 60 s (or so) UsrLEDs stop flashing leaving UsrLEDs 0 & 1 On and UsrLEDs 2 & 3 OFF* :-( the unit does not present itself to the network (Network-ove-USB cable) :-( the unit does not present itself to the network with an RJ45 Ethernet cable connected (I'm using my Lan Printer cable for this - just disconnect it from the printer and reconnect it to the BBB and cycle power on the network switch. ;-( It's not possible to ssh in via terminal (Mac) or browse (192.168.7.2) to it via Safari or Chrome. Unit appears to have stalled during boot... Power UP : *Debian 8.6 with uSD Card-1- inserted* (no boot switch needed, simply apply power) : ;-) correct power up. After 45 s (or so) UsrLEDs stop flashing and begin the 'cylon sweep'... :-) correct (?) eMMC Flash completed - All 4 UsrLEDs ON Power DOWN... Remove uSD Card Power UP : *Debian 8.6 eMMC no uSD Card inserted* ;-( incorrect power up. After 60 s (or so) UsrLEDs stop flashing leaving UsrLEDs 0 & 1 On and UsrLEDs 2 & 3 OFF :-( the unit does not present itself to the network (Network-ove-USB cable) :-( the unit does not present itself to the network with an RJ45 Ethernet cable connected (I'm using my Lan Printer cable for this - just disconnect it from the printer and reconnect it to the BBB and cycle power on the network switch. ;-( It's not possible to ssh in via terminal (Mac) or browse (192.168.7.2) to it via Safari or Chrome. Unit appears to have stalled during boot... Power DOWN... Insert uSD Card-2- Power UP : *Debian 8.6 eMMC and Debian 8.6 uSD Card-2- inserted* ;-) correct (?) power up. Various UsrLEDs flash, flash, flash... :-( the unit does not present itself to the network (Network-ove-USB cable) :-( the unit does not present itself to the network with an RJ45 Ethernet cable connected (I'm using my Lan Printer cable for this - just disconnect it from the printer and reconnect it to the BBB and cycle power on the network switch. ;-( It's not possible to ssh in via terminal (Mac) or browse (192.168.7.2) to it via Safari or Chrome. Unit appears to be working (UsrLEDs flash away quite happily) BUT that's it... *Note the difference between uSD card inserted (here, uSD card Boot) and uSD card absent (above, eMMC boot)* Power DOWN... Remove uSD Card Power UP : *Debian 8.6 eMMC no uSD Card inserted* ;-( incorrect power up. After 60 s (or so) UsrLEDs stop flashing leaving UsrLEDs 0 & 1 On and UsrLEDs 2 & 3 OFF :-( the unit does not present itself to the network (Network-ove-USB cable) :-( the unit does not present itself to the network with an RJ45 Ethernet cable connected (I'm using my Lan Printer cable for this - just disconnect it from the printer and reconnect it to the BBB and cycle power on the network switch. ;-( It's not possible to ssh in via terminal (Mac) or browse (192.168.7.2) to it via Safari or Chrome. Unit appears to have stalled during boot (again)... So, I conclude : My BBB is NOT yet bricked (good news) because : although it will not complete a boot sequence via the built-in eMMC (not so good news) it WILL complete a boot sequence via the uSD card (-2-) (good news) and it does appear to (re-) flash the eMMC from uSD card (-1-) when a Flasher image is inserted. My questions : Why ? Anyone with any bright ideas ? The way ahead ? Try the BBB on a Windows machine ? (I'm thinking network issues - but on BOTH my Macs ? ? ?) Wait for the Serial->USB adapter to arrive, connect it, power up and monitor the BBB's actions via a terminal ? Anyone with any ideas at all ? Thank you. Ian On Sunday, 13 November 2016 18:34:46 UTC+1, Dennis Lee Bieber wrote: > > > Talking to myself in public... a bad sign... > > On Sun, 13 Nov 2016 12:07:05 -0500, Dennis Lee Bieber > <[email protected] <javascript:>> declaimed the following: > > > As an experiment, I'm connecting my second BBB (which I think > still has > >the original OS, I'll check after it gets done loading drivers, which is > >taking some time) over just USB, using a port directly on the computer. > > > > Hmmm -- interesting, it came up (eventually -- felt like 5 > minutes to > >get the drivers loaded from M$, and that was a few minutes after booting > >using USB power) on USB with a 39MB Windows partition showing, but seems > to > >have had an updated OS > > > > As an added data point, I shutdown my primary BBB, and took it to > the > desk where I connected using just a USB cable (running to an unpowered hub > that was a built-in of this desk). It came up -- and I got the wait while > Windows again search M$ for RNDIS and CDC drivers. Apparently these need > to > be "re-installed" for each USB port the BBB is ever connected to. Another > reason to not use the USB connection <G> > > After logging in, ifconfig showed that eth0 had no IP address > (strangely, it did show an IPv6 address, but not the IPv4 used on my LAN). > Connecting a cat-5 cable had no effect, even "ifconfig eth0 up" made no > changes. Issuing a reboot command, however, and waiting through the USB > reconnect, logging back in, NOW showed eth0 with an IP address. So, based > on that, the DHCP request is only performed during boot, and not on cable > connection. And, in a surprise to me (since I was unable to do this when I > first received the BBB) BOTH eth0 and usb0 links were active (though the > clock update only took place with the eth0 active). > -- > Wulfraed Dennis Lee Bieber AF6VN > [email protected] <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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a9726e66-f774-42e4-8141-a323a8daa6db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
