**** BEGIN LOGGING AT Wed Dec 13 03:00:02 2017 Dec 13 05:26:32 day 2 with Beaglebone Black Wireless -- still unable to connect to wifi. I'm logged in, run 'sudo connmactl', then 'enable wifi' returns "Error wifi: Method 'SetProperty' with signature 'sv' on interface 'net.connman.Technology' doesn't exist". What does this mean? Dec 13 05:28:19 I tried what zmatt suggested yesterday: "head -c 32 /sys/bus/nvmem/devices/0-00500/nvmem | hexdump -C". He said bytes 12-15 should be 42 57 41 35 ("BWA5") but I don't see those numbers. Dec 13 05:29:53 so I followed some directions that said ground TP1 and run "dd if=/opt/scripts/device/bone/bbbw-eeprom.dump of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom" Dec 13 05:30:37 rebooted and nothing seemed to change. Dec 13 05:33:01 Am I missing something or is my board messed up? Dec 13 05:33:33 maybe a better question: Am I messed up or is my board missing something? Dec 13 05:38:14 using the recommended latest debian image 9.1-lxqt-armhf-2017-08-31 Dec 13 05:47:36 when I run /opt/scripts/tools/version.sh i get "eprom:[A336BNLT?0" but the question mark is highlighted like an unrecognized character. Dec 13 05:47:59 ohh Dec 13 05:48:09 sounds like you may have one with misprogrammed eeprom Dec 13 05:48:19 this is a known problem Dec 13 05:48:53 and your attempt to fix it was unsuccessful I'd say Dec 13 05:49:23 maybe go SD card Dec 13 05:49:25 oh wait you're the same person as earlier, sorry, just noticed what you said, lol Dec 13 05:49:39 lol. Dec 13 05:49:45 Life_Is_A_Bone: ? Dec 13 05:49:48 mbrr: I Dec 13 05:50:18 mbrr: my guess would be that you failed to ground TP1 properly (and keep it grounded during the write) Dec 13 05:51:33 while it is grounded, the eeprom is writable (and any writes are immediately reflected when you read the eeprom again) Dec 13 05:51:53 okay. I have a wire going from TP1 to a metal table. Do i need to actually solder it for a good connection? Dec 13 05:52:15 lol, no you need to use a ground pin of the BBB, not a random metal object Dec 13 05:52:47 aah. Dec 13 05:53:08 what is the difference? just curious? Dec 13 05:53:12 any of the pins marked "DGND" in this diagram: http://beagleboard.org/static/images/cape-headers.png Dec 13 05:54:35 the difference is that there's no electical path between your table and the ground of the beaglebone Dec 13 05:54:54 basically you just attached a large table-shaped wire to the TP1 pin, but that wire still doesn't connect to anything Dec 13 05:55:39 I thought ground was just like an electrical dump for receiving discharges. That must not be the case... Dec 13 05:55:48 no Dec 13 05:56:06 to be fair, ground is a term with Dec 13 05:56:11 to be fair, ground is a term with multiple related meanings Dec 13 05:56:53 okay. so I connect the wire to a dgnd pin and tp1 and ran that same dd command. Dec 13 05:57:19 double-check the contents of the eeprom before rebooting Dec 13 05:57:29 since as long as you haven't rebooted, you can still fix problems Dec 13 05:57:40 that is the version.sh? Dec 13 05:57:46 or my command Dec 13 05:57:52 either is fine Dec 13 05:58:23 this is promising. no more weird ? character. Dec 13 05:58:52 eeprom:[A335BNLTBWA50000BBWG*] Dec 13 05:59:29 looks like you may be good to go :) Dec 13 06:00:28 fingers crossed while i reboot. thanks for your help 2x Dec 13 06:06:01 booted up again but connmanctl>enable wifi gives the same error and iwconfig shows no wlan device Dec 13 06:06:11 that's weird Dec 13 06:06:57 can you pastebin the output of head -c 32 /sys/bus/nvmem/devices/0-00500/nvmem | hexdump -C Dec 13 06:10:33 yes but first, am I supposed to remove the SD card that I flashed debian onto? Dec 13 06:10:41 doesn't matter Dec 13 06:11:13 is it running of off internal storage? Dec 13 06:12:16 PCMan FileManager shows rootfs as a connected device. that seems wrong Dec 13 06:12:42 if you boot from sd card, it's running from sd card Dec 13 06:12:51 otherwise it'll run from internal eMMC Dec 13 06:13:33 I just flashed the SD card with the debian image, stuck it in, and booted. and have been booting Dec 13 06:13:43 then you've booted from sd card Dec 13 06:18:25 https://pastebin.com/wh9A9dma Dec 13 06:27:26 hm, that looks fine to me Dec 13 06:27:34 there's no wlan0 interface visible when you check: ip link Dec 13 06:27:35 ? Dec 13 06:28:36 nope. 1 lo, 2 eth0, 3 & 4 usb Dec 13 06:28:51 that's really bizarre Dec 13 06:29:39 :/ Dec 13 06:30:18 might I have received a beaglebone black in a bbbw box? Dec 13 06:30:27 they look completely different Dec 13 06:30:32 well Dec 13 06:30:57 nvm. says wireless on the bottom Dec 13 06:31:14 https://beagleboard.org/static/images/BeagleBoneBlackWireless_A3.jpg Dec 13 06:31:19 https://beagleboard.org/static/ti/product_detail_black_lg.jpg Dec 13 06:31:49 the presence or absence of an ethernet connector is a rather obvious difference Dec 13 06:32:23 yeah. it has the 2 antenna Dec 13 06:32:30 that too Dec 13 06:32:46 which image did you flash to sd card? try booting from eMMC instead? Dec 13 06:33:23 I flashed the latest debian gui from 3-31. So just remove the SD and boot? Dec 13 06:33:50 2017-03-31 ? that sounds pretty old Dec 13 06:34:27 it was the newest GUI versionon the /latest-images site Dec 13 06:34:34 btw unless you specifically need a desktop gui, I'd recommend the iot image Dec 13 06:35:15 Will the IoT image boot to a terminal window if I connect a monitor or strictly SSH? Dec 13 06:35:41 it'll still have a commandline login on hdmi Dec 13 06:35:47 just no gui Dec 13 06:36:40 Okay. well I have that image on a different SD card already because I tried messing around with it earlier. should I try the eMMC first? is that just booting after I remove the SD? Dec 13 06:36:49 yes Dec 13 06:36:59 power off, remove card, power on Dec 13 06:48:02 okay. when I boot without an SD card the GUI looks a little different and now 'ip link' shows wlan0 Dec 13 06:51:03 and we're online. thank you zmatt! Dec 13 07:00:13 okay so something weird going on with the image you flashed to sd card (or maybe due to a change you made while trying to fix your problem?) Dec 13 07:01:30 my suggestion would be to just reflash eMMC with the latest iot image (generally whatever is on eMMC when shipped is not particularly recent)... you can do so by flashing an sd card and then uncommenting one line in its /boot/uEnv.txt Dec 13 07:02:18 the gui image tends to leave very little free space on eMMC, which is not a good thing Dec 13 07:02:25 okay. /boot/uEnv.txt in the root SD card after I flash it? Dec 13 07:03:27 thanks again. Dec 13 07:12:09 yeah, there's one commented line in there with something-something-eMMC-flasher, it shouldn't be hard to find Dec 13 11:13:13 hi Dec 13 11:14:33 can any one share the IRQ based GPIO Status monitoring example code for BBB ? Dec 13 12:28:25 raviteja: you mean for the sysfs gpio interface? I might have an example for that somewhere... Dec 13 12:30:32 yes Dec 13 12:30:48 could you pls. share Dec 13 12:32:01 i just tired this code but still i am not getting any chages at out put side. can any one help on this Dec 13 12:32:13 #include #include #include #include #define A 0 #define B 1 void dump_value(int fd) { char buffer[1024]; lseek(fd, 0, 0); int size = read(fd, buffer, sizeof(buffer)); buffer[size] = NULL; printf("\t\t size: %d buffer: %s\n", size, buffer); } void dump_event(int fd, struct pollfd *pfd) { short revents = pfd->revents; printf("rev Dec 13 12:34:12 sorry.. i gone through this below link.. example code Dec 13 12:34:31 https://bwgz57.wordpress.com/2012/04/15/beaglebone-gpio-irq/ Dec 13 12:37:59 please don't paste multiline text into chat Dec 13 12:38:06 it results in a mess and gets truncated Dec 13 12:38:50 that code looks fine to me Dec 13 12:40:00 (could be more efficient) Dec 13 12:46:37 did you configure your pins as described in the article? have you confirmed that you can see the gpio change value? Dec 13 12:50:55 yes i did the same and i connected to P8_45 & P8_46 (70,71). Dec 13 12:57:40 zmatt. i got the out change Dec 13 12:57:47 output Dec 13 12:58:09 I'm not sure what you mean by that Dec 13 12:58:18 i changed the gpios to 50 & 60th pin then i got changes Dec 13 13:02:00 the above link example code i tested with the P9_12 & P14_14 (60,50), then i got the changes in output side Dec 13 13:02:36 P9_14 Dec 13 13:43:38 Recommened X15 supply discontinueed at Digikey: https://www.digikey.com/product-detail/en/VEF65US12/1470-2300-ND/4488679 Dec 13 13:47:13 Crofton|work: so what about this one? https://www.digikey.com/product-detail/en/xp-power/VEC65US12/1470-3102-ND/5726822 Dec 13 13:55:39 Just pointing out the wiki points to one that is discontinued Dec 13 13:57:20 the replacement has even less standby power consumption Dec 13 13:58:39 so update the wiki? Dec 13 14:01:18 fixed Dec 13 14:01:39 bonus points for anyone that can point me at a cable I can use with a bench power supply :) Dec 13 18:34:13 does some 1 has wroking code for reading MPU6050 as bonescript or something else? Dec 13 20:35:12 "callback is not a function" someone? Dec 13 21:15:30 literally what it says... the callback function provided was not actually a function Dec 13 21:47:14 Could someone confirm this would work with an X15? https://www.digikey.com/product-detail/en/tensility-international-corp/10-01935/839-1249-ND/5638259 Dec 13 23:57:58 We fried 2 Beaglebones in a row and I do not know how running a motor through a motor driver board can do that :( Dec 14 00:28:30 I can think of roughly a dozen ways Dec 14 00:29:32 can you sketch up a schematic showing how the motors and motor power supply were connected to the driver board, how the beaglebone was powered, and the gauge of wire used for each such connection? Dec 14 00:29:43 also a link to the driver board would be helpful Dec 14 02:01:21 help Dec 14 02:01:49 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ^C --- 8.8.8.8 ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9073ms Dec 14 02:38:58 anyone happen to know the part # for the soc on the raspberry pi zero w ? Dec 14 02:39:13 I know its an elpida ic but can't seem to find the part Dec 14 02:40:36 * myself taps gently on his IRC client, as it seems to be displaying the wrong channel name... Dec 14 02:41:11 huh. Dec 14 02:41:51 :) **** ENDING LOGGING AT Thu Dec 14 03:00:00 2017