Back
[05:18:02] <DO9XE> Hey there, I got a problem with my avr-gcc... I am only able to compile for a atxmega64a3, but not for a atxmega64a3u :p the problem is, that the io-header-file for the a3 doesn't contain anything for USB, but the one from the a3u does. when I try to compile for the a3u my gcc suggests me the a3. Does anyone know this problem?
[05:19:44] <RikusW> get a newer set of headers, or add relevant registers manually ?
[05:20:11] <DO9XE> my packet manager tells me i have the latest version :P
[05:20:27] <DO9XE> avr-gcc 4.9.2-1 [installed]
[12:40:14] <megal0maniac> Hi all!
[12:40:25] <N1njVacation> Hi mega!!
[12:40:29] <N1njVacation> Oops
[12:40:50] <N1njaneer> I WISH I was still on vacation :D
[12:41:05] * Lambda_Aurigae is on vacation
[12:41:12] <Lambda_Aurigae> short 2 day vacation, but, still.
[12:41:15] <megal0maniac> About to start with a project, simple light control. Pushbutton on an interrupt pin and output to a 2n2222 to an LED strip. What is the best way to debounce?
[12:41:26] <megal0maniac> To conform to good practice and whatnot
[12:41:30] <Lambda_Aurigae> megal0maniac, hardware or software?
[12:41:36] <megal0maniac> Software
[12:41:58] <megal0maniac> I want minimal component count. Could put a delay in my ISR but I feel I'll be shouted at :P
[12:41:58] <N1njaneer> If software, it's easy enough to just add a slight delay in the loops if the application is simple enough.
[12:42:01] <Lambda_Aurigae> all kinds of ways there.
[12:42:16] <N1njaneer> The solution is not incorrect if it gets the job done.
[12:42:16] <Lambda_Aurigae> http://www.stefangordon.com/simple-avr-button-debounce/
[12:42:31] <N1njaneer> As long as you understand why one size does not fit all. :)
[12:42:37] <megal0maniac> Fair
[12:42:56] <N1njaneer> But for really simple applications, the fastest and most reliable way is usually also the most eloquent.
[12:42:58] <megal0maniac> So I guess delay in the ISR is okay then. There's no reason not to for this specific application
[12:43:21] <N1njaneer> Nope!
[12:44:01] <megal0maniac> I got an LED backlit keyboard. But the etching is dark so the light always needs to be on to see the keys. To be cheap, the LED strip is just connected to the scroll lock LED, but I have software which doesn't want scroll lock to be on. So I'm making my own control
[12:44:03] <N1njaneer> If you had multiple things going, you could do something like set a variable in the ISR and then debounce from inside of a counter, etc. or from the mainline loop.
[12:44:22] <megal0maniac> Probably just toggle between on, off and maybe some pattern just for kicks
[12:44:39] <megal0maniac> But it's dead simple and only 2 IO
[12:44:46] <N1njaneer> A simple RC circuit on the pushbutton is also extremely easy. :)
[12:44:54] <megal0maniac> But it needs to be tiny
[12:45:05] <megal0maniac> So if I can do it in software, then I shall
[12:46:38] <Tom_itx> software is glue
[12:46:48] <megal0maniac> I love glue
[12:53:21] <LeoNerd> But you can't sniff software
[12:57:32] <Lambda_Aurigae> yes you can.
[12:57:35] <Lambda_Aurigae> with the right software.
[12:57:56] <Lambda_Aurigae> sniffing elmers is kinda lame though.
[12:58:01] <N1njaneer> Inhale deeply through the JTAG
[12:58:25] <Lambda_Aurigae> and if you overclock you can smell the bits burning!
[13:15:43] <N1njaneer> Mimosas at the shop today!
[13:36:45] <LeoNerd> Mmm, so I have a tiny13 here I don't really know what to do with. I received it with a bunch of other stuff. It seems a bit small for much of excitement
[13:37:44] <LeoNerd> No UART or USI, no ADC, only 1Ki flash,...
[13:43:42] <N1njaneer> I've used ATTINY13's for a bunch of stuff
[13:44:38] <N1njaneer> Most recently voltage-monitoring via ADC for a relay fail-over on power as well as flashing LED on the power switch when the fail-over is active :)
[15:28:07] <Jartza> hi there
[15:36:28] * N1njaneer waves
[15:43:49] <LeoNerd> N1njaneer: tiny13 doesn't have an ADC I didn't think
[15:47:37] <N1njaneer> It does. :)
[15:47:50] <N1njaneer> It had better, else my hardware somehow magically works quite well :)
[15:48:38] <N1njaneer> I'm not aware of any AVR's off the top of my head that do not include ADCs
[15:56:02] <LeoNerd> Ohh, hmmm
[15:56:20] <LeoNerd> Maybe I could do a little tester thing with it
[16:16:47] <Tom_itx> tiny10 has adc
[16:17:25] <Jartza> I think all avrs have
[16:17:36] <Tom_itx> no
[16:17:37] <Tom_itx> not all
[16:17:49] <Tom_itx> some have comparators with no adc
[16:26:06] <Jartza> ahh yeah
[16:26:24] <LeoNerd> IIRC the tiny2313 is very odd
[16:26:43] <LeoNerd> tiiiiny amount of memory, almost no peripherals, but still loads of IO pins. I can't offhand think what I'd use that for, either
[16:33:53] <Jartza> lately I've played with tiny88
[16:37:34] <Jartza> and looked at tiny828
[16:37:46] <Jartza> I don't know why some of those chips are called "tiny" :)
[16:38:11] <Jartza> "8KB of in-system programmable (ISP) Flash, 256-byte ISP EEPROM, 512-byte internal SRAM, 8-bit timer/counter and 16-bit timer/counter with PWM, 10-bit ADC,USART, TWI, 2x SPI, 32KHz ultra low power oscillator, +-2% accurate 8MHz internal oscillator and debugWIRE for on-chip-debug. The ATtiny828 MCU has 28 GPIO pins and ADC channels available on all pins."
[16:42:16] <LeoNerd> Hah.. wow, that one is crazy
[16:42:24] <LeoNerd> I thought the "tiny"841 is bad enough
[16:54:30] <Jartza> tiny88 has a load of features for it's price though
[16:54:36] <Jartza> even much cheaper than attiny85
[17:04:45] <hetii> Hi :) And merry christmas for you all :)
[17:05:15] <Jartza> merry christmas!
[17:07:09] <Lambda_Aurigae> merry kiss my ass and a hoppy nude beer.
[17:08:28] <Jartza> that too ;)
[17:08:44] <Jartza> https://scontent-b-fra.xx.fbcdn.net/hphotos-xpa1/v/t1.0-9/10858558_810210125686943_4258637232932803937_n.jpg?oh=7ed01e647bfca2e2c35167c379a58fa6&oe=550093A7
