**** BEGIN LOGGING AT Fri May 03 02:59:57 2019 May 03 09:14:58 Can somebody pleasee help me May 03 09:15:26 I am trying to access BBB via putty but it is giving me a network unreachable error May 03 09:16:30 This error is existant only on my PC. It is working fine on my laptop and my friends PC May 03 09:16:40 Any idea what might be the issue ? May 03 11:49:00 Hello i cant enter the web site from the usb May 03 12:09:47 which board are you trying to use? May 03 12:20:31 tbr: are you scaring people off again by asking them complicated questions? ;) May 03 12:20:50 zmatt: and succeeding at it! May 03 12:21:18 * tbr looks forward to the bbb-ai - more chance to be informed and unhelpful May 03 12:33:42 \o/ May 03 12:53:26 also, you mean bb-ai, not bbb-ai :P May 03 12:54:03 oh, right. That's just because jkridner hasn't sent me one yet! ;-) May 03 12:54:19 lol May 03 12:56:31 do the old EA X15 boards work again with current images? Last time I remember hearing there was at the least some manual twiddling involved. May 03 13:49:39 tbr which EA board? May 03 13:51:38 run, sudo /opt/scripts/tools/version.sh and give us the eeprom/model from that script: May 03 14:08:50 rcn-ee[m]: will do once I get home (so will take > 4 h) May 03 14:09:35 rcn-ee[m]: the batch that got sent out in the first more public wave May 03 14:11:10 tbr, there were a few 'early' batches, some required you to "return" it to TI or destroy... So run https://rcn-ee.net/rootfs/bb.org/testing/2019-04-28/stretch-iot/am57xx-debian-9.9-iot-armhf-2019-04-28-4gb.img.xz so we can see what version you really have.. May 03 14:12:53 rcn-ee[m]: nah, it wasn't one of them. must have been around late 2014 May 03 14:14:49 then your probably pretty safe.. i still have one of the first odd units that i use for boot testing.. it's not offically supported by anyone. ;) May 03 14:16:25 good good. I only remember someone said that either the board or the silicon had some ugly quirks. Anyway, no need to dwell on this. Have enough rope (image above) to try and hang myself by. May 03 14:17:36 The 2nd phy was limited to 100Mbit.. May 03 14:17:44 just plug in the top one May 03 18:48:29 Hey, does anyone have advise on connecting a Beaglebone Black to OSX High Sierra? I've got a customer using one that can't seem to get the BBB to be recognized with the serial over USB connection May 03 18:50:58 Heliodyne: first step would be to verify if that device works properly with a different computer May 03 18:51:17 if the beaglebone is running a sufficiently recent system, it should definitely be recognized May 03 18:51:50 certainly did when we programmed it and sent it out to customer (we use the BBB as a back-end for our solar controller) May 03 18:52:22 wait, do you really mean serial over usb, or networking over usb? May 03 18:52:54 because serial over usb should basically always work May 03 18:53:18 probably networking. just trying to do the typical mini-usb to usb connection to access 192.168.7.2 interface May 03 18:53:41 that's networking, not serial May 03 18:53:51 serial does not involve an IP address :P May 03 18:55:57 so, basically for networking over usb there are two choices: the usb-standard "CDC-ECM", and microsoft's non-standard priorietary RNDIS. Mac implements the standard, Microsoft doesn't give a shit about standards and only implements their custom RNDIS protocol, Linux pragmatically implements both May 03 18:57:00 for that reason, recent images from beagleboard.org actually expose themselves as a composite device that has two usb networking interfaces: one CDC-ECM and one RNDIS (in addition to the serial and mass-storage interfaces) May 03 18:57:58 OK May 03 18:58:02 if your firmware only exposes an RNDIS interface, then using it on Mac hosts may be problematic May 03 18:58:49 I would imagine that's the case, I'm unforturnately not the developer so I apologize ahead of time for redundant and silly questions that follow May 03 18:59:27 We have our MAC using customers install a horndis driver and a FTDI driver, I assume that indicates we're using the RNDIS interface? May 03 18:59:46 yes, and the ftdi driver is probably completely pointless May 03 19:00:23 I just tested one on an older OSX release and it worked just fine, so that tells me that the way newer versions of osx handle this communication is where my issue lies? May 03 19:00:42 are you using the latest HoRNDIS version? May 03 19:01:13 previously, no, but in troubleshooting this case I've tracked down the latest version and had the customer install and try again to no avail May 03 19:02:20 lol, I like how the official pronounciation of "HoRNDIS" is "horrendous" May 03 19:02:38 haha, I found that very appropriate as well May 03 19:02:45 shit's awful May 03 19:03:46 anyway, you can try digging around on their issue tracker, or if necessary make a new issue => https://github.com/jwise/HoRNDIS/issues May 03 19:04:15 that's pretty much all the advice I can offer May 03 19:04:58 forsure. Thanks for the help May 03 19:05:34 you by chance know what rel8 / reI7 is? May 03 19:07:24 presumably release 8 / release 7 (of HoRNDIS)? :P May 03 19:08:26 this is why i'm a mechanical engineer May 03 19:08:28 haha May 03 19:08:36 thanks May 03 19:10:25 good luck **** ENDING LOGGING AT Sat May 04 02:59:57 2019