**** BEGIN LOGGING AT Sat Feb 23 02:59:56 2019 Feb 23 12:07:24 bbb can take 12V from barrel jack? just saw email in mailing list. Feb 23 12:08:29 sicelo: no Feb 23 12:09:01 all beaglebone variants require 5V, except for the beaglebone blue Feb 23 12:09:30 that's what i thought too. in fact, mine has a 5V sticker on the power-in jack Feb 23 12:09:52 maybe he meant the blue .. he just said BBB Feb 23 12:10:46 the beagleboard-x15 also uses 12V, but that's not a beaglebone Feb 23 12:11:34 true. i've never seen all these boards, except online :) Feb 23 12:11:44 you can feed it 12V *once* scnr… Feb 23 12:11:58 i was lucky to get gifted the BBB at a debconf a couple of years ago Feb 23 12:12:06 *black, that is Feb 23 12:43:10 I wish designers didn't use USB or barrel jacks for DC power on this sort of thing. They're OK for desktop experiments but awful for boards that are built into things. Would like to see JST or molex style latching board connectors, or rising-block terminals. Feb 23 12:43:43 artag: you can power the beaglebone via the P9 header Feb 23 12:44:04 which is what is typically used when integrating the beaglebone into things Feb 23 12:44:21 that's exactly what I'm doing. But I have to have a little daughter board (which carries a switching regulator in this case) Feb 23 12:45:32 well normally when the beaglebone is built into something, you need more stuff connected to it than power anyway Feb 23 12:45:42 having a usb gadget interface on the usb power at least makes that somewhat sensible, unlike r-pi Feb 23 12:46:13 well usb has also become the standard for powering stuff Feb 23 12:46:39 sure, for portable objects. but a board-level thing isn't really that. Feb 23 12:46:57 and usb micro is a pretty awful standard Feb 23 12:47:12 hmm? Feb 23 12:47:29 they break off too easily and are at the limit of their power handling Feb 23 12:47:47 and the latches don't work very well Feb 23 12:48:15 because they're designed to be easy to remove, not reliably fixed in place Feb 23 12:48:18 I can't say I've had much trouble with them, but I also don't have a lot of things that use micro-usb (the BBB is mini) Feb 23 12:49:16 mini is a bit more robust but actually rated for lower insertions and latches even less well. That tends to fall out, whereas micros tend to get torn off the board. Feb 23 12:49:44 C is rated higher but still a bit flimsy Feb 23 12:50:06 maybe try to abuse your hardware a bit less? ;) Feb 23 12:50:18 :) Feb 23 12:52:41 I had a teensy at a burning man event. It was my backup - I used it to test s/w before putting it on the real unit (which was safely boxed up). Just caught it with my hand one time and I had a power-less teensy. Good thing I didn't need it as a spare ! Feb 23 19:17:17 Is there a way to tell how all my gpio's configured on my BBB? Feb 23 19:20:29 zmatt made a script for this Feb 23 19:20:32 if I remember correctly Feb 23 19:21:00 now I have to remember his github handle Feb 23 19:21:24 @mawk do you know where is the scrip located? Feb 23 19:21:52 My problem is some BBB kernels don't work with the touch screen LCD. Feb 23 19:22:04 I'm searching Feb 23 19:22:28 https://github.com/mvduin/bbb-pin-utils Feb 23 19:22:45 So I am trying to find out what are the different setting on the GPIO's to get the LCD up and goin. The LCD works with ubuntu 18 but not with the 14 Feb 23 21:19:30 * zmatt . o O ( so... use ubuntu 18 ? or better yet, use an image that's actually supported? ) Feb 23 21:29:01 zmatt I would suggest debian unless you need comercial support. ALL Linux drivers are way behind however in support. So you can't use newer machines with linux. Namely because of the way things are setup between the manufactures and SW systems with NDA's if it's open source you can't write an open source driver. Feb 23 21:29:46 what are you talking about? Feb 23 21:30:03 ubuntu use? Feb 23 21:30:16 my remark was referring to the guy who apparently was trying to run ubuntu 14 on his beaglebone Feb 23 21:30:39 woa... that's kind of retro. Feb 23 21:30:54 I'm programming in D Feb 23 21:30:55 because why not Feb 23 21:31:02 20:22 < KK> So I am trying to find out what are the different setting on the GPIO's to get the LCD up and goin. The LCD works with ubuntu 18 but not with the 14 Feb 23 21:31:09 mawk: why not in rust? Feb 23 21:31:20 rust is neat Feb 23 21:31:27 yeah people keep asking me this Feb 23 21:31:32 I don't know, I haven't tried rust yet Feb 23 21:31:38 I was looking for a C replacement for systems programming Feb 23 21:31:52 may you rust in peace? Feb 23 21:31:59 and I thought rust will maybe be too cumbersome for system; but it's on my list of languages to try next Feb 23 21:32:10 which has rust, go and haskell Feb 23 21:32:50 go and haskell seem odd entries for that list Feb 23 21:33:03 it's not a list for system programming, just a general list of languages I want to learn Feb 23 21:33:07 ok Feb 23 21:33:15 but the ones for system programming are d, go and possibly rust Feb 23 21:33:35 go? even though it needs a heavy runtime with gc? Feb 23 21:33:41 (iirc) Feb 23 21:34:12 I don't know how go works under the hood; I'd say that D needs a heavy runtime with GC too Feb 23 21:34:21 but as long as the performance is here I don't really mind Feb 23 21:34:23 I don't know much about D Feb 23 21:34:38 what I need is just good interoperability with the syscalls and other C functions and structures Feb 23 21:35:30 D has an optional runtime that has a GC, otherwise the language is like a better C Feb 23 21:35:54 and with a clearer grammar that is fully unambiguous and can be parsed in a single pass, so compiles fast Feb 23 21:35:59 but that's just the icing on the cake Feb 23 22:02:01 it's all a matter of available resources and if other applications need the system whilst it's running I guess. Feb 23 22:04:16 also yeah I picked go because I heard it's been engineered specifically for networking Feb 23 22:04:37 so fits perfectly what I do in systems programming Feb 23 22:04:51 not especially networking but there's always an event loop here and there when I do stuff Feb 23 22:05:09 and I like coroutines, and callbacks aren't that nice Feb 23 22:17:26 call backs can be a pain, namely you get weird results if you are careful. I despise them especially from interrupts. Feb 23 22:18:03 aren't careful me and my typing skills well the keyboard is especially slow to boot. Feb 23 22:19:06 Can I overwrite the following directory in Beaglebone /sys/kernel/debug/pinctrl/44e10800.pinmux? Feb 23 22:19:27 lol, no Feb 23 22:19:38 Why not? Feb 23 22:19:56 kk: why are you trying to use an obsolete version of an obscure (on the beaglebone anyway) distro Feb 23 22:19:59 ? Feb 23 22:20:04 because it's a file with some debug information Feb 23 22:20:23 reflecting the current state of pinmux Feb 23 22:20:37 Isn't 44e10800.pinmux where all the gpios getting configured? Feb 23 22:20:45 (which depends on your Device Tree configuration and driver requests) Feb 23 22:21:04 it has no information about gpios, it has information about pinmux Feb 23 22:21:34 debug info about gpio is in /sys/kernel/debug/gpio/ Feb 23 22:21:47 The problem I have I built my machine with Ubuntu 14.04 and works fine but now I want to add the touch screen LCD but the touchscreen LCD doesn't work with 14.04 unless if I change it to unbuntu 18 Feb 23 22:22:15 So I want to find a way to change the pinmux file so I get the LCD to work Feb 23 22:22:18 why are you not using a debian image that's actually recommended and supported? Feb 23 22:22:45 Because I am using other devices and they didn't work with Debian Feb 23 22:22:56 if you use an unofficial image, you can expect to have to deal with problems like these Feb 23 22:23:21 No the ubunto is an official image. I got it from BBB website Feb 23 22:23:49 https://beagleboard.org/latest-images I don't see any ubuntu image here Feb 23 22:24:36 ok let me check where I got the image I will send you a link Feb 23 22:24:58 I don't need a link, I know ubuntu images exist Feb 23 22:25:12 I'm just pointing out they are not the official images from the beagleboard.org website Feb 23 22:25:13 https://elinux.org/Beagleboard:Ubuntu_On_BeagleBone_Black Feb 23 22:25:19 yeah, that's a random wiki page Feb 23 22:25:30 Ohh really? Feb 23 22:25:44 not completely random of course, but those are not officially supported images Feb 23 22:25:46 Ok let me try Debian and see if I can get it to work Feb 23 22:25:56 moreover, you said it works with the current version of ubuntu Feb 23 22:26:03 Ok thanks for the advice Feb 23 22:26:25 The LCD works with Ubuntu 18 Feb 23 22:26:29 but not 14 Feb 23 22:26:32 saying "it doesn't work when I use a ancient and obsolete version of the OS" will pretty much guarantee the response "so don't use an ancient and obsolete version" Feb 23 22:27:23 Ok let me try debian and see if that will work Feb 23 22:28:01 you should only use unofficial images or ancient images if you have sufficient knowledge of embedded linux systems to be able to fix any problems you'll invariable run into Feb 23 22:28:11 *invariably Feb 23 22:28:50 kk zmatt speaks reality don't try to use something you can't get help with easily or is impossible to fix Feb 23 22:29:24 Ok please let me know which link on the BBB images has the emmc flasher? Feb 23 22:29:42 I don't want to install an image to work on SD card only Feb 23 22:30:21 that page doesn't have any flashers (annoyingly), but you can turn any image into a flasher by uncommenting one line in /boot/uEnv.txt Feb 23 22:30:45 (the line has "flasher" in it, I think it's near the bottom) Feb 23 22:32:27 So you saying I need to create the sd card and after I boot I go to /boot and edit uEnv.txt Feb 23 22:33:15 for convenience, strawsondesign hosts flasher images: http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz (which should just be the same as the official image but with /boot/uEnv.txt modified. I haven't verified this image, but I think I'd trust strawsondesign to not have fucked up this simple thing) Feb 23 22:33:32 yes, that's the typical way Feb 23 22:34:04 e.g. you use sudo nano /boot/uEnv.txt Feb 23 22:34:27 ok let me try Feb 23 22:34:28 uncomment the last line of the file (remove the "#" in front of "cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh"), save it, and then reboot Feb 23 22:35:26 ok thanks zmatt Feb 23 22:50:01 zmatt your ubuntu comment makes more sense now :D **** ENDING LOGGING AT Sun Feb 24 02:59:56 2019