**** BEGIN LOGGING AT Thu Feb 11 02:59:58 2016
Feb 11 03:04:12 <veremit> smarquis: try your question over in #beagle-bonescript .. don't think it fits with the main topics here
Feb 11 03:05:58 <smarquis> Ok thanks!
Feb 11 03:10:46 <veremit> smarquis: have you tried the other pwm pins? or just that one?
Feb 11 03:11:22 <veremit> you might want to get whether pinMode has been set (or is default)
Feb 11 03:17:20 <Sujit> I am trying to boot my beaglebone black with an angstrom distribution microsd card but my BBB is showing up the original Debian os only and not the angstrom image...what to do here, plz help
Feb 11 03:29:19 <veremit> Sujit: once you have inserted the uSD card, with the board powered OFF, you hold the S2 button by the card slot WHILE applying power to the board, until you start to see the LEDs flashing
Feb 11 03:29:37 <yates> anyone seen zmatt? is he on holiday?
Feb 11 03:29:39 <veremit> only by this method do you force the board to read the uSD first.
Feb 11 03:29:55 <veremit> yates: probably eating pizza or working or sleeping.
Feb 11 03:30:23 <yates> nah.
Feb 11 03:30:36 <yates> he's here a lot. if he isn't, he's not.
Feb 11 03:31:01 <veremit> yates: right
Feb 11 03:33:35 <veremit> much like rcn-ee .. when he's here .. he's here :D
Feb 11 03:34:38 <veremit> yates: brought the work telit home :D
Feb 11 03:34:50 <veremit> no crappy usb on this thing .. rs232 or nawt
Feb 11 03:35:10 <veremit> in fact .. ttl serial lol someone stole the rs232 driver chip lol
Feb 11 03:35:24 <veremit> so that's ripe for direct connection to the beagle uart pins :D
Feb 11 03:36:04 <veremit> gm862 .. just the gprs one.
Feb 11 03:37:00 <veremit> I was hoping to use it for SMS when the power goes out/etc. :)
Feb 11 03:45:05 <yates> veremit: actually robert answered my email already.
Feb 11 03:45:18 <veremit> there ya go
Feb 11 03:45:27 <yates> but his answer was close to meaningless.. as far as i can tell
Feb 11 03:46:03 <yates> "Odd, that's the same usb device I've been using to setup a demo on a bbg.. I've been using the v4.1.x-rt-ti branch.."
Feb 11 03:46:08 <yates> that's it..
Feb 11 03:46:29 <yates> he's probably overloaded and spent 41 seconds on it...
Feb 11 03:47:46 <yates> i guess we're all supposed to use his branch? or what? what is the take-away?
Feb 11 03:51:15 <veremit> what branch are you using?
Feb 11 03:51:21 <veremit> 3.8 *laugh*
Feb 11 03:51:38 <veremit> kidding :p
Feb 11 03:53:06 <yates> am33x-v4.4
Feb 11 03:53:42 <veremit> you own special or some mainline derivative ..
Feb 11 03:54:02 <veremit> really gotta be very careful with patches and such with these arm boards
Feb 11 03:55:42 <veremit> ok I must zzz .. been up 30-odd hours :/ need rest .. bbl sometime .. eventually :D
Feb 11 03:55:46 <veremit> niters o/
Feb 11 03:56:17 <yates> night veremit
Feb 11 03:56:40 <yates> it's from bb-kernel repo
Feb 11 03:57:06 <veremit> hmm .. if it were me, I'd be starting form 4.1-ti I have to confess
Feb 11 03:57:13 <veremit> anyhow.. zzz .. good luck!
Feb 11 04:49:54 <yates> so it appears the kernel driver driver/musb_cores.c issues a Babble message when it gets a babble interrupt from the am3352 usb peripheral.
Feb 11 04:50:20 <yates> what sorts of things cause the am3352 usb peripheral to generate babble interrupts?
Feb 11 04:52:33 <yates> i see no documentation on that in the am335x trm
Feb 11 04:58:00 <kremlin> does the BBB have the same built-in JTAG over USB debugger that the beaglebone has?
Feb 11 04:58:49 <yates> kremlin: i think so
Feb 11 04:59:01 <yates> but we don't have that on our board
Feb 11 04:59:27 <kremlin> what do you mean
Feb 11 05:00:06 <yates> well, maybe we do. i need back backpedal
Feb 11 05:00:20 <yates> is that function built into the am335x?
Feb 11 05:00:28 <yates> into its usb peripheral, that is?
Feb 11 05:00:40 <kremlin> yes
Feb 11 05:00:51 <kremlin> the one where you do not need to buy a $100 JTAG debug board
Feb 11 05:01:06 <kremlin> this: http://beagleboard.org/static/Docs/ccs-jtag-simple.htm
Feb 11 05:02:43 <yates> so then, yes, we do.
Feb 11 05:03:20 <yates> oh i'm confused. you are not commenting on my problem, are you?
Feb 11 05:03:29 <kremlin> oh, shit, hahaha
Feb 11 05:03:33 <kremlin> no i am not
Feb 11 05:03:34 <kremlin> sorry
Feb 11 05:03:41 <yates> no, the mistake is mine.
Feb 11 05:04:25 <yates> yes, i've read that it does have that ability. that's apparently why they didn't bother to populate the jtag connector on the board.
Feb 11 05:05:13 <kremlin> oh, shoot
Feb 11 05:05:17 <kremlin> from the wiki: "There is no JTAG over USB support on the BeagleBone Black. The BeagleBone Black is different than the BeagleBone. JTAG is an uninstalled option."
Feb 11 05:12:06 <yates> kremlin: that is a little unclear, imo
Feb 11 05:12:16 <kremlin> yes but
Feb 11 05:12:28 <kremlin> upon further resaerch
Feb 11 05:12:43 <kremlin> there is a 20 pin pad header on the bottom onto which you solder a specific connector
Feb 11 05:12:59 <kremlin> a ribbon cable attaches to it which attaches to a seperate debug board
Feb 11 05:13:07 <kremlin> which connects to the host machine via USB
Feb 11 05:13:07 <yates> kremlin: yes, that's correct
Feb 11 05:13:12 <yates> yes
Feb 11 05:13:16 <yates> indeed i have one of those
Feb 11 05:13:30 <yates> xds100, i believe
Feb 11 05:13:54 <yates> they're only about $80
Feb 11 05:13:58 <yates> not too bad
Feb 11 05:14:01 <kremlin> :(
Feb 11 05:14:13 <yates> back in the 90's, a jtag debugger for the TI dsps was $4000
Feb 11 05:14:28 <kremlin> heh
Feb 11 05:14:37 <kremlin> i am still out of beer money for a few weeks
Feb 11 05:15:44 <yates> https://www.digikey.com/product-detail/en/TMDSEMU100V2U-20T/296-31067-ND/2261950
Feb 11 05:15:51 <kremlin> just ordered :)
Feb 11 05:16:09 <yates> :)
Feb 11 05:22:42 <vengadesh> hello sir am using beagle bone black
Feb 11 05:23:19 <vengadesh> for that i need to install ubuntu version what is the correct procedure for that
Feb 11 05:28:51 <yates> veremit: do you have any knowledge of the musb driver drivers/musb_core.c ?
Feb 11 05:29:02 <yates> oh wait, you want to sleep..
Feb 11 05:29:07 <yates> well, anyone then?
Feb 11 05:31:11 <av500> nobody can sleep when having musb on his mind
Feb 11 05:42:58 <vengadesh> no konwledge about that sir
Feb 11 05:43:24 <vengadesh> sir how can i use extra storage memory card in bbb
Feb 11 05:58:30 <vengadesh> sir
Feb 11 05:59:10 <vengadesh> how can i make the board always boot from sd card
Feb 11 06:20:34 <yates> av500: you got that right
Feb 11 06:21:36 <yates> Robert responded to an email on this babble problem with: "Odd, that's the same usb device I've been using to setup a demo on a bbg.. I've been using the v4.1.x-rt-ti branch.."
Feb 11 06:22:11 <yates> is he implying the musb_core.c is patched in this kernel version to work around this problem?
Feb 11 06:23:10 <yates> why wouldn't it be in my am33xx 4.4 ?
Feb 11 06:24:19 <av500> yates: I worked with TI Socs for a decade, musb problems was always with us
Feb 11 06:25:01 <yates> oh that's discouraging...
Feb 11 06:25:33 <yates> I looked into the drivers/musb_core.c driver tonight (very roughly) and it appears that the babble message comes from receiving a babble interrupt from the AM335x on-board USB peripheral.
Feb 11 06:25:52 <yates> f that is the case, how can any patch or kernel version fix this problem?
Feb 11 06:26:08 <yates> It appears what we need to do to fix our problem is understand what causes the AM335x USB peripheral to generate this interrupt, e.g., does it monitor power variations, DM/DP voltages, etc., or what?
Feb 11 06:26:37 <yates> or is my logic flawed?
Feb 11 06:27:40 <yates> i've seen at least one patch that attempts to restart the bus and reenumerate the devices. i guess that's one thing you can do.
Feb 11 06:28:42 <yates> what does "musb" even mean? what is the "m"?
Feb 11 06:29:28 <yates> basically usb OTG?
Feb 11 06:30:16 <yates> av500: ?
Feb 11 06:31:05 <yates> zmatt: ?
Feb 11 06:31:08 <yates> help!!!!
Feb 11 06:38:13 <yates> what does "musb" even mean? what is the "m"?
Feb 11 06:39:40 <yates> why does no one want to answer me?
Feb 11 06:39:46 <yates> am i ignorant?
Feb 11 06:39:52 <yates> are they ignorant?
Feb 11 06:40:10 <yates> what?
Feb 11 06:40:20 <yates> busy with the kids and wife?
Feb 11 06:40:25 <vagrantc> the pain is too much
Feb 11 06:40:42 <yates> vagrantc: oh but i LIKE pain...
Feb 11 06:40:55 <yates> don't you?
Feb 11 06:40:58 <yates> :)
Feb 11 06:41:13 <vagrantc> in appropriate times and places
Feb 11 06:43:51 <yates> what is it that's painful?
Feb 11 06:43:57 <yates> my questions?
Feb 11 06:44:11 <yates> the usb subsystem?
Feb 11 06:44:14 <vagrantc> there is a pact of silence
Feb 11 06:44:16 * vagrantc waves
Feb 11 06:44:59 <yates> er, bye...
Feb 11 06:45:03 <yates> silent one.
Feb 11 06:50:44 <snowSTAFF> What is the signal level corresponds to 1 bit output PRU?
Feb 11 06:52:33 <yates> probably 0/3.3v?
Feb 11 06:56:00 <snowSTAFF> Yes, i think same. But, when i check pin p9_27(mode 5, 0x05) and set 1, multimeter shows 0.
Feb 11 06:59:55 <av500> yates: m = mentor
Feb 11 07:00:06 <av500> the company that made that USB IP core
Feb 11 07:00:10 <av500> er, core IP
Feb 11 09:06:03 <zmatt> yates: I have actually answered that
Feb 11 09:07:14 <zmatt> full name is actually musbmhdrc
Feb 11 09:07:37 <zmatt> (Mentor USB msomething highspeed dual-role controller)
Feb 11 09:15:09 <zmatt> ah, multi-point
Feb 11 09:15:38 <av500> m = mental
Feb 11 09:15:44 <zmatt> lol
Feb 11 09:23:51 <snowstaff> Guys, need your help. Can i use only one byte memory on PRU for assembler and C code? I used c24+1 and changed the value from C code, but assembler no reaction on change.
Feb 11 09:33:35 <zmatt> your question is too vague to give any useful answer, but your hypothesis is obviously nonsensical: the PRU can of course fully access the various data RAMs
Feb 11 09:43:11 * av500 uses the 16550 UART scratch register for data exchange
Feb 11 09:46:08 <zmatt> hehe
Feb 11 10:03:25 <snowstaff> My mistake. Most likely misspelled code on assembler. =(
Feb 11 10:27:49 <yates> av500: aha.
Feb 11 10:29:06 <yates> zmatt: i'm a human, not a computer, but thanks again.
Feb 11 10:30:45 <yates> old 8085 instruction: XCHG
Feb 11 10:30:57 <yates> (HL with DE)
Feb 11 10:34:00 <yates> zmatt: do you know anything about the usb babble message emitted by musb_core.c? namely, on the am335x platform, isn't that a result of a babble interrupt from the am335x usb peripheral?
Feb 11 10:45:12 <snowstaff>  I forgot to clean up SYSCFG =(( oh my...
Feb 11 10:57:13 <yates> is the musb_core.c driver only used for the TI SoCs?
Feb 11 10:58:50 <yates> yes (or at least "products from TI").
Feb 11 10:58:57 <yates> "This version of the driver has only been used with products from Texas Instruments."
Feb 11 10:59:01 <yates> thanks yates!
Feb 11 10:59:06 <yates> yer welcome...
Feb 11 11:05:44 <snowstaff> xD
Feb 11 12:57:33 <Pranky> good afternoon
Feb 11 12:57:47 <Pranky> ladies and gentelman
Feb 11 13:05:29 <geeko> hello there
Feb 11 13:05:55 <geeko> how can i install kernel source code
Feb 11 13:06:34 <snowstaff> bye all
Feb 11 13:07:44 <Pranky> i am trying to do that now
Feb 11 13:11:53 <geeko> anybody?
Feb 11 13:13:16 <geeko> hello ... its urgent....
Feb 11 14:22:44 <yates> 6 minutes and he's gone...
Feb 11 14:36:00 <felon-> heh
Feb 11 14:36:08 <felon-> thats how they roll
Feb 11 14:45:28 <adis> neko iz Bosne
Feb 11 14:45:30 <adis> za razgovor
Feb 11 14:45:32 <adis> bilo ko
Feb 11 14:45:33 <adis> ???
Feb 11 15:19:27 <zmatt> "Don't flag your question as 'Urgent', even if it is for you.  That's your problem, not ours." -- How To Ask Questions The Smart Way
Feb 11 15:49:08 <Oped> hey there
Feb 11 15:49:59 <Oped> I would like to ask about the ethernet on BeagleBoard-X15
Feb 11 15:50:40 <Oped> Is the ethernet connected via a USB controller to the board or via an ethernet controller?
Feb 11 15:51:01 <vagrantc> i'm fairly certain it's not via usb
Feb 11 15:52:06 <Oped> I tried to look at the schematic of the board and it seems it doesn't have an ethernet controller on board
Feb 11 15:52:49 <Oped> Do you know where I can find the conformation on the controller
Feb 11 15:57:21 <Asanga> hi
Feb 11 15:57:56 <Asanga> Hi  i like to know BeagleBone Black can use as a Ethercat master?
Feb 11 15:59:16 <Asanga> https://www.youtube.com/watch?v=oF8fHxd34yY
Feb 11 16:00:42 <Asanga> any guys know about it
Feb 11 16:07:26 <Asanga> hi
Feb 11 16:08:18 <zmatt> vagrantc: since Oped was too impatient to wait for an answer: x15 has real ethernet, slightly newer version of same subsystem as on the bbb, but this time both ports are connected to gigabit PHYs
Feb 11 16:11:42 <twoten> My BBB is on Debian 4.15 - I have compiled my device tree overlay but when I try to enable it I get sh: echo: I/O error - what is the correct way to write to slots?
Feb 11 16:12:24 <sriram_> when will beaglebone x-15 will release
Feb 11 16:14:24 <sriram_> hai when will beaglebone x-15 release in market
Feb 11 16:14:42 <sriram_> hello anybody is there
Feb 11 16:16:26 <twoten> I'm here - are you?
Feb 11 16:21:18 <veremit> haha
Feb 11 16:31:56 <zmatt> twoten: the old way of loading overlays (mildly abusing capemgr) should still work the same, and there's new also an official non-bbb-specific mechanism using configfs
Feb 11 16:33:02 <zmatt> make sure cape-universal is disabled since it will likely conflict with pretty much any overlay
Feb 11 16:33:25 <zmatt> also, make sure cape-universal is disabled since... eww.
Feb 11 16:34:45 <zmatt> maybe check the main dts(i) files whether there's been any change to things you reference in your overlay
Feb 11 16:35:37 <zmatt> other than that I don't have much advice... I never really use overlays, although I know they work
Feb 11 17:27:11 <twoten> just got back from walking my dog
Feb 11 17:27:38 * ogra_ hopes its a beagle at least
Feb 11 17:28:24 <twoten> zmatt: thanks again - this is the only non-trivial entry in my slots file: Override Board Name,00A0,Override Manuf,cape-univarsaln
Feb 11 17:28:32 <twoten> greyhound
Feb 11 17:29:02 <twoten> so I guess I do have cape-univarsal enabled
Feb 11 17:30:01 <twoten> I put my cape entry into /etc/default/capemgr - I wonder how to do I cause it to load? reboot?
Feb 11 17:36:51 <rcn-ee> twoten, /etc/default/capemgr is read at boottime... so a reboot..
Feb 11 17:37:40 <rcn-ee> correction, it's read by an init script at boot tiem.. ;)
Feb 11 17:40:15 <twoten> okey dokey!
Feb 11 17:44:54 <twoten> every time I log in I have to set my network dns address to my router - is there a way to make it stick once and for all?
Feb 11 17:45:38 <stt_michael> dhcp broken?
Feb 11 17:46:07 <twoten> always some crazy number
Feb 11 17:51:49 <twoten> I rebooted and still my overlay does not appear in slots
Feb 11 17:52:32 <twoten> dmesg | grep capemgr reports that it tried to load it but: slot #4: failed to resolve tree
Feb 11 17:53:27 <twoten> I'll try it with a built in overlay instead of my custom one
Feb 11 17:54:03 <stt_michael> what are the surrounding debug messages/
Feb 11 17:54:23 <stt_michael> "it doesn't work" doesnt' really help .. "why doesn't it work" is the natural follow-on question ..
Feb 11 17:54:59 <twoten> part_number 'BB-1WIRE-P9-22', version 'N/A'
Feb 11 17:55:14 <twoten> slot#4: override
Feb 11 17:55:35 <twoten> Using override eeprom data at slot 4
Feb 11 17:56:25 <twoten> slot #4,: 'Override Board Name,00A0,Override Manuf,BB-1WIRE-P9-22'
Feb 11 17:56:49 <twoten> slot #4: Failed to resolve tree
Feb 11 17:57:28 <twoten> part_number 'cape-universaln', version 'N/A'
Feb 11 17:57:48 <twoten> slot #5: override
Feb 11 17:58:08 <twoten> Using override eeprom data at slot 5
Feb 11 17:58:12 <rcn-ee> twoten, post your full dmesg on pastebinit  ;)
Feb 11 17:58:47 <twoten> slot #5: 'Override Board Name,00A0,Override Manuf, cape-universaln'
Feb 11 17:58:58 <twoten> good idea
Feb 11 17:59:12 <rcn-ee> twoten, btw, also compare against: https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/BB-W1-P9.12-00A0.dts
Feb 11 17:59:18 <rcn-ee> as i know that one works..
Feb 11 18:03:06 <twoten> pastebin.com/SDy3rTV6
Feb 11 18:03:51 <rcn-ee> twoten, wrong dtc version.. line 299...
Feb 11 18:04:03 <rcn-ee> use /usr/local/bin/dtc
Feb 11 18:04:51 <rcn-ee> we left /usr/bin/dtc for legacy 3.8.13 based kernel's..
Feb 11 18:05:22 <twoten> oh, so I run it from a terminal?
Feb 11 18:05:55 <rcn-ee> or clone https://github.com/beagleboard/bb.org-overlays/
Feb 11 18:06:10 <rcn-ee> copy your *.dts to ./bb.org-overlays/src/arm
Feb 11 18:06:17 <rcn-ee> then from ./bb.org-overlays/
Feb 11 18:06:23 <rcn-ee> type "make ; sudo make install"
Feb 11 18:06:50 <rcn-ee> and if you need the newer dtc, run "./dtc-overlay.sh"...
Feb 11 18:06:55 <twoten> I just did that clone this morning
Feb 11 18:07:28 <twoten> so I take it that I compiled my device tree file with the wrong dtc?
Feb 11 18:07:48 <rcn-ee> yeap...
Feb 11 18:08:20 <twoten> wow, thanks for saving me weeks of rolling a boulder up hill in hell!
Feb 11 18:08:59 <rcn-ee> but also compare against the other onewire example, as the "&gpioX" value of X is now 'correct' vs one of in 3.8.x
Feb 11 18:09:59 <twoten> gotcha, and then compile with the write one - will the priveledged echo then work without the rebooting?
Feb 11 18:10:29 <rcn-ee> twoten, as long as cape-univeral is loaded it wont... as there will be a pin conflict...
Feb 11 18:10:44 <rcn-ee> you can disable that in /boot/uEnv.txt look for 'cape_universal=enable'..
Feb 11 18:11:00 <twoten> excellent, thank you very much!
Feb 11 18:19:07 <twoten> okay I disabled cape_universal, recompiled my dts and copied it into /lib/firmware and rebooted
Feb 11 18:24:45 <twoten> Ha! dmesg reports no cape_universal loaded and BB-1WIRE loded successfully
Feb 11 20:45:21 <zachjacobs> Hello all.  I'm trying to get plymouth splash screen working on a BeagleBoneBlack and it seems to be failing on boot.  I'm unsure how to proceed and would appreciate some help.  I think the crash comes when plymouth tries to start using the frame buffer but I'm unsure of how to intrepret the crash.  I would very much appreciate some assistance and hope this is the correct method to try to get help.  plymouth logs: http://pastebin
Feb 11 20:45:55 <zachjacobs> startup logs: http://pastebin.com/LrbHaQUx  uEnv.txt args: optargs=splash plymouth:debug plymouth.ignore-serial-consoles
Feb 11 21:15:39 <alex_____> hello
Feb 11 21:15:48 <alex_____> can someone help me
Feb 11 21:19:42 <Catfang> What's up Alex?
Feb 12 00:26:55 <GenTooMan> apparently alex didn't hang around for very long.
Feb 12 00:38:30 <Catfang> Guess not!
Feb 12 00:48:42 <GenTooMan> Oh well you can't get answers if you ask for help and disappear.
Feb 12 01:14:00 <yates> <60 seconds. amazing the lack of patience in the world these days...
Feb 12 01:15:31 <yates> so no one knows a magic bullet for Ye Old USB Babble Interrupt?
Feb 12 01:15:42 <yates> we're dying on the vine, here...
Feb 12 01:16:20 <yates> https://e2e.ti.com/support/embedded/linux/f/354/t/489649
Feb 12 01:19:00 <yates> "babble killed our project"
Feb 12 01:19:48 <yates> i know: everyone here knows but they're keeping it a secret!
Feb 12 01:21:24 <yates> no one wants to acknowledge the pink elephant in the room...
Feb 12 01:21:35 <yates> bad for business...
Feb 12 01:28:03 <ds2> 50cal should get rid of the interrupt
Feb 12 01:59:35 <zmatt> yates: I've seen babble too, though it was on a flaky prototype board and didn't return on later ones
Feb 12 02:01:25 <zmatt> the root problem is presumably electrical in nature, but it's hard to say more than that
Feb 12 02:08:15 <zmatt> yates: and the brittleness of usb on the bbb is hardly a secret... it gets regularly mentioned here :P  though I must admit so far it usually seemed to be working for me (except on that one board)
Feb 12 02:11:49 <zmatt> apparently it was worse in the past -> http://logs.nslu2-linux.org/livelogs/beagle/beagle.20150207.txt   <KaaK> Babble and VBus errors are probably the most common (that i've personally experienced). the `musb' host driver has had a ton of work that helps on both accounts.
Feb 12 02:18:02 <zmatt> yates: ah, someone helpfully dumped the musb core docs online -> http://dl.linux-sunxi.org/users/tom/musbmhdrc_pspgUSB.pdf
Feb 12 02:51:37 <stt_michael> o,o
Feb 12 02:51:53 <stt_michael> reverse engineer, zmatt, immediately ! :P
**** ENDING LOGGING AT Fri Feb 12 02:59:58 2016