**** BEGIN LOGGING AT Thu Jun 21 03:00:01 2018 Jun 21 07:31:09 Help Jun 21 07:32:17 All linux command will work on beagle bone black (Debian .9.3) Jun 21 07:34:10 what is actual mean for making real time patching in bbb Jun 21 07:55:53 Anupam: 1) learn what realtime means Jun 21 07:56:04 Anupam: 2) learn how to do your variant of real time in linux Jun 21 07:56:07 Anupam: 3) ... Jun 21 07:56:10 Anupam: 4) profit Jun 21 07:58:48 So how can we make linux with real time features Jun 21 08:56:01 KotH: you know, to do the thing with the thing, but "real time" Jun 21 08:56:28 it's a requirement that things never take imaginary time Jun 21 08:59:50 zmatt: i am very well aware of that fact Jun 21 13:25:28 I have troubles with Internet-over-USB, with the BBB connected to a Debian host: https://pastebin.com/VyjnhMws Jun 21 13:29:19 hi Jun 21 13:29:33 how to sync time in Beaglebone Jun 21 13:30:11 when it gets restarted resetting date to older date Jun 21 13:33:43 anurag: I think it should automatically sync via ntp Jun 21 13:33:57 also the date shouldn't reset when restarted, just when power-cycled Jun 21 13:34:13 anurag: don't send private messages. Jun 21 13:35:10 Nicolas: that looks wrong, why does your computer have both 192.168.7.2 and 192.168.7.1 ? Jun 21 13:35:50 yes Jun 21 13:36:05 But fort that we need internet in beagleboard Jun 21 13:36:12 IF I am not wrong Jun 21 13:36:15 anurag: or a local ntp server Jun 21 13:36:48 (if your dhcp server supplies the ip of an ntp server to use, that will be used. otherwise you'll need to manually configure one) Jun 21 13:36:59 alternatively you could use an external RTC with backup battery Jun 21 13:37:47 in beagleboard can we attache external RTC with battery Jun 21 13:37:48 ? Jun 21 13:38:15 you mean beaglebone? Jun 21 13:38:20 and yes you can Jun 21 13:39:30 e.g. attach it via the i2c2 bus (which is enabled by default on P9.19-20) and use an overlay to declare it Jun 21 13:39:47 zmatt: I don't know.. In /etc/network/interfaces I only have one enxa0f6f... Jun 21 13:40:04 Thanks zmatt Jun 21 13:40:43 Nicolas: you're using ifupdown rather than a "real" network manager? are you using some sort of minimalistic debian install? Jun 21 13:42:10 I don't recommend the use of ifupdown. desktop systems typically use gnome network manager, while for everything else I'd recommend systemd-networkd Jun 21 13:43:46 although if I have to guess, I wonder if you're actually using a network manager *and* ifupdown, with one having automatically configured the interface correctly and then ifupdown adding the wrong ip as a result of your manual configuration in /etc/network/interfaces (the config file of ifupdown) Jun 21 13:44:03 but that's just a guess :) Jun 21 13:44:36 zmatt: Nope, it is a desktop. Never touched a (gui)network manager D: Jun 21 13:45:31 I'm trying to implment PRU on BBB and I get an unknown variable PRUSS_INTC_INITDATA Jun 21 13:45:34 okay so it's probably exactly what I said: gnome network manager probably configured the interface correctly for you, and in addition to that you misconfigured it using /etc/network/interfaces ;) Jun 21 13:46:51 hi zmatt Jun 21 13:47:18 plaurie: yes I saw your question Jun 21 13:47:39 PRUSS_INTC_INITDATA is a macro declared in pruss_intc_mapping.h Jun 21 13:48:41 that's what Ithought but is isn't in my copy Jun 21 13:49:07 Hey Zmatt, I am Prakash, Anurag cowoker. We have already designed baseboard without RTC. Is there any internal RTC which can handle the time stamp. Jun 21 13:49:37 OK I'll go and try again. Jun 21 13:50:12 anurag: there is an internal rtc, but it doesn't support a backup battery. even if it did, if you didn't design your board with a backup battery, then obviously nothing is going to be able to magically retain the date and time for you Jun 21 13:50:56 (when the board is powered off) Jun 21 13:51:19 the internal rtc is used to keep the time across reboots when the board remains powered Jun 21 13:51:55 Yesterday I successfully access the BBB via SSH, but no DNS. (Out of the box didn't work, only after installed isc-dhcp-server) Then making work DNS, obviously I screwed up some of these conf files. Now I only can ping but not ssh the BBB Jun 21 13:51:57 plaurie: I'm not sure what to say, it's right there... https://github.com/beagleboard/am335x_pru_package/blob/master/pru_sw/app_loader/include/pruss_intc_mapping.h#L98-L104 Jun 21 13:52:36 Nicolas: you installed a dhcp server? on what? that sounds like a recipe for making a big mess Jun 21 13:53:02 it should simply work plug-and-play out of the box Jun 21 13:54:02 It didn't work. Jun 21 13:55:17 that's really odd Jun 21 13:56:39 you're definitely not meant to install a dhcp server to get anything working, except when connecting via an ethernet network that doesn't already have one (e.g. if you just connect an ethernet cable between your computer and the beaglebone) Jun 21 13:56:55 the beaglebone already runs a dhcp server on the usb interfaces Jun 21 13:57:16 I'm gonna remove isc-dhcp, and rollback the mess. Jun 21 13:57:53 maybe just reflash (to the latest iot image) to start from a fresh state? unless there's other stuff on eMMC you want to preserve Jun 21 14:00:29 zmatt: Because a faulty debian in the eMMC? Jun 21 14:01:07 you're still running whatever it got shipped with? then you never know how old the image is Jun 21 14:02:02 I kinda meant more "just in case you mucked something up and forget to restore something" but if you've never reflashed eMMC then I would definitely recommend reflashing to the latest iot image yes :P Jun 21 14:04:44 zmatt: (Just in case, the pastebin I linked is from my host desktop debian) Jun 21 14:04:53 yes I understood that Jun 21 14:05:46 the latest image from the .org? Jun 21 14:06:03 yeah first download link at https://beagleboard.org/latest-images Jun 21 14:09:46 zmatt: thanks. Also thanks for the dmesg pastebin :) Jun 21 14:37:23 zmatt: there's a line of code: tpruss_intc_initdata pruss_intc_initdata = PRUSS_INTC_INITDATA; which fails to compile because 'tpruss_intc_initdata' hasn't been declared anywhere Jun 21 14:39:10 it's declared in prussdrv.h Jun 21 14:42:07 Aaargh - you're right. It's in the directory but the compiler isn't seeing it. maybe it needs to see one of the standard headers first Jun 21 14:42:22 ehm what? Jun 21 14:42:54 you need to #include a header Jun 21 14:44:25 The code I'm compiling has prussdrv.h declared, and tpruss_intc is declared in it, but the compiler hasn't noticed. Jun 21 14:44:49 that sounds really bizarre Jun 21 14:45:52 and you're not getting any errors prior to that? (always fix errors from top to bottom, since earlier errors can cause later errors as a side-effect) Jun 21 15:08:52 zmatt: ssh -> bbb: it worked!. But, once logged in the bbb, I can't see anything, let alone ping 8.8.8.8 Jun 21 15:09:23 oh that's what you meant Jun 21 15:09:56 zmatt: (after flashing latest image) Jun 21 15:10:18 with 'no dns' you meant 'the beaglebone has no internet access' ... if you said that it would have been instantly clear what you were talking about :P Jun 21 15:11:00 you're right that it doesn't have internet access via usb in the default configuration, since there's no way to get that working without significant manual configuration on the user's side Jun 21 15:11:28 it does work out of the box if you can plug it into an ethernet network with internet access Jun 21 15:11:56 no dns = In my host machine, ping www.google.com fails, but with 8.8.8.8 worked. Jun 21 15:13:21 eh what? on your host? what the beaglebone has to do with whatever networking problems you have on your host? Jun 21 15:15:25 oh you meant that as part of an attempt to share your internet connection to the bbb, you managed to muck up your host's internet access? yeah I can believe that Jun 21 15:16:11 Because of me. My mistake. I did a rollback, now the host (debian desktop) works well. I can ssh to the beaglebone. Jun 21 15:16:25 sharing internet via usb to the beaglebone requires somewhat tricky setup on both host and beaglebone Jun 21 15:16:34 oohh Jun 21 15:17:02 if possible at all, connecting the beaglebone to internet via ethernet is what I'd recommend Jun 21 15:22:54 The other way (usb), it is worth? e.g. If I would like to use the BBB with a notebook in a library? Jun 21 15:25:03 Or just plug in a usb wifi and walk away Jun 21 15:25:53 usb wifi probably works out of the box, that's not the same as attaching the bbb as a usb device to a host (different role) Jun 21 15:26:43 and it's not very hard with systemd-networkd at least, but I don't know the appropriate steps when using gnome network manager on the host or connman (the default) on the beaglebone Jun 21 15:26:56 plus reconfiguring the beaglebone's networking is an easy way to accidently lose access to it Jun 21 15:28:10 if you're somewhere with your laptop and a beaglebone, if your laptop has ethernet then just connect them using a short ethernet cable and enable internet sharing on your laptop (if gnome network manager has that built in) Jun 21 15:33:23 zmatt: I'll try Jun 21 20:34:26 Hello. I want to connect a common anode RGB LED to P8_3 to P8_6, then set the cathode pins to output PWM (to control all three colours easily). I'm a little worried feeding the current back into output pins might damage my BBB, though nothing I have found in the reference docs forbids this. Can someone confirm this works? Jun 21 21:12:38 AnimaInvicta: you shouldn't drive leds directly with gpios, use a led driver Jun 21 21:12:51 (e.g. a transistor) Jun 21 21:13:00 try to limit current through gpios to 4 mA Jun 21 21:33:49 zmatt: thanks for the advice. I probably should have mentioned that I put a resistor inline on the anode to prevent the LED from cooking. With that, I get about 3 mA. Jun 21 21:34:54 AnimaInvicta: you need a resistor for each color Jun 21 21:36:09 Nicolas_: sorry if this is a stupid question, but what difference does that make? Jun 21 21:36:48 it doesn't as long as you turn on only one led at any given time. it makes a big difference if you turn on all three Jun 21 21:39:05 1. the current is distributed across the leds, hence turning on multiple leds will make all of them dimmer 2. different leds (especially different colors) have different voltage drop, causing the current to distribute highly unevenly Jun 21 21:40:17 zmatt is right Jun 21 21:41:29 So the big difference is in the brightness. Got it. Jun 21 21:41:58 yes, the leds will strongly influence each other, hence you can't sanely control them independently Jun 21 21:44:36 having a separate resistor for each led fixed that problem Jun 21 21:45:21 anyway, if the current is limited to 3 mA per gpio, I think it should be okay. there's also a limit on total current across the gpios, but I don't think you have to worry about that when connecting three leds :) Jun 21 21:48:58 OK, thanks. Speaking of current, I'm still a bit worried (probably mostly out of ignorance) about feeding current back into a GPIO configured as output. Is there any risk of damage? Jun 21 21:49:37 (max total current rating is 100 mA for I/O supply domain HV6 and 50 mA for each of HV1-HV5. You can find the supply domain to which each io belongs on the BBB tab of my pins spreadsheet - https://goo.gl/Jkcg0w ) Jun 21 21:50:10 "output" does not refer to the direction of current but to the fact that significant current flows at all Jun 21 21:50:29 in contrast, no significant current flows through an input Jun 21 21:51:35 when configured as output, gpios are "push-pull", i.e. they will source current when high and sink current when low Jun 21 21:51:42 and do both equally happy Jun 21 21:52:19 the amount of current is the only thing to worry about, not the direction Jun 21 21:52:49 That's good to know. Jun 21 21:53:30 along with the voltage of course. the common anode cannot exceed 3.3v Jun 21 21:55:56 hmm, ok, I have a pushbutton wired up to GPIO60 on a BBB wireless. Polling for the value works a-ok. However, I'm having trouble getting edge-triggered events working; after "echo both > gpio60/edge" and "echo rising > gpio60/edge", "cat gpio60/value" still works exactly the same as polling. Jun 21 21:57:07 lpsmith: getting events from sysfs works in a fairly non-obvious way, and isn't something you can use simply with echo or cat Jun 21 21:57:29 (it requires using poll() to receive a POLLPRI event, or similarly epoll with EPOLLPRI) Jun 21 21:57:42 https://gist.github.com/mvduin/578509d458da8948ae3a14a81dc639e4 Jun 21 21:57:51 zmatt, I'm a reasonably seasoned linux system programmer, so I'll give it a shot. Thanks. Jun 21 21:59:23 but yeah, this webpage appears to be wrong. At least at the present time. http://beaglebone.cameon.net/home/using-the-gpios Jun 21 21:59:41 ok. short summary: configure edge, open the value attribute and read the initial value, then whenever you get a POLLPRI event on the fd read the value again. you need to seek to the beginning to read it again, or combine the fseek() and read() into one pread() call Jun 21 22:00:16 yep, it is wrong, and if it was ever not wrong then that's before my time :) Jun 21 22:59:46 hello everybody. I'm just starting with new BBB rev. C. I connected it, flashed latest debian image to SD so it runs from it now. Connected, updated, tried to follow instructions to disable HDMI cape because I need SPI, failed on this line: echo BB-SPI1-01 > /sys/devices/bone_capemgr.*/slots because I just don't have that directory. And this is problem #2, because #1 is I can't connect now... too long?, I'll split Jun 21 23:00:23 you're following outdated instructions Jun 21 23:00:53 yes I got it already but didn't find new Jun 21 23:00:59 but first, unless there's stuff on eMMC you need to preserve, I recommend either reflashing eMMC or at the very least erasing it (using: sudo blkdiscard /dev/mmcblk1 ) Jun 21 23:01:37 if an old bootloader is present on eMMC, a recent image on SD will still boot but can have weird problems Jun 21 23:02:17 I actually can run it from microSD now Jun 21 23:02:31 so eMMC is fine, just old Jun 21 23:02:32 yes, that's what I said: it will still boot but can have weird problems Jun 21 23:03:07 hence, if you want to run from SD card, I strongly recommend erasing eMMC Jun 21 23:03:50 hm never thought of that, but why? Jun 21 23:04:12 old versions of the bootloader don't understand most of the config options in /boot/uEnv.txt Jun 21 23:04:30 erasing the bootloader from eMMC will cause the bootloader present on SD card to be used instead Jun 21 23:05:18 Also I didn't finish, it actually IS running fine, but I feel like I'm doing something wrong with networking Jun 21 23:06:10 well what did you do that caused you to be no longer able to connect? Jun 21 23:06:23 given that you were able to try commands, so evidently you were able to connect earlier Jun 21 23:06:54 If I boot it from eMMC it will also connect fine with microSD, because my PC saved IP it first got from virtual DHCP Jun 21 23:07:18 I have no idea what you mean by that Jun 21 23:08:15 sure I was able. Not without problems, but it somehow happened Jun 21 23:08:45 I'm also still learning linux, networks and Arch I'm currently on Jun 21 23:09:13 ah okay, you mean you still have problems with your host's network config Jun 21 23:09:24 in that case maybe ask in an irc channel for Arch ? :) Jun 21 23:10:04 It doesn't seem so, because it's all fine with that old image Jun 21 23:10:33 in it DHCP is working fine so my host PC gets IP and connects Jun 21 23:10:36 the usb networking stuff has changed over time, but it should work out of the box for any version Jun 21 23:11:01 I don't suppose you have an ethernet lan you can plug the beaglebone into instead? Jun 21 23:11:24 and with new one it can't get the IP, it only tries to use one it already remembered, if that connection is still in same session Jun 21 23:12:13 sec, I'll find what it says Jun 21 23:12:23 that doesn't make sense, especially since rebooting the beaglebone (to switch between eMMC and SD) will unavoidably cause the usb interface to temporarily disappear, so it shouldn't even be possible to retain any configuration across that Jun 21 23:13:25 anyway, if you have an ethernet network available I wouldn't bother messing with usb networking in the first place Jun 21 23:15:05 I use this to connect: $ sudo dhclient -d -v enp5s0u2 Jun 21 23:15:24 and get... DHCPDISCOVER on enp5s0u2 to 255.255.255.255 port 67 interval 14 Jun 21 23:15:24 DHCPDISCOVER on enp5s0u2 to 255.255.255.255 port 67 interval 18 Jun 21 23:15:24 DHCPDISCOVER on enp5s0u2 to 255.255.255.255 port 67 interval 5 Jun 21 23:15:24 No DHCPOFFERS received. Jun 21 23:15:24 No working leases in persistent database - sleeping. Jun 21 23:15:38 skipped many lines, all same Jun 21 23:15:44 you're *manually* using dhclient? does arch have nothing resembling a network manager? Jun 21 23:15:54 DHCPDISCOVER on enp5s0u2 to 255.255.255.255 port 67 interval 2 Jun 21 23:15:54 No DHCPOFFERS received. Jun 21 23:15:54 No working leases in persistent database - sleeping. Jun 21 23:15:54 Terminated Jun 21 23:16:20 well, yes, for now Jun 21 23:17:02 I guess I'll come with something more convenient later, but it's ok Jun 21 23:17:18 but anyway, I don't know what to say... I vaguely remember that the intern we had a long time ago (who also used Arch) also had problems at first connecting to the beaglebone via usb networking Jun 21 23:17:30 on the other hand I've never seen any problems on a debian host Jun 21 23:18:26 btw that log I provided was without prior connection with eMMC Jun 21 23:18:39 and if it was one, then ... Jun 21 23:18:54 like I said, I can't even begin to imagine how that would make a difference since the interface should completely disappear Jun 21 23:18:55 DHCPDISCOVER on enp5s0u2 to 255.255.255.255 port 67 interval 14 Jun 21 23:18:56 DHCPDISCOVER on enp5s0u2 to 255.255.255.255 port 67 interval 16 Jun 21 23:18:56 No DHCPOFFERS received. Jun 21 23:18:56 Trying recorded lease 192.168.7.1 Jun 21 23:18:56 bound: renewal in 1228 seconds. Jun 21 23:19:29 it's trying that last lease, and magically it all works Jun 21 23:19:36 also, I think normally you'd get 192.168.6.1 as lease rather than 192.168.7.1 Jun 21 23:19:40 on current images Jun 21 23:19:56 no, it depends Jun 21 23:20:06 can be both Jun 21 23:20:25 yes, but by default Jun 21 23:20:34 192.168.7.1 is the rndis interface selected by Windows Jun 21 23:21:06 192.168.6.1 is the cdc-ecm interface used by default Jun 21 23:22:03 if I remember correctly Jun 21 23:22:10 hmm checked that again and you're right, it's mentioned for Win Jun 21 23:22:19 Idk... but it works Jun 21 23:22:25 really ancient images only supported RNDIS Jun 21 23:22:51 so that would explain why you got that lease on eMMC Jun 21 23:23:36 anyway, I'm still inclined to blame your Arch system since the problems you're having are not problems other people normally have Jun 21 23:23:46 hm, don't get that Jun 21 23:24:57 well... then can you give me some advice on how can I debug that? Jun 21 23:25:26 I only have access with usb now Jun 21 23:25:54 having said that, I haven't tested usb networking in the default config any time recent myself. I don't really use images in the default config, nor do I frequently use usb networking (I normally connect via Ethernet). Having said that, whenever I used usb networking, it Just Worked™ Jun 21 23:26:19 (I personally use systemd-networkd on both my host systems and on beaglebones) Jun 21 23:26:32 eh Jun 21 23:26:42 what distro? Jun 21 23:26:45 debian Jun 21 23:26:51 right Jun 21 23:27:09 (on both host and beaglebones) Jun 21 23:28:13 ok. I tried debian too, but Arch are good to learn something... always, haha Jun 21 23:28:15 of course no doubt you can get things working on Arch too. but that was exactly my experience with Arch: you have to put in effort to get things working :) Jun 21 23:28:20 is* Jun 21 23:28:59 yeah it's normal) So I'm trying to gid deeper once again Jun 21 23:29:12 just not sure how this time Jun 21 23:29:23 I don't mind having to tweak configuration to tune a system to my preference, but when I used Arch I experienced a pervasive lack of sane defaults Jun 21 23:29:34 I guess wireshark from host will not tell me much Jun 21 23:29:40 I didn't use it for very long though, and it was a while ago Jun 21 23:30:54 haha, +1 here, but I'm already using it as my main for half a year, and I really love my custom feeling Jun 21 23:32:10 choosen openbox and every little thing Jun 21 23:33:37 well, maybe you know then on #2 - how to disable that HDMI cape with latest debian? Jun 21 23:33:45 sure Jun 21 23:34:12 except my instructions will probably fail to work when booting a new image using an old bootloader on eMMC :) Jun 21 23:34:34 but anyway, you can disable hdmi audio and other such things using config vars in /boot/uEnv.txt Jun 21 23:34:50 don't we all just love how fast things go obsolete. Jun 21 23:35:45 be aware that value of the various disable_/enable_$whatever=1 vars doesn't matter, only their presence or absence. so comment/uncomment them, don't try to set them to 0 Jun 21 23:35:49 I still don't get how that can affect. Isn't that bootloader just a piece of code telling CPU where to read code from? Something different here Jun 21 23:35:52 ? Jun 21 23:36:10 Mono: the bootloader (u-boot) is responsible to passing the device tree to the kernel Jun 21 23:36:28 ow, okay Jun 21 23:36:50 makes more sense then Jun 21 23:36:54 in recent images, that device tree is assembled from a base dtb and overlays based on settings in /boot/uEnv.txt (and based on auto-detected CAPEs if any) Jun 21 23:37:42 anyway, to use SPI or most other peripherals you simply configure the relevant pins using the 'config-pin' utility at runtime Jun 21 23:37:51 the /dev/spidev* devices already exist by default Jun 21 23:37:52 hm, thendo I need to edit this /boot/uEnv.txt on eMMC? Jun 21 23:37:57 no, SD Jun 21 23:38:01 ok Jun 21 23:38:29 if you don't want to erase eMMC, you can temporarily bypass it by powering the beaglebone on while holding down the S2 button Jun 21 23:38:37 (you can let go of the S2 button once the power led turns on) Jun 21 23:38:59 this removes eMMC from the search order of devices where ROM attempts to find u-boot Jun 21 23:39:18 btw, if I just mess eMMC somehow, will it be fine and load from SD? Jun 21 23:39:20 this is persistent across reboots/resets, the S2 button is only sampled at power-on Jun 21 23:39:59 interesting Jun 21 23:40:03 yes you can completely wipe eMMC, it will then boot entirely from SD card. that's actually what I recommended if you want to boot from SD card and don't need to keep the contents of eMMC Jun 21 23:40:37 wiping sector 256 also suffices (unless it's a reaaaaaaaly ancient image) Jun 21 23:40:41 I guess it's of now importance then Jun 21 23:40:50 no* Jun 21 23:41:04 GenTooMan: I love when obsolete things become cool, and resurrect, like the IBM 1401 Jun 21 23:41:13 eMMC isn't important. there's no way to "brick" the beaglebone other than by causing physical hardware damage Jun 21 23:41:41 thank you zmatt! Will try that Jun 21 23:42:10 maybe that old device tree is really the cause Jun 21 23:42:41 you can also easily reflash eMMC by uncommenting the eMMC-flasher line in /boot/uEnv.txt on the SD card and then rebooting Jun 21 23:42:55 (iirc it's the last line of the file) Jun 21 23:43:36 that flashes image from SD? Jun 21 23:43:41 yes Jun 21 23:43:56 ok thx! Jun 21 23:44:14 it basically just reformats eMMC, copies over the contents of SD to eMMC, generates new SSH keys, stuff like that Jun 21 23:44:46 forgot I don't have SD reader right now Jun 21 23:45:22 bought some cheap one, but can't get it working on Arch Jun 21 23:45:47 if you can boot the BBB from eMMC, you've got an SD reader :) Jun 21 23:45:57 yeah, I heard of that Jun 21 23:46:32 right ;D Jun 21 23:46:32 just (as root) mkdir /mnt/tmp; mount /dev/mmcblk0p1 /mnt/tmp; vi /mnt/tmp/boot/uEnv.txt Jun 21 23:46:35 or so Jun 21 23:47:18 hm Jun 21 23:47:49 but how to reflash SD with that? Jun 21 23:48:14 oh I thought you already had a recent image on SD card? Jun 21 23:48:46 yea but I'm not sure if it's not a mess already) Jun 21 23:48:49 although, if there's any chance you somehow mucked up that image then you should probably wait until you can put a clean image on sd Jun 21 23:48:52 yeah Jun 21 23:48:52 fair enough Jun 21 23:49:40 don't know how to dd with.. sftp? Jun 21 23:49:54 is that possible? Jun 21 23:50:10 I also know how to turn a beaglebone into an sd card reader for your host, but that requires being able to reach the bbb by some means other than usb networking (i.e. ethernet or serial console) Jun 21 23:50:33 brb Jun 21 23:50:43 don't have that for now Jun 21 23:50:45 back Jun 21 23:50:52 ure fast Jun 21 23:51:15 well, later then Jun 21 23:51:24 anyway Jun 21 23:51:43 thanks for the tips Jun 21 23:52:09 you can also dd the image to /dev/mmcblk0 on the bbb... the problem is that you probably don't have space to keep the image temporarily on eMMC Jun 21 23:53:34 you could however for example do something like this on the beaglebone: ssh your-host cat image.img.xz | xzcat >/dev/mmcblk0 (beware: on some old systems, SD card might be mmcblk1 instead) Jun 21 23:53:43 maybe Jun 21 23:53:53 I think it's 16Gb Jun 21 23:54:07 the image isn't Jun 21 23:54:10 oh, eMMC Jun 21 23:54:14 right Jun 21 23:54:27 then unlikely Jun 21 23:54:35 latest iot image is < 0.5 GB compressed Jun 21 23:55:06 but the beaglebone ships with the gui image by default rather than the iot image, so eMMC might be stuffed pretty full Jun 21 23:56:14 I'll look into this Jun 21 23:56:39 of course if you like having a headache getting stuff to work, you can try installing Arch on the beaglebone too ;) Jun 21 23:57:04 haha Jun 21 23:57:17 It's unstable there Jun 21 23:57:31 as they told me Jun 21 23:58:31 I'll better stick with better-known things with great community) Jun 22 00:01:30 oh that key changed again Jun 22 00:10:53 stick with what you can work with I always say nothing worse than nothing working and showing nothing for your effort Jun 22 00:11:14 aand I have 424Mb free while image is 454Mb. No luck for today. Jun 22 00:12:29 Well, I learn if something isn't working Jun 22 02:22:47 Did someone say Motor Bridge Cape? Jun 22 02:25:49 I just checked and the Motor Cape (new) is in development. Do any people here need to have a tester? Jun 22 02:26:48 I can waste hours upon hours on more motors and a Motor Cape. Jun 22 02:27:01 waste = yea boy! Jun 22 02:31:56 someone has to do it? Jun 22 02:36:11 Right! Jun 22 02:36:45 me, me, me Jun 22 02:38:23 and the guy next too you apparently Jun 22 02:39:22 Ha. Jun 22 02:39:36 I was thinking... Jun 22 02:39:40 Yes...thinkin. Jun 22 02:40:15 I'll avoid thinking poetry.. really. Jun 22 02:40:50 I thought there is probably a reason for the "development" notion as of now instead of "production" label. Jun 22 02:40:51 ... Jun 22 02:40:57 This is what I thought. Jun 22 02:41:37 It likely means they haven't experimented enough on the suitability of the device in question. Jun 22 02:41:51 Aw. I understand. Jun 22 02:42:14 My thought is this...obviously these people are smarter than me in this subject. Jun 22 02:42:19 No guess work here. Jun 22 02:42:27 ... Jun 22 02:42:49 But...not all people are professional user space persons. Jun 22 02:43:00 Some people, most, are like me. Jun 22 02:44:11 they likely have more experience and knowledge yes. Always remember the Titanic was design by professionals and the Ark by ameteurs. Jun 22 02:45:16 Please remember...me, me, me. Jun 22 02:45:37 Forget the sunken and floaters. Me! Jun 22 02:45:42 ... Jun 22 02:45:43 Ha. Jun 22 02:46:03 Just joking. GenTooMan: Are you using a Motor Cape yet? Jun 22 02:46:37 set_: no I have a bit too busy with work. putting in rather long weeks. Jun 22 02:47:00 Oh. Me too. Jun 22 02:47:23 I have been mowing and going. 35000 sq. ft. and just me. Jun 22 02:47:31 Talk about boring days. Jun 22 02:47:57 I need a new thing in my life. Motors! Jun 22 02:48:29 Hmm that's about an acre I think an acre is 46000 that's boring to do with a push mower yes. Jun 22 02:48:58 Right. I have a trail cutter. The power is there, v-twin! Jun 22 02:49:12 Hardened steel blade, 30". Jun 22 02:49:20 Chop, chop. Jun 22 02:49:29 ... Jun 22 02:49:37 It use to take me 3 hours to mow the lawn but it was 1.5 acres. Jun 22 02:49:45 Not bad! Jun 22 02:49:59 Riding mower of course, otherwise it took 3 days Jun 22 02:50:21 It is a 750 x 520. I am on foot. Sometimes I use a riding mower. Jun 22 02:50:35 The riding mower is bumpy. Ouch. Jun 22 02:50:50 Anyway... Jun 22 02:51:14 I thought things w/ electronics could progress my "mowering" capabilities. Jun 22 02:52:02 Battery powered systems usually can have ATTACHMENTS! I had to yell b/c the "attachments" part is fascinating. Jun 22 02:52:02 Mowing is a dangerous and complicated process. Jun 22 02:52:20 ... Jun 22 02:52:23 Yep. Jun 22 02:52:32 Hint, hint. Jun 22 02:53:08 The best method is to start simple and get something simple to work. IE something that can cut straight rows and stop safely. Jun 22 02:53:21 I have tried to incorporate the BBB into mowing for years. I am a partitioned fat failure. Jun 22 02:53:32 For now! Jun 22 02:54:14 Your first challenge would be navigation no? IE getting the thing to move from a to b without going off in the weeds (litterally) Jun 22 02:54:26 I know. I cannot get over the remote control methods of things. I keep finding bogus info. and long tales. Jun 22 02:54:30 Oh... Jun 22 02:54:31 ... Jun 22 02:54:31 yea. Jun 22 02:55:51 I say remote control b/c navigation seems too complicated for now. Jun 22 02:55:58 So something that isn't a mower and you can control with simple inputs would be a start. Once you have it sort of navigating around then you can consider adding things to cut grass. A rumba is a similar application only for cleaning. Jun 22 02:56:21 Yep. I have a self-made prototype of sorts. Jun 22 02:56:38 dubed the chumba? Jun 22 02:57:02 It looks like a battle bot but it is for helping "hummanity.' Jun 22 02:58:01 "comes with well used TASER attachment for snoopy neighbors and riotous predators" Jun 22 02:58:28 I actually have this thing plugged in right now. It makes its lefts, rights, and straights well done. Jun 22 02:58:29 ... Jun 22 02:58:56 It is like a tornado. It starts wide and long and then promotes to inner squares. Jun 22 02:59:28 ...I know. Boring! But...it is cool to me. Jun 22 02:59:31 Only it doesn't suck? standard edge following with cut material outward. **** ENDING LOGGING AT Fri Jun 22 03:00:01 2018