**** BEGIN LOGGING AT Mon Jul 23 03:00:01 2018 Jul 23 04:08:46 Hello...I see there are no real suggestions for Marlin and the BBB. Are people on this idea or not? I wanted to know if anyone was using Marlin on their BB of choice. Jul 23 04:12:52 Attempting! Jul 23 04:16:29 e Jul 23 04:19:17 BBBW, if you are nasty? Jul 23 04:33:57 Ooh, Ooh. Is the USB device on the BBB a teensy++ 2.0? I am looking at the schematic now. No info. yet but when I go to Devices and Drivers on the Desktop, I get a screen after clicking on the BBB icon. It shows that it is in fact a Teensy but does not show what version. Send rations! Jul 23 04:47:02 it's a mentor graphics something-or-other Jul 23 04:47:05 OTG host controller Jul 23 04:47:08 non ehci compliant Jul 23 04:47:10 sucks ass Jul 23 04:52:40 Aw! Jul 23 06:43:58 Hi? Jul 23 06:44:10 Hi? Jul 23 06:44:53 you're not even sure whether you're saying hi? Jul 23 07:27:21 hi all Jul 23 13:17:08 Hello everyone, I would like to modify my sd image on my main computer before flashing it Jul 23 13:17:34 Since I have a Debian ARM image, but am running Ubuntu x86, it seems that chroot is the way to go Jul 23 13:17:44 but, I have issues with resolv.conf Jul 23 13:18:13 does anybody know how to go about setting this up without hosing the image? Jul 23 13:18:47 (FYI, I'd like to modify it on my main computer because (1) it's much faster and (2) it'll write less to the SD card) Jul 23 13:19:44 Up to this point, I have tried to mount the image directly following these instructions: Jul 23 13:19:44 https://www.linuxquestions.org/questions/linux-general-1/how-to-mount-img-file-882386/ Jul 23 13:20:23 then setting up qemu-user-static following Mollow pg 259 Jul 23 13:21:30 (that is also explained in the appendix here: https://wiki.debian.org/QemuUserEmulation) Jul 23 13:21:41 I think systemd-nspawn --bind=$(which qemu-arm-static) should work? Jul 23 13:22:19 (after apt-get installing qemu-user-static) Jul 23 13:23:36 * dcmertens is installing systemd-container Jul 23 13:24:58 e.g.: systemd-nspawn --bind=$(which qemu-arm-static) -i bone-debian-9.3-iot-armhf-2018-03-05-4gb.img Jul 23 13:25:32 for me that yields an environment where 'apt-get update' works Jul 23 13:25:57 Hmm, my first attempt did not go well, but I'll try your second approach Jul 23 13:26:11 optionally pass hostname with -M beaglebone or similar Jul 23 13:26:40 and maybe use --bind-ro instead of --bind just to be safe Jul 23 13:27:31 systemd-nspawn also has options for handling /etc/resolv.conf, but the default worked for me Jul 23 13:29:12 I get the error about url name resolution, so I'll look into resolv.conf, I suppose Jul 23 13:48:10 the -n option to systemd-nspawn didn't work, but manually changing /etc/resolve.conf did Jul 23 14:04:15 ehh, why would you try -n ? -n guarantees your container does *not* have internet access Jul 23 14:05:43 the docs were less than clear on this point Jul 23 14:06:24 is there any reason to keep ardupilot packages? Jul 23 14:06:33 I'm tempted to simply remove them Jul 23 14:07:23 if you're making your own image, you might just want to start with a console image and install whatever you need, instead of starting with the iot image and removing what you think is superfluous Jul 23 14:07:44 the latter is typically harder and more error-prone Jul 23 14:08:14 (and no there's no reason to keep ardupilot if you're not using it) Jul 23 14:08:55 * dcmertens looks for console image Jul 23 14:09:20 https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Stretch_Snapshot_console Jul 23 14:09:29 thanks! I was about toask Jul 23 15:29:40 Hi, I want to use a stepper motor with my BB Blue. What inputs does the stepper motor connect to on the board? And will I still need to use an H-bridge? Jul 23 15:52:31 kim_ I think most folks around here know a fair bit about BBs, but relatively little about stepper motors Jul 23 15:52:50 what kinds of outputs does the stepper motor produce? Jul 23 15:54:01 Hello Jul 23 15:54:02 https://stackoverflow.com/questions/51482823/node-sass-does-not-yet-support-your-current-environment-linux-unsupported-archi Jul 23 15:54:14 I need a help please Jul 23 15:56:34 beagle, I think you'll need to talk with the folks over at Node Sass Jul 23 15:56:52 I doubt anybody here would know where to get started with that problem Jul 23 16:04:35 dcmertens , there are 4 outputs on the stepper motor. Direction +-, and step +- Jul 23 16:04:53 https://www.safaribooksonline.com/library/view/beaglebone-cookbook/9781491915660/ch04.html Jul 23 16:05:14 this website shows how to connect a bipolar stepper motor for a BB black, but i'm wondering how that would be done on the Blue. Jul 23 16:12:38 a stepper has inputs, not outputs Jul 23 16:19:13 ok. do you know what pins on the BB Blue these need to be connected to? Jul 23 16:20:23 kim_, does this help? https://groups.google.com/forum/#!category-topic/beagleboard/ZXSTPIcV4OU Jul 23 16:21:42 kim_: if the output voltage of the integrated motor outputs of the blue is tolerable for the motor then you can use those Jul 23 16:23:48 (those run off V_BATT) Jul 23 16:25:17 dcmertens, yes, I have seen that schematic before and it is pretty helpful Jul 23 16:25:39 zmatt, so i could use the DC motor driver outputs for the direction +- Jul 23 16:25:56 what about the other two necessary inputs? Jul 23 16:27:02 I don't understand, based on the link you gave a stepper doesn't have a "direction" input Jul 23 16:27:26 but just two steps of motor coils Jul 23 16:27:30 *sets Jul 23 16:28:36 (based on Figure 4-9. Model of a bipolar stepper motor Jul 23 16:28:37 ) Jul 23 16:29:44 which you'd connect to two motor outputs Jul 23 16:48:18 I see what you're saying Jul 23 16:48:26 Thanks, i'll give that a try Jul 23 16:48:49 so an h-bridge is not necessary for the BB blue motor drivers Jul 23 16:49:25 the blue's motor drivers *are* h-bridge drivers Jul 23 17:02:58 ok great, thanks Jul 23 18:20:20 Does anybody know how to tweak systemd so that nfs mounts wait for the network to be online? Jul 23 18:21:46 lemme check how I setup my nfs mount Jul 23 18:21:56 I feel like remote-fs-pre.target should depends upon... Jul 23 18:22:06 network-online.target Jul 23 18:22:59 fwiw, nfs mounting works on older images; I do not know enough about how they differ Jul 23 18:23:29 why would that matter though? the initial packet loss shouldn't be a problem right, it'll just retry? Jul 23 18:23:57 I don't know enough about nfs to give a useful answer Jul 23 18:24:09 oh right, I made my nfs mountpoint an automount, so it doesn't even get automatically mounted at boot (only at first access) Jul 23 18:24:37 Got it, I've seen that configuration Jul 23 18:24:44 thanks Jul 23 18:28:09 zmatt, that would involve the options "noauto,x-systemd.automount" right? Jul 23 18:29:04 here's how I have things: https://pastebin.com/nntDUXQy Jul 23 18:29:37 I don't remember the exact reason for overriding nfs-idmapd.service Jul 23 18:30:40 never mind, I see the reason: the unmodified nfs-idmapd.service requires nfs-server.service Jul 23 18:31:25 thanks!! Jul 23 18:38:04 hum, somehow the first time automount is bugging out for me right now though, even though subsequently it works fine. ho hum, this is new, it used to work fine Jul 23 18:44:45 oh lol what Jul 23 18:45:16 ??? Jul 23 18:47:18 the usb0 interface created by g_ether (which I enabled a while back for some testing purposes but is typically unused) caused systemd-networkd-wait-online.service to timeout Jul 23 18:47:30 yep, that was it, problem solved Jul 23 18:47:30 oh Jul 23 18:48:05 (added RequiredForOnline=no to the [Link] section of its .network file) Jul 23 18:49:02 which implies that actually the nfs mountpoint does wait for network-online.target for me Jul 23 18:49:44 well, that seems to me the most sensible thing, I am just having a hard time figuring out the minimal action required to achieve it Jul 23 18:50:34 It seems I should be able to create /etc/systemd/system/nfs-client.target.wants directory Jul 23 18:50:46 then link network-online.target into that directory Jul 23 18:50:58 I'm pretty sure that dependency already exists by default Jul 23 18:51:13 since it does for me, and I didn't add it Jul 23 18:51:31 yes, but I don't see where it has been put into place Jul 23 18:52:18 for example, /lib/systemd/system/nfs-client.target only requires remote-fs-pre.target Jul 23 18:52:42 this is what I see when I access /nfs for the first time after boot: Jul 23 18:52:45 https://pastebin.com/raw/aiZ0WvM8 Jul 23 18:54:01 cool Jul 23 18:54:33 oh wait, did I add it? Jul 23 18:55:02 hm Jul 23 18:55:06 no, I didn't Jul 23 18:55:41 systemctl show -p WantedBy network-online.target shows: WantedBy=nfs.mount Jul 23 18:56:23 so it seems systemd invented that dependency automagically Jul 23 18:56:31 On my machine, that gives: ntp.service apt-daily.service hostapd.service Jul 23 18:58:21 "Network mount units automatically acquire After= dependencies on remote-fs-pre.target, network.target and network-online.target. Towards the latter a Wants= unit is added as well." Jul 23 18:58:54 (man systemd.mount) Jul 23 18:59:48 also "By default all remote mounts defined in /etc/fstab pull this service in, in order to make sure the network is up before it is attempted to connect to a network share." -- https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ Jul 23 19:00:03 so if that's not happening for you, something is very broken Jul 23 19:00:27 which systemd version are you using? Jul 23 19:00:57 hmm, gimme a sec Jul 23 19:02:00 https://pastebin.com/yZGDpqK3 Jul 23 19:02:16 it might have been the fstab options Jul 23 19:02:27 I'm going to try to reboot and we'll see if it continues to give trouble Jul 23 19:03:21 if you can't find the cause, you could also try systemd 237 from stretch-backports Jul 23 19:03:36 good to know Jul 23 19:04:11 ok, yeah, it boots fine Jul 23 19:04:23 looks like I just needed better fstab options Jul 23 19:04:25 zmatt++ Jul 23 19:04:29 heh ok Jul 23 19:07:23 zmatt, I have one or two more boot questions for you. :-) Jul 23 19:07:31 go ahead Jul 23 19:07:51 the boot process waits for about 45 seconds before saying "fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1" Jul 23 19:08:17 that device exists on the booted BB Jul 23 19:08:26 you're booting from sd card? Jul 23 19:08:37 yes, for the moment Jul 23 19:08:42 then I'll flash Jul 23 19:10:10 Just prior to that it has a message about waiting for suspend/resume; I'll paste the set of 10 lines of interest... Jul 23 19:10:47 https://pastebin.com/NHRYcwWv Jul 23 19:10:50 hmm, not sure, I don't think I've ever seen an issue like what you're describing. for what it's worth though, I'm not using initramfs at all, so this error couldn't possibly happen for me Jul 23 19:11:20 I suspect the Gave up waiting for suspend/resume device Jul 23 19:11:25 is also coming from initramfs Jul 23 19:11:43 I'd be hapy to get rid of it, I just don't know how to go about doing that Jul 23 19:11:50 you remove it Jul 23 19:12:03 I was going to propose that, but it seemed too simple Jul 23 19:12:03 oh right, you probably have a kernel with a bogus dependency on it Jul 23 19:12:20 whatever RCN packaged up... Jul 23 19:12:44 rcn introduced a dep on initramfs in some kernel packages for reasons that never became clear to me Jul 23 19:13:17 I remove that when building my own kernel, but it's also very easy to replace initramfs-tools by a dummy version, or you can just disable it in its config file Jul 23 19:13:42 for testing you can just manually remove /boot/initrd.* Jul 23 19:13:53 (or move/rename it) Jul 23 19:13:59 really? I would have thought I would need to modify something in uEnv.txt, too Jul 23 19:14:04 nope Jul 23 19:14:05 I'll rename it and see what happens Jul 23 19:15:10 yeah, no problems, and gets rid of that strange boot hang Jul 23 19:15:13 zmatt += 2 Jul 23 19:15:36 here's a dummy initramfs-tools package: https://liktaanjeneus.nl/initramfs-tools_1.0_all.deb Jul 23 19:16:00 Installing that would prevent future generation of initramfs, I suppose? Jul 23 19:16:25 yeah, although you can also just leave it installed but disable it in /etc Jul 23 19:17:36 if you do use the dummy version, put a package hold on it to ensure you won't accidently "upgrade" it to a real initramfs-tools if its version ever reaches 1.0 (it's 0.131 currently) Jul 23 19:17:51 heheh Jul 23 19:18:11 nah, I think I'll just rename the initrd file Jul 23 19:18:37 I'll make a note of it in my installation notes, so the next time I do this process from scratch, I'll check then Jul 23 19:18:41 in, like, 2 years Jul 23 19:18:44 -) Jul 23 19:18:46 :-) Jul 23 19:19:30 that's fragile though, since lots of packages will trigger a regeneration of the initramfs Jul 23 19:19:51 but my BBs are never going to be upgraded Jul 23 19:19:53 at least set update_initramfs=no in /etc/initramfs-tools/update-initramfs.conf Jul 23 19:20:02 they won't even have a connection to the internet Jul 23 19:20:09 ok, that I can do Jul 23 19:20:49 well never say never, an issue could always show up down the road Jul 23 19:21:55 wget https://liktaanjeneus.nl/initramfs-tools_1.0_all.deb && sudo dpkg -i initramfs-tools_1.0_all.deb is an easy fix to ensure the initramfs can't be accidently regenerated Jul 23 19:25:42 done! Thanks! Jul 23 19:28:15 (and you can then remove initramfs-tools-core) Jul 23 19:31:01 * dcmertens tries Jul 23 19:31:21 brb, shopping Jul 23 22:15:54 anybody have success using a stepper motor with BeagleBone blue? There doesn't seem to be much documentation for that online. Jul 23 23:49:03 I have a beaglebone Black I believe I blew up by running too much current to a usb device. Anyone know what kind of troubleshooting I can do to make sure it’s not just a brick? Jul 23 23:49:24 that shouldn't be possible Jul 23 23:50:38 Which , the running of a device that needed too much power? Or bricking it because of that? Jul 23 23:50:57 damaging, let alone bricking, the bbb Jul 23 23:51:21 overcurrent should result in the usb port's power being cut off Jul 23 23:51:51 even if it didn't, overcurrent would just cause the beaglebone itself to switch off Jul 23 23:53:59 I had a USB powered USR modem, that I was going to have the system emulate an HP2000 mainframe running Time Share Basic. It ran for a couple hours then died, it won’t start up, but the leds still li Jul 23 23:54:36 your sentence got cut off at "but the leds still li" Jul 23 23:54:37 Light up, but it never finishes booting anymore Jul 23 23:55:12 that definitely doesn't sound like a brick then Jul 23 23:55:42 have you tried flashing a fresh image to sd card and boot from that? Jul 23 23:56:32 Yes, numerous times. I ended up replacing it with a BBG. But I don’t care for the green as much. Jul 23 23:56:58 hum Jul 23 23:57:10 what exactly is the led activity you see? Jul 23 23:59:11 I’ll have to find it and hook it back up. Lately I’ve been doing more projects with Rpi’s Jul 24 00:01:36 Ugh, it’s so hard using a phone to chat. Jul 24 00:01:49 then why are you using a phone to chat? :P Jul 24 00:02:38 I’ve also been teaching my kids some programming and electronics using the BBC micro:bit Jul 24 00:03:50 anyway, things that might help when booting from sd card is powering on with S2 button held down (just in case eMMC contains a really old image compared to the sd card you're trying to boot), and the serial console may be informative in case of boot issues Jul 24 00:05:55 Yeah, I’d have to hook up something to monitor the serial console. I’ll try that out when I pull it out. Jul 24 00:06:16 your problem description sounds quite puzzling to me... if you somehow did cause damage by overcurrent via usb (which I'm pretty sure shouldn't be possible) then I'd either expect a dead usb host port, or a system that doesn't even power on Jul 24 00:07:26 Originally what was supposed to happen was the BBB and modem connected to a TI Silent 700 thermal teletype terminal that logs into the HP TSB system. Jul 24 00:09:22 thermal teletype? o.O Jul 24 00:09:32 Because a couple years ago for BASIC’s 50th “birthday” I put together an exhibit called “It’s basically BASIC”. I had half a dozen different machines, all running different types of BASIC. Jul 24 00:10:18 Look up the TI Silent 700 series of terminals. Interesting little beasts Jul 24 00:11:32 neat Jul 24 00:12:04 But the Silent 700 and the BBB was supposed to represent BASIC from the mid 70’s until the early 80’s when the libraries switched to video terminals from teletypes Jul 24 00:13:52 Eventually I was going to mount the BBB somewhere in the case of the 700, to literally turn it into a stand-alone device. Jul 24 00:14:20 hehe, a teletype with an ethernet jack instead of a phone jack Jul 24 00:14:53 sucks that your bbb got fried... I really wonder how that happened Jul 24 00:16:05 Another neat thing I have, is a little device called WiFi232. It has a 25 pin RS232 connection. The computer/terminal “thinks” it’s a Hayes compatible modem, except you atdt IP addresses or domain names of telnet servers. Jul 24 00:16:29 usually if a bbb dies it's a straightforward case of overvoltage applied to an I/O, and typically results in a board that doesn't even power on anymore Jul 24 00:16:33 haha, that's cool Jul 24 00:17:11 Other than having the modem plugged in, I can’t think of anything else that happened to it. Considering I was in the middle of some tests when it just stopped Jul 24 00:18:07 Yeah, I’ve used it to have a number of my vintage systems connect to some of those BBS systems out there on the Internet Jul 24 00:19:25 It’s helpful for transferring software, especially for oddball/old machines. Like my Kaypro II, the Atart Portfolio, and so on. Jul 24 00:20:17 I have to run for now. Dishes to do, etc Jul 24 00:20:38 later :) Jul 24 00:23:02 zmatt: I'm with py-uio. How can I compile pwmss2.dtsi as overlay? Jul 24 00:23:15 https://github.com/mvduin/overlay-utils Jul 24 00:25:45 Okay. I was trying py-uio/dts/bin/dtsi-to-overlay Jul 24 00:26:23 ah right there's still a Makefile in that dir too Jul 24 00:26:32 does it no longer work? it still should Jul 24 00:26:58 basically overlay-utils lived in that subdir of py-uio before I split it off into a separate project Jul 24 00:28:20 It no longer work I guess Jul 24 00:28:49 works for me Jul 24 00:29:09 what error are you running into? Jul 24 00:29:32 (when doing 'make pwmss2.dtbo' ) Jul 24 00:30:01 maybe usage error: "-:1: Parse error" (never used perl) Jul 24 00:30:36 I am no longer able to ssh into the bbb, don’t what happened it was just fine a day ago Jul 24 00:30:54 CoffeeBreakfast: well you don't usee dtsi-to-overlay directly, you use the makefile Jul 24 00:30:57 *use Jul 24 00:34:09 Looks like I'm not getting an ipv4 address. Anyone know what could cause this? Jul 24 00:34:25 network settings? Jul 24 00:34:45 how are you making that particular conclusion? Jul 24 00:34:47 zmatt: the dtsi-to-overlay in py-uio works. I was wrong :P Jul 24 00:35:40 :) Jul 24 00:36:07 Screened into BBB then ran tcpdump on usb0 and all I see are ipv6 request...? Jul 24 00:36:30 Unee0x: uhh, usb0 would have static configuration Jul 24 00:36:47 if you've screened into it, just check 'ip addr' Jul 24 00:36:52 It does... Jul 24 00:37:18 oh you mean your computer doesn't get one, I thought you meant the bbb doesn't get one Jul 24 00:37:44 I think the default image uses dnsmasq for that, but I'm not sure Jul 24 00:49:44 zmatt: just for curiosity's sake, what are '# 1 ""' and such in the output of dtsi-to-overlay? Jul 24 00:57:35 line markers to ensure error messages from dtc can indicate where the problem is (hopefully) Jul 24 01:02:27 great Jul 24 01:43:14 ecap-pwm-test.py works just fine. Awesome! Jul 24 01:43:22 :D **** ENDING LOGGING AT Tue Jul 24 03:00:00 2018