**** BEGIN LOGGING AT Sun Feb 10 02:59:56 2019 Feb 10 03:00:04 with a bit of luck, the inverter can also do the level shifting for you Feb 10 03:00:09 That is what I thought but that is only for the Rasp. Pi I think Feb 10 03:00:18 no it isn't Feb 10 03:00:28 Please hold. Let me get that link real quickly. Feb 10 03:00:48 https://dev.px4.io/en/tutorials/linux_sbus.html is the link. Feb 10 03:00:54 It says only for Rasp. pi. Feb 10 03:01:02 no it doesn't Feb 10 03:01:25 they just used an rpi Feb 10 03:01:40 but anything that merely requires an uart will work on any device that has an uart Feb 10 03:02:35 the first note even says that while "The driver has been tested on Raspberry Pi running Rasbian Linux", "It is expected to work on all Linux versions, and through all serial ports. Feb 10 03:02:38 " Feb 10 03:02:58 which is also exactly what I expect Feb 10 03:02:59 I get that. Feb 10 03:03:14 and the beaglebone has a bunch of uarts you can use Feb 10 03:03:34 routing it to an eqep pin would be completely useless Feb 10 03:03:40 I understand. I thought I would follow the guide from mirkix. Feb 10 03:03:49 He has a schematic and a nice photo. Feb 10 03:03:59 routing it to a pru pin (which PRU_E_B is) means you'd need a software uart in pru Feb 10 03:04:07 link? Feb 10 03:04:21 https://github.com/mirkix/ardupilotblue Feb 10 03:04:49 It was difficult to get my head around the idea at first. Feb 10 03:05:17 How could I use this functioning w/out a uart pin was my question but they must have figured out a way. Feb 10 03:05:26 eqep? Feb 10 03:05:28 Right? Feb 10 03:05:31 hmm, they do use software decoding Feb 10 03:05:37 no it's a pru pin Feb 10 03:05:43 Right. Feb 10 03:05:49 the PRU pin in eqep. Feb 10 03:05:56 no Feb 10 03:06:00 that doesn't even make sense Feb 10 03:06:07 pru and eqep are two separate and unrelated things Feb 10 03:06:15 I just looked in the BBBlue schematic. Feb 10 03:06:36 It should the four eqep connections, specifically E4, w/ PRU as two of the pins. Feb 10 03:06:44 should = showed Feb 10 03:07:35 the blue has four connectors intended for encoders, three connect to the three eqep instances, the last one connects to pru for software decoding Feb 10 03:07:36 Maybe it was a mislabeling. Feb 10 03:07:45 Oh. Feb 10 03:07:48 Okay. Feb 10 03:08:14 and I see the pin they specifically use can also be muxed to the pru ecap Feb 10 03:08:18 which is probably what they use Feb 10 03:08:22 Right. Feb 10 03:08:36 ok yeah, that's... horribly inefficient, but it works I guess Feb 10 03:08:44 the multiprotocol autodetection thing is convenient Feb 10 03:08:58 are you using an X8R ? Feb 10 03:09:01 That is the idea. I have been unsuccesful so far but the person at that github page tends to lean towards that pru pin. Feb 10 03:09:02 Yes! Feb 10 03:09:06 X8R! Feb 10 03:09:09 ok, they say it has 3.3V output Feb 10 03:09:10 I have one. Feb 10 03:09:14 Right. Feb 10 03:09:23 But I have to power it w/ up to 10v. Feb 10 03:09:30 in the sbus. Feb 10 03:09:50 Does the pru pin go to the signal line? Feb 10 03:09:54 so then the only thing you need to beware of is that you should ensure the beaglebone is never powered off while it is connected to the receiver, if the receiver is powered on Feb 10 03:10:06 Oh. Feb 10 03:10:07 Okay. Feb 10 03:10:14 So, I power down the receiver first? Feb 10 03:10:54 yes Feb 10 03:11:00 B/c I think I can hotplug things in that receiver b/c it is cheap compared to the BBBlue. Feb 10 03:11:21 I'm not concerned about the receiver, I'm concerned about the blue Feb 10 03:11:28 I should put a button on it. Me too! Feb 10 03:11:34 That thing is $80.00 large. Feb 10 03:12:11 I have heard of instance w/ people using the librobotcontrol or px4 for BBBlue use. Feb 10 03:12:18 There is really unlimited ideas circulating. Feb 10 03:12:20 so, that page you linked says "Make sure the signal does not exceed 3.3 volts, otherwise your BeagleBone Blue can be damaged", which is true, but a more accurate thing to say is "Make sure the signal does not exceed the 3.3V supply of the beaglebone" Feb 10 03:12:34 (does not significantly exceed) Feb 10 03:12:39 Okay. Feb 10 03:12:52 the critical difference between those two statements is that if the beaglebone is powered off, its "3.3V supply" is 0V Feb 10 03:13:06 in other words, the signal must then also not (significantly) exceed 0V Feb 10 03:13:46 I get that idea. So, would a servo connection be ideal for powering the Receiver and setting up the signal line from the PRU (BBBlue)? Feb 10 03:14:10 using a level shifter would certainly increase safety (e.g. using a transistor and pull-up like the s.bus linux on rpi example shows) Feb 10 03:14:22 I have no idea what you mean by that Feb 10 03:15:10 I get that they are just wires. But, I would have one from the PRU to the same three Pin, Sbus connection in the receiver as the battery connections happen to be located too. Feb 10 03:15:25 Does that make more sense? Feb 10 03:15:25 ??? Feb 10 03:15:30 Dang it. Feb 10 03:15:39 Let me draw a schematic. Feb 10 03:15:42 Do you have time? Feb 10 03:15:48 also you never have only one wire between two devices Feb 10 03:15:57 at the very least it would be two: signal and ground Feb 10 03:16:14 Oh. I got it. I think that is where the fellow went wrong. Feb 10 03:16:45 I can tie in the GND from the battery to the Sbus w/ the GND from the E4 pin (PRU). Feb 10 03:17:06 common gnd! Feb 10 03:17:10 you could just use the 6V power output of the beaglebone to power the receiver Feb 10 03:17:16 No. Feb 10 03:17:23 why not? Feb 10 03:17:25 I need a separate power source. Feb 10 03:17:30 why? Feb 10 03:17:41 From people who have dealt w/ this idea for a bit, I have taken their advice. Feb 10 03:17:43 For one... Feb 10 03:18:12 separate power source makes the whole thing more complex and very greatly increases the risk of damaging the beaglebone blue by accident Feb 10 03:18:19 I need to have a good power source w/out loosing power from my LiPo, i.e. 9v. Feb 10 03:18:30 That is why I came here tonight. Feb 10 03:18:47 The receiver takes up to 10v. Feb 10 03:18:54 4 to 10v. Feb 10 03:18:57 about. Feb 10 03:19:02 yes I just read that Feb 10 03:19:07 9v is perfect. Feb 10 03:19:18 I even got a connection made. Feb 10 03:19:21 6V is too Feb 10 03:19:36 Right but it would drain my LiPo, right? Feb 10 03:19:52 otherwise it would drain whatever other battery you use Feb 10 03:20:13 Right. LiPo are expensive and a pain to maintain. Feb 10 03:20:43 zmatt: May I please show you a schematic? Feb 10 03:20:54 but... they're rechargeable. I don't see the problem? Feb 10 03:21:05 why would you want two batteries instead of just one? Feb 10 03:21:10 I have this online schematic tool. I always needed a reason to try it. Feb 10 03:21:12 Oh. Feb 10 03:21:33 Um...separate sources are for higher effeciency. Feb 10 03:21:41 Of the batteries. Feb 10 03:22:13 depending on what you mean by "efficiency" in this context, the lipo most likely wins easily from whatever other battery you use Feb 10 03:22:26 there's a reason why rc uses lipo Feb 10 03:22:39 So, if I ran two LiPo batteries in parallel, I can last longer and fly more. Feb 10 03:23:03 I would not have to check w/ the idea of running for only the 30 min marker. Feb 10 03:23:15 or just get larger batteries... it ultimately depends on your weight limit Feb 10 03:23:36 Right, I could do that but I do not want to get fancy just yet. Feb 10 03:23:42 but that weight would definitely be better spent on increasing the lipo size than on adding some random other battery for some part of your thing Feb 10 03:23:45 Well, cost is an issue as usual. Feb 10 03:24:15 zmatt: Let me show you this schematic really quickly but i have to type it up first, please! Feb 10 03:25:00 thing is, if you use a separate battery, that means the receiver stays powered (on its own battery) when the beaglebone shuts down because the lipo has drained Feb 10 03:25:08 at which point you'll be damaging the beaglebone Feb 10 03:25:49 powering the receiver from the beaglebone's 6V output (which is controlled by a gpio) ensures that the receiver will also power down Feb 10 03:26:13 thus minimizing the risk of damaging the beaglebone Feb 10 03:27:01 I could not get the receiver to pair w/ the transmitter on the BBBlue power output alone. Feb 10 03:27:03 if you use independent power supplies, I strongly urge you to use a level shifter Feb 10 03:27:14 Okay. I will try the level shifter. Feb 10 03:27:20 I have one handy. Feb 10 03:27:46 6v yes but I do not know what the issue was... Feb 10 03:27:54 uhh, you probably just did something wrong then? it's not really important in the end since you only have to pair it once Feb 10 03:27:57 No pairing took place. Feb 10 03:28:04 did you enable the 6V output? Feb 10 03:28:11 Probably not. Feb 10 03:28:26 I cannot remember. I only attached the power output to the receiver. Feb 10 03:28:36 And that was it, most likely. Feb 10 03:28:39 since, and this may surprise you, a 6V power output that's turned off, does not provide any power Feb 10 03:28:47 Aw! Feb 10 03:28:50 Got it. Feb 10 03:28:58 That is my mistake. Feb 10 03:29:07 But...the receiver did show that it was powered. Feb 10 03:29:29 then you probably just did something wrong Feb 10 03:29:42 also, which pin exactly did you use to obtain power? Feb 10 03:30:54 Now, right now, I have no way to knowing. That is long lost in the notebook. Which notebook? No clue right now. Feb 10 03:31:13 power out! Feb 10 03:31:18 The power out connection! Feb 10 03:32:05 * zmatt sighs and goes to do something else Feb 10 03:32:10 Sir, Feb 10 03:32:13 Okay. Fine. Feb 10 03:32:56 https://github.com/jadonk/beaglebone-blue/blob/master/docs/BeagleBone_Blue_balloons.png is the photo w/ the power out connector in the diagram. Feb 10 03:33:22 Photo. Whatever. Feb 10 03:35:22 that connector has two power outputs, neither of which is 6V Feb 10 03:35:33 Oh! Feb 10 03:35:59 https://www.circuitlab.com/editor/#?id=7pq5wm shows the funny schematic. That online thing did not have the tools I needed to draw correctly. Does it show? Feb 10 03:36:11 also the 5V there is not a safe one to use, since it is "always-on", i.e. it does not shut off when the beaglebone powers down Feb 10 03:36:21 Oh. Feb 10 03:36:30 Hmmm. Feb 10 03:36:32 Okay. Feb 10 03:36:38 that's why I specifically recommended the 6V Feb 10 03:37:00 that link just gave me a default page Feb 10 03:37:20 Where is the 6v located. Feb 10 03:37:30 Okay. No issue. I will try something else. Feb 10 03:37:39 on the servo motor output header Feb 10 03:37:44 Oh! Feb 10 03:38:09 I was checking the uart, eqep, and gpio pins. Feb 10 03:38:18 you can enable the 6V using: echo 1 >/sys/class/gpio/gpio80/value Feb 10 03:38:23 The GPS can handle 5v. Nice. Feb 10 03:38:30 Okay. Feb 10 03:38:41 the GPS connector has a 5V supply which you should also never use Feb 10 03:38:49 Oh. Feb 10 03:38:50 Dang. Feb 10 03:38:50 it's the same one as on the power out connector Feb 10 03:38:55 Okay. Feb 10 03:38:55 same problem Feb 10 03:38:58 Aw. Feb 10 03:39:09 fortunately plenty of gps receivers are fine with 3.3V Feb 10 03:39:27 yeah I'm really not happy with how power supplies were handled on the blue Feb 10 03:39:51 It is okay. There are workarounds like you are describing. Feb 10 03:39:52 it really invites inflicting damage to the beaglebone Feb 10 03:40:18 I know. Me, I am foolish at times, I could have damaged my BBBlue many times Feb 10 03:40:33 Or worse, where it sits. Feb 10 03:40:55 This is the exact reason why I do not act so quickly on my odd ideas. Feb 10 03:41:11 6v it is! Feb 10 03:42:04 It is actually hard to miss in the schematic. It is the largest lettering in the entire schematic. Feb 10 03:42:15 6vREG! Feb 10 03:44:27 very few 6V regulators exist Feb 10 03:45:24 even so, using the inverter circuit from https://dev.px4.io/en/tutorials/linux_sbus.html#signal-inverter-circuit (which also acts as a level shifter) and connecting it to a serial input (e.g. the DSM connector) would be the preferred option I think Feb 10 03:45:39 Okay. Feb 10 03:45:54 I can try that. I saw one of the Uart connectors are labeled as such. Feb 10 03:46:00 it removes all safety concerns of the power domain crossing, and as a bonus it's also more efficient Feb 10 03:46:11 Hmmm. Nice! Feb 10 03:46:22 I'd just use the DSM2 connector Feb 10 03:46:28 I will try it out, too. Feb 10 03:46:34 I will try out all avenues now. Feb 10 03:46:46 it has exactly the three pins you need: ground, 3.3V (for the pull-up resistor), and uart signal input Feb 10 03:47:05 Okay. Feb 10 03:47:14 It is jotted down in the log. Feb 10 03:47:26 GenTooMan: the beaglebone blue has one integrated Feb 10 03:49:05 GenTooMan: not sure what you mean by "very few 6V regulators exist", typically you use resistors to set the output voltage (it's a buck converter, not an LDO of course) Feb 10 03:53:00 That dang site said I had to pay them to save files. Feb 10 03:53:01 Boo! Feb 10 03:53:14 I cannot show you my schematic just yet. Feb 10 03:53:31 Paper and pen to the rescue! Feb 10 03:59:29 https://imgur.com/a/9bmcHVr Feb 10 03:59:43 That is the current config. of my battery and pru to sbus receiver. Feb 10 04:00:05 But...zmatt: I will try what you were describing too. Feb 10 04:00:27 that will never do anything whatsoever Feb 10 04:00:54 Oh. That is just for the receiver. Feb 10 04:01:14 like I said, you never have only one wire between two devices, you always need a closed circuit Feb 10 04:01:40 Okay. Just like a three prong extension cord? Feb 10 04:01:45 Got it. Feb 10 04:01:56 So, i just need to use the GND of the E4 Pin. Feb 10 04:02:12 Damn it. I already snipped 'em. Feb 10 04:02:23 Well. Back to the old drawing board. Feb 10 04:03:24 or...I can do what you described. I will let you know either way. It should be fun. Feb 10 04:06:37 https://imgur.com/a/oQF3XlW is the update? Feb 10 04:09:44 https://photos.app.goo.gl/S38CeKmFUe8gBwdn7 would be the connection using the inverter circuit shown on that sbus linux page Feb 10 04:11:02 what you've drawn should work yes, but it is probably nicer to use the ground pin on the sbus header Feb 10 04:11:23 so that your power and signal cables are not stuck together Feb 10 04:11:49 Okay. Feb 10 04:12:54 and like I said, if you don't use a level shifter, I urge you to use the 6V output from the beaglebone servo header instead of a separate battery Feb 10 04:13:18 Okay. That is a nice, easy schematic I can get. Feb 10 04:13:26 I will try that out. Feb 10 04:13:46 I shared it by accident while trying to send it to my e-mail. Feb 10 04:13:49 Aw! Feb 10 04:13:50 if you use the inverter circuit to connect to DSM2 it won't matter how you power the receiver (although using the 6V supply from the beaglebone still makes more sense than a separate battery in my opinion) Feb 10 04:14:18 Okay. That is cool then. I will try your way for a new way. Feb 10 04:16:15 So then, I would just have to access the uart by config-pin and use that .service file to start it on boot? Feb 10 04:16:40 I think those pins are configured correctly by default on the blue Feb 10 04:16:47 Or, should I use that echo ? > ... Oh! Feb 10 04:16:49 Okay. Feb 10 04:17:00 that echo is to turn the 6V power supply on Feb 10 04:17:03 So, they are, by default, set up. Feb 10 04:17:07 Right. Feb 10 04:17:33 I understood that the 6v is supplied by that echo 1 > /.../.../ cmd. Feb 10 04:18:08 I took a note down. You are like a regular teacher on a Sat. night, mate. Feb 10 04:18:17 ok yeah, the DSM2 signal is configured as uart by default Feb 10 04:18:22 zmatt: Oh! Feb 10 04:18:36 so if you use that, no config-pin required Feb 10 04:18:40 Yea boy! Feb 10 04:19:16 I will use that schematic from the site. I actually have a unidirectional level shifter right here. Feb 10 04:19:23 Oh wait. Feb 10 04:20:00 I need two resistors and a transistor. Feb 10 04:20:19 Got that covered and I have no way of knowing how I got these tools/parts. Feb 10 04:20:36 Sometimes things just work out. Feb 10 04:20:38 Sheesh. Feb 10 04:20:53 there are no doubt also ICs that do the whole just for you, but it does need to invert, not merely level-shift Feb 10 04:21:31 Oh. Feb 10 04:22:23 zmatt: very fix fixed regulators are 6V is what I meant. you have to use a adjustable regulator almost always to get 6V that's all Feb 10 04:23:02 GenTooMan: yeah I don't even know why it's 6V... I guess it must be a thing in the mysterious world of rc for some reason Feb 10 04:23:29 So, the npn trans. creates a higher voltage and then I need to dull that voltage down w/ the resistors? Feb 10 04:24:44 zmatt: receivers use to use 4AA alkaline batteries or 5AA nicads back in the times way back. Now they use LiPo for the receiver pack or have a single pack and a regulator etc. Feb 10 04:26:05 Yea. The NiCAD battery is what I was used to. Feb 10 04:26:46 set_: SN74LV1T04 is an example of an inverting level shifter Feb 10 04:26:53 Okay. Feb 10 04:27:24 it would replace the transistor and both resistors Feb 10 04:28:59 Yea. It makes sense. Two to Three or reverse. Feb 10 04:29:17 There are only five connections that can be made. Feb 10 04:29:23 ??? Feb 10 04:29:36 Two in and three out? Feb 10 04:29:41 Or three in and two out? Feb 10 04:29:46 Or that is silly? Feb 10 04:30:02 I would have to read more on it. Feb 10 04:30:12 I am going to stick w/ the NPN trans. and the two resistors. Feb 10 04:30:14 it has four connections: GND, VCC (connect to 3.3V of beaglebone), A = input (signal from receiver), Y = output (signal to beaglebone) Feb 10 04:30:23 Oh. I saw five pins. Feb 10 04:30:40 yes but one is "NC" (Not Connected) Feb 10 04:30:59 http://www.ti.com/lit/ds/symlink/sn74lv1t04.pdf...Oh! Feb 10 04:31:03 I just saw that. Feb 10 04:31:49 dunno why they used a 5-pin package instead of a 4-pin one... maybe to ensure you can't accidently place it the wrong way around (rotated 180 degrees) Feb 10 04:32:04 Oh! Yep. That is most likely the idea. Feb 10 04:32:32 I have seen those eight to 16 pin chips. I have gotten them turned around nicely before. That dot is so small at times. Feb 10 04:32:40 we've actually had this happen in manufactured boards.... twice... Feb 10 04:32:42 I guess it matters what frame of mind I am in. Feb 10 04:33:13 The BBBW and the MotorCape are tricky if someone is not paying attention. Feb 10 04:33:26 You could easily turn the Cape in the incorrect dir. Feb 10 04:33:48 Since there is not a Ethernet connection. Feb 10 04:34:18 Odd but it could happen. Feb 10 04:34:28 yeah, it would have been better if the connectors had different pin count or something Feb 10 04:35:07 1, 2 and 1, 2. Feb 10 04:35:21 That is the part to pay attention too. Feb 10 04:35:26 too = to Feb 10 04:35:48 It is on the cape and the board in relation to each other. Feb 10 04:36:17 Simple issues have made my silly minded before. Feb 10 04:36:58 you could also just put some colored sticker on one side of both cape and beaglebone Feb 10 04:37:08 Yep. Feb 10 04:37:13 Or even markings. Feb 10 04:37:21 Colored markers and such. Feb 10 04:37:35 The black and white sticker is what fooled me. Feb 10 04:37:52 One is one side and the other one, the Cape, is on the other side. Feb 10 04:38:33 Dang stickers. Feb 10 04:39:00 zmatt: Before you get bored of me, what do you think I should bring for my guests at the Maker Faire? Feb 10 04:39:04 ... Feb 10 04:39:06 sticker wise? Feb 10 04:39:15 your e-mail address. Feb 10 04:39:17 Just kidding. Feb 10 04:40:12 I have this neat-o thermal printer. I was going to give out some stickers to the youngsters. Feb 10 04:40:28 Giraffes? Feb 10 04:41:09 BBB.io Giraffes? Feb 10 04:41:49 I know I can use the site to show people what the board can do online via the .service and I cannot use the Beagle Icon. Feb 10 04:42:38 Outside of that, I am completely clueless on rules and regs. Feb 10 04:54:33 the pru clk thingie persists with the latest rc Feb 10 04:58:01 also now the usbnet is brought up randomly at boot Feb 10 04:58:59 having fun with bleeding-edge kernels? Feb 10 04:59:08 lol Feb 10 04:59:09 yeah Feb 10 04:59:15 well I want the newest bug fixes Feb 10 04:59:22 to develop my 802.15.4 Feb 10 04:59:23 the newest bugs you mean ;) Feb 10 04:59:28 but that also means I have the newest bugs Feb 10 04:59:28 lol Feb 10 04:59:29 yeah Feb 10 04:59:43 ah fair, if 802.15.4 is in rapid development Feb 10 05:00:03 I don't think it is, but if other parts of the kernel are that way I won't have to adapt Feb 10 05:00:12 well actually it may be Feb 10 05:00:22 a git blame from the time I built rc2 showed changed from a few days ago Feb 10 05:03:01 maybe try compiling an actual mainline kernel without any patches? or (a lot quicker) just compile the dtb in mainline, copy it to /boot/dtbs and set it explicitly using dtb=am335x-boneblack.dtb in /boot/uEnv.txt (iirc this automatically disables u-boot overlays, but you could comment out overlay-related stuff just in case) Feb 10 05:03:43 if remoteproc-pru works with the mainline dtb, you know the problem is in the DT Feb 10 05:04:15 otherwise, if it works with a mainline kernel, then the problem is in the patches done for the -bone kernel Feb 10 05:04:32 otherwise, it's a bug in mainline and should be reported to the linux-omap mailing list Feb 10 05:05:14 yeah Feb 10 05:06:26 of course I have no idea what other things will break if you use a mainline dtb let alone a mainline kernel, but I don't think you're using all that much custom functionality in the first place Feb 10 05:06:35 what image are you using anyway? iot or console? Feb 10 05:06:56 IOT Feb 10 05:07:01 but with graphics disabled Feb 10 05:07:14 "graphics disabled" ? Feb 10 05:07:24 systemctl set-default multi-user.target Feb 10 05:07:38 isn't that the default already on the iot image? it has no X11 or whatever Feb 10 05:07:43 ah ? Feb 10 05:07:47 then I have the graphical image Feb 10 05:07:50 ew Feb 10 05:07:59 but with X11 disabled yeah Feb 10 05:08:03 lol Feb 10 05:08:07 why are you using the graphical image? Feb 10 05:08:08 I thought I'd hook the bbb to a screen Feb 10 05:08:12 Someone on the forums just asked about the GPS connection on the BBBlue. Feb 10 05:08:18 then I realized I have no adapter for the mini hdmi thing so I disabled it Feb 10 05:08:27 "The 5v power source does not power down." Feb 10 05:08:29 Yep! Feb 10 05:08:38 set_: exactly that Feb 10 05:08:50 That is what I told him/she/whatever. Feb 10 05:09:06 Okay. I will stay out of your guys' hairs now. Feb 10 05:09:09 Oops. Yep. Feb 10 05:09:17 mawk: if you're doing work on kernel stuff, I imagine that you might appreciate a leaner image more, to reduce boot time Feb 10 05:09:49 even the iot image takes aaaages to boot Feb 10 05:10:25 console! Feb 10 05:10:36 while https://liktaanjeneus.nl/boot.svg is not that hard to achieve if you don't need all the crap that's installed and enabled by default Feb 10 05:12:21 Who made that image? Feb 10 05:12:35 I bet you could get rid of avahi too. Feb 10 05:12:36 you can produce one using: systemd-analyze plot >boot.svg Feb 10 05:12:44 Aw! Feb 10 05:12:47 I use avahi Feb 10 05:12:50 Oh. Feb 10 05:12:55 Oops-a-daisy. Feb 10 05:13:01 For what? Feb 10 05:13:09 also, avahi takes like.. no time Feb 10 05:13:15 Okay. Feb 10 05:14:19 I guess people add stuff not knowing exactly how long the booted system will then take to start up. Feb 10 05:14:56 avahi lets you find devices by hostname, even if your router doesn't provide local dns, or borks it up, or if you just connect a device directly to your computer and there's no router at all Feb 10 05:15:06 i.e. I never use IPs Feb 10 05:15:14 Oh. Feb 10 05:16:00 See. You are more knowledgeable on that subject. I got that service installed a while back but never found time to make things work w/ it. Feb 10 05:16:15 It will most likely take a lifetime. Feb 10 05:16:25 yeah zmatt , that's a good idea Feb 10 05:16:29 you're dutch ? Feb 10 05:16:29 it works automatically, once it's installed your device is discoverable by hostname.local Feb 10 05:16:34 yes Feb 10 05:16:42 Oh. Feb 10 05:16:49 I'm half your compatriot then Feb 10 05:16:57 I'm franco-dutch Feb 10 05:17:00 but I don't speak it Feb 10 05:17:13 my father is from drachten, friesland Feb 10 05:17:20 and seduced a french woman during his studies in germany Feb 10 05:17:23 and that's how I was born Feb 10 05:17:30 AMERICA! Feb 10 05:17:31 (being able to resolve ".local" names depends on having libnss-mdns installed, although I think Google Chrome can resolve them even without it) Feb 10 05:17:40 mawk: heh, nice Feb 10 05:18:00 Oh. Feb 10 05:18:23 I think I have libnss but not that -mdns option. Feb 10 05:18:30 Oh well. Feb 10 05:18:36 I just have not gotten to use it yet. Feb 10 05:19:20 mawk: also, hot tip if you ever end up having to use the serial console for more than a few minutes, e.g. to debug something: it turns out, that if you bump the baudrate from 115200 to 460800, the serial console becomes 4x as fast! (who'd have thunk!) Feb 10 05:19:33 lol Feb 10 05:19:38 I thought 115200 was the maximum Feb 10 05:19:41 which is really noticable with things like vim Feb 10 05:19:45 yeah Feb 10 05:20:12 nope. 460800 isn't the limit either, but it's the higest speed that's supported by basically everything Feb 10 05:20:17 normally I use the ethernet over usb, with a static ip on both side it works great Feb 10 05:20:24 until it randomly fails with a new kernel Feb 10 05:20:32 why not just ethernet? Feb 10 05:20:38 that's one more wire Feb 10 05:20:42 and why a static ip? Feb 10 05:20:49 with usb I have power and connectivity Feb 10 05:20:53 fair enough Feb 10 05:20:59 until it fails Feb 10 05:21:04 yeah Feb 10 05:21:51 a static ip because it's as if it were a point to point link, only one party on both sides Feb 10 05:21:56 though you can probably also boost the reliability thereof a lot by disabling the hideous startup script that sets up usb networking, and just add g_ether to /etc/modules Feb 10 05:21:58 the default config uses a /30 even Feb 10 05:22:06 yeah Feb 10 05:22:15 that script sets up two usb interfaces Feb 10 05:22:17 I don't know why Feb 10 05:22:20 I do Feb 10 05:22:26 also it gets the mac address from some complicated means Feb 10 05:22:32 eg from eeprom, unless it's cached Feb 10 05:22:35 if I read it right Feb 10 05:22:53 eFUSE actually Feb 10 05:23:04 and the other day it brittled away, the two mac addresses were the same for some reason Feb 10 05:23:05 the SoC itself has a range of 3 MAC addresses Feb 10 05:23:19 so on my computer one interface was enx1cba8ca2ed6c and the other was rename15 Feb 10 05:23:23 because it had the same mac Feb 10 05:23:47 it's done like this for industrial reasons ? Feb 10 05:24:06 to fix the address in production or something Feb 10 05:24:06 it's just done to have a fixed MAC address Feb 10 05:24:18 yeah Feb 10 05:24:28 over reinstalls Feb 10 05:24:31 I get it Feb 10 05:25:31 I guess it could also generate them randomly at first boot, except people tend to copy filesystems Feb 10 05:25:40 and then you have two devices with the same MAC Feb 10 05:25:49 yeah Feb 10 05:26:05 the SoC has three assigned globally-unique MAC addresses, it makes sense to use them Feb 10 05:27:20 as for the static ip, I wouldn't bother myself and just rely on link-local IPv6 and avahi :P Feb 10 05:27:43 hostnames ftw Feb 10 05:28:11 nicolas@desktop:~$ getent ahostsv6 beaglebone.local Feb 10 05:28:11 ::ffff:10.255.255.4 STREAM beaglebone.local Feb 10 05:28:15 that doesn't feel right lol Feb 10 05:28:42 lol, probably only have ipv4-only mdns in your nssswitch.conf Feb 10 05:29:14 try avahi-resolve-host-name beaglebone.local Feb 10 05:30:05 it does the same thing Feb 10 05:30:12 avahi allows link-local by default I guess Feb 10 05:30:14 that's kinda the point Feb 10 05:30:44 it doesn't return an IPv6 address? that's odd Feb 10 05:31:01 actually I've never seen avahi produce an IPv6-mapped IPv4 address Feb 10 05:31:23 ah Feb 10 05:31:28 with -6 it gives the ipv6 address Feb 10 05:31:56 for nss it had « hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines » in its config Feb 10 05:32:05 so I guess I need to add mdns6_minimal and all will be fine Feb 10 05:32:11 or just remove the 4 Feb 10 05:32:16 right Feb 10 05:32:29 I hope debian has a good reason to ship this config by default Feb 10 05:32:42 I'm trying to remember Feb 10 05:32:44 now it works Feb 10 05:32:51 both with nss and avahi Feb 10 05:33:12 I can use LL only Feb 10 05:33:22 of course link-local ipv4 works too, but it tends to take longer since often it's only used when dhcp times out Feb 10 05:33:36 yeah Feb 10 05:35:28 thanks for the help, and good night Feb 10 16:11:06 Hello Feb 10 16:12:52 Hello Feb 10 16:14:21 I want to start contributing can anyone guide me up? Feb 10 16:24:29 github is where alot of projects are available for download Feb 10 18:07:04 @davidm Feb 10 18:07:26 @davidm welcome to the beagleboard chat Feb 10 18:09:13 testing 123 Feb 10 18:28:48 Hey! Feb 10 18:28:53 Hope you are are all doing well! Feb 10 18:29:14 I am bb rookie! So please try to be patient. Feb 10 18:29:23 I am trying to have my board start on power. Feb 10 18:30:21 Would you be nice enough to point to some kind of documentation? Feb 10 18:30:23 Hello! Feb 10 18:30:29 bbb.io! Feb 10 18:30:36 Hey! Feb 10 18:30:54 you can try getting started on bbb.io. Feb 10 18:31:00 OK Feb 10 18:31:15 https://beagleboard.org/getting-started Feb 10 18:31:23 Thanks Feb 10 18:31:26 Yep. Feb 10 18:31:27 I tried that Feb 10 18:31:30 Oh. Feb 10 18:31:32 What is the issue? Feb 10 18:31:39 I will try to read again Feb 10 18:31:49 but couldn't find any reference to autoboot on power Feb 10 18:31:56 (I might have missed that) Feb 10 18:32:05 Okay. Did you use etcher and are you using Win or Linux for your desktop? Feb 10 18:32:42 I got the BeagleBoard-X15 with debian (desktop edition) Feb 10 18:32:48 Oh. Feb 10 18:32:57 Please hold. I will get the other docs. Feb 10 18:33:05 Thank you so much! Feb 10 18:33:24 https://beagleboard.org/x15 is a resource for starting up. Feb 10 18:33:39 Andre: So, you need an image right? Feb 10 18:33:48 So your board boots? Feb 10 18:34:18 oh Feb 10 18:34:19 yes Feb 10 18:34:37 https://beagleboard.org/latest-images has the x-15 image you need. It is the third one down on that page. Feb 10 18:35:39 Andre: Do you know how to get the image on your board? Feb 10 18:35:59 Trying to figure it out now Feb 10 18:36:06 give me a sec please Feb 10 18:36:14 Okay. Are you using...oh okay. No issue. Have fun! Feb 10 18:36:31 and thanks for your help! Truly appreciate it Feb 10 18:36:37 Yep. Feb 10 18:37:09 Oh and that image is for a SD Card only. It is not for the flasher image. Feb 10 18:37:20 flasher = eMMC Feb 10 18:39:10 https://www.elinux.org/Beagleboard:BeagleBoard-X15 for when you get bored. Feb 10 18:39:22 Linux BeagleBoard-X15 4.9.35-ti-r44 #1 SMP PREEMPT Sat Jul 1 00:54:33 UTC 2017 armv7l GNU/Linux Feb 10 18:39:33 Is that what you have on your board as of now? Feb 10 18:39:56 this is uname - a directly from the board indeed. Feb 10 18:40:02 uname -a Feb 10 18:40:44 https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28stretch-iot.29_.28BeagleBoard-X15.29 Feb 10 18:40:45 Thanks for elinux.org link I studied that as well, just somehow cannot find a reference to any BIOS equivalent Feb 10 18:40:48 That is the newer image. Feb 10 18:41:18 OK Feb 10 18:41:18 We are using 4.14.x now. Feb 10 18:41:24 I think? Feb 10 18:41:25 I will certainly update this asap Feb 10 18:41:30 Let me check again. Feb 10 18:41:32 Okay. Feb 10 18:41:39 "Linux BeagleBoard-X15 4.9.35-ti-r44" Feb 10 18:41:42 I saw "we" but that is just me. Feb 10 18:41:59 <<< unaffiliated Feb 10 18:42:08 I just like to chat basically about stuff. Feb 10 18:42:21 Appreciate your help, honestly! Feb 10 18:42:26 awesome! Feb 10 18:42:47 I will work on the new built Feb 10 18:42:50 Hey. You may want to update the image entirely. One thing. If you are updating... Feb 10 18:44:00 to change power on boot I assume it would be some kernel variable or pin on the board Feb 10 18:44:11 just cannot find any reference - I am still new to this.... Feb 10 18:45:02 You may want to check what bootloader version you have. I think specific bootloaders only work, from my perspective, w/ specific images. For instance...the BBB and other credit card sized BBBs get the bootloader from eMMC even though the BBB is booted from SD Card. Feb 10 18:45:03 ... Feb 10 18:45:36 Unless...you hold down the S2 button or erase what is on your eMMC. Feb 10 18:45:45 I believe I have u-boot Feb 10 18:45:53 But, that is just the BBB boards w/ that button. Feb 10 18:46:10 I will have to review more of this x15 to find out which ideas were put into the board. Feb 10 18:46:46 Andre: I am sure we use u-boot overlays now, i.e. esp. w/ the newer kernels and images. Feb 10 18:47:00 At least for those of us who like simplicity. Feb 10 18:47:12 https://www.dropbox.com/s/gm8s89u0mgnokc9/Screenshot%202019-02-10%2012.47.10.png?dl=0 Feb 10 18:47:47 This could be an answer to my question Feb 10 18:47:51 but I juts dont get it ;( Feb 10 18:48:10 So, you need a header on your board or jumpers? Feb 10 18:48:29 or neither or both? Feb 10 18:48:33 I dont know Feb 10 18:48:39 I want the board to start when I plug in the power Feb 10 18:49:06 Oh. Please hold for someone smarter on this subject. I currently thought the board booted. Feb 10 18:49:15 b/c of what you typed to me w/ uname -a. Feb 10 18:50:41 Andre: I am sorry. I thought things were moving in a direction where I could pursue assistance. I think I am unmanned for this task now. Feb 10 18:50:43 I am sorry. Feb 10 18:50:55 Thanks again! Nice to meet you. Feb 10 18:50:59 Please hold for other people. I am sure people will be around at some point. Feb 10 18:51:03 Nice to meet you. Feb 10 18:51:16 No worries at all! Feb 10 18:51:21 Appreciate you reaching out! Feb 10 18:51:48 Okay. I felt like I was a welcoming party when you told me about the x15 and booting issues. Feb 10 18:51:51 I will work on flashing of the new iso. Feb 10 18:51:54 No issue at all. Feb 10 18:51:55 Okay. Feb 10 18:53:36 https://github.com/beagleboard/beagleboard-x15 could show some extra info. Feb 10 18:53:53 checking now Feb 10 18:55:01 13 of 27 Feb 10 18:55:06 Check that page Feb 10 18:55:31 what document exactly Feb 10 18:55:32 ? Feb 10 18:55:50 Oh. sorry. Ha. Um, please hold. Oh. the .pdf schematic. Feb 10 18:55:59 rev. B1. Feb 10 18:57:31 They have the "boot sequence" there in black on that page. Feb 10 18:58:21 Hey Andre: brb. I need a break from life and fun. I will be back in a bit. Feb 10 18:58:41 Thanks ;) Feb 10 19:02:24 FYI Feb 10 19:02:29 https://www.dropbox.com/s/gjj4kltu18r3pl0/Screenshot%202019-02-10%2013.02.24.png?dl=0 Feb 10 19:02:33 same info ;) Feb 10 19:03:05 Now I have to find them on the board hahahahaha Feb 10 19:03:52 Andre: oh yeah, the beagleboard-x15 not auto-starting is kinda annoying Feb 10 19:04:03 Hey zmatt Feb 10 19:04:11 so there is no way to auto start the board? Feb 10 19:04:49 let me check what the deal with it is... iirc there was a way Feb 10 19:05:03 like, with a jumper or something Feb 10 19:05:10 thats what I am thinking Feb 10 19:05:16 this is consider IOT Feb 10 19:05:25 I doubt there is no autotstart feature..... Feb 10 19:08:36 @zmatt thanks ;) Feb 10 19:11:28 yeah, I'll need a moment to dig around. at the very least there's the powerhold jumper, but that's not quite the same as autostart. I'm also wondering if some pmic config might persist if the backup battery were installed (which would also maintain the rtc) Feb 10 19:13:20 appreciate it;) Feb 10 19:13:53 the powerhold jumper (J5) will force the board on unconditionally Feb 10 19:14:53 (this used to have a hazard if there's no boot image, due to pu/pd contention in default state after reset, but it looks like that has been fixed) Feb 10 19:15:24 it does mean you can't power down at software request, the board would simply power back on Feb 10 19:25:28 OK Feb 10 19:25:31 @zmatt Feb 10 19:25:32 Thanks Feb 10 19:25:48 Analyzing the map of the board now.... Feb 10 19:27:33 @zmatt thats great news Feb 10 19:32:55 it's unfortunate the RPWRON pin isn't accessible, not even as testpoint, since I think tying that one high would result in the board powering up without forcing it to stay on Feb 10 19:33:21 I just found other J pins Feb 10 19:33:29 cannot find 5 Feb 10 19:35:03 really? I saw it immediately: 2-pin header (unplaced) right next to the PMIC Feb 10 19:35:42 There is a high possibility I am just blind ..... Feb 10 19:36:24 https://elinux.org/File:BBX15-TOP_SIDE.jpg below the PMIC you see a row of four inductors (grey squares), and J5 is to the right of them Feb 10 19:38:09 I bow to you for being patient with me! Feb 10 19:38:13 Got it! Feb 10 19:38:19 :) Feb 10 19:38:33 Will short them and see what happens! Feb 10 19:38:35 Thank you so much! Feb 10 19:58:00 If anyone has a problem with this in the future, J5 (I shorted j5 with copper cable) works fine. It need couple seconds and boots the beagleboard x15. Thanks for help again. Feb 10 20:39:44 so I'm trying to compile the rc_test_motors.c file in the debian and it's erroring at Feb 10 20:40:30 in the original code it's in a line "#include " Feb 10 20:41:03 I'm thinking i need to find this file and make it available to include, being new to c compiling I'm asking for help Feb 10 20:41:24 hmm, weird it should find that Feb 10 20:41:41 I found the .c file at: http://www.strawsondesign.com/docs/librobotcontrol/rc_test_motors_8c-example.html Feb 10 20:41:43 which image version are you using? Feb 10 20:41:49 (cat /etc/dogtag ) Feb 10 20:42:32 bb debian image 2017-04-09 Feb 10 20:42:49 that's pretty old, you may want to grab the latest iot image Feb 10 20:43:00 librobotcontrol is installed by default on it Feb 10 20:43:26 ok, let me find a chip... Feb 10 20:43:41 "a chip" ? you mean a microsd card? Feb 10 20:43:51 yep Feb 10 20:44:13 found an 8 gig that's do eh Feb 10 20:44:25 that'll Feb 10 20:44:29 anything that's at least 4GB is fine Feb 10 20:45:07 you can find instructions for reflashing at https://beagleboard.org/getting-started Feb 10 20:45:34 thanks Feb 10 20:45:40 you can also choose to just work from sd card instead of reflashing, but in that case you should at least erase eMMC using: sudo blkdiscard /dev/mmcblk1 after booting from sd card Feb 10 20:45:51 (otherwise the old bootloader on eMMC can cause problems) Feb 10 21:41:52 so I am supposed to edit the /boot/uEnv.txt file, is there a way to do that on the bb Feb 10 21:42:14 I put the card in an older bbblack and i can see it but I'm not mounted Feb 10 21:42:51 I should say fdisk sees it Feb 10 21:49:17 hmm, maybe not Feb 10 21:53:46 you can just boot from the sd card and then edit /boot/uEnv.txt Feb 10 21:53:54 and then reboot Feb 10 21:54:11 you can also mount it on any linux system, including a beaglebone Feb 10 21:55:06 x86 is hideous Feb 10 21:55:14 I wish I had been asked to do a kvm client for ARM Feb 10 21:55:17 that'd be novel and fun Feb 10 21:55:30 but no, I'm stuck with x86 and that terrible BIOS thing and that ugly bzImage thing with its 16-bit code Feb 10 22:05:45 zmatt, will I have to start over, meaning will I lose my wifi and other setup work when I flash the mmc? Feb 10 22:25:31 does /dev/mmc/blk0p1 sound right for the SD card Feb 10 22:25:39 sorry Feb 10 22:26:15 " /dev/mmcblk0pl" Feb 10 22:26:49 and how can I tell the l's from the 1's in this damn thing Feb 10 22:27:08 supper time! Feb 10 22:42:59 mmcblk0p1 rather Feb 10 22:43:01 no ? Feb 10 22:43:31 /dev/mmcblk${MMC_NR}p${MMC_PART} Feb 10 23:27:38 I put it in an ubuntu machine now it comes up as /dev/sdd1 Feb 10 23:27:41 won't mount Feb 10 23:32:00 it mounted... seems like a pain Feb 10 23:34:09 ok, now, using nano, edited the uEnv.txt file no problem but it won't save the file Feb 10 23:34:25 error writing uEnv.txt: read-only file system Feb 10 23:34:42 sudo nano? Feb 10 23:34:46 ar Feb 10 23:35:37 same issue Feb 10 23:35:43 Ut oh. Feb 10 23:35:53 Did you sign in as root or ubuntu? Feb 10 23:36:01 user Feb 10 23:36:05 Oh. Feb 10 23:36:16 I must have missed a mile of info. on this one. Feb 10 23:36:39 Are you listening to the eewiki? Feb 10 23:36:40 na, I was monkeying around... moved to a pc that has ubuntu on it Feb 10 23:36:48 Oh. Feb 10 23:37:28 So, you are not able to sign in on your BBB w/ an Ubuntu machine or you have Ubuntu on your BBB? Feb 10 23:37:40 or both? Feb 10 23:38:45 ubuntu on pc, I used it to sign into bbb but the sd card came up as " /dev/mmcblk0pl" seemed wrong Feb 10 23:38:52 Oh. Feb 10 23:39:07 Did you cc your own distro? Feb 10 23:39:07 so I moved the chip over to the pc Feb 10 23:39:15 ? Feb 10 23:39:19 Hmm. Feb 10 23:39:30 Did you cross compile your own bbb image? Feb 10 23:40:12 no, downloaded, etched onto SD, now trying to edit uEnv.txt Feb 10 23:40:39 Oh and for some reason, the dog-gone uEnv.txt file will not save. Got it. Feb 10 23:41:04 Hmm. That sounds very odd even for me. Feb 10 23:41:26 give me a minute, I think I'm using the wrong terminal program out of ubuntu Feb 10 23:41:33 I do all sorts of miscalculations at times. Did you show everyone the paste of your file? Feb 10 23:41:35 Okay. Feb 10 23:43:34 I just use the basic terminal program on the Ubuntu Desktop. Feb 10 23:43:54 I set it up as gnome and xfce as a backup. Feb 10 23:45:41 that's what I was using, it wouldn't let me login as root Feb 10 23:47:33 Is it your computer? Feb 10 23:47:47 su or sudo -i? Feb 10 23:48:11 It may make you root, though. Feb 10 23:48:17 w/ other instances. Feb 10 23:48:40 it took that Feb 10 23:48:54 which one did you end up using? Feb 10 23:49:13 sudo -i Feb 10 23:49:20 Yea. That works, too. Feb 10 23:49:29 Now, you are root right? Feb 10 23:50:43 correct, same problem though, can't edit read-only file system Feb 10 23:51:06 Oh. Feb 10 23:51:21 You might have taken away privileges for writing to that file? Feb 10 23:53:23 Some files are readable and can be written to, also. Some are both and some are neither. Feb 10 23:53:49 I am sure you can search for making files under root privilege writeable. Feb 10 23:54:05 Check out the all powerful google. Feb 10 23:54:26 Or...you can try chmod for the search. Feb 10 23:54:29 ok, been there... not good, talk to ya later Feb 10 23:54:37 Okay. Feb 10 23:54:39 Sorry. Feb 10 23:54:47 Later for now. Feb 10 23:55:53 thank you for taking the time and your patience. I'll get it Feb 11 00:03:14 Good luck! Feb 11 00:03:22 i think i got it Feb 11 00:04:12 i unmounted, used the ubunto as root to ssh into the bbb, put the sd card in bbb, mounted, edited, saved, checked, seems ok now Feb 11 00:04:26 ubunto machine is old, software is too Feb 11 00:10:08 Aw! Feb 11 00:10:15 What works, works! Feb 11 00:18:48 I used a bbb through the ubuntu machine to edit the file Feb 11 00:18:56 now I have to flash the emmc Feb 11 00:20:46 can you ssh into the bbb? Feb 11 00:21:26 I don't mean some sort of access through a web gui cloud9 thing Feb 11 00:21:54 actual ssh into the bbb. Feb 11 00:22:32 I did, I edited the sd card, I powered down, powered back up holding the user/boot button to flash Feb 11 00:22:45 now I'm getting led flashes night rider style Feb 11 00:22:53 hadn't seen that before Feb 11 00:23:03 how long does a flash take? Feb 11 00:23:38 I let it go for at least 2 beers. Feb 11 00:23:57 does the night rider led flash mean something to you? Feb 11 00:24:10 now solid Feb 11 00:24:14 now off Feb 11 00:24:53 I know it's almost a sin but I have no beers in the house, I'll have to settle for a 7 n 7 Feb 11 00:25:23 pull the card out and and rejuice it. Feb 11 00:27:07 done, normal led flashing has returned Feb 11 00:31:11 that's the old bbblack, lost my root user, that will have to wait Feb 11 00:31:53 maybe this was answered, did I lose all prior data on the unit? Feb 11 00:33:48 that's kind of intrinsic to the notion of "reflashing" ? Feb 11 00:35:16 and root account doesn't support login by default, but you can just use sudo for the rare occasion you need it. the debian account should be sufficiently privileged for day to day use Feb 11 00:35:27 nice way of saying yes Feb 11 00:36:10 I guess I should append a warning whenever I recommend reflashing Feb 11 00:36:24 but I need the practice anyway so... now the blue, in night rider mode Feb 11 00:37:01 hmm, you're reflashing a second time? Feb 11 00:37:03 na, was a bad question Feb 11 00:37:21 no, a second bb first was an older black, now a blue Feb 11 00:37:25 ah Feb 11 00:38:02 used the black as a Guinea pig sorta Feb 11 00:38:09 beware that sufficiently old blacks only have 2GB of eMMC, in which case recent iot (let alone lxqt) images don't fit anymore Feb 11 00:38:26 then it'll be the blue that took a crap on me and wouldn't let me in via usb Feb 11 00:38:27 because they got too bloated -.- Feb 11 00:38:53 oof! well it flashed and let me in via ssh Feb 11 00:41:30 this bb black seems to have 4 gig so not so old, over 3 years Feb 11 01:00:32 vdr: assuming the beaglebone has internet access, you may also want to consider installing updates (sudo apt update && sudo apt upgrade) since the image is already a few months old. having the latest version of the bb-customizations package will also reduce boot time significantly Feb 11 01:04:27 on it **** ENDING LOGGING AT Mon Feb 11 03:00:11 2019