**** BEGIN LOGGING AT Sat Sep 13 02:59:58 2014
Sep 13 03:15:27 <agmlego> I do not think so.
Sep 13 05:07:58 <m_billybob> Only diff betwen B and C was eMMC size, *and* I think there was a different processor used.
Sep 13 05:58:23 <zsnafu> well hello hello
Sep 13 06:00:14 <_ziggy_> hello :D....
Sep 13 06:00:25 <_ziggy_> im trying to cross compile from win using eclipse to the bbb
Sep 13 06:00:42 <_ziggy_> i got everything to compile in eclipse and run on the bbb
Sep 13 06:00:54 <_ziggy_> thouh i'm having a hard time debugging
Sep 13 06:01:03 <_ziggy_> im using gdbserver on the bbb
Sep 13 06:01:30 <_ziggy_> and set up a remote debugger in ecilpse using the gdb in linaro
Sep 13 06:01:47 <_ziggy_> though when i try to debug i get the following:
Sep 13 06:02:05 <KotH> i guess, the first step for you is to learn that you want to develop embedded linux stuff on a linux system
Sep 13 06:02:05 <_ziggy_> $1 = 0xff
Sep 13 06:02:05 <_ziggy_> Cannot access memory at address 0x0
Sep 13 06:02:05 <_ziggy_> Cannot access memory at address 0x0
Sep 13 06:02:05 <_ziggy_> The target endianness is set automatically (currently little endian)
Sep 13 06:02:05 <_ziggy_> No source file named C:\\path\\to\\file\\test1\\src\\main.cpp.
Sep 13 06:02:39 <KotH> you are trying to dereference a null pointer
Sep 13 06:02:48 <_ziggy_> no
Sep 13 06:02:51 <KotH> yes
Sep 13 06:02:53 <_ziggy_> no
Sep 13 06:02:57 <KotH> that's what gdb tells you
Sep 13 06:03:07 <_ziggy_> it says that at the beginning of the file
Sep 13 06:03:12 <_ziggy_> because it cant find the source file
Sep 13 06:03:28 <KotH> well..
Sep 13 06:03:31 <KotH> see above
Sep 13 06:03:36 <KotH> use linux
Sep 13 06:03:43 <KotH> get rid of eclipse
Sep 13 06:03:49 <KotH> makes life easier
Sep 13 06:03:54 <_ziggy_> that doesn't solve the problem
Sep 13 06:05:43 <KotH> if it doesnt, it makes it easier for you to debug the problem
Sep 13 06:05:54 <KotH> again: using windows for embedded linux development is masochism
Sep 13 06:06:14 <_ziggy_> yea not really
Sep 13 06:08:05 <_av500_> _ziggy_: tried to login and run gdb locally on the BBB?
Sep 13 06:08:25 <_ziggy_> that defeats the purpose of what im trying to do
Sep 13 06:08:49 <_ziggy_> i can try
Sep 13 06:09:02 <_ziggy_> just sec
Sep 13 06:09:50 <_ziggy_> yea
Sep 13 06:09:52 <_ziggy_> it seems i can
Sep 13 06:09:55 <_ziggy_> and step through it just fine
Sep 13 06:11:41 <_ziggy_> which would indicate the binaries has all the debug info in it
Sep 13 06:23:50 <shreya> hi , we can connect webcam with beaglebone black in 2 ways, first is with usb and second is by using i2c (begalebone black cap).between them which on will be fast (taking input and image processing) ?
Sep 13 06:24:18 <KotH> usb
Sep 13 06:26:09 <shreya> <kotH> thanks..then y the begalebone black cap use i2c connction?
Sep 13 06:26:45 <KotH> shreya: the BBB does not have a camera
Sep 13 06:27:02 <KotH> shreya: i dont know which cape you are using, but i guess you have to ask the guy who designed it
Sep 13 06:27:33 <shreya> ohkk...can u give me reason y we use usb? i m not able to get proper reason
Sep 13 06:27:46 <KotH> uhmm...
Sep 13 06:27:55 <KotH> did you evaluate different cameras?
Sep 13 06:27:59 <KotH> if not, you should do that
Sep 13 06:28:06 <KotH> then you know whether you want to use usb or not
Sep 13 06:28:37 <shreya> kotH: different camera means by cmos or ccd?
Sep 13 06:29:19 <KotH> different camera means different manufacturer/interface/whatever
Sep 13 06:29:28 <shreya> ohkk.
Sep 13 06:29:29 <KotH> unless you are building your own camera module
Sep 13 06:30:25 <_av500_> I2C again?
Sep 13 06:30:35 <_av500_> shreya: you cannot connect a webcam with I2C
Sep 13 06:30:59 <shreya> av500: okk
Sep 13 06:31:14 <shreya> I2C agin means ?
Sep 13 06:32:23 <shreya> av500: y we can't connecr webcam with I2C . can u give reason?
Sep 13 06:32:39 <_av500_> are you the same guy as last night?
Sep 13 06:32:55 <nyt-> lol
Sep 13 06:32:56 <shreya> nop..i m here first
Sep 13 06:33:27 <_av500_> why I2C?
Sep 13 06:33:34 <_av500_> where did you read that?
Sep 13 06:33:59 <KotH> shreya: no, you may not send me private messages
Sep 13 06:34:00 <_ziggy_> there's camera's with i2c
Sep 13 06:34:02 <_ziggy_> http://www.uctronics.com/mt9t112-mi-soc3132-31mp-hd-cmos-camera-module-adapter-board-jpeg-out-p-1440.html
Sep 13 06:34:08 <shreya> http://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2013/08/18/bbb--imaging-with-a-pru-connected-camera
Sep 13 06:34:42 <KotH> _av500_: there are i2c camera modules...rare but they exist
Sep 13 06:34:51 <KotH> _av500_: no idea what their use case is, though
Sep 13 06:34:59 <shreya> ok
Sep 13 06:35:21 <_ziggy_> hobbiest
Sep 13 06:35:32 <_ziggy_> i did a few things with cameras on the arduino
Sep 13 06:35:38 <_ziggy_> through i2c
Sep 13 06:35:51 <_ziggy_> http://www.arducam.com/
Sep 13 06:36:25 <_av500_> _ziggy_: did you read any of the links you posted?
Sep 13 06:36:37 <_av500_> if its I2C, why are there a dozen wires?
Sep 13 06:36:42 <nyt-> pru
Sep 13 06:36:44 <nyt-> even in the title
Sep 13 06:36:46 <nyt-> of the link
Sep 13 06:36:53 <_ziggy_> av500...some of them support spi too
Sep 13 06:36:56 <_av500_> http://www.element14.com/community/servlet/JiveServlet/showImage/38-12890-171994/cam_all.jpg
Sep 13 06:37:07 <_av500_> answer my question
Sep 13 06:37:14 <_av500_> why are there so many wires?
Sep 13 06:37:23 <_av500_> i2c needs 2 wires, add GND and VCC, that is 4
Sep 13 06:38:37 <_ziggy_> uh
Sep 13 06:38:43 <_ziggy_> there are no wires on the links i posted
Sep 13 06:38:48 <_ziggy_> theres wires on the site shreya posted
Sep 13 06:38:56 <_av500_> http://www.element14.com/community/servlet/JiveServlet/showImage/38-12890-171994/cam_all.jpg
Sep 13 06:39:00 <_ziggy_> i think that's what you're looking at
Sep 13 06:39:02 <_av500_> see this?
Sep 13 06:39:05 <_ziggy_> write..i didn't post that dude
Sep 13 06:39:13 <_ziggy_> right
Sep 13 06:39:29 <_ziggy_> yup i sure do see that
Sep 13 06:39:30 <_av500_> _ziggy_: in what you posted, why does the module have so many pins?
Sep 13 06:39:35 <_av500_> 20
Sep 13 06:39:38 <_av500_> and not just 4
Sep 13 06:39:42 <_ziggy_> in what post?
Sep 13 06:39:49 <_av500_> 08:34 <        _ziggy_ > http://www.uctronics.com/mt9t112-mi-soc3132-31mp-hd-cmos-camera-module-adapter-board-jpeg-out-p-1440.html
Sep 13 06:39:54 <_av500_> stop being obtuse
Sep 13 06:40:46 <_ziggy_> obtuse? well since i posted 2 sites...i think asking which one is a fair question
Sep 13 06:42:40 <_av500_> so, back to the question
Sep 13 06:42:47 <_av500_> what are D0-D7
Sep 13 06:43:18 <nyt-> the arducam link he posted will run on i2c or spi
Sep 13 06:43:24 * nyt- shrgs
Sep 13 06:43:45 <_ziggy_> like i said
Sep 13 06:44:06 <_ziggy_> and the the other site says it runs on i2c
Sep 13 06:44:11 <_ziggy_> so what the fuck is the matter?
Sep 13 06:44:35 <shreya> plz don't fight guys
Sep 13 06:44:38 <_av500_> all is fine
Sep 13 06:44:45 <_av500_> google beaglebone and i2c
Sep 13 06:44:48 <_av500_> and you are done
Sep 13 06:45:26 <shreya> ohk
Sep 13 06:45:29 <shreya> thanks
Sep 13 06:46:06 <_av500_> just ask yourself, what are the D0-D7 pins n both of the modules above
Sep 13 06:46:56 <shreya> yupp...that what i was think, bcz in i2c there are four things...gnd , vcc and 2 data
Sep 13 06:47:48 <nyt-> lol
Sep 13 06:47:52 <nyt-> no data on i2c
Sep 13 06:47:54 <nyt-> data on the other pins
Sep 13 06:48:12 <nyt-> i2c just to configure
Sep 13 06:48:14 <nyt-> then 8 data pins
Sep 13 06:49:45 <_av500_> one link has the data sheet to the sensor
Sep 13 06:49:53 <_av500_> the other link shows how it is hooked up to a BBB
Sep 13 06:50:02 <_av500_> the information is all there
Sep 13 06:51:49 <shreya> ok
Sep 13 06:51:50 <_av500_> and the arducam links says: Data[N-1..0]: Data output from the sensor, N is the internal ADC bit width.
Sep 13 06:52:12 <nyt-> [09/12/2014@14:51] -// Quit by Guest19567(1bfb252a@gateway/web/freenode/ip.27.251.37.42):
Sep 13 06:52:14 <nyt-> same dude
Sep 13 06:52:38 <_av500_> but yes, the arducam shield converts that to SPI it seems
Sep 13 06:53:15 <nyt-> busted :/
Sep 13 06:53:22 <_av500_> :)
Sep 13 06:53:31 <KotH> lol
Sep 13 06:53:33 <KotH> nyt-: good job!
Sep 13 07:19:45 <m_billybob> that definately was the same person from last night
Sep 13 07:20:05 <m_billybob> short two character "ok" responces
Sep 13 07:20:41 <m_billybob> didnt someone last night come to the conclusion that I2C was only used to control the cam ?
Sep 13 07:20:49 * m_billybob shrugs
Sep 13 07:21:04 <m_billybob> and once again . . .
Sep 13 07:32:08 <Humpelstilzchen> m_billybob: yes
Sep 13 07:32:53 <Humpelstilzchen> image data is not send over i2c
Sep 13 08:55:15 * _av500_ still wants gigI2C
**** BEGIN LOGGING AT Sat Sep 13 13:56:10 2014
Sep 13 15:04:37 <Guest92447> Hi all, I have a A6 beagleboard black to repair... When I try to read 24c32 EEPROM on board (I2C0 @0x50) all is FF or 55. Where I can found original EEPROM file ? Thank you
Sep 13 17:16:32 <raj_> Guys??
Sep 13 17:17:58 <raj_> I'm using beaglebone black to develop image processing application
Sep 13 17:18:14 <raj_> i use a belkin 4 port USB 2.0 Hub
Sep 13 17:18:18 <Humpelstilzchen> you have attached the camera over spi/i2c?
Sep 13 17:18:42 <raj_> it works fine when I connect my keyboard and mouse
Sep 13 17:18:57 <agmlego> How are you powering the hub?
Sep 13 17:19:03 <agmlego> How are you owering the bone?
Sep 13 17:19:23 <raj_> I connect the camera the hub powers down after some time like few seconds
Sep 13 17:19:45 <raj_> I power the Hub from the beaglebone USB port
Sep 13 17:19:52 <agmlego> THat is wrong.
Sep 13 17:20:08 <agmlego> We talked abotu this last time, remember?
Sep 13 17:20:25 <raj_> Is there another way to rectify this ?
Sep 13 17:20:28 <agmlego> The hub needs to hav its own power; powering things over the USB port from the bone is generally a bad idea.
Sep 13 17:21:02 <agmlego> The bone is not designed to provide very much power over its USB host port.
Sep 13 17:21:29 <raj_> Is ther a better way I can power my hub exteranlly ?
Sep 13 17:21:59 <agmlego> ...yes, use the power adapter that came with the hub, and insert it into the hub's external-power port.
Sep 13 17:22:07 <raj_> But when the camera is connected directly to the bone it works
Sep 13 17:22:25 <agmlego> Or, if the hub did not come with an adapter, buy one that provides the listed voltage and current, and insert it into the hub's external-power port.
Sep 13 17:22:39 <raj_> My Hub doesnot have a external port to power it
Sep 13 17:22:44 <agmlego> Or, if the hub does not have an external-power port, buy a new hub and associated adapter.
Sep 13 17:23:17 <agmlego> The camera worked plugged into the bone directly because the bone was only powering the camera. Now the bone is powering the camera and the hub.
Sep 13 17:23:27 <agmlego> And whatever else you have on the hub.
Sep 13 17:23:49 <agmlego> THis is why the hub needs to have its own power; then the hub can power all the devices attached to it, and the bone does not have to.
Sep 13 17:23:54 <raj_> Thank you all for helping me!
Sep 13 17:24:10 <agmlego> No problem. Try to remember everything we talked about this time, OK?
Sep 13 17:24:35 <raj_> Yeah Yeah ! Sure
Sep 13 17:31:36 <raj_> Do You have any suggestion for a specific hub ?
Sep 13 17:32:29 <Humpelstilzchen> just get one that includes a power adapter
Sep 13 17:43:41 <honestly> anyone here set up the linux-tools along with their kernel?
Sep 13 21:09:10 <zsnafu> hm
Sep 13 21:09:23 <zsnafu> quite
Sep 13 21:09:29 <zsnafu> *quiet
Sep 13 21:19:55 <LuaStoned> too quiet
Sep 13 21:19:55 <LuaStoned> too quiet
Sep 13 21:26:43 <zsnafu> hey do you happen to know how to get access to the keyboard on the bbb
Sep 13 21:26:44 <zsnafu> in c
Sep 13 21:26:51 <zsnafu> hm
Sep 13 21:26:52 <zsnafu> n/m
Sep 13 21:27:02 <zsnafu> is it just scanf
Sep 13 21:27:38 <zsnafu> pfft
Sep 13 21:27:55 <zsnafu> blonde moment
Sep 13 21:31:08 <veremit> scanf is one .. there should be a 'readkey' equivalent (can't remember which language or keyword!)
Sep 13 21:32:28 <zsnafu> getchar()?
Sep 13 21:33:00 <veremit> sounds about right
Sep 13 21:33:55 <zsnafu> ool
Sep 13 21:33:57 <zsnafu> *cool
Sep 13 21:34:06 <zsnafu> is there a way to put an interrupt on the keyboard?
Sep 13 21:34:12 <zsnafu> usb
Sep 13 21:35:11 <veremit> some languages have a 'keypressed()'
Sep 13 21:35:18 <zsnafu> im doing it in c
Sep 13 21:35:31 <zsnafu> :/
Sep 13 21:35:35 <veremit> oh interrupt .. probably ..
Sep 13 21:35:43 <veremit> you'll have to register a handler
Sep 13 21:36:11 <zsnafu> right
Sep 13 21:36:15 <zsnafu> cool i think i found an example
Sep 13 21:36:51 <veremit> :)
Sep 13 21:37:04 <veremit> I've done it with much simpler microcontrollers .. but never x86
Sep 13 21:37:12 <veremit> ./etc
Sep 13 21:37:18 <zsnafu> it's on the bbb
Sep 13 21:37:26 <veremit> x86/arm/etc :P
Sep 13 21:37:41 <veremit> actually .. was using an M3 .. but the arm handler is quite ocmplicated if youre setting it up by hand
Sep 13 21:37:50 <zsnafu> ;/
Sep 13 21:38:00 <veremit> under linux you'll be fine :)
Sep 13 21:38:04 <veremit> kernel handles it
Sep 13 21:38:14 <zsnafu> so..i was thinking of just hooking up a keyboard to the bbb..and transmitting it through uart
Sep 13 21:38:32 <zsnafu> was going to do it with an interrupt so i don't have a busy loop just looking
Sep 13 21:38:40 <zsnafu> know of a better way?
Sep 13 21:40:13 <veremit> sounds good enough to me
Sep 13 21:40:23 <veremit> what are you trying to achieve?
Sep 13 21:41:21 <zsnafu> that's it
Sep 13 21:41:27 <zsnafu> well
Sep 13 21:41:39 <zsnafu> keyboard -> tranfer over uart
Sep 13 21:41:43 <zsnafu> recieve by another bbb
Sep 13 21:41:44 <zsnafu> print
Sep 13 21:44:50 <zsnafu> ok
Sep 13 21:44:50 <zsnafu> so
Sep 13 21:44:54 <zsnafu> cross compiling
Sep 13 21:45:29 <zsnafu> im able to cross compile and remotely deploy
Sep 13 21:45:32 <zsnafu> but im unable to debug
Sep 13 21:46:07 <zsnafu> im using a remote debugger...it goes into debug...but then i have no options
Sep 13 21:46:08 <zsnafu> cant step
Sep 13 21:46:11 <zsnafu> continue etc
Sep 13 21:47:32 <veremit> no serial debug?
Sep 13 21:47:55 <zsnafu> no
Sep 13 21:48:21 <veremit> hmm its worth the few bucks/etc to have
Sep 13 21:49:47 <zsnafu> how would a serial debugger be different than just using gdb over ssh?
Sep 13 21:50:33 <veremit> well if ssh is ok ... :)
Sep 13 21:50:52 <veremit> assuming it doesn't hang/etc
Sep 13 21:51:02 <zsnafu> ah
Sep 13 21:51:09 <veremit> I've not done a lot of debugging, so can't really say, thouh
Sep 13 21:51:14 <zsnafu> but the whole point was to use a gui interface
Sep 13 21:51:17 <zsnafu> for gdb
Sep 13 21:51:24 <zsnafu> through eclipse
Sep 13 21:51:27 <veremit> yeah gdb is supposed to be good
Sep 13 21:52:08 <veremit> I've never made eclipse/gdb/jtag/etc work together .. seemed a lot of work
Sep 13 21:52:31 <veremit> but I could easily have been doing it wrong!
**** BEGIN LOGGING AT Sat Sep 13 22:07:00 2014
**** ENDING LOGGING AT Sun Sep 14 02:59:59 2014