**** BEGIN LOGGING AT Thu May 17 03:00:02 2018 May 17 03:25:54 Hi all May 17 03:34:43 I've been using my bbb via SSH and things were great, not sure what it is I did but that is not possible anymore May 17 03:35:28 it is running the latest debian image May 17 03:50:12 I hope you're not expecting anyone to be able to diagnose your bbb based on that information :) May 17 03:50:57 No i don't expect anyone to but I would not know where to start at the moment May 17 03:52:42 check serial console, or boot from sd card and try to diagnose the system May 17 03:58:19 Booting from SD card sounds like a good approach, thank you. Just to clarify though, booting from SD card does not mean erasing existing image? May 17 04:03:11 uhh no, unless you boot a flasher May 17 04:03:36 but for example the images at bbb.io/latest are all fine May 17 04:04:02 thank you zmatt May 17 09:58:33 show-pins, excellent program zmatt May 17 09:59:41 which touch lcd display do you suggest for bbb rev c May 17 09:59:43 ? May 17 11:46:20 no idea May 17 13:22:46 hello everyone May 17 13:23:15 is it possible to connect an external antenna to the beaglebone black wireless (i want to put it into a metal enclosure) and if so, can someone recommend one? May 17 14:45:59 sgflt: I don't have any specific recommendation, but certainly you can. just detach the default antennas and connect suitable micro-coax cables to external antennas. (if you want to have only one, you'll need to check which one is the primary and make sure the driver is configured to disable the other antenna) May 17 16:19:31 Hi! need help regarding the use of nano command in BBB rev C May 17 16:19:37 zmatt: thanks May 17 16:20:14 also, can the adc inputs survive brief overvoltage of 10-15%? (2.0-2.1V)? May 17 16:20:27 getting error message:: error reading lock file.....:not enough data read May 17 16:22:50 what are you trying to do? May 17 16:25:22 tried creating a new file using nano speedcal.py May 17 16:25:45 Till now the no. of files in BBB are 7 each of 1 or 2 KB size May 17 16:28:52 well that shouldn't pose a problem May 17 16:31:35 @tbr: So why is it giving a msg of "error reading lock file", even when creating it for the first time. May 17 16:33:30 https://askubuntu.com/questions/939527/getting-error-while-opening-etc-profile May 17 16:33:53 is there still another nano process running? May 17 16:34:03 if not, remove the swp file May 17 16:36:29 how do I remove the other nano process ? Is it also related to emptying the cache? May 17 16:37:18 sgflt: I would be nervous, but the abs max ratings in the datasheet give a "transient overshoot and undershoot specification at IO terminal" of "25% of the corresponding IO supply voltage for up to 30% of signal period" May 17 16:37:33 sgflt: of course those are abs max ratings, not recommended operating conditions May 17 16:38:51 stan: "pkill nano" for example, but you'll need to remove the swap file too May 17 16:39:43 zmatt: i have some 4-20 mA, which might output 24+ mA while firing up. i have some schottky-diodes for safety, but those have a forward voltage of about +0.22 V or so May 17 16:45:12 @tbr: do we have remove all the .swp files ? Could plz tell the command ? May 17 16:46:29 stan: if no nano process is running, then it's safe to remove those May 17 17:15:59 Still getting the error "error reading lock file" when creating a new file May 17 17:28:19 @tbr:Still getting the error "error reading lock file" after deleting all swp files and killing nano processes May 17 17:37:01 stan: no idea. might be something specific to what you are doing May 17 18:16:27 out of space on eMMC ? May 17 19:29:15 @zmatt: getting this error - IOError: [Errno 16] Device or resource busy. As discussed yesterday we used pull up resistor of 4.7 Kohm between SDA & 3.3V and SCL & 3.3V May 17 19:29:38 what does the kernel log say? May 17 19:29:55 How to check the kernal log? May 17 19:30:08 dmesg or journalctl -k -b May 17 19:30:37 it says, time out waiting for busy May 17 19:30:51 sorry, waiting for bus ready May 17 19:32:00 Kernel command line: console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait cohe Nov 03 17:16:43 beaglebone kernel: PID hash table entries: 2048 (order: 1, 8192 bytes) May 17 19:33:42 any idea about the issue, I am trying all the possibilities to make it work May 17 19:33:48 then the driver thinks the i2c bus is in use May 17 19:34:10 which kernel version are you using? May 17 19:34:30 How would I know about it? May 17 19:34:38 uname -r May 17 19:34:56 4.9.82-ti-r102 May 17 19:36:57 Anything else, I would check for the sensor? May 17 19:37:21 okay, then the only plausible reason is that the sda or scl pin is held low (hardware problem), or perceived as low (pinmux problem) May 17 19:37:45 measure voltage on the pins to confirm they're high May 17 19:38:07 use my show-pins script to double-check the pinmux: https://github.com/mvduin/bbb-pin-utils/#show-pins May 17 19:38:56 I'm afk for a bit, will be back later May 17 19:39:55 Ok, May 17 19:40:03 Sure May 17 20:12:25 @zmatt: u there? Measured the voltage on the sda and scl pins. it is showing 3.3V May 17 20:20:38 stan: please don't send private messages May 17 20:22:59 (I'm still kinda afk, but I'll be back soon. meanwhile, did you check pinmux?) May 17 20:41:41 Hello all - I've been having trouble connecting my BB to internet. I can SSH to it over ethernet cable, but it won't ping any non-local IP May 17 20:43:01 it will ping my desktop through my desktop's local ethernet IP and its WiFi IP May 17 20:44:21 did it get a default route from the dhcp server? (check with "ip route") May 17 20:44:48 ip route gives a number of entries May 17 20:44:54 should I copy/paste them here? May 17 20:45:03 never copy/paste into irc May 17 20:45:15 use a paste service like pastebin.com (or one of the many others) May 17 20:45:20 OK, one sec then May 17 20:45:26 a default route starts with "default via" May 17 20:45:50 https://pastebin.com/PeAmuxq2 May 17 20:46:02 the default is: default via 192.168.0.1 dev eth0 May 17 20:46:10 that is my router's IP May 17 20:46:14 okay, so it has a default route May 17 20:46:25 and ping -n 8.8.8.8 fails? May 17 20:46:35 yes May 17 20:46:41 what does it say? May 17 20:47:17 seems to hang at 'PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.', then Ctrl-C gives 37 packets transmitted, 100% packet loss May 17 20:47:53 hmm May 17 20:48:28 more info: it isn't connected to my desktop via USB (only connections are power, ethernet, and serial) May 17 20:49:15 can it resolve names? i.e. 'host google.com' ? May 17 20:49:45 ;; connection timed out; no servers could be reached May 17 20:49:50 I was wondering what those 68.105.* entries were, but they seem to be dns servers... of your provider presumably May 17 20:50:16 are those ips in /etc/resolv.conf ? May 17 20:50:49 The three 68... IPs are, yes May 17 20:51:30 okay May 17 20:51:31 hm May 17 20:52:17 so... it got a dhcp lease, which proves it can talk to your router May 17 20:53:04 maybe check if there are weird firewall rules in place for some reason? there shouldn't be, but if that's not it then I'm leaning towards "some odd problem with your network or router" May 17 20:53:34 iptables -L lists firewall rules May 17 20:54:27 https://pastebin.com/0bqBmtrL May 17 20:54:41 this is when I enter that command while SSH'ed in to the device May 17 20:54:54 i.e. no firewall rules May 17 20:55:59 @zmatt: couldnt check pinmux. We have internet restrictions in our lab. The pins are high since voltage is 3.3V always. Any other suggestions? May 17 20:56:11 I'm also looking at router settings. Nothing under port forwarding/triggering, nothing active under IP filtering May 17 20:56:36 I have an address reservation for my device's MAC address to an internal IP address May 17 20:56:43 stan: your restrictions are your problem, not mine :P May 17 20:58:08 sscirrus: is it the same ip address that the beaglebone actually has? (i.e. 192.168.0.123 ) May 17 20:58:18 (I've seen pretty confused routers) May 17 20:58:25 yes May 17 20:58:57 well May 17 20:58:59 ¯\_(ツ)_/¯ May 17 20:59:04 haha May 17 20:59:18 time for packet sniffing maybe? May 17 20:59:24 I'll try deleting everything specific my router has on the BB and restarting both May 17 20:59:51 generally there's no good reason to hard-assign IPs. just use hostnames May 17 21:01:03 stan: like I said, the i2c peripheral sees scl and/or sda low. since your pins are high, that means the main suspect is pinmux May 17 21:01:13 (also maybe double-check you really have the right pins) May 17 21:02:12 my show-pins script is the best tool I know of for inspecting the current pinmux configuration **** ENDING LOGGING AT Fri May 18 03:00:03 2018