I just unpacked a Beaglebone Black board and try to get it started as tethered to a PC via USB. I can find and read START.HTM from the BBB.
When it comes to Step #2, Install drivers, I start getting problems: 4 of the drivers fail to install on my Windows10 host:
Linux Developer Community (usbser) Ports
BeagleBone CDM Driver Package - Bus/D2XX Driver
BeagleBone CDM Driver Package - VCP Driver
Linux Developer Community Net
After that step #3 fails, probably as a consequense of above. My web browser (either Firefox or Chrome) will not find http://192.168.7.2.
I’ve also tried on other computers, running Windows 8 and Windows 7, with no further success.
Do you still get the same driver install problems on the Windows 7 PC as you see on your Windows 10 host or is that primarily a problem with accessing the URL in your web browser?
Actually, on the Windows 7 the symptoms were a bit different. It was an old machine with only 4GB RAM and the PC seemed to be overloaded during the installation with locked screen for most of the time.
So the only similarity I can be sure of is the URL not responding.
Anyhow, I think I’ve found problem on Window 10: It won’t install drivers lacking valid MS-signature. It doesn’t tell you that, it simply tells you that installlation failed (thank you Microsoft).
I turned off this signature checking and now it work (even step #3). So I’m back on track again.
Ther must be more rookies having this problem out there: Try google https://youtu.be/71YAIw7_-kg to disable this feature.
Or, BBB: Get this signature from MS. It seems to be a matter of $99 to get it.
The 5 minutes needed to get up and started (according to your purchase text) has grown to more than 5 hrs…
On Wed, 7 Feb 2018 07:42:23 -0800 (PST), Jon Lundstrom
<j.b.lundstrom@gmail.com> declaimed the
following:
Ther must be more rookies having this problem out there: Try
google https://youtu.be/71YAIw7_-kg to disable this feature.
Or, BBB: Get this signature from MS. It seems to be a matter of $99 to get
it.
The 5 minutes needed to get up and started (according to your purchase
text) has grown to more than 5 hrs...
As I recall, the newest BBB images no longer require custom drivers on
Win10 -- they are supposed to work using M$ distributed rndis (or whatever)
drivers, which are found by Win10 automatically.
This should be the case, but some folks have reported a regression with the 1709 update around the first of the year.
Well, the web sever on my BBB wasn’t responding to 192.168.7.2 before I installed the drivers according to step #2. My Windows 10 should be up-to-date.
Thank you guys, for the attention.