**** BEGIN LOGGING AT Sat Jan 04 02:59:58 2014
Jan 04 03:07:32 <hiredman> I am trying to control a tv via ir signals from a beaglebone, I am using a little 555 timer circuit to modulate the signal to ~38khz, but nothing I do has any effect on the tv
Jan 04 03:08:20 <hiredman> does anyone know of good write up or how to for this kind of project? or maybe a list of common pitfalls?
Jan 04 03:08:28 <prpplague> hiredman: time to get an oscope/la and check your timings
Jan 04 03:08:51 <ds2> u sure the LED is driven hard enough?
Jan 04 03:10:10 <hiredman> prpplague: I have, and it seems good, I am not entirely sure what the tolerance might be around this kind of thing, but it is close enough to trip a 38khz ir reciever I have
Jan 04 03:10:50 <hiredman> ds2: that is a good question, when I look at it using a digital camera the led seems as birght as the one in the remote
Jan 04 03:11:22 <hiredman> and I have it setup about half a foot from the tv's reciever
Jan 04 03:29:37 <SpeedEvil> hiredman:  Do you have a scope?
Jan 04 03:29:56 <SpeedEvil> Well - first - obvious things.
Jan 04 03:30:10 <SpeedEvil> Try varying it from 30-50khz slowly, and see if you get a response.
Jan 04 03:30:26 <SpeedEvil> Make sure you haven't got markl/space inverted
Jan 04 03:31:24 <SpeedEvil> It can be useful to take your 555 circuit, connect it to the LED of the existing remote through a filter - and see if it works
Jan 04 03:38:33 <hiredman> tricky, I don't have a way to easily vary my 555 circuit to get different frequencies
Jan 04 03:41:24 <ds2> why not?
Jan 04 03:41:32 <ds2> put a pot in series with the resistor
Jan 04 03:41:36 <ds2> or change out the timing cap
Jan 04 03:41:42 <ds2> or just ditch the 555 all together
Jan 04 03:41:45 <ds2> and use the PWM hw
Jan 04 03:41:58 <zmatt> you're aware that the UART on am335x can generate consumer IR signals directly, including the 38 kHz modulation?
Jan 04 03:42:12 <ds2> that'd would be too easy :D
Jan 04 03:42:46 <zmatt> (section 19.3.8.3 of the TRM)
Jan 04 03:43:05 <ds2> zmatt: got patches handy? ;)
Jan 04 03:43:42 <zmatt> yes, unload the relevant driver, mmap /dev/mem, and program the thing yourself :P
Jan 04 03:44:06 <ds2> *twap*
Jan 04 03:45:23 <zmatt> the uart is fun to configure!  thanks to the bizarre constraints and stuff like certain registers only being visible when some bits elsewhere are set, it's almost like a puzzle adventure game
Jan 04 03:46:02 <mrpackethead> zmatt: hope you dont' need to use the HDMI or the eMMC whwen you want to use the PRU
Jan 04 03:46:11 <zmatt> mrpackethead: ?
Jan 04 03:46:19 <mrpackethead> which would be anothe way of doing it!
Jan 04 03:46:42 <mrpackethead> use the PRU to generate IR
Jan 04 03:47:33 <zmatt> the PRU is nice, but I still wouldn't be in any hurry to implement stuff in software when there's a hardware peripheral available with precisely the functionality you need
Jan 04 03:50:09 <ds2> it is no worse then any other indirectly addressed setup
Jan 04 03:50:19 <ds2> PHYs, Soundblaster cards, etc are all like that
Jan 04 03:51:03 <zmatt> ds2: well it's pretty awful compared to pretty much every other peripheral on TI SoCs
Jan 04 03:52:17 <zmatt> even for themselves... (I noticed the DM814x ROM makes a small mistake in UART initialiation)
Jan 04 03:52:28 <zmatt> *initialization
Jan 04 03:53:09 <hiredman> zmatt: no kidding
Jan 04 03:53:39 <hiredman> ds2: I don't have a pot laying around unfortunately
Jan 04 03:54:32 <ds2> zmatt: I strongly disagree
Jan 04 03:54:49 <zmatt> ds2: well, I suppose there
Jan 04 03:54:51 <hiredman> zmatt: if I can't get this working this, I doubt going down the uart rabbit hole is going to be productive for me
Jan 04 03:55:00 <mrpackethead> ok, i owe the world a favor.
Jan 04 03:55:01 <zmatt> 's all kinds of awfulness to choose from
Jan 04 03:55:12 <mrpackethead> i now need to equalise teh karma
Jan 04 03:55:20 <mrpackethead> anyone got a problem.
Jan 04 03:55:42 <zmatt> hiredman: I don't know, fiddling with an external 555 timer sounds a lot hairier to me
Jan 04 03:56:51 <mrpackethead> that is a hard way of doign thigns! there IR encoding IC's that do all the hard work for you.
Jan 04 03:57:41 <hiredman> yep, I seem to have burnt mine out, which is why I have the 555 timer :)
Jan 04 03:59:36 <zmatt> sigh... or, you let one of the am335x's many UARTs with built-in IR encoder and modulator do all the hard work for you :P
Jan 04 04:00:50 <hiredman> zmatt: what is TRM? I assumed it was the beaglebone reference manual, but I don't see a section 19.3.8.3
Jan 04 04:01:08 <zmatt> technical reference manual
Jan 04 04:01:16 <hiredman> ah
Jan 04 04:01:33 <zmatt> the 4728-page slab of dead tree that describes the processor that's on the beaglebone
Jan 04 04:02:56 <zmatt> (of course its light weight is in part because TI omits documentation they feel isn't appropriate for the target audience)
Jan 04 04:03:35 <zmatt> http://www.ti.com/lit/ug/spruh73j/spruh73j.pdf
Jan 04 04:05:26 <hiredman> oh god my eyes just glazed
Jan 04 04:08:38 <hiredman> I guess I could look at the pwm stuff, but I have been trying to avoid getting in to the whole device tree whateverness which it seems like you need to for pwm and I not convinced the modulation is the problem
Jan 04 04:09:44 <zmatt> yea I dunno what exactly you need to do under linux to grab devices for yourself... so far I've only done baremetal programming so I haven't had that particular problem yet
Jan 04 04:16:04 <zmatt> PWM module is more for motor control or stuff like that... it would be overkill for generating a carrier, you could grab a timer output for that.  either way I don't see how it's going to be any help for generating an IR signal
Jan 04 04:16:49 <zmatt> since you'd need to manually create the bit timing then, which is painful
Jan 04 04:30:39 <zmatt> hiredman: how are you doing the bit timing right now anyway?  I hope not manually though GPIO ?
Jan 04 04:37:54 <hiredman> zmatt: not sure what you mean
Jan 04 04:38:26 <hiredman> actually I've made some progress, I think the ir codes I have are wrong or I am not intepreting them correctly
Jan 04 04:38:33 <zmatt> you're trying to send an IR code of some sort right?
Jan 04 04:38:44 <hiredman> I am able to turn the tv on and off now
Jan 04 04:38:50 <zmatt> woot
Jan 04 04:38:59 <hiredman> so home free I guess
Jan 04 04:39:16 <hiredman> just hours and hours of trying to find the correct bit sequences to go :)
Jan 04 04:43:21 <zmatt> the uart can also demodulate and decode IR, you could have checked what the actual remote sends ;-)
Jan 04 04:46:36 <zmatt> (sorry, will stop now)
Jan 04 04:50:14 <hiredman> sure, but what I really want are the discrete input switching codes, which I don't have a remote that sends
Jan 04 04:54:59 <zmatt> ah
Jan 04 05:40:44 <jesselang> Howdy. How can I go about getting Debian on a BBB?
Jan 04 07:52:09 <yogi> anybody got Fedora 20 running on a new beagle black?
Jan 04 15:44:30 <samgtr> I'm interested in contributing to this org
Jan 04 15:44:40 <samgtr> where do i get started from ?
Jan 04 15:48:24 <vmayoral> hi samgtr
Jan 04 15:49:01 <vmayoral> how about taking a look at some projects @ http://beagleboard.org/?
Jan 04 15:49:23 <vmayoral> you can decide on what you want to contribute and then maybe we can give you better pointers
Jan 04 15:49:33 <samgtr> yeah sure thanks
Jan 04 15:52:28 <p0ff> How would one start if interested in contributing to BeagleBoard specifically on the node.js and javascript platforms?
Jan 04 15:52:37 <p0ff> start contributing**
Jan 04 17:32:17 <Razor_Kickass> guys after updating my beaglebone black via internet on lan.... it added 2 more users and also my root password was changed from the default null password... how to i remove the 2 new users and change my current password from "pass" to ""
Jan 04 17:33:13 <Russ_> http://linux.die.net/man/1/passwd
Jan 04 18:16:15 <Razor_Kickass> hi russ thats not helping...:( i tried to lock and unlock its still asking for password
Jan 04 18:23:50 <anujdeshpande> l
Jan 04 23:38:03 <grantsmith> hi, I'm trying to enable spidev0 on an A5A, following the instructions here: http://elinux.org/BeagleBone_Black_Enable_SPIDEV. However, it creates /dev/spidev1.0, not dev/spidev0.0. Any clues as to why ?
Jan 05 00:00:52 <veremit> grantsmith: created the right dts file? no issues with hdmi on BBB?
Jan 05 00:01:48 <veremit> oh my , those instructions look confusing
Jan 05 00:02:19 <grantsmith> veremit,  it is my understanding that HDMI is only a problem with spi1
Jan 05 00:02:37 <grantsmith> so I'm trying to enable spi0
Jan 05 00:02:37 <veremit> yup
Jan 05 00:02:55 <veremit> I can see a terrible mix of SPI0/1-00/1-00/1 in names .. lol
Jan 05 00:04:57 <veremit> ok so you've got the firmware file in /lib/firmware, added the thingy to capemgr .. changed your kernel command-line and rebooted?
Jan 05 00:06:48 <grantsmith> yes
Jan 05 00:07:10 <grantsmith> and now i have  /dev/spidev1.0
Jan 05 00:07:54 <veremit> and no spidev0
Jan 05 00:08:00 <grantsmith> exactly
Jan 05 00:08:06 <veremit> checked dmesg?
Jan 05 00:09:07 <grantsmith> [   51.095254] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2 <--- lots of those
Jan 05 00:12:02 <veremit> if you test it .. does the sp1 link to the spi0 pins, by any chance?
Jan 05 00:15:51 <veremit> it not, spi1 applies to the hdmi and sp0 hasn't been initialised
Jan 05 00:17:29 <grantsmith> wow i have no clue
Jan 05 00:17:38 <grantsmith> group: spi0_pins_s0
Jan 05 00:17:38 <grantsmith> pin 84 (44e10950)
Jan 05 00:17:40 <grantsmith> ... etc
Jan 05 00:18:07 <grantsmith> gah... this is all very new to me
Jan 05 00:23:45 <veremit> embedded devices commonly load configurations for their peripherals from "device-tree" files .. which is the dts/dto file you created
Jan 05 00:23:59 <veremit> this is then loaded by the beagle cape-manager at boot-time
Jan 05 00:26:07 <musufu> actually its loaded by bootloader (uboot) and given to the kernel,
Jan 05 00:26:26 <veremit> true .. technical detail :)
Jan 05 00:26:28 <musufu> cape-manager is using it with kernel's api for searching capes only
Jan 05 00:26:45 <musufu> other drivers are also searching in it for their devices
Jan 05 00:32:15 <veremit> the device-tree configures the processor .. and tells drivers which peripherals are active .. so that they load and configure correctly
Jan 05 00:32:23 <veremit> or thats the idea.
Jan 05 00:32:57 <musufu> :] yep, think so
Jan 05 00:43:00 <veremit> so .. if spidev0 is not appearing .. either something is preventing it .. or its not bein detected/enabled/activated/configured by the driver
Jan 05 00:46:06 <musufu> yes, your device-tree might be causing it. did you compile the kernel on your own? it should be fine with original kernel/device-trees in pre-installed angstrom
Jan 05 00:46:16 <grantsmith> im beginning to wonder if spidev1.0 is spi0 and spidev2.0 is spi1
Jan 05 00:46:33 <musufu> (assuming it's beaglebone)
Jan 05 00:46:38 <grantsmith> this is the original angstrom kernel
Jan 05 00:47:02 <veremit> what does spidevtest tell you?
Jan 05 01:08:53 <veremit> bbiaf
**** ENDING LOGGING AT Sun Jan 05 02:59:58 2014