**** BEGIN LOGGING AT Fri Nov 20 02:59:58 2015
Nov 20 04:47:20 <Set_> hello...
Nov 20 08:41:00 <GrumpeiYokoi> So does the BBB use the PRUs to drive HDMI or something? Or is it just some kind of bus conflict to use them at the same time?
Nov 20 08:44:03 <av500> no
Nov 20 08:44:10 <av500> PRU has nothing to do with HDMI
Nov 20 08:44:18 <av500> HDMI is on the LCD pins
Nov 20 09:13:22 <zmatt> which is also the only mux option for nearly all I/Os of pru core 1
Nov 20 09:14:07 <zmatt> hdmi audio also conflicts with some pru core 0 gpio pins
Nov 20 09:14:47 <zmatt> so there's not really any intrinsic kind of conflict between HDMI and PRU, but HDMI steals more than half of the available pru gpios
Nov 20 09:14:51 <zmatt> due to mux conflicts
Nov 20 09:15:08 <zmatt> (HDMI or LCDC in general)
Nov 20 09:19:31 <GrumpeiYokoi> So... you could in theory use them at the same time if you were careful?
Nov 20 09:21:16 <GrumpeiYokoi> I'm mainly asking because everything I read about PRUs indicates you should disable HDMI
Nov 20 09:27:48 <zmatt> it's a simple matter of making sure you don't have a pin conflict
Nov 20 09:28:19 <zmatt> there's not really a "being careful" factor since the kernel will simply refuse conflicting pinmux requests
Nov 20 09:28:52 <GrumpeiYokoi> Ah, right
Nov 20 09:29:23 <GrumpeiYokoi> I keep forgetting the kernel is at least somewhat control w/r/t IO
Nov 20 10:18:43 <zmatt> if you let it, yes
Nov 20 10:18:46 <zmatt> O:)
Nov 20 10:19:05 <zmatt> but doing so is indeed recommended for things like pinmux
Nov 20 10:19:15 <GrumpeiYokoi> Oh, right, you're a rawarrior
Nov 20 10:19:22 <zmatt> lol
Nov 20 10:20:45 <zmatt> btw, not sure if I shared it already, but if you ever have any doubts about the state of your pinmux, I made a script that displays it -> http://gerbil.xs4all.nl/show-pins-v2.pl.gz
Nov 20 10:28:43 <GrumpeiYokoi> I was always scared of Perl b/c of all the 'or die' statements
Nov 20 10:28:49 <GrumpeiYokoi> i don't want my scripts to die :(
Nov 20 10:28:55 <zmatt> lol
Nov 20 10:28:59 <zmatt> I do
Nov 20 10:29:14 <zmatt> I deliberately make sure the script dies if anything doesn't parse exactly as expected
Nov 20 10:29:42 <zmatt> better that than risking misparsing and misinterpreting the data and as a result presenting bullshit to the user
Nov 20 10:30:15 <GrumpeiYokoi> Well, I'd really have to strain to read this but it could come in handy, thanks.
Nov 20 10:30:38 <zmatt> make sure you make your terminal window wide enough for its output
Nov 20 10:30:46 <GrumpeiYokoi> (I hardly know perl at all)
Nov 20 10:30:47 <zmatt> otherwise it'll be a pain obviously
Nov 20 10:30:52 <zmatt> well you don't need to read the script
Nov 20 10:31:07 <zmatt> you run it and stare at the pretty output :P
Nov 20 10:31:17 <GrumpeiYokoi> Certainly, but it is nice to be able to understand the things you're using
Nov 20 10:32:13 <GrumpeiYokoi> The last time I looked at a Perl script it was to fix a build problem with LLVM on Windows
Nov 20 10:32:26 <KotH> GrumpeiYokoi: i'm pretty sure there is a module so that you can write "or seppuku" in perl ;)
Nov 20 10:32:43 <GrumpeiYokoi> Which usually leads to death :)
Nov 20 10:32:54 <GrumpeiYokoi> That's funny, either way
Nov 20 10:33:19 <zmatt> GrumpeiYokoi: trying to read an ugly little perl script I hacked together in very little time will not help you with any pinmux problems
Nov 20 10:34:01 <GrumpeiYokoi> Their build script involved, shell, perl, python, makefiles, a custom program that generates C++ code from another language, and also supported CMake
Nov 20 10:34:10 <Shadyman> hurk
Nov 20 10:34:15 <GrumpeiYokoi> It was a lot of moving parts
Nov 20 10:34:21 <GrumpeiYokoi> I don't think it's as all over the place these days
Nov 20 10:34:46 <zmatt> sounds like https://codepoints.net/U+1F4A9
Nov 20 10:36:09 <GrumpeiYokoi> "dog dirt"
Nov 20 10:36:16 <GrumpeiYokoi> Quite a euphemism
Nov 20 10:36:53 <zmatt> just a synonym, the official name is, as you can see, pile of poo
Nov 20 10:36:54 <GrumpeiYokoi> I like how they have to explain what feces are
Nov 20 10:37:05 <zmatt> I think that's just scraped from wikipedia?
Nov 20 10:37:12 <zmatt> indeed it is
Nov 20 10:37:13 <GrumpeiYokoi> yeah
Nov 20 10:37:31 <GrumpeiYokoi> But that they felt the need to cite an explanation for what feces are kind of tickles me
Nov 20 10:38:25 <GrumpeiYokoi> I think of Unicode as a very dry, technical subject so I guess this softens them a bit in my eyes
Nov 20 10:38:30 <GrumpeiYokoi> softens their stool
Nov 20 10:38:52 <tbr> time to use https://codepoints.net/U+2620 for function names and variables
Nov 20 15:26:38 <zmatt> hmm... dilemma
Nov 20 15:26:46 <zmatt> the easy solution or the interesting solution?
Nov 20 15:26:47 <rcn-ee> do it!
Nov 20 15:29:03 <zmatt> on linux I can now conveniently trap bus errors with try-catch (although it's of course slow as fuck due to two visits to kernel space)
Nov 20 15:29:15 <zmatt> now I need something similar on baremetal
Nov 20 15:30:24 <zmatt> am I going to try to get unwinding to work there (in general, and in particular through an exception frame, and without pulling in some giant pile of unwinding code)
Nov 20 15:30:48 <zmatt> or use some quick hack to just make it work for the single use case I have right now
Nov 20 15:30:53 <zmatt> hmm
Nov 20 19:14:42 * zmatt curses Arteris for the obnoxious restrictions on the interconnect registers
Nov 20 19:15:01 <punto_> hi
Nov 20 19:27:08 <beagle_TI> hello
Nov 20 19:27:32 <beagle_TI> I wish to use 30 GPIO pins on BBB
Nov 20 19:27:42 <beagle_TI> but board has only 19
Nov 20 19:27:56 <beagle_TI> is there any way i can increase the no of pins
Nov 20 19:28:10 <beagle_TI> or change the other pins in GPIO
Nov 20 20:37:28 <_av500_> BBB has 68 or so GPIOs
Nov 20 20:52:33 <Mian> Hello, first time to be here...
Nov 20 20:53:40 <zmatt> _av500_: weird indeed, I wonder where he got the 19 from
Nov 20 21:28:12 <_av500_> Mian: keep it here
Nov 20 21:36:52 <James_Johnson> dammit someone asks a question that I know the answer to and they leave
Nov 20 22:14:00 <chillfan> hey
Nov 20 22:14:27 <chillfan> has anyone tried building debian for the beagle bone black? I'm having some issue with it
Nov 20 22:15:30 <chillfan> on running the vmdebootstrap script provided by debian I get Command failed: /usr/share/debootstrap/examples/beagleboneblack-customise.sh /tmp/tmpvIKTUp
Nov 20 22:15:52 <chillfan> and python throwing a traceback seems to be the problem
Nov 20 22:17:21 <chillfan> i'm guessing I'm missing some python module or another but the debian guide doesn't exactly state the pre-requisites for this
Nov 20 22:17:41 <James_Johnson> shouldn’t reading the traceback tell you what the problem is?
Nov 20 22:18:23 <chillfan> if i understood what it goes on about maybe
Nov 20 22:18:56 <James_Johnson> can you at least put the traceback up on pastebin or something?
Nov 20 22:19:16 <chillfan> sure, i'll have a go
Nov 20 22:19:35 <chillfan> it's a tad annoying as i'm doing the build itself inside a vm
Nov 20 22:19:42 <chillfan> but i'll have a go at putting it somewhere
Nov 20 22:27:29 <chillfan> give me a min, setting up the vm with an xserver/browser
Nov 20 22:37:03 <chillfan2> http://pastebin.com/cmnNHbAw
Nov 20 22:37:18 <chillfan> that's basically the issue ^
Nov 20 22:43:08 <James_Johnson> chillfan you may have to look at the vmdeboostrap source to see what command is failing
Nov 20 22:51:35 <chillfan> hm
Nov 20 22:51:46 <chillfan> i'll have a go at putting in 'debug' echo commands
Nov 20 22:55:46 <chillfan> will maybe see which part of  the script is the problem that way
Nov 20 22:57:40 <chillfan> is there another way I might create the image file? I mean.. say I do a debootstrap install with everything that's needed, can I then convert that?
Nov 20 23:38:16 <cyberh0me> hello
Nov 20 23:40:10 <cyberh0me> whats wrong with my beaglebone black who sends continuosly a C char on uart?
Nov 20 23:53:46 <cyberh0me_> kopfkwsaogkqpür
Nov 20 23:55:42 <cyberh0me_> kpkop
Nov 21 00:01:44 <zmatt> cyberh0me_: unable to find a bootable device
Nov 21 00:02:21 <zmatt> default boot order is { eMMC, μSD, uart, usb }
Nov 21 00:02:36 <zmatt> the CCC is an attempt to boot via uart
Nov 21 00:03:32 <zmatt> if you power on with the SD button (S2) pressed the boot order becomes { spi, μSD, usb, uart }
Nov 21 00:09:12 <Guest89616> ?
Nov 21 00:09:27 <Guest89616> whats that for a fucking server
Nov 21 00:12:13 <zmatt> ?
Nov 21 00:49:24 <felon-> evening everyone
Nov 21 00:51:40 <felon-> I just recieved my beaglebone black and followed the instructions on the webpage, and flashed debian to the microsd... but it doesnt have the default ip of 192.168.7.2 now.... any ideas? or suggestions (be sides a ping sweep w/ nmap)
Nov 21 00:56:31 <Set_> Hello...
Nov 21 00:59:09 <Set_> So...I read, from another user on #beagle, that UART and i2c are for device to device. Is this right?
Nov 21 01:01:46 <Set_> I looked it up. I read into it. I found that UART is an old connection that used to connect old computers to typewriters.
Nov 21 01:03:14 <Set_> If this UART can connect old stuff to older stuff, I can probably make my BBB talk to my new item of envy (HT702). Right?
Nov 21 01:05:27 <Set_> See...this is it. The ribbon cable and board to wire connection would have to be bought. I know this is crappy of me but can I use UART to connect two devices (BBB and GrandStream)? Okay...I will stay patient now!
Nov 21 01:13:59 <Set_> I found a 2010 TI.com .pdf and if you are interested: http://www.ti.com/lit/ug/sprugp1/sprugp1.pdf.
Nov 21 01:14:05 <Set_> I am going to read from this.
Nov 21 02:12:07 <Set_> How can I code my UART to connect to "N?"
Nov 21 02:23:57 <Set_> i.e. programming my UART must be done with .dlh and .dll files. Oh and REVID1 and REVID2 for peripheral info...blah! I have to call on a scratch pad or something to write my files. But, yes but, I have to use the LCR (Line Control Register) to find my files in Jessie, right?
Nov 21 02:24:46 <Set_> Test time!
Nov 21 02:30:15 <Set_> I got it now...
Nov 21 02:30:21 <Set_> How can I get scratch-pad?
Nov 21 02:43:15 <Set_> How many kilobytes of scratch-pad memory are on the BBB?
Nov 21 02:55:41 <felon-> goooogle
Nov 21 02:56:36 <Set_> Googie!
Nov 21 02:56:49 <Set_> Sorry...google!
**** ENDING LOGGING AT Sat Nov 21 02:59:59 2015