**** BEGIN LOGGING AT Mon Aug 04 02:59:59 2014
Aug 04 05:08:29 <Rotti> hi
Aug 04 10:49:16 <Abhisek> hi
Aug 04 10:50:34 <Abhisek> i need to knw that can i use  Matlab/Simulink on BeagleBone Black for image processing
Aug 04 10:55:50 <shah> how can i interface my webcam/digicam to beaglebone black using usb cable to capture image
Aug 04 13:19:03 <mistawright> hi guys i need some help. I had my beaglebone black powered from a l298n breakout and had it operating the h-bridge and controlling speed using a pwm pin. I then tried to get a servo working by connecting it to p9_14. I had the enable a from the h-bridge connected to p8_19. When I attempted to set the duty after setting the period my beaglebone black just shutdown. this happens everytime i do this. I have the servo gro
Aug 04 13:19:03 <mistawright> unded and powered from the same h-bridge. do i need a ground directly between the servo and the beaglebone black?
Aug 04 13:19:14 <mistawright> what could cause this behavior?
Aug 04 13:36:09 <pzn> how can I know if the BBB watchdog is enabled and running, or if it was disabled by some program? I have a running BBB with ssh access to it.
Aug 04 14:27:01 <w0lt> Can anyone tell me how to keep the NVC server going on a BeagleBone-Black?  currently, after I disconnect, it won't allow me to reconnect.  Thanks in advance !!
Aug 04 14:27:18 <w0lt> That's VNC, not NVC..  :-)
Aug 04 14:38:10 <Humpelstilzchen> w0lt: not a BBB specifig problem..
Aug 04 14:59:36 <mistawright> hi guys i need some help. I had my beaglebone black powered from a l298n breakout and had it operating the h-bridge and controlling speed using a pwm pin. I then tried to get a servo working by connecting it to p9_14. I had the enable a from the h-bridge connected to p8_19. When I attempted to set the duty after setting the period my beaglebone black just shutdown. this happens everytime i do this. I have the servo gro
Aug 04 14:59:36 <mistawright> unded and powered from the same h-bridge. do i need a ground directly between the servo and the beaglebone black? what could cause this behavior?
Aug 04 15:59:27 <elik> Hi, I'm using the beaglebone black with the debian distribution.
Aug 04 15:59:42 <elik> I notice there are ttyO* and ttyS serial devices
Aug 04 15:59:55 <elik> When I enable an overlay, it creates the ttyO devices
Aug 04 16:00:20 <elik> but by default, I have ttyS0 through ttyS3 created
Aug 04 16:00:33 <elik> enabling UART2, I end up with a ttyO2 as well
Aug 04 16:00:54 <elik> I know the omap serial driver uses the ttyO prefix from some kernel digging, but where do these ttyS come from?
Aug 04 16:03:14 <vagrantc> ttyS is a traditional serial interface
Aug 04 16:03:24 <elik> right
Aug 04 16:03:29 <elik> but to which hardware is it tied?
Aug 04 16:04:10 <elik> on a side note, if someone can provide some insight as to why ttyO was used for omap serial ports, given they are fairly traditional serial interfaces
Aug 04 16:10:56 <LetoThe2nd> elik: thats just because many of the UART ip peripherals on arm socs started out with other suffixes initially
Aug 04 16:11:17 <LetoThe2nd> given they're not 8250 compliant (or what ever that classic one was)
Aug 04 16:11:54 <LetoThe2nd> but in the end they provide comparable features to the userland, so they can also present themselves as standard ttyS*
Aug 04 16:12:00 <elik> LetoThe2nd: ok, I though that all ports that tried to emulate that chip ended up as ttyS
Aug 04 16:12:13 <elik> LetoThe2nd: are there plans in the future to change the name back to ttyS?
Aug 04 16:13:06 <LetoThe2nd> elik: no idea. but most things like that can be configured to be ttyS* instead of their own suffix (omap should, atmel can, have not used others so far.)
Aug 04 16:13:21 <elik> LetoThe2nd: through udev?
Aug 04 16:13:35 <LetoThe2nd> elik: no, kernel config.
Aug 04 16:13:37 <elik> LetoThe2nd: or as module options
Aug 04 16:13:41 <elik> ok
Aug 04 16:13:56 <LetoThe2nd> elik: just check the respective drivers
Aug 04 16:13:59 <elik> LetoThe2nd: and would you happen to know about those ttyS devices I see?
Aug 04 16:14:14 <LetoThe2nd> elik: not in your particular case, sorry.
Aug 04 16:15:01 <elik> alright, thx for the info LetoThe2nd!
Aug 04 16:35:48 <leiflindholm> Is there any public documentation/description/source code of the ROM code which loads MLO on BeagleBone Black?
Aug 04 16:49:48 <elik> leiflindholm: what loads the MLO is burned inside the AM335x, and I don't think that source code is available
Aug 04 16:50:15 <elik> leiflindholm: that being said, it's documented in the datasheet, under the boot sequence
Aug 04 16:50:22 <leiflindholm> elik: I didn't think so, but I figured it was worth asking :)
Aug 04 16:50:39 <leiflindholm> elik: yeah, but it's quite high-level blocks and arrows
Aug 04 16:51:22 <elik> leiflindholm: that's to my knowledge, I'm not a reference by any mean :)
Aug 04 16:51:38 <leiflindholm> elik: still appreciated, thanks
Aug 04 16:51:48 <elik> leiflindholm: high level, but usually sufficient given the interface is fairly clear cut (do some setup, jump to address)
Aug 04 16:51:59 <elik> leiflindholm: why were you looking for it anyway?
Aug 04 16:52:13 <elik> issue with a boot mode?
Aug 04 16:53:30 <leiflindholm> well, I have a GSoC student doing a UEFI port, and I just wanted to look into how far back we could take the port if we wanted it to
Aug 04 16:53:47 <leiflindholm> currently loading a UEFI image called u-boot.bin onto the MMC :)
Aug 04 16:54:18 <leiflindholm> so I was a bit curious as to what the boot ROM does for the boot from MMC option
Aug 04 16:54:32 <leiflindholm> and if that could ever be compatible with GPT partitioning
Aug 04 16:55:22 <mistawright> hi guys is there any reason why using the beaglebone black to control an l298n and a servo would cause the beaglebone black to shutdown? I am able to get the motor going and but when i try to set the duty of the servo it shuts down
Aug 04 16:55:43 <leiflindholm> elik: ^^
Aug 04 16:56:48 <tbr> leiflindholm: it's pretty hardwired for FAT, unless you use its raw device option, then it expects MLO at a fixed offset
Aug 04 16:57:23 <leiflindholm> tbr: oh, that sounds intriguing
Aug 04 16:57:31 <leiflindholm> tbr: the fixed offset
Aug 04 16:57:39 <tbr> that should be in the TRM
Aug 04 16:57:48 <leiflindholm> tbr: did I miss that in the TRM? bah, need new glasses
Aug 04 16:59:00 <elik> leiflindholm: interesting project
Aug 04 16:59:03 <leiflindholm> tbr: found it - much obliged
Aug 04 16:59:09 <tbr> :)
Aug 04 16:59:43 <leiflindholm> and if I keep the number of partitions low, it should be doable...
Aug 04 16:59:58 * vagrantc hasn't had much luck with MLO at offset
Aug 04 17:00:42 * leiflindholm runs away and plays with that idea anyway
Aug 04 17:00:51 <tbr> leiflindholm: keep in mind that it's very space constrained
Aug 04 17:01:13 <vagrantc> leiflindholm: would be really interested how it goes
Aug 04 17:01:20 <leiflindholm> tbr: oh yeah - it would have to be a minimal trampolie thing
Aug 04 17:01:27 <leiflindholm> trampoline
Aug 04 17:01:32 <tbr> MLO IIRC runs in some crazy small SRAM as it needs to set up DDR3 etc
Aug 04 17:01:41 <leiflindholm> (much like MLO)
Aug 04 17:01:57 <leiflindholm> "The boot image is downloaded directly into internal RAM at the location 0x402F0400 on GP devices. The
Aug 04 17:02:00 <leiflindholm> maximum size of downloaded image is 109 KB.
Aug 04 17:02:03 <leiflindholm> "
Aug 04 17:02:06 <leiflindholm> so, yeah
Aug 04 17:02:13 * leiflindholm really runs away, has a bus to catch
Aug 04 17:02:20 <tbr> :)
Aug 04 17:04:56 <elik> Posted that earlier, but does anybody know what hardware ttyS is bound to, on the debian image that comes with bbb
Aug 04 17:05:48 <pzn> USB-OTG is the big-usb connector or the mini-usb?
Aug 04 17:06:38 <tbr> pzn: essentially both, what are you trying?
Aug 04 17:07:02 <tbr> elik: ttyOx not S?
Aug 04 17:07:24 <elik> tbr: I know ttyO* are tied to uarts, but I have ttyS0 through ttyS3
Aug 04 17:08:54 <pzn> tbr, I'm experiencing random reboots, going from hourly to weekly intervals. found a mailing list discussion about disabling the usb-otg to try to fix this reboots
Aug 04 17:09:33 <pzn> tbr, what I have is powered by the 5V plug, and using the big-usb connector for pluging a 3G-modem
Aug 04 17:10:06 <tbr> if you want to use the modem, no way to get rid of musb
Aug 04 17:10:11 <pzn> tbr, should I have this "USB-OTG" feature enabled to be able to use an usb-modem?
Aug 04 17:10:30 <pzn> tbr, sorry... what is "musb"?
Aug 04 17:11:00 <tbr> elik: no idea if the kernel does anything with those, check with userspace tools
Aug 04 17:11:37 <tbr> pzn: that's the USB IP core providing both USB ports
Aug 04 17:11:58 <pzn> tbr, and what is usb-otg?
Aug 04 17:12:02 <elik> tbr: not sure which tools I can use to investigate further
Aug 04 17:12:37 <tbr> pzn: a standard
Aug 04 17:12:54 <Nitin_> hi
Aug 04 17:13:38 <pzn> tbr, ok, got it. just didnt understand what usb is related to IP... did you mean the IP networking? when you said "USB IP core"... I just use the uart-over-usb thing, nothing related to IP
Aug 04 17:18:57 <tbr> pzn: IntellectualProperty-core a subsystem of a System on a Chip
Aug 04 17:23:55 <pzn> tbr, ok, got it
Aug 04 17:50:34 <mistawright> can anyone help me with my problem? I am at a lost. i had been making progress and beginning to really enjoy my beaglebone black
Aug 04 17:56:38 <vagrantc> mistawright: you might want to describe your problem, then people will know if they can help
Aug 04 18:26:03 <mistawright> vagrantc, I have. been in here since morning. But the issue I ran into. I am powering my beaglebone black from a volt pin on my h-bridge breakout and also a servo from another 5 volt pin. I am able to get the motor started fine. when I set the duty of the servo the beaglebone black shuts down. I only have the signal pin connected to the beaglebone black from the servo. So I am not sure if it is wiring or something else
Aug 04 18:30:30 <Humpelstilzchen> mistawright: use a separate power source
Aug 04 18:30:33 * vagrantc would only make wild guesses that there's a significant power drop for some reason...
Aug 04 18:33:00 <mistawright> everything is powered through the hbridge which is powered through a 3 cell lipo
Aug 04 18:34:41 <mistawright> this is the hbridge: http://www.vetco.net/catalog/product_info.php?products_id=14337&gclid=Cj0KEQjw3vyeBRDt673h5ZTYrdQBEiQAzhkf8kuSV6rNjAZ6tTugTy-xIQG1pPgZIqmdGeVIah1dkXwaAhfs8P8HAQ
Aug 04 18:35:00 <Humpelstilzchen> L298 .o0()
Aug 04 18:35:21 <Humpelstilzchen> uhm
Aug 04 18:35:34 <Humpelstilzchen> Onboard 5-Volt DC Regulator (A jumper selects between external 5-Volt power or the onboard 5-volt regulator.) <--you are using this one to power your beagle?
Aug 04 18:35:35 <mistawright> Humpelstilzchen, would you recommend something better? didnt want to drop as much on a motor cape as i did the beaglebone
Aug 04 18:35:48 <mistawright> yeah on board
Aug 04 18:36:05 <Humpelstilzchen> L298 is so last century...well the Arduino people seem to like it anyway
Aug 04 18:36:14 <mistawright> also attempting to power the servo from a 5 volt pin
Aug 04 18:36:38 <mistawright> what would you suggest. I want something that can deliver more punch to my motors without all the heat that i have noticed on this thing
Aug 04 18:36:55 <Humpelstilzchen> mistawright: the onboard is probably for low current consumers
Aug 04 18:37:08 <Humpelstilzchen> use a separate 5V supply
Aug 04 18:42:06 <mistawright> this should be fun. thanks for the helps guys
Aug 04 18:51:15 <mistawright> Humpelstilzchen, forgot to ask, what would be a better h bridge/breakout to use over the l298n
Aug 04 18:55:25 <Humpelstilzchen> mistawright: depends on what you need
Aug 04 18:55:53 <Humpelstilzchen> mistawright: you can check some sites like pololu.com for available boards
Aug 04 19:16:34 <mistawright> thanks again
Aug 04 19:46:20 <tbr> pololu makes decent stuff
Aug 04 19:46:45 <tbr> just to be sure I'd use two separate regulators.
Aug 04 19:56:00 <mistawright> i'll keep that in mind. hoping to have this car controlled by my beaglebone black so i can get to figuring out how to control it
Aug 04 20:02:52 <leiflindholm> tbr: (since vagrantc seems to have gone offline) it works! wrote MLO to 128K offset (as per 26.1.7.5.5), pressed button at power-on and it starts telling me I'm a very bad person on the console
Aug 04 20:03:20 <leiflindholm> with my home-built u-boot version ID in the message
Aug 04 20:03:56 <leiflindholm> elik: ^^
Aug 04 20:04:00 <paddy> hi !!
Aug 04 20:05:29 <leiflindholm> and actually, since it scans with a 128K stride, I can fit as many GPT partitions on there as I want to
Aug 04 20:29:53 <tbr> leiflindholm: glad you figured it out for yourself
Aug 04 20:31:51 <leiflindholm> tbr: thanks for mentioning "raw" mode
Aug 04 21:21:52 <elik> leiflindholm: nice :)
Aug 04 21:34:23 <newsham> hi.  i just got a bealgeboard (rev D).  i have it hooked up to serial with a usb/serial converter.  i'm using a 5v power supply to power it.  when i poewr it up, i'm only getting noise on serial line (at 115200)
Aug 04 21:34:52 <newsham> if i udnerstand correctly, uboot should be coming up during boot on the serial line, right?
Aug 04 21:35:01 <newsham> (even without an sdcard installed in it)
Aug 04 21:45:10 <newsham> i suspect my board is broken but i want to be sure.. *sigh*
Aug 04 21:47:01 <newsham> it looks like the "garbage" is timed right for different output i'd expect, but its all garbled, like its the wrong speed or something
Aug 04 22:38:29 <newsham> hmm.. the beagleboard's serial is +-15v not 0/3.3v?
Aug 04 22:38:49 <veremit> rs-232 is rs232
Aug 04 22:38:52 <veremit> uart is ttl
Aug 04 22:40:12 <newsham> this port connects directly to an rs232 port on a pc according to the refman
Aug 04 22:41:09 <veremit> 9pin D-type is usually idle -ve active +ve
Aug 04 22:41:21 <veremit> headers are 3v3 ttl
Aug 04 22:42:45 <newsham> hmm i get -5.66v on Tx on the p9 header
Aug 04 22:43:20 <newsham> (pin 3)
Aug 04 22:44:13 <veremit> yea if its got a driver chip, that would be likely
Aug 04 22:44:46 <veremit> if you scope it, will probably swing to +5.6v on data pulses
Aug 04 22:45:13 <veremit> usually runs off a charge pump
Aug 04 22:46:12 <newsham> dont have a scope
Aug 04 22:46:29 <newsham> so this bboard wants rs232 not ttl uart?
Aug 04 22:46:35 <newsham> maybe thats why my serial wasnt working
Aug 04 22:46:50 <veremit> they're not compatible
Aug 04 22:46:51 <veremit> ;)
Aug 04 22:47:31 <newsham> i just assumed uart/ttl everyone does that (even bbone black)
Aug 04 22:48:20 <veremit> if it comes direct from the processor, it will be ttl (+5v or +3v3 idle)
Aug 04 22:48:46 <veremit> if its come through a driver it will be inverted and negative. You'll beable to see if there's a driver chip
Aug 04 22:48:50 <veremit> else you're reading somethign wrong.
Aug 04 22:48:56 <veremit> be^able
Aug 04 22:49:13 <veremit> Rx/Tx swap is a favourite
Aug 04 22:49:26 <newsham> hah! eet works!
Aug 04 22:49:38 <newsham> yah, this one wants rs232 not ttl/uart
Aug 04 22:50:01 <veremit> it should be described in the System Reference Manual and/or wiki
Aug 04 22:50:17 <veremit> the black is definitely TTL I can say that .. debug header and p8/p9 pins.
Aug 04 22:50:19 <newsham> yah, it doesnt really say much, but it does say to hook it to a pc serial port :)
Aug 04 22:50:29 <newsham> yah i just hooked up a black 15min ago.. worked fine ttl
Aug 04 22:50:34 <veremit> but it doesn't have any D-type connectors , which is the easy give-away
Aug 04 22:51:00 <newsham> the beagleboard doesnt have a d connector either.. its on a 2x5 header
Aug 04 22:51:14 <veremit> oh so its like a PC motherboard then probably
Aug 04 22:51:22 <veremit> they often have a 2x5
Aug 04 22:51:41 <newsham> they say to use a ribbon-to-D cable
Aug 04 22:52:56 <veremit> there ya go .. enough hints I would say ;)
Aug 04 22:53:13 <newsham> yah but subtlety and specs arent the best mates :(
Aug 04 22:53:33 <veremit> rtfm ;) lol
Aug 04 22:54:14 <newsham> i did, many times :(
Aug 04 22:54:23 <newsham> was getting close to returning it.. thats why i wanted to check here first
Aug 04 22:54:39 <newsham> not that it helped.. nobody suggested the problem :(
Aug 04 22:55:03 <veremit> well .. if you had a meter, scope .. its not hard to figure out .. :P
Aug 04 22:55:23 <veremit> as long as you know what you're looking for/at
Aug 04 22:57:33 <newsham> all's well that ends well.. cheers
Aug 04 22:57:57 <veremit> welcome :)
Aug 04 22:58:26 <veremit> I like easy problems :D
Aug 04 22:58:52 <veremit> although .. with 2 other engineers .. nailed a video capture issue last night betwwen 10pm -3am :D
Aug 04 23:57:21 <Sargun>  net_adm:ping('bar@instance-2.c.rugged-nimbus-611.internal.').
Aug 04 23:57:21 <Sargun> er
**** ENDING LOGGING AT Tue Aug 05 03:00:00 2014