**** BEGIN LOGGING AT Mon Apr 16 03:00:01 2018 Apr 16 10:29:46 anyone any ideas about what the beagle does to wake up from sleep? Apr 16 10:29:53 it takes quite a long time to wake up Apr 16 10:32:57 Hi. Do anyone have a pinout map for x15? I've bought an expantion connector, and trying to control the GPIO pins. Apr 16 10:34:33 https://github.com/beagleboard/beagleboard-x15/ - have you checked that? Apr 16 10:34:38 yes Apr 16 10:35:31 It says I need to check the pinout map, but there is none Apr 16 10:37:11 page 27 of the rev_1B pdf Apr 16 10:37:24 TonyTheLion: I don't recall it taking any noticable time to wake up, but it's been ages since I've done anything with suspend Apr 16 10:39:03 zmatt: from my measurements it takes at least 8 seconds Apr 16 10:39:08 Krissmaster: maybe my spreadsheet may also be of use -> https://goo.gl/jiazTL Apr 16 10:39:19 we need it to take no more than 1 max 2 secs Apr 16 10:39:32 TonyTheLion: that sounds ridiculously slow Apr 16 10:39:36 it seems it spends at least 3 secs recovering the USB/network interfaces Apr 16 10:39:44 don't know what the other time goes into Apr 16 10:39:52 dmesg is not very revealing otherwise Apr 16 10:40:39 ethernet will take a bit to get link up yet, although technically the system isn't in suspend anymore at that time Apr 16 10:40:56 *to get link up again Apr 16 10:41:13 Thanks zmatt. I will take a look at that Apr 16 10:41:15 actually, no that stays up during sleep Apr 16 10:41:15 also if it's DHCP it will depend on DHCP server performance Apr 16 10:41:41 TonyTheLion: which sleep mode are you using? Apr 16 10:41:46 standyb Apr 16 10:41:53 standby* Apr 16 10:43:43 that's the lightest sleep mode... that's really weird, it should be able to wake up from that essentially instantly Apr 16 10:44:16 which kernel? Apr 16 10:45:02 4.9.78-ti-r94 Apr 16 10:45:09 so there's a deeper sleep mode Apr 16 10:45:11 ? Apr 16 10:45:42 the only sleep modes I found were "mem" and "standby" Apr 16 10:45:50 also, how are you determining this time? time until it responds again via network, or until it responds again via serial console? Apr 16 10:46:03 ye ssh Apr 16 10:46:15 okay so maybe it's just the network manager being annoying Apr 16 10:46:26 seems plausible Apr 16 10:46:58 so to test it properly, I need to connect it over serial Apr 16 10:47:02 can you pastebin the dmesg output of a resume event? Apr 16 10:47:10 sure Apr 16 10:48:08 https://pastebin.com/i8GaLcun Apr 16 10:49:02 that's not much, maybe journalctl ? Apr 16 10:58:33 https://pastebin.com/CxdEpvk7] Apr 16 10:58:41 https://pastebin.com/CxdEpvk7 Apr 16 10:58:46 the latter one Apr 16 10:59:52 this looks to me like resume fully completed within a single second Apr 16 11:00:26 hmm so I guess I've been fooled by the network coming up taking a longer time Apr 16 11:01:07 it shouldn't though, I don't think network really goes down Apr 16 11:01:14 there's no link down message Apr 16 11:01:44 or maybe the ssh connection Apr 16 11:02:12 does the link go down? you should be able to tell by checking the leds on the ethernet connector Apr 16 11:02:28 if you rely on network being there instantly, you will need to take additional steps Apr 16 11:02:53 ah, finally found it... "mem" corresponds to deepsleep Apr 16 11:02:55 e.g. use networkd instead of network-manager. Or maybe connman, that could also be fast Apr 16 11:03:04 looks like he's using connman Apr 16 11:03:14 given the log message from connmand Apr 16 11:03:17 ok Apr 16 11:03:28 might still be possible to set options Apr 16 11:03:38 the leds go off on the network interface Apr 16 11:03:41 in standby Apr 16 11:03:59 so standby is the deeper sleep right? Apr 16 11:04:05 no, mem is deeper Apr 16 11:04:28 okay, so it deliberately disables the phy during sleep Apr 16 11:05:18 more of the other leds stay on during "mem" sleep Apr 16 11:05:26 the blue ones on the board Apr 16 11:05:27 huh Apr 16 11:05:38 which is why I thought it was not deeper than standy Apr 16 11:06:26 sounds like a bug causing some activity led(s) to not be disabled before entering deepsleep? weird Apr 16 11:07:47 what documentation did you find this what sleep corresponds to what cpu sleep state in? Apr 16 11:08:01 drivers/soc/ti/pm33xx.c Apr 16 11:08:29 is that the TI cpu api thingy? Apr 16 11:08:45 its not the on the beagle by default, is it? Apr 16 11:09:05 in the kernel 4.9-ti series kernel tree Apr 16 11:09:14 ah I see Apr 16 11:09:17 which you said you were using Apr 16 11:09:28 ye but I didn't compile this kernel Apr 16 11:09:50 I'm using whatever was on the device when I bought it Apr 16 11:10:32 yeah you're definitely not using the latest kernel in that series Apr 16 11:10:48 oh Apr 16 11:10:59 and do you have to manually compile the kernel to update it? Apr 16 11:11:04 of course not Apr 16 11:11:50 you can use apt to install a specific kernel, and there's also an update script somewhere in /opt that will look up the latest kernel within a series of choice and install that for you Apr 16 11:12:11 oh very nice Apr 16 11:12:51 latest in the 4.9-ti series is currently 4.9.88-ti-r110, and latest in the 4.14-ti series is 4.14.34-ti-r43 Apr 16 11:13:13 whats the difference between 4.9 and 4.14? Apr 16 11:13:28 if there's even a simple answer to that Apr 16 11:13:58 that 4.14 is about a year newer than 4.9 ? Apr 16 11:14:17 so really to have the latest we'd need to run 4.14 Apr 16 11:14:46 4.14 is the latest LTS kernel series (and -ti kernel series only use LTS kernels) Apr 16 11:15:49 btw depending on how old the system image on your beaglebone is, you may also want to consider reflashing it to the latest image... which is the easiest way to update things like the bootloader and such Apr 16 11:16:18 when using "whatever was installed" you never really know how old it is... although at least it's not ancient if it came with a 4.9 kernel Apr 16 11:16:35 I only bought it a month or two ago Apr 16 11:16:40 but ye you have a very good point Apr 16 11:16:58 it might have been sitting on a shelf for a while, etc Apr 16 11:17:11 exactly, they're not flashed right before shipping Apr 16 11:18:04 and fairly significant changes were made in the not-very-distant past Apr 16 11:28:27 anyway, I'm afk for now, back later Apr 16 13:23:25 hello, I have a silly question: where can I find documentation for constants used in sample code such as the constant "LOW" : var b = require('bonescript'); var state = b.LOW; Apr 16 13:25:00 I see this kind of syntax in many code samples but I cannot find any documentation on which constants are available for use Apr 16 13:28:02 that seems to be the source for bonescript: https://github.com/beagleboard/bonescript Apr 16 13:28:36 https://github.com/beagleboard/bonescript/blob/master/src/constants.js Apr 16 20:37:32 hi there channel :-) Apr 16 20:38:10 fortnight is been here? Apr 16 20:56:53 Hi Apr 16 20:57:11 I am unable to SSH to the beaglebone after flashing Apr 16 20:57:30 It seems like it is a know problem Apr 16 20:57:48 i am unable to understand the steps with older posts on google Apr 16 20:57:57 just double checking Apr 16 21:04:25 lasur2, apt-get install ssh Apr 16 21:04:56 as root, of course Apr 16 21:07:38 Thanks dury Apr 16 21:07:46 I will try that right now Apr 16 21:12:04 Hi Apr 16 21:12:31 I did sudo apt-get install ssh Apr 16 21:12:41 I still cant ssh to BBB Apr 16 21:12:44 Also Apr 16 21:13:24 BBB does not respond to Ping either Apr 16 21:14:20 I am on a VMware virthual manhine and flashed my BBB an hour ago Apr 16 21:15:08 did it install Apr 16 21:21:57 yes Apr 16 21:22:08 but I have same problem Apr 16 21:25:05 have to go getting late over here :-) Apr 16 21:35:47 Anyone have any information on how to use the 157 GPIO pins on the BB-X15? Apr 17 00:13:41 lasur2: your problem description is extremely vague. which image did you flash? how did you flash it onto the beaglebone? does it seem to be booting normally based on led activity? how are you trying to ssh to it? what posts are you referring to? Apr 17 00:14:21 right now the information you've given can basically be summarized as "it doesn't work" Apr 17 00:14:54 which is not something anyone can help you with in a useful wau Apr 17 00:14:56 *way Apr 17 00:15:53 if you're reading old posts, most likely they're talking about something completely different from whatever problem you're having Apr 17 00:22:53 anyway, time for sleep Apr 17 00:35:51 Jzaw Apr 17 00:35:57 are you still there Apr 17 00:36:02 I am sorry Apr 17 00:36:15 for the vague description Apr 17 00:36:27 but this seems to be a known problem Apr 17 00:37:08 Sorry , is that Zmat Apr 17 00:44:57 Here are some of the answers to your questions: Apr 17 00:45:18 which image did you flash? Ans: bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz Apr 17 00:45:27 how did you flash it onto the beaglebone? USing SD card Apr 17 00:45:37 does it seem to be booting normally based on led activity? yes it boots Apr 17 00:45:54 I can ping from Windows command prompt on 192.168.7.2 this works fine Pinging 192.168.7.1 works on windows command prompt Apr 17 00:46:04 192.168.7.2 on google chrome shows the BB homepage and connected higligted in green Apr 17 00:46:18 This was not happening yesterday, The new image flashing helped solve this Apr 17 00:46:31 how are you trying to ssh to it? what posts are you referring to? I have VMware virtual machine installed and have Ubuntu 16.04 installed Apr 17 00:46:46 From the VM, on dolloar prompt, I am trying to SSH ssh -l root 192.168.7.2 This was working earlier bt fails now after the image was flashed. Apr 17 00:47:06 I am looking at similar posts on google Apr 17 00:56:20 sudo ssh debian@192.68.7.2 Apr 17 00:56:43 lasur2: Use this ^ Apr 17 01:03:19 ok Apr 17 01:04:02 I will try Apr 17 01:04:52 Doesn't help Apr 17 01:05:04 As i said ping from $ prompt fails Apr 17 01:05:18 did you get your image from beagleboard.org/latest-images? Apr 17 01:05:53 USb0 connection is not seen if i use ifconig Apr 17 01:06:06 No I did not get it from latest images Apr 17 01:06:09 Try another usb. Apr 17 01:06:10 Oh. Apr 17 01:06:17 Where did you get this image file? Apr 17 01:07:01 Here is the link: https://debian.beagleboard.org/images/bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz Apr 17 01:07:09 Oh. Apr 17 01:07:12 That is old news. Apr 17 01:07:20 BBB is a part of my Z-wave controller development kit Apr 17 01:07:25 Try an updated version of the image. Apr 17 01:07:26 Oh. Apr 17 01:07:35 The above image was the recommended one by the techsupport Apr 17 01:08:11 I can't go with other images assomething else may fail Apr 17 01:08:21 If you go to BeagleBoard.org and see the Cape section of their site, it will show which Capes are supported. Apr 17 01:08:36 i.e. Official Capes. Apr 17 01:09:03 That 8.3 lxqt image is from a long time ago. Apr 17 01:09:18 circa 2016 like it stated. Apr 17 01:09:25 Iyes Apr 17 01:09:27 yes Apr 17 01:09:38 Two years ago...people were not maintaining the kernel all that well from what i heard. Apr 17 01:09:42 So, people moved on. Apr 17 01:10:10 Now, we, well at least me personally, use the Stretch images and beyond. Apr 17 01:11:05 Look here: https://beagleboard.org/latest-images are the "recommended" images. Apr 17 01:11:23 I typed recommended b/c up-to-date means current support. Apr 17 01:12:01 how do I know which one is the equivalent of what I want Apr 17 01:12:05 I can try Apr 17 01:12:12 If you do not want to get the "newer" images, finding people may be hard on you. Apr 17 01:12:14 Oh. Apr 17 01:12:33 LXQT is now LXDE. I think. You want a GUI, right? Apr 17 01:12:55 no GUI Apr 17 01:12:59 oh. Apr 17 01:13:02 i guess Apr 17 01:13:20 Get the console image, instead. The GUI is the LXDE. Hold. I will go and look. Apr 17 01:13:35 I will Apr 17 01:13:38 i am here Apr 17 01:13:49 LXQT is the GUI and IoT is w/out the GUI. Apr 17 01:13:59 Sorry for the mix up. Apr 17 01:14:41 Your image you were booting off of stated LXQT. I would assume that you can use that still. Apr 17 01:15:49 So, use the recommended image for SD Card on beagleboard.org/latest-images or here: https://beagleboard.org/latest-images. Apr 17 01:16:18 ... Apr 17 01:16:54 9.3 (Stretch) LXQT is w/ the GUI. I am sure you can get more and more current support from this image compared to other images. Apr 17 01:17:21 Ok I will try Apr 17 01:17:40 They have forums on Adafruit.com too. Their BeagleBone type option has people w/ ideas and needs. Apr 17 01:17:55 I will be in tomomorrow around this time Apr 17 01:17:59 Oh... Apr 17 01:18:02 Hold on. Apr 17 01:18:05 Before you go. Apr 17 01:18:22 Um, forget it. I totally forgot. Apr 17 01:18:30 Did you find that image? Apr 17 01:18:48 the 9.3 LXQT? Apr 17 01:19:35 I found the same image bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz Apr 17 01:19:40 no its 8.3 Apr 17 01:19:46 lasur2: I will be here as usual. Oh and maybe there are others that might be here as well. Who knows? There are a lot of people that know more than me. Apr 17 01:19:52 Use 9.3. Serious. Apr 17 01:20:13 ok thanks Apr 17 01:20:15 They have it set up w/ an easier way of controlling GPIO, Capes, and other ideas revolving around the BBB. Apr 17 01:20:35 ok i understand Apr 17 01:20:41 I think they may have put in a lot of time on the current images. Apr 17 01:20:43 Yea! Apr 17 01:21:08 lasur2: Okay then...I guess I will try to see you tomorrow. I cannot wait to hear how this goes. Apr 17 01:21:47 lasur2: Are you using etcher to flash the image(s)? Apr 17 01:21:59 yes Apr 17 01:22:05 Se Apr 17 01:22:05 Good news. Apr 17 01:22:07 Set Apr 17 01:22:16 I have this last question Apr 17 01:22:21 Shoot Apr 17 01:22:53 I see that 9.1 has the same name ending with LXQT Apr 17 01:23:10 but 9.3 has a name ending with 4GB IoT Apr 17 01:23:44 So I was wondering if it was still the same or not Apr 17 01:23:52 9.3 (Stretch)...it is their most current, supported image they have. I think this is correct. BBB.io! LXQT is the GUI. IoT is the console image. Apr 17 01:24:11 ok Apr 17 01:24:11 IoT = not GUI Apr 17 01:24:20 ok Apr 17 01:24:21 LXQT = GUI Apr 17 01:24:25 Yea! Apr 17 01:24:31 ok great Apr 17 01:24:33 That is really the difference. Apr 17 01:24:48 I will try and talk to you tomorrow Apr 17 01:24:54 thanks so much !! Apr 17 01:24:54 Cool beans. Apr 17 01:24:58 No issue. Apr 17 01:25:24 Okay...Manana! **** ENDING LOGGING AT Tue Apr 17 03:00:05 2018