On Sun, 13 Nov 2016 03:49:58 -0800 (PST), "'Ian Watts' via BeagleBoard"
<
beagl...@googlegroups.com> declaimed the
following:
>Thanks for that.
>
>Indeed, updating the uEnv.txt file (using nano) WITHIN the //boot/uboot/
>folder ON the uSD card worked a treat (needed (obviously) USB-network
>access to achieve this) !
>Cylon-style lights etc... followed by a reboot all good !
>Wow, was I pleased !!
>
Hmmm... /boot/uboot is empty on my SD card (and that's the "Jessie"
card rather than the "Wheezy").
Oh, if you did activate the flasher mode, I presume you did remove the
SD card after flashing? Unless the flasher script turns off the flasher
line, booting with the card in place will just trigger another flash
operation.
>However, the sting, is that the BBB no longer presents itself to the
>network over USB. I tried pretty much everything to do with keyhosts,
I haven't used the USB connection since the first time connecting to an
as-shipped card. Unless one has the host computer configured as a gateway
(M$ "Internet Connection Sharing") it doesn't give much -- the BBB can't
get out to access the world (not even a time-server to update the clock).
And with a cat-5 running from it to a router, the Ethernet connection seems
to take priority, effectively shutting down the USB Ethernet. (Though
ifconfig implies it is there)
debian@beaglebone:~$ ifconfig
eth0 Link encap:Ethernet HWaddr d0:39:72:18:3e:e5
inet addr:192.168.2.105 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fdf2:d52e:b5c7:0:d239:72ff:fe18:3ee5/64 Scope:Global
inet6 addr: fe80::d239:72ff:fe18:3ee5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:224 errors:0 dropped:0 overruns:0 frame:0
TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24717 (24.1 KiB) TX bytes:36824 (35.9 KiB)
Interrupt:175
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:166 errors:0 dropped:0 overruns:0 frame:0
TX packets:166 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:13548 (13.2 KiB) TX bytes:13548 (13.2 KiB)
usb0 Link encap:Ethernet HWaddr d0:39:72:18:3e:e0
inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
debian@beaglebone:~$
>renewing DHCP leases etc... etc... nada... nothing... the BBB simply isn't
Sometime back I set my router up to reserve an address for the BBB (and
a Raspberry PI 3) so... while still DHCP assigned to the boards, they stay
the same value, so I don't have to hunt for them each time.
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
debian@beaglebone:~$ uname -a
Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 2016 armv7l
GNU/Linux
debian@beaglebone:~$
(That's the misnamed image on
http://beagleboard.org/latest-images -- the
page says 2015, but it is this summer.)
And cloud9 is reachable -- haven't seen that in over a year either <G>
But had a red popup about "language worker could not be loaded"
The board I normally fiddle with has this on the SD card:
debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l
GNU/Linux
debian@beaglebone:~$
and is reachable over Ethernet, I haven't tried USB
>
>So, how do I re-connect to a naughty / really peeved BBB ?
>I'm happy to go Ethernet cable - no probs - but how ? I have an ethernet HP
>laser printer here in my office (years old, but faithful) so disconnected
>the RJ45 from its bottom and connected it to the BBB. Powered up the BBB
Is that laser printer cable going through a DHCP router? If it isn't,
you likely have a fixed local IP on it. And... is it a straight through or
cross-over cable (if it has a router connection, it should be normal
straight-through). I'll admit I'm grabbing at straws here -- I don't know
if the BBB has an auto-sense Ethernet (mostly found on modern routers so
one doesn't need a cross-over cable to connect from router to router); a
straight through cable with no router would have the wrong "polarity" at
one end and without auto-sense the hardware won't negotiate a connection.
Does the router have enough DHCP addresses left (mine is configured to
assign 192.168.2.100 through 192.168.2.114, and I show assignments on:
.100, .102 (Nook HD), .104 (RPi3), .105 (BBB #1), .106 (WII U), .107
(Blackberry), .108 (TV), .109 (computer), .110 (Epson printer), .111
(Samsung/Nook), .112 (Nook Glow), .113 (HP printer)... And that doesn't
account for my original Nook (kept at work) and the RPi3 WiFi (both of
which might be the unidentified addresses (Think I'll up the available
address range -- if I ever do something with the TIVA 1294 and 129E boards,
they'll need slots too)
>(external power supply, not USB) but still nothing seems to be making
>itself available to the network... As I understand it, if it can 'see; the
>network, it should at least be saying something like, 'Howdy, would someone
>like to assign me an IP address please ?' and, if not getting one, then
>assign itself a self-assigned 169.254.x.x number. At least I should then be
>able to see the BBB if not properly communicate with it ! But in my case
>nothing.
>Looking at my router's assigned IP addresses etc. does not show up anything
>like a BBB or 'unknown' device, just verifiable devices (tablet, phone,
>laptop and work station). Turning each one off / on simply verifies it's
>connection in the router's connected devices list... No 'odd' connections /
>devices...
Okay, you do have a router. I'd ask about the MAC addresses it shows,
but since the MAC is not printed on the BBB it might not be useful. And
since I have fixed IP assignments on the MAC addresses with a user-defined
name, my router status page isn't useful (as you see above I have a few
items that don't show a name -- I had to check the TV for its MAC address).
Do you have the Ethernet LEDs on the BBB and the router showing a
connection? Was the cable connected when you booted?
>
>So, I guess, seeing as how the BBB no longer wants to talk over USB (to be
>fair, with all the messing about, this could be the BBB or the device
Do you have a microHDMI<>HDMI cable (and a TV/Monitor with HDMI input),
an available USB hub (preferably powered) and USB keyboard&mouse? (hub not
needed if you have, say, Logitech "Unifying" wireless keyboard&mouse). If
you do, you should be able to operate in stand-alone (no network or
computer connection) mode while attempting to debug the BBB. You will need
the wall wart to power the BBB.
That should let you check "ifconfig" for status... THEN connect the
cat-5 cable and recheck (possibly with a reboot). You'll want to see if the
ethernet connection shows as UP, and what IP address it reports (I'd expect
none before connecting the cable).
At this point, unless you have a bad Ethernet jack, I'd be tempted to
blame the host computer and/or firewalls. I recall seeing traffic about Mac
USB tethering drivers being problematic -- HoRNDIS being the main one
available (though the home page is focused on using it with an Android
phone to gain external internet access by tethering). OTOH: I did see both
RNDIS and CDC drivers being loaded on Windows when I tried.
Maybe running Wireshark would let you see some if there is any traffic
from the BBB.
>-1- connect via Ethernet cable (c/w external power supply to the BBB). Is
>this possible ? Are there any hints, tips or pointers for me here please ?
Well... that is my normal operating process... But I'm on Windows, and
haven't had any problems (other than finding the IP address before I set
the router to lock it to the MAC of the board). And my configuration is a
mess! DSL modem (192.168.1.x) to WiFi router (192.168.2.x) split to
computer and to an 8-port switch (switch does not assign DHCP addresses...
But might be one of the unknowns I list above since it does have a
configuration capability) with two printers, and two unallocated cat-5 (a
short one to my keyboard position when I hook the BBB up locally, and a
longer one used when it is across the room or for updating my laptop). I
tend to take the RPI3 upstairs and connect to a TV as it has WiFi; use
Logitech keyboard/mouse).
>-2- (my preferred option, simply because I don't have to mess about with
>networks) modify the uEnv.txt file directly on the uSD card from my
>computer (not the BBB - no connection !) and re-flash. Is this possible ?
Since I was able to mount the card on a Debian virtual machine running
on Windows (which doesn't do the ext# file systems at all), it should be
possible on a Mac. You may need to find the proper device entry to do the
mount with, specifying the proper filesystem (if it is a recent BBB image,
you no longer have a split partitioning to worry about).
Though I'd recommend using a recent standard image
https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
to write to the SD card... And ensure that you can get that to work BEFORE
trying to flash the eMMC with the image. Only after you can connect to the
BBB when booting off the SD card should you consider changing the card to a
flasher. As I mentioned above -- while I have a Jessie image on SD card,
I'm still running Wheezy in the eMMC.
And again, debugging this could entail going stand-alone mode with a
TV/keyboard/mouse (or obtaining an adapter for the debug serial port --
pity the BBB is wired differently from the one that came with an RPi
accessory kit -- though it might be possible to use jumper wires to swap
the connections).