**** BEGIN LOGGING AT Tue Oct 14 02:59:59 2014
Oct 14 07:11:05 <Mounicq1> Hi! where can i find doc to config pins in dts file?
Oct 14 07:11:36 <Mounicq1> I want to use P9_21 P9_22 in mode 2 for i2c2
Oct 14 07:48:47 <vinu> I hvae BBB with debian 7 and I'm trying to create daemon in it but I'm getting locale setting failed warning. I ignored warning and checked it is still running as daemon but it is not. I tried to set locale but locales are not updating please help.
Oct 14 07:50:14 <mashiara> unless your program itself is set to exist on any tiny failure then failing to set locale should not affect it like this
Oct 14 07:50:21 <mashiara> s/exist/exit/
Oct 14 07:54:29 <vinu> but same program on my ubuntu dell laptop is getting configured as daemon without any warnings. and it is not working when i'm trying on BBB
Oct 14 08:02:01 <mashiara> Ubuntu uses upstart and Debian uses old style init still, completely different approaches
Oct 14 08:02:43 <mashiara> you could install ubuntu on your BBB
Oct 14 08:05:24 <honestly> so install whatever locale the program wants to use
Oct 14 08:30:14 <maquefel> why official distributions and all guides involve FAT partition? Only for windows mounting?
Oct 14 08:30:43 <_av500_> maquefel: because the ROM code only knows FAT
Oct 14 08:33:02 <maquefel> _av500_: interesting, ty
Oct 14 08:37:14 <_av500_> the SoC can boot from "raw" SD or from FAT
Oct 14 08:37:22 <_av500_> and FAT is easier to end users
Oct 14 08:40:03 <Noob_linux>  help debugging Uncompressing Linux... done, booting the kernel hang
Oct 14 08:40:20 <_av500_> we do not have a crystal ball
Oct 14 08:40:26 <Noob_linux> i enabled early print and DEBUG_LL still no debug lo
Oct 14 08:40:27 <_av500_> we also dont see your desk/screen
Oct 14 08:40:49 <_av500_> kernel command line?
Oct 14 08:42:15 <Noob_linux> optargs="consoleblank=0 kgdbcon kgdboc=ttyO2,115200"
Oct 14 08:42:16 <Noob_linux> console="tty0 console=ttyO2,115200n8"
Oct 14 08:43:29 <Noob_linux> sry I understand that,
Oct 14 08:43:43 <Noob_linux> atleast a way to proceed could help
Oct 14 08:43:46 <woglinde> av500 oh raw sd, did not know that, how to prepare it?
Oct 14 08:44:02 <woglinde> dd to whole sd?
Oct 14 08:46:31 <maquefel> _av500_: http://processors.wiki.ti.com/index.php/Linux_Core_U-Boot_User's_Guide#Writing_to_NAND_from_U-Boot - this one ?
Oct 14 08:48:54 <Noob_linux> https://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat
Oct 14 08:49:00 <_av500_> woglinde: its in the TRM
Oct 14 08:49:24 <_av500_> is ttyO2 correct?
Oct 14 08:49:56 <Noob_linux> yes
Oct 14 08:49:59 <_av500_> woglinde: ROM checks at 4 locations in the sd/nand for a certain header
Oct 14 08:51:34 <woglinde> av500 ah thanks
Oct 14 08:52:32 <_av500_> woglinde: you can alo interleave a sector 0 MBR and raw boot
Oct 14 08:52:45 <_av500_> if you dont use the location at 0 for the boot code
Oct 14 08:55:33 <maquefel> _av500_: founr the instruction - thanks!
Oct 14 08:56:54 <Noob_linux> any help?
Oct 14 08:57:18 <_av500_> what kernel is that?
Oct 14 08:58:16 <Noob_linux> its a source compiled from yocto for 3.2.28
Oct 14 08:58:34 <maquefel> :-D
Oct 14 08:58:43 <rwr> 3.2 is excellent. don't upgrade
Oct 14 08:58:59 <_av500_> 2.6.32 was the excellent one
Oct 14 08:59:03 <rwr> yes, too
Oct 14 08:59:16 <_av500_> followed by 2.6.10mv5
Oct 14 08:59:24 <Noob_linux> yes, that is working for me
Oct 14 09:00:10 <Noob_linux> but for purposes of debugging my compiling from yocto
Oct 14 09:00:32 <woglinde> Noob_linux debugging what?
Oct 14 09:00:38 <Noob_linux> and it currently yocto has this version
Oct 14 09:00:56 <rwr> Noob_linux: jtag that bitch bro
Oct 14 09:01:12 <_av500_> rwr: please watch your language
Oct 14 09:01:18 <rwr> sry bro
Oct 14 09:01:29 <Noob_linux> its for learning purpose
Oct 14 09:01:45 <Noob_linux> i don not have access to tag
Oct 14 09:01:49 <Noob_linux> *jtag
Oct 14 09:02:17 <Noob_linux> kind of project
Oct 14 09:02:24 <_av500_> Noob_linux: did you ask in #yocto?
Oct 14 09:02:35 <_av500_> this is not really a #yocto support channel
Oct 14 09:02:51 <rwr> Noob_linux: do you have a parallel port on your pc? you can find parallel jtag board for like $10
Oct 14 09:03:47 <rwr> or if you can afford it, https://www.adafruit.com/product/1369
Oct 14 09:04:08 <_av500_> usually this can be solved without jtag
Oct 14 09:04:45 <Noob_linux> i will see if I can get one
Oct 14 09:05:15 <_av500_> but again, without a crystal ball, it is hard to see what you did
Oct 14 09:05:36 <Noob_linux> _av500_ : sry, yes I understand that
Oct 14 09:06:05 <Noob_linux> i asked for what to look
Oct 14 09:06:17 <Noob_linux> what can go wrong
Oct 14 09:06:22 <_av500_> console=
Oct 14 09:06:24 <Noob_linux> those information
Oct 14 09:06:26 <_av500_> no device tree
Oct 14 09:06:30 <_av500_> stuff like that
Oct 14 09:06:40 <_av500_> uboot messing up
Oct 14 09:06:49 <_av500_> many things
Oct 14 09:07:19 <Noob_linux> and how can I confrim that since early_print and Debug_ll doesn't seem to worl
Oct 14 09:07:23 <Noob_linux> *work
Oct 14 09:07:36 <rwr> use the jtag, Noob_linux
Oct 14 09:08:09 <Noob_linux> any other flags or printk or ...
Oct 14 09:08:39 <rwr> http://www.ebay.com/itm/-/170980187990 USB, only $22
Oct 14 09:09:00 <Noob_linux> _rwr_ : thanks, but it takes time to get one and I have no experience working with that (although I willing to learn)
Oct 14 09:10:01 <rwr> it's like your usual gdb, really
Oct 14 09:10:17 <woglinde> Noob_linux just use a kernel you know its working
Oct 14 09:11:37 <rwr> woglinde: but he wants to learn the building of a kernel
Oct 14 09:12:08 <woglinde> rwr for building a kernel I do not need a jtag either
Oct 14 09:13:03 <rwr> me neither however in case it wouldn't boot jtag could be useful
Oct 14 09:17:59 <woglinde> hm looks like the speaker for the skia talk do not shows up
Oct 14 09:23:57 <woglinde> ah I thought his talk would be later
Oct 14 09:24:00 <woglinde> ups he
Oct 14 09:45:16 <tasslehoff> I created a sysfs node to test setting the gamma table I'm playing with. I try to shove 256 32-bit values in there with echo $values > /sys/fs/node. Something decides to split it up and call my store function thrice.
Oct 14 09:58:53 <tomba> tasslehoff: is your return value from store() correct? it should return the same number as it got (presuming you processed it all).
Oct 14 10:00:28 <tomba> tasslehoff: oh, the amount of data you have is probably higher than PAGE_SIZE. in that case I think you just have to deal with multiple calls. somehow.
Oct 14 10:02:42 <tomba> hmm, or not. what kind of format you use? I guess it should all fit in PAGE_SIZE
Oct 14 10:10:19 <tasslehoff> tomba: got a phonecall here, let's see
Oct 14 10:12:38 <tasslehoff> tomba: I return 0, so that is a bug. but that is not the main problem. The line consists of 2816 characters, and store() is called with 1008, 1008 and the rest.
Oct 14 10:14:42 <tomba> tasslehoff: ok. hm, well. I'm guessing here, but I think sysfs expects all the data to be written at the same time, with a single write() call. the shell can probably split the echo in any way it feels like.
Oct 14 10:15:45 <tomba> so... I'm not sure if some other shell command would be guaranteed to do it with single call. but it's trivial to write your own app, at least to try out if that is the reason.
Oct 14 10:16:25 <tasslehoff> tomba: good thoughts. I'll investigate some more.
Oct 14 10:18:18 <tasslehoff> it does not split if I pipe it to wc
Oct 14 10:18:45 <tomba> hmm?
Oct 14 10:19:38 <tasslehoff> eh, not sure if that made sense when I think about it :)
Oct 14 10:20:19 <tomba> you mean "echo ahdasd | wc" ? you can't tell how many write calls that does
Oct 14 10:20:51 <tasslehoff> tomba: exactly :)
Oct 14 10:22:18 <tasslehoff> tomba: strace shows one write call.
Oct 14 10:22:31 <tomba> maybe dd does it. write the data to a file, then dd if=file of=/sysfs/foo bs=4096
Oct 14 10:22:35 <tomba> oh
Oct 14 10:23:49 <tomba> well, no idea =). I have not used sysfs to write such a big amount of data. and it's not designed for that, for sure (but I still don't see why it wouldn't work for this).
Oct 14 10:24:13 <tomba> another idea is that you could try the firmware load system, i.e. load the gamma table as a firmware
Oct 14 10:29:08 <tasslehoff> tomba: dd worked.
Oct 14 10:29:53 <tomba> that's odd. are you sure echo did only one write?
Oct 14 10:30:46 <maquefel> can some one explain:
Oct 14 10:30:56 <maquefel> U-Boot # mmc write ${loadaddr} 0x100 0x100 U-Boot # mmc write ${loadaddr} 0x200 0x100
Oct 14 10:31:10 <maquefel> after MLO to memory load
Oct 14 10:31:21 <maquefel> why are we writing the same
Oct 14 10:31:27 <maquefel> to defferent address?
Oct 14 10:32:00 <tasslehoff> there was only one write statement in the strace-output for both wc and >
Oct 14 10:32:03 <tasslehoff> tomba: ^
Oct 14 10:34:09 <_av500_> maquefel: as said, the ROM code checks 4 places
Oct 14 10:34:13 <_av500_> redundancy
Oct 14 10:34:19 <_av500_> some sectors might go bad or so
Oct 14 10:34:37 <tomba> tasslehoff: hmm, I wonder... even if echo does just one write, how does it go to the sysfs file... the data is written to stdout, and redirected to the file. maybe there are other buffers in between, and those are flushed with multiple writes.
Oct 14 10:35:11 <maquefel> _av500_: can i use dd to write this on sd card?
Oct 14 10:35:29 <tasslehoff> tomba: it has to be something like that. using files suits me better, and this is not production code anyway, so dd is fine.
Oct 14 10:35:36 <maquefel> _av500_: or the only option to write raw is from uboot?
Oct 14 10:35:44 <tasslehoff> now I just gotta fight some more with sscanf :)
Oct 14 10:37:22 <_av500_> maquefel: sure you can
Oct 14 10:37:37 <_av500_> your PC can access the whole card
Oct 14 10:37:42 <maquefel> _av500_: weeeeeeeee - thank you
Oct 14 10:37:49 <_av500_> but you need an MLO with the proper headers
Oct 14 10:38:05 <maquefel> _av500_: i ll use guide for sitara am335x
Oct 14 10:38:46 <maquefel> _av500_: thak you for your time
Oct 14 10:42:59 <day> what happens if i use the standard arm kernel?
Oct 14 10:43:34 <day> that comes with debian f.e.? will this work? or does the beaglebone need something special?
Oct 14 10:47:27 <maquefel> day: your question makes no sense - there are many arms - waht do you mean by standart arm kernel?
Oct 14 10:49:30 <day> maquefel: i can download a standard x64 debian distribution. The kernel just works with all x64 compatible cpus
Oct 14 10:49:38 <day> maquefel: is there something like that for arm as well?
Oct 14 10:49:55 <day> or does each and every arm board need a fully customized kernel?
Oct 14 10:50:54 <maquefel> day: there is official bbb debian distribution
Oct 14 10:50:56 <maquefel> http://beagleboard.org/latest-images
Oct 14 10:51:00 <day> f.e. my current beaglebone distribution uses the normal arm repos for packages. but the kernel sources are pulled from a different special repo
Oct 14 10:51:20 <day> maquefel: it just works for the 4gb version iirc
Oct 14 10:51:24 <day> or is super large
Oct 14 10:51:30 <maquefel> well... you got the idea
Oct 14 10:51:41 <maquefel> you need special kernel sources
Oct 14 10:51:47 <maquefel> customized for board
Oct 14 10:52:09 <day> aww. why can x64 pull it of but arm cant?
Oct 14 10:52:28 <day> less standardization?
Oct 14 10:54:56 <maquefel> becouse all x86 and x64_86 are the same
Oct 14 10:57:29 <day> maquefel: i thought the kernel would be so close to the hardware that it still sees the hw differences between different cpus. I guess these differences are evened out by the kernel drivers?
Oct 14 10:58:53 <maquefel> well... not between cpu actually
Oct 14 10:59:17 <maquefel> well you use stock kernel for example for bbb
Oct 14 10:59:26 <maquefel> you are ensured that all devices works
Oct 14 10:59:40 <maquefel> ethernet, nand, mmc drivers
Oct 14 10:59:58 <maquefel> some devices that use nand - have hardcoded partition table for example
Oct 14 11:01:01 <day> what would would not work then?
Oct 14 11:01:13 <maquefel> all
Oct 14 11:01:25 <day> i thought ethernet nand and mmc drives work
Oct 14 11:01:59 <day> you wrote stock kernel ensures that all devices work on the bbb o0
Oct 14 11:03:23 <maquefel> get kernel config at least
Oct 14 11:03:27 <maquefel> and try compile
Oct 14 11:04:22 <day> tbf. the kernel is a big mystery to me :/ I get the very basics, and know fragments, but the few times i touched it i broke it :D
Oct 14 11:08:19 <maquefel> break it until you are done
Oct 14 11:08:29 <maquefel> get some tftp/nfs guide
Oct 14 11:08:46 <maquefel> i know nothing about debian
Oct 14 11:09:01 <maquefel> i don't know if it is possible to use non stock kernel/headers\
Oct 14 11:09:16 <maquefel> or is it easy to do this
Oct 14 11:28:34 <huddlwenf> Hi, does anyone know what it means when all 4 USER-leds are blinking in the exact same heartbeat pattern?
Oct 14 11:34:26 <thow> check if    cat /sys/class/leds/*/trigger  is the same
Oct 14 12:52:30 <tasslehoff> tomba: I allocated a page with alloc_page(GFP_KERNEL | GFP_DMA); that should be something the dss can work with?
Oct 14 12:55:01 <tasslehoff> I used page_address() to get a virtual address and fill out my gamma table. then I tried virt_to_phys(page_address()) to get an address for the dss.
Oct 14 12:56:20 <tomba> tasslehoff: maybe dma_alloc_coherent() is easier
Oct 14 12:57:00 <tasslehoff> tomba: started out with that one, but couldn't figure out why it always returned ENOMEM
Oct 14 12:59:45 <tomba> oh. hmm right, it could be that the dss device is not setup to alloc dma memory. omapdss doesn't allocate any dma memory, as it gets the buffers from other drivers.
Oct 14 13:02:11 <tasslehoff> tomba: but the driver could be setup to do it?
Oct 14 15:57:47 <black_13> how does up chop/channel the linux on the beagle black c rev
Oct 14 16:08:02 <black_13> anyone home
Oct 14 16:29:28 <Jpic1212> hello
Oct 14 16:29:44 <Jpic1212> some expert out there
Oct 14 16:30:52 <Jpic1212> There is an actual tutorial about How to install ubuntu on BB XM rev C1 and don´t die trying.
Oct 14 16:31:14 <Jpic1212> I´m tired about it
Oct 14 16:31:39 <thurgood> if you have a question, just ask.. someone may respond
Oct 14 16:32:17 <Jpic1212> i did all that i founded on the internet but just get worst the solution
Oct 14 16:33:13 <Jpic1212> Somebody have an actual tutorial step by step about how to install UBUNTU on BB xm,,,, please
Oct 14 16:33:25 <Jpic1212> thurgood
Oct 14 16:33:28 <Jpic1212> help me
Oct 14 16:34:02 <thurgood> haven't tried ubuntu on the xM
Oct 14 16:34:17 <Jpic1212> no men,, dont say that
Oct 14 16:34:21 <thurgood> not sure there is support for that post 12.04 either
Oct 14 16:35:02 <Jpic1212> itsome expert friend that works with ubuntu
Oct 14 16:35:51 <thurgood> http://elinux.org/BeagleBoardUbuntu#BeagleBoard_xM maybe?
Oct 14 16:36:20 <thurgood> looks fairly easy just download, uncompress and dd
Oct 14 16:37:24 <Jpic1212> that page i´ve read , i´m going to continue reading again, maybe this time i found something diferent
Oct 14 17:30:26 <YAO> Hello
Oct 14 17:43:10 <black_13> kids
Oct 14 17:43:19 <YAo> Hello
Oct 14 17:43:42 <black_13> how do i update the debian image on the beagle b rev c
Oct 14 17:43:51 <black_13> is there a guide there probably is
Oct 14 17:46:14 <YAo> I am new in this live chat.  I don`t know to setting the GPIOS  in BeagleBoard XM, i use Archlinux distribution.
Oct 14 17:46:20 <YAo> Can i help me?
Oct 14 17:56:00 <Sulphurik> I need help with my beagleboard
Oct 14 18:53:47 <ecdhe> I've got the adafruit BBB GPIO library working for output; I can configure a pin as output and toggle it.
Oct 14 18:54:39 <ecdhe> I was trying to read from pin P9_25; I configured it, then checked it's state, but I couldn't detect its state -- the state always appeard to be "LOW".
Oct 14 18:55:20 <ecdhe> When I put a scope on P9_25 (which is configured to be an input) I see a 24.5MHz sinewave.
Oct 14 18:58:42 <ecdhe> Then I checked /sys/devices/bone_capemgr.9/slots to make sure that there wasn't a device tree overlay that would enable some function on the pin... no luck there.
Oct 14 19:01:33 <ecdhe> What do I need to do to make P9_25 a GP-input?
Oct 14 19:01:46 <ecdhe> And why is there a 24.5MHz signal on it?
Oct 14 19:05:17 <agmlego> YOu see a sine wave on an IO pin?
Oct 14 19:06:00 <woglinde> use the PRU for gpio
Oct 14 19:06:05 <woglinde> its even faster
Oct 14 19:06:30 <agmlego> woglinde: I am pretty sure that is not ecdhe's question.
Oct 14 19:11:11 <ecdhe> agmlego, well, it's not a good square, but looking a little closer it's like it's trying to be.
Oct 14 19:11:46 <agmlego> OK, so then not actually a sine then. OK.
Oct 14 19:11:48 <ecdhe> Could also be my scope proble, the test point is a few inches from the BBB header.
Oct 14 19:12:07 * agmlego was trying to figure out where the true-sine hardware on the bone came from.
Oct 14 19:15:30 <ecdhe> agmlego, sorry, it's pretty smooth...  I'll send you a pic.
Oct 14 19:17:07 <agmlego> I really am not that interested in it.
Oct 14 19:20:16 <ecdhe> agmlego, I took it anyway...  https://img.bi/#/76KJdNJ!SZTmvONlKjV3ix7qAcVGyzIg4A6LJdeP8ArKaTFK
Oct 14 19:22:03 <ecdhe> So that clock matches what I've seen for the top speed of spi.
Oct 14 19:22:41 <ecdhe> Ultimately, I just want to use the P9_25 as an input.
Oct 14 19:23:15 <agmlego> Why that one in specifc, when you have so many others to choose from?
Oct 14 19:51:21 <m0rgan> Hi, someone knows what drivers (eQEP, eCAP, ePWM, UART, CAN, I2C) are okay or not?
Oct 14 20:07:16 <thurgood> m0rgan: in what context?
Oct 14 20:10:58 <wrl_> I am trying to use a device tree overlay to  configure a gpio interrupt for a kernel device driver. Everything looks good. The pin shows as a an input in pins, the driver probe routine finds the hardware, and an IRQ is mapped and shows up in /proc/interrupts. I have used a scope to confirm ints are arriving on expected pin, but the ISR is never called. Can anyone offer any tips for next steps?
Oct 14 20:11:51 <mashiara> give this person a medal, a properly formed request for help for once!
Oct 14 20:12:08 <mashiara> unfortunately I have no idea how to help you, you seem to know more of this stuff I do...
Oct 14 20:13:53 <wrl_> sadly, my question pretty much disclosed my entire knowledge base on this.  I suspect I am missing something in my dts file, but have found no examples that do anything differently
Oct 14 20:14:41 <thurgood> just because it's set as input doesn't mean it's associated with an interrupt
Oct 14 20:15:04 <thurgood> I don't know how to do that in device trees unfortunately
Oct 14 20:16:31 <wrl_> the pin is gpio2_2.  In the driver fragment, I set interrupt-parent = <$gpio2> and interrupts = <2 0>.  I've also tried <2 1>
Oct 14 20:17:43 <wrl_> Is there something I should be doing in the pinmux or elsewhere to state that this pin is used as an interrupt?
Oct 14 20:17:45 <m0rgan> @thurgood: under linux
Oct 14 20:19:59 <m0rgan> @thurgood: for example to be capable to measure a frequency (in userspace) with an eCAP
Oct 14 20:22:17 <wrl_> the call to devm_request_threaded_irq() in the driver returns success, and /proc/interrupts shows IRQ 162 as GPIO assigned to the driver
Oct 14 20:24:03 <wrl_> I don't think the user space interrupt capability can help me. I need to connect a gpio on a cape to an ISR in an existing kernel device driver.
Oct 14 20:26:54 <wrl_> Unfortunately, my debug skills are not strong enough to figure out where the observed hardware signal is getting lost between P8-7 and the ISR that has supposedly been linked to it.
Oct 14 20:30:33 <wrl_> well, thanks to everyone for trying. I was having difficulty logging on to the forum, so though I would give chat a try.
Oct 14 20:40:39 <ecdhe> agmlego, why NOT that one in specific? Can P9_25 not be used as a GPIO input?
Oct 14 20:40:46 <agmlego> I have no idea./
Oct 14 20:41:06 <agmlego> But there are many, many other GPIO, and the one you chose appears to have something else on it.
Oct 14 20:47:28 <thurgood> https://groups.google.com/forum/#!topic/beagleboard/g2DC1GeybSE
Oct 14 20:48:27 <thurgood> looks like there's an external clock already driving it
Oct 14 20:57:24 <thurgood> seems like a bit of a hassle but doable to use that pin... but I would use one that's actually free
Oct 14 20:57:53 <ecdhe> thurgood, you're awesome!
Oct 14 20:58:40 <ecdhe> I appreciate the link, now I know how do make a change if I need to.  I have two applications and one of them needs HDMI, the other we're going to re-spin the BBB without it.
Oct 14 20:59:20 <thurgood> looks like it's not necessary for hdmi unless you want audio with it
Oct 14 21:08:11 <ecdhe> thurgood, that makes sense.  The discussion in your link was helpful!
Oct 14 21:09:07 <ecdhe> The only part that didn't make sense to me was where they said udev would take 60 seconds to discover the existing peripherals if you removed the default board files from the kernel.
Oct 14 21:09:30 <ecdhe> Not that I'm going to do that...
Oct 15 00:33:52 <dvdmiller90> hi I am trying to re-create the demo at http://beagleboard.org/project/stache
Oct 15 00:34:15 <dvdmiller90> however double click on the Beagle desktop icon never starts the app
Oct 15 00:34:26 <dvdmiller90> Checking the log shows http://pastebin.com/c9t6YZn7
Oct 15 00:34:36 <dvdmiller90> do you have any idea of what may go wrong?
**** BEGIN LOGGING AT Wed Oct 15 01:30:49 2014
**** ENDING LOGGING AT Wed Oct 15 03:00:00 2014