**** BEGIN LOGGING AT Fri Aug 11 03:00:01 2017 Aug 11 03:16:12 success! Aug 11 03:16:20 * MrCurious stops laying in wait Aug 11 03:18:27 ok so what was it? d'oh moment? Aug 11 03:19:10 pretty much, seem it comes default configured with /boot/uEnv.txt lacking a dtb=beaglebone-blue-something-something line Aug 11 03:19:22 looked in boot/dtbs/*/ Aug 11 03:19:25 and it clicked Aug 11 03:19:49 re-testing now with scanse.io lidar on uart2 using GPS port Aug 11 03:21:40 and it works! Aug 11 03:25:31 dtb=am335x-boneblue.dtb Aug 11 03:25:42 that was the secret sauce for /boot/uEnv.txt Aug 11 04:02:49 uhhh, that should not be necessary Aug 11 04:03:16 if dtb= is omitted then u-boot will use the correct default, unless the board eeprom has been misprogrammed Aug 11 04:03:53 i have 3… tried with 1 that was fresh out of the box Aug 11 04:04:12 uart2 would not work until i added the line Aug 11 04:05:48 can you pastebin a kernel log when booted with dtb left unset in uEnv.txt ? Aug 11 04:06:22 I know that with the bbb wireless there have been production problems with misprogrammed eeproms, I wonder if that's happening again with the blue Aug 11 04:08:56 booting the 2 boxed ones to find which is virgin, then will pastebin a dmeg for you. give me 10 minutes Aug 11 04:14:58 https://pastebin.com/8SMB9ZUj Aug 11 04:15:09 zmatt: ^^^^ Aug 11 04:15:50 the ports show up in dmesg, but no /dev/ttyOx shows up. add in that line, and those dev's appear Aug 11 04:16:03 line 8 shows it is in fact using the boneblue dtb Aug 11 04:17:40 it says it… checking now if the ttyOx dev's are there and i grabbed the wrong board Aug 11 04:23:45 ok, you are right, comes out of the box working. must have been something i did following the EduMIP instructions Aug 11 04:24:05 guess they are not just not compatible, but following them disadvantages you... Aug 11 04:28:33 i need to look into these 2 boards more tomorrow, find the one i didnt install tio on, then test again Aug 11 04:59:38 suppose if i were creating image for BB blue. i would include a readme or web page or exported usb file system that said "all ports are configured to work." Aug 11 06:54:13 when I run connmanctl command in my BBB, it shows command not found Aug 11 06:54:25 any help with this please? Aug 11 06:58:30 connmanctl: command not found Aug 11 07:25:17 how can i know what IP could have a "blind" BBB (it is'nt displaying anything on HDMI or LCD cape) so i can try to SSH it? Aug 11 11:28:52 MrCurious: The GPS port on Blue is ttyS2 (or ttyO2): https://github.com/beagleboard/beaglebone-blue/wiki/One-Liner-Module-Tests#GPS Aug 11 13:57:54 Do you ever tried to measure mains voltage with Ain inputs ?? Aug 11 13:59:28 I cannot find an affordable ac to dc voltage scaler (to scale down 230Vac to around 1-1.5 Vdc Aug 11 14:00:41 Ain readings are unstable, while DC voltmeter at Ain input is..... Aug 11 14:47:24 jkridner: i think something got goofed when i installed edumip. i couldnt get tio screen to read from ttyS2 until i added a dtb= line into the uEnv.txt Aug 11 14:48:15 well, I screwed up on one of the versions of the .dtb. 'perl /opt/scripts/device/bone/show-pins.pl -v' is helpful. Aug 11 14:49:23 and that just went into my notes file :) Aug 11 15:04:06 i'm trying to build and deploy a linux distro to an sdcard using yocto. my yocto build completes successfully and provides a .sdcard file in the deploy directory. Aug 11 15:04:13 according to the last section here, "FLash SDCard Image", https://github.com/Freescale/Documentation/wiki/Build-and-Flash-the-SD-card-Image, all i have to do is dd the .sdcard image over Aug 11 15:04:20 dd if=imagename-imx53qsb.sdcard of=/dev/sdb Aug 11 15:04:28 will this dd automatically setup all the correct partitions and file system types (e.g., ext4)? Aug 11 15:11:20 yates: dd does a bit level copy from source (if=) to destination (of=) Aug 11 15:14:21 so it depends on wether Yacto created disk image files or something else. If the instructions for yacto suggest that dd line then they are probably creating a disk image Aug 11 15:15:19 But if those docs are about othe sdcard images then it may not Aug 11 15:15:30 gparted shows the first partition is unallocated of size 4 MiB, the second partition if a fat16 fs of size 8 MiB, and the third partition is ext4 fs of size 628 MiB. there is final fourth partition "unallocated" of size 13.83 GB Aug 11 15:15:38 You'll have to find out what Yacto is outputing Aug 11 15:15:45 Yacto? ha Aug 11 15:16:27 yocto :) Aug 11 15:16:37 sounds about right Aug 11 15:17:17 yeah. Aug 11 15:17:54 MLO and such would live in the first unallocated bit Aug 11 15:25:01 tho neither of my ianges have the FAT partition. That sounds more like A RPi type layout Aug 11 15:25:23 But I have no experience with Yocto Aug 11 15:30:16 Just getting started on a Green Wireless so assume I know nothing. :) Trying to play with the usr LEDs. By default they are blinking in a set pattern. 0,2 on 1,3 off, oscillating at about 1Hz. How can I figure out what is triggering this pattern? I checked the platform/leds/leds/beaglebone:green:usr*/trigger files and they are all set to [none]. Aug 11 15:31:32 AndrewC_: /sys/class/leds/beaglebone\:green\:usr*/trigger should say Aug 11 15:31:56 It says a lot and I don't know how to interpret it: Aug 11 15:32:03 oh, you know, I bet wifidog is toggling them. Aug 11 15:32:04 AndrewC_: The green Wireless includes a node script that does that wired flashing Aug 11 15:32:09 have you configured your wifi? Aug 11 15:32:09 [none] rc-feedback kbd-scrollock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock nand-disk usb-gadget usb-host mmc0 mmc1 mmc2 timer oneshot heartbeat backlight gpio default-on rfkill0 phy0rx phy0tx phy0assoc phy0radio Aug 11 15:32:29 and buggers up trying to play with them Aug 11 15:32:29 userspace stuff can be a bit unmanaged in Linux-land. Aug 11 15:33:17 Yep wifi is configured. Aug 11 15:33:32 You can delete or move that nodejs script I just cant ermember where it lives Aug 11 15:33:42 I think https://groups.google.com/forum/#!topic/beagleboard/oml2QLmRADs describes the same LED pattern. Aug 11 15:33:54 so, that's the wifidog pattern. Aug 11 15:34:36 connect to your board's SSID and configure the wifi connection, then it'll stop pestering you. Aug 11 15:34:59 rcn-ee didn't like wifidog, so it never landed on the non-green boards. Aug 11 15:35:17 On My green it was just a lets make the leds blink pretty script that the green wireless includes Aug 11 15:35:24 Ok that makes sense, I figured some process was mucking with them. Aug 11 15:35:32 we get a lot of requests for something similar for Blue/Black-Wireless, but haven't landed on a widely approved solution. Aug 11 15:35:41 It was one of my early search and destroy missions :) Aug 11 15:35:51 freemor: :-) Aug 11 15:36:35 Hehe yeah kinda regretting going with the BBGW but I'm stuck with it for now. Aug 11 15:37:03 But then stock images had a lot of stuff I didn't need Aug 11 15:37:41 They're nice once they are sdet up Aug 11 15:38:09 Talking to you fom one right now in while having a coffe in a local cafe Aug 11 15:40:59 freemor: :-) Aug 11 15:41:18 yep it's pretty sweet Aug 11 15:43:07 It just take a bit of learning and configuring.. but The process of configuring it definitely helps learn about how things are set up Aug 11 15:43:50 But that led blink script is annoying at first Aug 11 15:44:02 Yeah still trying to find where to turn it off. Aug 11 15:45:05 ok it's in a folder that nodejs uses for scripts that it should start when nodejs starts up Aug 11 15:45:36 if you are ssh'd in you could try sudo systemctl stop nodejs Aug 11 15:46:17 which will stop NodeJS for the time being and that should stop the blinking Aug 11 15:47:27 Ok tried that, got "Failed to stop nodejs.service: Unit nodejs.service not loaded." Aug 11 15:48:59 Hmm BBGW definitely starts node at start.. must be named slightly diffrent the what I typed Aug 11 15:49:15 the need it for cloud9, nodered, etc Aug 11 15:50:17 Wish I had my other BBGW handy. the image on this one is so not stock anymore that It's a bit hard to help Aug 11 15:53:50 try systemctl stop bonescript Aug 11 15:54:21 and maybe systemctl stop bonescript-autorun Aug 11 15:54:29 Ok, no output from that command and the LEDs are still blinking. Aug 11 15:54:51 Same result for the second command. Aug 11 15:55:02 These things just won't die. :) Aug 11 15:55:13 and maybe systemctl stop nodered Aug 11 15:55:20 lol Aug 11 15:55:57 I should have made a wiki as I went though all that the first time :) Aug 11 15:57:25 Ok I tried brute force and started killing procs. Killing "npm" stopped the blinking. Aug 11 15:57:59 I've gotta run... there are others in here that have BBGWs and have killed that same script. It is definitely a nodeJs or noderedc auto start script Aug 11 15:58:37 Thanks freemor! Aug 11 15:58:40 That I do remember Aug 11 15:58:43 Yw Aug 11 15:58:53 Enjoy your leds :) Aug 11 16:01:27 So anyone know why npm would be blinking my usr LEDs? Aug 11 17:20:07 Ok just FYI, I think I figured out the blinking LED on the Beaglebone Green Wireless. There are calls to led.on("start"/"ok"/"error") in /usr/local/lib/node_modules/wificonfig/lib/wifi.js. Commenting them out and rebooting stopped the blink pattern. Aug 11 17:20:24 How annoying. Aug 11 18:04:59 Anyone know how to read the value of this heart rate sensor? I'm trying to get it via python and Cloud9 (for now). http://wiki.seeed.cc/Grove-Finger-clip_Heart_Rate_Sensor_with_shell/ Aug 11 18:05:49 It's a Grove device plugged into the Green Wireless onboard I2C grove connector. Aug 11 18:19:39 h Aug 11 18:19:51 (Sorry, wrong window.) Aug 11 18:23:40 AndrewC_: make sure it's in the correct grove port. (the i2c one) then use Pythons i2c libraries. Aug 11 18:26:51 there are come code examples on the page you linked. important facts are: Read a byte from I2C device 0xA0 (8 bit address), it’s the heart rate. Aug 11 18:29:19 Ah ok, got it now. Had to install python-smbus module and then I could use the Adafruit_I2C module. Aug 11 18:29:43 And had to shift the 0xA0 by 1 (to 0x50) to get the address they want. Aug 11 18:32:54 ...and is your heart beating? :) Aug 11 18:34:16 the i2cget command may be useful for testing Aug 11 18:36:25 Aye, heart is beating. :) Aug 11 18:36:44 Good to know :) Aug 11 18:36:47 Although when I take the sensor off, it keeps reporting the oldest value. Not particularly useful... Aug 11 18:39:19 add a microswitch that gets depreddes when worn.. connect to one of the P headers.. and check programmactically to see if the value is good or if the sensor is floating in the air? Aug 11 18:40:14 Yeah I need to find the schematic or read up on the parts on this sensor, see what it thinks it is doing. Aug 11 18:40:55 what sensor is this? Aug 11 18:41:12 http://wiki.seeed.cc/Grove-Finger-clip_Heart_Rate_Sensor_with_shell/ Aug 11 18:42:59 heh optical Aug 11 18:43:03 $24?! Aug 11 18:43:49 i am guessing all you have to do is read the HR over I2C? Aug 11 18:44:23 AndrewC_ is annoyed that it still reports last value when removed Aug 11 18:45:34 ds2 Yup, that's all I'm doing for now. Although it apparently has updatable FW via a serial interface. Aug 11 18:46:22 AndrewC: Have you seen the MAX30003 modules? have to do some processing but it gives you more control Aug 11 18:48:27 Nah I was just looking for something simple I could connect via Grove connector. Just playing around with it for now, not making a product out of it. Aug 11 18:49:49 and now you can check your cats HR and your buggies, and see how they change when the cat gets close to the buggie.. loads of fun. :) Aug 11 18:49:52 I do find it frustrating that Seeed went to the trouble of creating BBG and BBGW (presumably so they could sell more Grove modules) but then don't have sample code for making those Grove modules work with the Beaglebones. ;) Aug 11 18:55:44 depends on what you want to play with Aug 11 18:55:57 the raw data is interesting from an analysis standpoint Aug 11 18:57:14 Oh nice, they provide the schematic. Aug 11 18:57:34 There's an "eagle file" link that has it in PDF format. **** ENDING LOGGING AT Sat Aug 12 03:00:00 2017