**** BEGIN LOGGING AT Mon Nov 17 03:00:00 2014
Nov 17 04:17:22 <Robert__> Hi All..
Nov 17 04:17:53 <Robert__> A potential user of beagleboard..
Nov 17 04:17:59 <Robert__> Need some advice..
Nov 17 04:18:29 <veremit> Don't. next question?! :p
Nov 17 04:18:57 <veremit> nvm
Nov 17 04:19:16 <Robert__> Hi Veremit..
Nov 17 04:19:35 <Robert__> Are you a common user..?
Nov 17 04:19:41 <Robert__> Or a moderator..?
Nov 17 04:19:52 <veremit> I'm just common :D
Nov 17 04:20:06 <Robert__> Oh okie cool..
Nov 17 04:20:12 <veremit> mods have an @
Nov 17 04:20:37 <Robert__> So, veremit, do you own a beagleboard..?
Nov 17 04:20:42 <veremit> I do
Nov 17 04:20:57 <veremit> runs a few bits and bobs here
Nov 17 04:20:59 <Robert__> Any idea on how's the after sales support works..?
Nov 17 04:21:09 <agmlego> ha.
Nov 17 04:21:12 <agmlego> hahaha.
Nov 17 04:21:14 <veremit> what are you looking for?
Nov 17 04:21:23 <agmlego> after-sales support.
Nov 17 04:21:25 <veremit> the 'support' is online and what limited help is here.
Nov 17 04:21:42 <veremit> but this isn't a production unit.
Nov 17 04:21:49 <veremit> there is no 'support contract'
Nov 17 04:22:35 <Robert__> okie..
Nov 17 04:23:01 <Robert__> I know it's a community owned by TI..
Nov 17 04:23:07 <veremit> in fact.. you're mostly on your own .. unless you believe your board has a fault, and needs to be RMA'd
Nov 17 04:23:12 <Robert__> But who does supply the board..?
Nov 17 04:23:34 <veremit> offical beagleboards are made by CircuitCo in US
Nov 17 04:23:39 <Robert__> What's the RMA about..?
Nov 17 04:23:51 <veremit> beagle-approved are made by Element14/farnell
Nov 17 04:24:24 <veremit> perhaps you should explore http://beagleboard.org a little .. :)
Nov 17 04:24:43 <Robert__> Sure..
Nov 17 04:25:11 <Robert__> I did notice there are few channels to download the sourcecode for Android..
Nov 17 04:25:47 <Robert__> Are you a android based user..?
Nov 17 04:25:55 <veremit> linux only
Nov 17 04:26:40 <Robert__> Oh okie, any idea which is the correct channel to get the Android sourcecodes, especially the new ones (KitKat)..?
Nov 17 04:27:07 <Robert__> :)
Nov 17 04:28:06 <veremit> http://elinux.org/Beagleboard:Android as a starting point
Nov 17 04:28:30 <veremit> http://2net.co.uk/tutorial/android-4.4-beaglebone also
Nov 17 04:29:18 <veremit> or http://2net.co.uk/tutorial/android-4.4-beaglebone-update
Nov 17 04:30:21 <veremit> good luck ! :)
Nov 17 04:44:24 <Robert__> Thanks..
Nov 17 04:50:23 <veremit> aaand sleeptyme .. nite all
Nov 17 07:57:18 <motzer> good morning
Nov 17 08:00:42 <motzer> Guys I am new to embedded linux and the BBB, but maybe you can help me to solve a basic task. I've got an acceleroemter connected via i2c to the BBB, I just want to sample data and the corresponding timestamp and save this into a file onto the micro sd card. Everything works fine but there are timing problems. When I plot my data there are strange jumps so acceleroemter data does not fit to the actual timestamp. Even if I set the samp
Nov 17 08:01:39 <honestly> motzer: well, firstly you need to fix your irc client so it doesn't send overlong messages that get cut off
Nov 17 08:01:40 <motzer> any code snippets ideas or standard solutions ? I think this is a basic problem - collect data via sensor and log them. But google does not help me at all
Nov 17 08:02:39 <motzer> i stopped at .."10Hz" cause I do not want to send something overlong
Nov 17 08:02:47 <av500> define "strange jumps"
Nov 17 08:03:27 <honestly> motzer: your first message stopped at "even if I set the samp"
Nov 17 08:03:56 <motzer> @ honestly okay i just wrote "even if i set the sample rate down to 10 Hz"
Nov 17 08:04:33 <motzer> @av500 : the plot ist not monoton it seems that an accelerometer value e.g  of 5seconds is plottet at an earliere time stamp value
Nov 17 08:05:10 <motzer> it looks like a little kid draws the plot and sometimes it goes backwards
Nov 17 08:05:48 <av500> your timestamps are monotone, right?
Nov 17 08:05:57 <av500> how do you obtain the timestamps?
Nov 17 08:06:05 <motzer> It think it is something with timing problems dring the save operation onto the sd card and nearly simultaniouse data acquisition
Nov 17 08:06:06 <av500> also, have a pic of that plot online?
Nov 17 08:06:20 <motzer> yes give me a minute I will upload one
Nov 17 08:06:28 <av500> well, you have a lot of RAM, does it get better if you just save to memory?
Nov 17 08:06:35 <av500> and not to SD
Nov 17 08:06:36 <av500> for a test
Nov 17 08:08:33 <motzer> give me a second i just make a new plot and up it somwhere
Nov 17 08:11:48 <motzer> http://img4web.com/view/TT6X5Q
Nov 17 08:12:33 <motzer> you can see the main course but these "drawbacks" are wrong
Nov 17 08:13:09 <motzer> i get the time via clock_gettime
Nov 17 08:13:27 <motzer> CLOCK_REALTIME with seconds and nanoseconds as output
Nov 17 08:15:13 <tbr> motzer: could it be this? http://stackoverflow.com/a/20483739/2648865
Nov 17 08:17:18 <motzer> tbr that is really the first hint after a long time =) i did not call in question these functions
Nov 17 08:17:52 <motzer> because I thought such system kernel stuff should be "good" enough for my purpose
Nov 17 08:18:39 <tbr> I'm sure it is, you still need to use things correctly though.
Nov 17 08:18:56 <motzer> thank you very much tbr I will check it out and is really a logic way to use the function
Nov 17 08:19:09 <motzer> and that nses is set back to 0 after every second
Nov 17 08:19:30 <motzer> i try it and give feedback ;-)
Nov 17 08:22:35 <av500> motzer: your timestamps should not be non-monotonic
Nov 17 08:22:42 <av500> so I would say you do something wrong
Nov 17 08:24:51 <motzer> is CLOCK_REALTIME not the right way for this task ? maybe CLOCK_MONOTONIC is the right way ?
Nov 17 08:26:35 <motzer_2> sorry disconnect
Nov 17 08:27:15 <motzer_2> dont know what cam through bevor I was kicked out - So what do you use to realize a timestamp on the beaglebone under linux ?
Nov 17 08:27:50 <tbr> this isn't particularly specific to the BBB
Nov 17 08:28:18 <Humpelstilzchen> I usually use localtime()
Nov 17 08:28:24 <tbr> it is more about the requirements of your timestamping and the answer is probably in the documentation of that function you are using
Nov 17 08:28:54 <tbr> logging time in very small increments is nothing new on linux
Nov 17 08:29:59 <motzer_2> yes okay Humpelstilzchen but seconds as max resolution is not enough for sampling my accelerometer I would be happy with 10Hz or even better if possible
Nov 17 08:30:26 <av500> motzer_2: I use CLOCK_MONOTONIC
Nov 17 08:30:40 <honestly> motzer_2: you should definitely use clock_monotonic instead of _realtime
Nov 17 08:30:41 <motzer_2> tbr so there is no easy going standard way just use this time variable and go on you have to make some workaround - ClOCK_MONOTONIC will be my next try
Nov 17 08:31:07 <motzer_2> av500: honestly  okay I will have a look at it
Nov 17 08:31:08 <av500> motzer_2: I use CLOCK_MONOTONIC and I convert it down to milliseconds
Nov 17 08:31:24 <tbr> why workaround? it's about reading and understanding documentation and matching it to your requirements.
Nov 17 08:31:33 <Humpelstilzchen> motzer_2: gettimeofday?
Nov 17 08:32:44 <motzer_2> Humpelstilzchen: maybe here is the same problem like with CLOCK_REALTIME
Nov 17 08:33:56 <Humpelstilzchen> motzer_2: Have you checked man timerfd_create?
Nov 17 08:37:36 <motzer_2> Humpelstilzchen: sounds good I will check both - first I try clock_monotonic in my code an if there are still problems I try a timer file
Nov 17 08:38:05 <motzer_2> thanks until now enough ideas and help for me to go on and try again some stuff =)
Nov 17 08:38:20 <Humpelstilzchen> motzer_2: the reference to the man page was for the difference in clocks
Nov 17 08:46:29 <Rotti> hi
Nov 17 08:46:31 <motzer_2> Humpelstilzchen:  which reference ?
Nov 17 08:47:17 <motzer_2> so with CLOCK_MONOTONIC i get the same issue without adjusting my code I thing you have to handle the reset of nanoseconds in some way
Nov 17 09:28:04 <grandpas> hi everyone
Nov 17 09:29:25 <grandpas> I have a question concerning the SYS_RESETn signal of the beaglebone black.
Nov 17 09:29:33 <grandpas> It is said "Do not drive any external signals into the I/O pins until after the SYS_RESETn signal is HI (3.3V)."
Nov 17 09:29:34 <av500> so ask
Nov 17 09:30:03 <grandpas> My quesition is : If I drive a signal to 0V, is it ok or not ?
Nov 17 09:30:14 <honestly> no.
Nov 17 09:30:15 <grandpas> Or it has to be in high impedance ?
Nov 17 09:30:23 <av500> yes
Nov 17 09:30:31 <grandpas> ok thks :)
Nov 17 09:30:38 <grandpas> can u tell me the reason for that ?
Nov 17 09:30:45 <grandpas> the BBB needs to set up its I/Os ?
Nov 17 09:31:34 <av500> its the CPU itself
Nov 17 09:31:49 <honestly> yes, the IO Port Controllers need to be initialised to a safe default state before it is safe to connect any signals to it.
Nov 17 09:31:50 <av500> so you would need to ask the TI silicon desing team
Nov 17 09:32:09 <av500> most likely nothing bad will happen, but it "could" happen
Nov 17 09:32:12 <av500> so better safe than sorry
Nov 17 09:32:19 <honestly> a connection to ground can cause a short or overcurrent just as well as a connection to some high voltage
Nov 17 09:32:39 <av500> if something happens, you cannot blame TI as they told you not to
Nov 17 09:32:41 <honestly> av500: having used a couple of arm-based MCUs... pads can and do blow out
Nov 17 09:32:46 <av500> sire
Nov 17 09:32:48 <av500> sure
Nov 17 09:33:07 <honestly> even if you think you're doing everything correctly
Nov 17 09:33:17 <av500> OTOH I am touching prototype PCBs for years with my bear hands and nothing happened :)
Nov 17 09:33:25 <woglinde> *g*
Nov 17 09:33:30 <grandpas> :)
Nov 17 09:33:34 <grandpas> ok thks
Nov 17 09:33:37 <honestly> av500: what does the bear think of that?
Nov 17 09:33:42 <av500> well, I dropped one once and that killed a BGA ball
Nov 17 09:33:51 <av500> stupid BGA
Nov 17 09:34:48 <honestly> I should actually consider that in the design of the system I'm building...
Nov 17 09:34:51 * av500 is also driving 3.3V serial into 1.8 UARTs for years
Nov 17 09:35:01 <ds2> do not drive it low either
Nov 17 09:35:17 <grandpas> even with a serial resistance ?
Nov 17 09:35:23 <av500> no
Nov 17 09:35:28 <ds2> I don't see what is the issue with that
Nov 17 09:35:38 <grandpas> =/
Nov 17 09:35:42 <ds2> if you have a signal, qualify it with a tristate buffer using the sys reset line
Nov 17 09:35:49 <woglinde> av500 try to drive 5V
Nov 17 09:35:58 <ds2> easier to drop that in then to debug why things don't work.
Nov 17 09:36:05 <av500> serial R might work too
Nov 17 09:36:13 <av500> if thats ok with your rise times
Nov 17 09:36:17 <grandpas> yes I was thinking of doing that, but wanted to be sure
Nov 17 09:36:25 <av500> woglinde: send me a board
Nov 17 09:36:32 <ds2> there are plenty of fast buffers
Nov 17 09:36:34 <woglinde> no I will leave now
Nov 17 09:36:44 <grandpas> thks everyone !
Nov 17 09:36:54 <ds2> cheap insurance
Nov 17 09:37:02 <grandpas> have a nice day
Nov 17 09:37:03 <av500> grandpas: also, there is a difference between making a commercial board
Nov 17 09:37:10 <av500> and making a one-off hobby schematic
Nov 17 09:37:21 <ds2> one should always design properly
Nov 17 09:37:28 <ds2> no excuse for half-ass crap ever
Nov 17 09:37:30 <av500> lalalala
Nov 17 09:37:34 <av500> I cannot hear you
Nov 17 09:37:44 <ds2> now fixing a prototype at the last second...that's a different story :D
Nov 17 09:37:46 <honestly> ...or making one that has to tolerate completely unbuffered vibrations/shocks from driving on an asphalt circuit...
Nov 17 09:38:04 <honestly> we used to use spring-loaded fuse casings
Nov 17 09:38:31 <honestly> and then wondered why the damn thing turned off every time we drove over the same spot on the course
Nov 17 09:38:35 <ds2> is that why the Gen8's had "interesting" behaviors? :D heheh
Nov 17 09:38:44 <av500> ds2: :)
Nov 17 09:39:08 <honestly> ds2: ALL the wirse bridges
Nov 17 09:39:11 <honestly> wire*
Nov 17 09:39:37 <ds2> design is different from implementation
Nov 17 09:40:03 <honestly> "if you have to be sloppy, be sloppy during implementation, not design"?
Nov 17 09:40:08 <ds2> if you cut corners at the design state, you might are cutting out options later
Nov 17 09:40:37 <honestly> it's far easier to leave a component out and bridge it than it is to bodge it in without a spot for it on the board
Nov 17 09:40:38 <ds2> something like that. you will make mistakes, design in ways to fix them ;)
Nov 17 09:43:11 <honestly> most of the inputs in the stuff I'm working on drives an optocoupler and the optocoupler drives the input pad
Nov 17 09:43:26 <honestly> would be fairly easy to put the reset line in front of that
Nov 17 09:47:22 <motzer_2> thanks guys it works now I use CLOCK_MONOTONIC_RAW and just handel the issue that nanoseconds get reseted every second but the digits do not last so there seems to be a jump back but in reality there is no jump =)
Nov 17 09:48:10 <honestly> yes... of course nanoseconds get reset every second
Nov 17 09:48:27 <honestly> the time is seconds + nanoseconds
Nov 17 09:49:15 <honestly> what do you mean by jump
Nov 17 14:28:53 <Kos-teK> Hello :)
Nov 17 14:29:10 <Kos-teK> I have a assive problem with the BeagleBone Black (Rev C)
Nov 17 14:29:23 <Kos-teK> (sorry for my poor English) i'm french
Nov 17 14:30:10 <Kos-teK> i have update the BBB to Debian Jessie, and i don't have capemgr folders....
Nov 17 14:30:52 <Kos-teK> like /sys/devices/bone_capemgr.9/
Nov 17 14:31:42 <Kos-teK> so i cannot use the Mikrobus Cape...
Nov 17 14:35:47 <av500> you can still use capes
Nov 17 14:36:02 <av500> you just need to create a new DT file that includes your cape stuff
Nov 17 14:36:13 <av500> this is also the generic linux way of using DT for now
Nov 17 14:36:28 <Kos-teK> av500: do you have a tutorial for create a DT for MikrobusCape ?
Nov 17 14:36:34 <Kos-teK> or just a DT :)
Nov 17 14:36:54 <Kos-teK> (thank you for your answer)
Nov 17 14:37:18 <av500> no
Nov 17 14:37:23 <av500> but google knows about DT
Nov 17 14:38:24 <Kos-teK> ok thanks :)
Nov 17 14:44:27 <Kos-teK> av500: a DT file have an extension like .dts or .dtbo ?
Nov 17 14:44:52 <hitlin37> .dts
Nov 17 14:45:27 <Kos-teK> ok thanks hitlin37
Nov 17 14:47:34 <hitlin37> the b in dtb is for binary
Nov 17 14:52:38 <av500> and o is for octal?
Nov 17 14:56:12 <nomis> more likely "o"verlay
Nov 17 14:56:41 <av500> "o"h
Nov 17 18:19:22 <kamileon> I am looking for a way to live stream captured data from a rlt-sdr to a local server.  My BBB is running ubuntu 14.04.  Any ideas?
Nov 17 18:19:52 <Humpelstilzchen> kamileon: tried rtp_tcp?
Nov 17 18:20:10 <Humpelstilzchen> rtl_tcp
Nov 17 18:21:17 <kamileon> no I havent
Nov 17 20:14:20 <kenrestivo> dt's are nontrivial
Nov 17 20:14:38 <kenrestivo> though i found this helpful http://www.youtube.com/watch?v=m_NyYEBxfn8
Nov 17 20:16:00 <kenrestivo> so, is cape manager officially dead now?
Nov 17 20:16:29 <kenrestivo> is current best practices that changes shouldn't be made at runtime, everything needs to be in compiled dt's and rebooted? i'm not clear on the status.
Nov 17 21:02:05 <jkridner> hi vvu
Nov 17 21:02:28 <jkridner> best to chat here or in a channel on google chrome.
Nov 17 21:02:41 * jkridner wonders what channel google chrome is discussed.
Nov 17 21:02:58 <vvu> have no clue about that
Nov 17 21:03:12 <vvu> when i look into it I was at https://developer.chrome.com/apps/usb#method-requestAccess
Nov 17 21:03:22 <vvu> but they changed this as I can see, maybe we have access now
Nov 17 21:05:23 <jkridner> I read that function was only for Chromebooks.
Nov 17 21:05:37 <vvu> yes, maybe now they included it into all platforms
Nov 17 21:05:40 <jkridner> right now, my app (https://github.com/jadonk/beagleboot) doesn't get any devices. :(
Nov 17 21:06:04 <jkridner> their device-info app finds several, but not the Bone's boot ROM.
Nov 17 21:06:28 <jkridner> device-info app (https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/usb/device-info) also doesn't find several other devices, like the built-in webcam on my macbook air.
Nov 17 21:06:59 <vvu> jkridner: that is what i was saying, some devices are taken by the OS and chrome does not let you get them back from the OS
Nov 17 21:07:03 <jkridner> I'm not sure if it matters if is part of the background app or an active page (don't know terminology)
Nov 17 21:07:12 <jkridner> oh. :(
Nov 17 21:07:23 <vvu> it does not matter, anyway chrome uses libusb in the background
Nov 17 21:08:06 <vvu> so that is why I was saying to use NaCl, we just implement everything in C using libusb and make the connections to the js in the webpage
Nov 17 21:11:13 <jkridner> k. I was looking forward to just implementing everything in .js :-)
Nov 17 21:11:50 <vvu> nop
Nov 17 21:12:06 <vvu> just a bit of js but again moar C
Nov 17 21:13:53 * vvu hates multiplatform stuff
Nov 17 21:15:06 <vvu> jkridner: can you add me as a colaborator to the repo and I will start the NaCl work
Nov 17 21:15:26 <jkridner> why not just fork and send pull requests?
Nov 17 21:15:44 <vvu> dat tru
Nov 17 21:16:44 <jbdatko> vvu: like the Cryptolib NaCl ?
Nov 17 21:17:06 * jbdatko is curious 
Nov 17 21:17:46 <vvu> jbdatko: nop, https://support.google.com/chrome/answer/1647344?hl=en
Nov 17 21:18:09 <jbdatko> Oh, native client… was all excited there for a second
Nov 17 21:18:30 * jbdatko goes back to his regularly scheduled programming
Nov 17 21:49:05 <jkridner> vvu: I'm checking out some of the stuff at https://gist.github.com/davidkelley/9002267 and preparing a post to https://groups.google.com/a/chromium.org/forum/#!newtopic/chromium-os-dev
Nov 17 21:50:08 <jkridner> vvu: make sure  you have https://github.com/jadonk/beagleboot/commit/9db5e5dd9d00b3828212be2429276a03ff23c630
Nov 17 21:51:19 <veremit> any news on the Arduino tre yet jkridner?
Nov 17 21:51:27 <jkridner> nope
Nov 17 21:51:48 <veremit> thats gonna be very cool
Nov 17 21:51:58 <veremit> is there any timeline besides "Soon"(tm0
Nov 17 21:52:00 <veremit> (tm)
Nov 17 22:55:08 <jmss> Hi, is there any image with Ubuntu GUI for XM?
Nov 17 22:55:32 <jmss> would it be too slow?
Nov 17 22:57:21 <tbr> the XM is not a desktop pc
Nov 17 22:58:09 <thurgood> slow yes, available probably, up to date, dunno
Nov 17 22:59:09 <thurgood> the xM at least had hardware video support something the bbb doesn't have
Nov 17 23:01:26 <jmss> I was evaluating the possibility of using it like a portable device for slide presentations
Nov 17 23:01:53 <jmss> it's probably not a good idea
Nov 17 23:03:45 <veremit> get a cheap laptop or tablet :)
Nov 17 23:03:49 <thurgood> there are probably better devices for that, cheaper if you're not prototyping something
Nov 17 23:04:27 <jmss> yes, that was the first idea
Nov 17 23:04:49 <jmss> I'll probaly use the XM to host a simple website
Nov 17 23:05:31 <jmss> selling it would probably be not a reasonable deal
Nov 17 23:06:01 <jmss> since it is much expensive and worst than the Black
Nov 17 23:09:59 <jmss> ok, thanks
Nov 17 23:38:01 <cabral> clear
Nov 17 23:38:15 <cabral> hello
Nov 17 23:56:44 <vvu> jkridner: so no luck with usb api :(
Nov 18 00:09:21 <jkridner> yeah, guess this just isn't possible to do reasonably. so irritated.
Nov 18 00:14:56 <vvu> jkridner: yep...now i am not even sure nacl works fully
Nov 18 00:27:49 * jkridner wants to kick the ROM code developers.
Nov 18 00:32:17 <vvu> jkridner: well you have @ti.com email :) can argue there a bit
Nov 18 00:33:13 <jkridner> uh, as an intern, didn't you get an @ti.com e-mail?
Nov 18 00:33:25 <vvu> yeah but was canceled at the end
Nov 18 00:33:29 <jkridner> guess you don't feel so inclined to kick them?
Nov 18 00:33:47 <vvu> i was inclied to kick people from code composer studio more than those ROM peeps
**** ENDING LOGGING AT Tue Nov 18 02:59:59 2014