**** BEGIN LOGGING AT Sun Jan 07 03:00:01 2018 Jan 07 03:00:11 Wei_: neither do I, but if you're using Windows 10 and have a sufficiently recent image flashed onto your beaglebone (I'm assuming you're using a beaglebone?), then you don't need to install any drivers at all Jan 07 03:01:18 ignores the sd card... does CCCCC like it is waiting for serial transfer Jan 07 03:01:39 jonnyw2k: yeah, so it's cycling through the boot methods Jan 07 03:01:44 including xmodem transfer Jan 07 03:01:56 But I just get start and read the START. Jan 07 03:02:28 Wei_: https://bbb.io/getting-started Jan 07 03:02:42 Step #2: Install drivers Jan 07 03:03:02 this is the #2 step I should do? Jan 07 03:03:09 Wei_: https://bbb.io/getting-started Jan 07 03:03:48 Wei_: most likely your beaglebone contains pretty old software. try booting from sd card or reflashing it (see the link I just gave) Jan 07 03:04:00 Yeah, I'm reading it now. Jan 07 03:04:48 mine Jan 07 03:04:49 jonnyw2k: so, the ROM bootloader is periodically trying to boot from sd card, but it decides it's not a viable boot device Jan 07 03:10:17 urghhh my bbb are too old Jan 07 03:11:41 doesn't support having /boot in the ext4 partition Jan 07 03:16:40 you're trying to boot from sd card on a BBB with ancient crap flashed to eMMC? Jan 07 03:16:52 power up while holding down the S2 button to bypass the ancient bootloader on eMMC Jan 07 03:20:01 yeah so the SD card works in a BBB and a different pocketbeagle, so that kind of rules out the usd card itself, probably just going to have to accept defeat and RMA it Jan 07 05:15:49 When show-pins returns P9.15 twice (two rows), what does that mean? Jan 07 05:15:53 P9.15 16 fast rx 7 gpio 1.16 lo >> P9_15 (pinmux_P9_15_gpio_pin) Jan 07 05:15:55 P9.15 34 fast rx up 7 gpio 2.00 Jan 07 05:23:23 for context: I am trying to get a SSD1351 based oled to work with SPI. Trying to run test.py from https://github.com/twchad/Adafruit_Python_SSD1351/blob/master/examples/test.py and have to configure P9.12 and P9.15 for Reset and DC ... that's why I ran `config-pin P9.12 out` and `P9.15 out` Jan 07 05:24:44 (also not sure if this is the go-to library) Jan 07 06:15:14 When I load the driver `sudo modprobe fbtft_device busnum=1 name=fb_ssd1351 gpios=dc:48,reset:60` dmesg returns "b_ssd1351: module is from the staging directory, the quality is unknown, you have been warned." ... but no fb* device in /dev Jan 07 06:23:58 any idea what I could try to identify the problem? Jan 07 06:28:43 ok so I rebooted and loaded the SPI0 uboot overlay. Then I tried `sudo modprobe fb_ssd1351 busnum=1 gpios=dc:48,reset:60` and just `sudo modprobe fb_ssd1351` ... but I get the error "[ 447.921369] spidev spi1.1: spidev spi1.1 16000kHz 8 bits mode=0x00 Jan 07 06:28:45 [ 447.921382] spidev spi1.0: spidev spi1.0 16000kHz 8 bits mode=0x01 Jan 07 06:28:47 [ 447.921479] fbtft_device: display not supported: 'fb_ssd1351'" Jan 07 06:28:57 oh sorry for formatting Jan 07 06:52:04 oh :) Jan 07 06:52:06 [ 2031.035312] graphics fb0: fb_ssd1351 frame buffer, 128x96, 24 KiB video memory, 4 KiB DMA buffer memory, fps=20, spi1.0 at 10 MHz Jan 07 06:52:22 so the solution was `sudo modprobe fbtft_device custom name=fb_ssd1351 busnum=1 buswidth=8 gpios=dc:48,reset:60 speed=10000000 width=128 height=96 bgr=1 Jan 07 06:52:24 init=-1,0xFD,0x12,-1,0xFD,0xB1,-1,0xAE,-1,0xB3,0xF1,-1,0xCA,127,-1,0xA0,0x74,-1,0x15,0x00,0x7F,-1,0x75,0x00,0x7F,-1,0xA1,96,-1,0xA2,0x0,-1,0xB5,0x00,-1,0xAB,0x01,-1,0xB1,0x32,-1,0xBE,0x05,-1,0xA6,-1,0xC1,0xC8,0x80,0xC8,-1,0xC7,0x0F,-1,0xB4,0xA0,0xB5,0x55,-1,0xB6,0x01,-1,0xAF,-3` Jan 07 06:52:48 this might have been the most arcane command line I have ever entered anywhere lol Jan 07 06:56:57 Note to self: This took an hour to solve. I am getting faster every time I fail! Jan 07 06:59:12 That's what they say, fail faster! Jan 07 06:59:22 seriously Jan 07 06:59:36 I think displays are one of the most complex components to understand Jan 07 06:59:36 Someday I'll invent a 4d printer that allows me to print failed parts before they've even been modeled. Jan 07 07:00:08 ok ask me for the init sequence then :P Jan 07 07:00:47 but it makes kind of sense, and I start to understand, it is just really demanding to look at the datasheets, select what kind of stuff on github you believe in, and all that Jan 07 07:03:09 so ... now I want to show the read out of my temperature sensor on that display. Any easy way to pipe command line output to /dev/fb0? Jan 07 13:35:41 Hello, I'm getting started with beagleboards, and have a quick question on the Device Tree. According to the AdaFruit tutorial on the DT, you need to make sure you add the compatibility list, such as `ti,beaglebone-black`. How do you find the appropriate name for your device? E.g. I'm on a BBB-wireless... is this the same as a BBB? If someone can point me in the right direction, it would be much appreciated Jan 07 14:16:31 lifesayko: do you mean DT itself or overlays? what are you trying to do with it exactly? Jan 07 14:23:43 hi, I am new for BBB. Just following the book exploringBeagleBone Jan 07 14:24:08 I've got some question. Jan 07 14:25:30 it seems that slots is no longer support since 4.4.x. So how do we interface the capemanager? Jan 07 14:27:24 capemanager still exists in 4.x, although in the very latest systems (since a few months or so) it's handled in u-boot instead of in the kernel Jan 07 14:27:52 for most purposes you don't need overlays anymore anyhow, since most functionality can be configured at runtime using config-pin Jan 07 14:34:09 Great! Thx! Jan 07 14:34:21 trying now! Jan 07 14:35:51 where can I get some info about the file system of latest debian? Jan 07 14:37:00 not sure what you mean by that Jan 07 14:37:37 suppose on the book or web page, there is /sys/kernel/debug/pinctrl/44e10800.pinmux/pins Jan 07 14:38:02 but in my bb, there is not. where shall I find them? Jan 07 14:39:29 uhh, just dig around, something like it should exist Jan 07 14:39:37 my show-pins script makes use of it Jan 07 14:39:40 okay, thx! Jan 07 14:40:21 I'm trying to set up the DTS for using CAN communication as described here: http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/ Jan 07 14:40:47 ztliu: /sys/kernel/debug/pinctrl/44e10800.pinmux/pins should actually definitely exist, otherwise my script would fail as well Jan 07 14:40:58 and I haven't heard any reports yet that it doesn't Jan 07 14:41:30 lifesayko: do the can interfaces show up already when you check with 'ip link' ? Jan 07 14:41:52 ztliu: any reports that it fails, I mean Jan 07 14:42:33 No, I haven't hooked it up yet, I thought I'd follow all the configuration steps first. Is this supposed to actually work out of the box now? Jan 07 14:42:43 zmatt: sorry, I've copied the wrong thing, I mean /sys/devices/bone_capemgr.9/slots Jan 07 14:43:43 lifesayko: I don't know, that's why I asked whether the can interface(s) exist immediately after boot, without further configuration Jan 07 14:44:12 lifesayko: if the can interface you want to use exists, then all you need is to use config-pin to setup the pinmux and then you can configure the interface and bring it up Jan 07 14:44:22 and then you were gone Jan 07 14:45:06 I see. As far as I can tell, it doesn't work out of the box: the CAN pins need to be expressly defined with a DTS. I can check tomorrow (don't have something to hook it up to atm) Jan 07 14:45:42 you don't need to have anything hooked up to check whether the interfaces exist Jan 07 14:46:25 But on a related note: according to that tutorial, to set the DTS I need to run `echo BB-DCAN1 > /sys/devices/bone_capemgr.*/slots`, but when I do that I get `No such file or directory` which seems really odd Jan 07 14:47:21 1. that path is severely obsolete 2. since half a year or so, capemgr is done in u-boot instead of in the kernel Jan 07 14:47:39 Aha. Okay, I ran `ip link` and get (among other things) `can0: mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 10 link/can` (and the same thing for can1) Jan 07 14:47:51 ok, so no overlay is needed at all Jan 07 14:47:57 just use config-pin to setup pinmux Jan 07 14:48:09 and then you can configure and bring up the interface Jan 07 14:49:27 awesome thank. Btw, do you have a reference that is up to date on this stuff? (like setting up pinmux with config-pin...) Jan 07 14:49:44 I find I'm wading through a lot of things just figuring out what is relevant and what isn't... Jan 07 14:50:18 I think it's just something like config-pin P9.24 can && config-pin P9.26 can Jan 07 14:51:35 thanks a lot! : ) Jan 07 14:53:14 in general, if it's years old, it's obsolete ;) Jan 07 16:02:32 lifesayko: It seems most of the changes are discussed in the Google Group for Beagle. It might make sense for you to subscribe to email updates there to stay up to date. I'm also having a steep learning experience, but so far it is rewarding. Jan 07 16:04:37 lifesayko: My rule of thumb is: If the article talks about $slots or capemgr.something I disregard that section, wehreas Linux userland stuff has a longer relevancy. It's so complicated because of the changes to the way pin muxing is done in the Linux Kernel. There are a couple of background articles on that. Jan 07 16:09:46 yeah, there were a few iterations in the kernel and basically most stuff that is out there is outdated kernel wise Jan 07 16:15:05 Yeah that part was really the hardest to get. And .dts files still freak me out with their semantics. config-pin and show-pins is pretty newbie friendly and a good way to learn, but mso much writing on the beagle bone happened in 2013 and 2014, so that is still very highly ranked by Google so that old stuff comes up a lot. If the eLinux wiki were editable, I would contribute some info just along picking it up Jan 07 16:15:07 for myself. Now I am keeping a OneNote doc on what actually works. Jan 07 16:18:09 Google should offer a deprecated warning for certain keywords to technical communities Jan 07 16:19:47 fasle: I get good mileage within Google search results -> Tools -> Any time -> past year Jan 07 16:20:28 yeah that is how I do it as well for these topics. Did you find out how to show search tools by default? I wish I could save me that extra click sometimes. Jan 07 16:33:22 fasle: ping wmat here on freenode for elinux write access Jan 07 16:56:49 cool thanks Jan 07 17:03:30 fasle: no sorry, not sure it's possible to set default search filters.. Jan 07 17:45:59 tbr: done Jan 07 17:49:44 :) Jan 07 17:51:26 anyboy here? i was wondering if the beagleboard x15 can boot automatically after a power outage... Jan 07 17:55:13 I think it's default to boot on power connect Jan 07 17:56:00 hm... maybe not on the x15... https://groups.google.com/forum/embed/?&parenturl=http%3A%2F%2Fbeagleboard.org%2Fx15&showsearch=true&showpopout=true&showtabs=true&place=forum/beagleboard-x15#!searchin/beagleboard-x15/auto$20power/beagleboard-x15/fck_GaOiV_o/tQZoS9spFgAJ Jan 07 17:59:21 maybe i'll try the j5 jump... but i don't quite understand the side effects mentioned. one poster says it could damage the processor after 120 hours, another seems to think it'd be ok as long as i'm not debugging u-boot Jan 07 18:00:29 right, there was something. I have to admit I haven't booted my X15 in ages Jan 07 18:01:35 the problem they reference is that until either u-boot is fully run or a linux kernel running, there is a state where some pin is loaded in a way that's "known not good in long term" Jan 07 18:02:27 thx tbr! that sounds like as long as i intent to always immediate boot linux, i should be ok Jan 07 18:02:59 yes Jan 07 18:03:27 later someone mentions some pmic behaviour oddities, just note them Jan 07 18:04:36 one more question - anyone know offhand a good workaround device or guide that can press the power button momentarily, maybe i can rig something to happen on power restore Jan 07 18:05:31 seems inelegant, but i'd guess somebody may have tried this with some device somewhere before... Jan 07 18:15:50 it's possible, but like you said, it's not very elegant Jan 07 18:16:29 although it would allow shutting down under software control at least (and auto-shutdown if no bootloader can be reached) Jan 07 18:22:49 cool thx zmatt Jan 07 18:33:09 It would be a little embarrassing to lash a 555 to your x15 as a power-on pulse generator, but it would work.. Jan 07 18:34:56 Grab an old wake-on-LAN NIC and solder it over :D Jan 07 18:40:08 cool ideas myself :) Jan 07 18:52:01 Hey, I am a 2nd year student (UG) and was wondering if there is any way that I can contribute to Beagle. I have had very less experience in C but want to gain more of it as I have a lot of interest in embedded systems. Can you help me out in some way that I can contribute and learn? Jan 07 18:52:30 what sort of projects interest you, anant? Jan 07 18:53:38 like, are you more into the electronics and physical/mechanical systems, motion control and CNC, that sort of thing? Or does pure software sound more fun, working on drivers and OS-level stuff? Are you fond of radio? Optics? Cars? Jan 07 18:54:40 And, do you have any interest in programming the PRUs? Jan 07 18:55:14 So I love to play with things that are more on the lower level like OS and Systems. I have had amazing projects using arduinos. But for me it has become more exciting to work on drivers. Jan 07 18:55:51 This comes to mind: I think there'd be a lot of interest in a CAN controller that lives in the PRU so you have more access to how it works: https://www.reddit.com/r/CarHacking/comments/7mgix1/can_transceiver_with_beaglebone_black_prus/ Jan 07 18:56:27 Also hacking up the stock linux SPI driver to support more chip-select lines using arbitrary GPIO would be nice :) Jan 07 18:56:48 myself: stock SPI driver already supports gpio chip selects Jan 07 18:57:13 Oh. I wonder if I was tinkering with an old version or just failed to rtfm properly. Jan 07 18:57:13 it has for quite a while already Jan 07 18:57:31 I think it needs kernel 4.9 or later, but I'm not 100% sure Jan 07 18:57:36 Last I really poked at it was ~3 years ago, so... Jan 07 18:57:56 but we use it in production, so it definitely works Jan 07 19:02:10 uhm. You will have to guide me a little more, I am a noob here. Jan 07 19:03:29 My standard advice for noobs is to take an interesting project that someone else has published, and copy it, just a simple copy. Just doing that, you'll encounter little details they didn't document, outdated things you need to fix, etc. You'll build skills and familiarity. Jan 07 19:03:47 And then once you have something working, start changing parts of it. Jan 07 19:04:05 That's why I was trying to get a sense of what sorts of things you find interesting, what sorts of projects motivate you. Jan 07 19:10:55 Ok, so I was checking out one of your projects related to synchronous data collection. That seemed intersting to me. Jan 07 19:12:58 I have had good experience with Verilog and running programs on FPGAs. But I wanted to get into embedded C and assembly programming related projects and this seemed pretty cool. Jan 07 19:29:52 the bbb *is* pretty cool... albeit suffering from a bit of lack of good uptodate documentation Jan 07 19:32:01 anant3110: How about you build a neat solution that makes it really easy to use & configure the PRUDAQ cape from a remote sigrok session on a desktop? That would be really cool and you could learn about PRU and all the hard stuff :) Jan 07 19:36:00 This seems pretty amazing and doable. To whom do I report back to? Jan 07 19:37:13 uhm well if you need beta testers, I'd be glad to help, but this stuff is way above my head. I do not know the developer, but I'd guess he would not mind some input because there are a lot of open ends, for example the server app when I last checked Jan 07 19:38:52 okay! So what I will do is get back here if there is some progress :) Jan 07 19:39:14 For the server: Would be great to have a system that I can remotely pulse to start sampling, and then get XML or raw data depending on the amount of data via a web API. Jan 07 19:40:11 awesome looking forward, send your most private phone number so I can remind you every day >-) Jan 07 19:58:10 lol Jan 07 19:58:34 this doesn't smell like ulterior motives at all, not at all Jan 07 20:02:13 hey when someone shows up and says "hand me a task", you hand 'em the most useful task! Jan 07 20:02:23 :) Jan 07 20:12:28 If you ever need a task, I'll be always there for you Jan 07 20:19:11 Speaking of a task... I am stuck with getting a SSD1351 based oled to work over SPI. (https://www.mikroe.com/oled-c-click). Here I collected my current dmesg, pinmux, lsmod, etc.output: https://pastebin.com/raw/UZes8KEL Jan 07 20:20:25 I'm at a loss because I don't really get any errors, but the display just does not do anything. My next step would be hooking it up to the Arduino and see if it works there. But maybe there's someting simple I oversaw. Jan 07 20:23:37 I'm a huge fan of hooking things up to an arduino and copypaste some working example code, just as a sanity-check against a dead chip or whatevre Jan 07 20:23:51 ok will do that first and report back Jan 07 20:24:37 hello. can someone help me with beaglebone black flashing? I am trying to do in next way: http://git.free-electrons.com/training-materials/tree/lab-data/common/bootloader/beaglebone-black/README.txt. But there is nothing happend while i am pressing BootSwitch Button Jan 07 20:27:04 It's unclear to me if you want to change the bootloader or install an operating system? Jan 07 20:31:36 I want to change bootloader Jan 07 20:31:39 uboot Jan 07 20:32:57 I feel like the single best thing that could happen to the Beaglebone community right now would be some magical web-wizard would cast 'Force Outdated Documentation To Identify Itself As Such And Link To Current Stuff' on all those stale pages. It's lovely that people were so excited about the beaglebone when it first came out, but... imagine if the front page of CNN right now was 80% full of news about Warr Jan 07 20:33:03 en G. Harding and Calvin Coolidge. Jan 07 20:35:50 myself: that might not be *so* bad Jan 07 20:36:48 this. Also lots of distributed info around in various blogs compared to the "authoritative" sources. I really wonder how the Arch Wiki folks manage it, they seem to get it right. **** ENDING LOGGING AT Mon Jan 08 03:00:02 2018