Back
[05:11:00] <thetruthisoutthe> avrdude: current erase-rewrite cycle count is 83886336 (if being tracked)
[05:11:02] <thetruthisoutthe> :)
[05:11:19] <thetruthisoutthe> new avrdude's counter code is buggy
[05:15:30] <RikusW> or eeprom values wasn't set
[05:15:43] <thetruthisoutthe> well i have used it
[05:15:51] <thetruthisoutthe> but the counting fails too
[05:16:16] <thetruthisoutthe> avrdude fails to read, increment, and rewrite the counter
[05:16:26] <thetruthisoutthe> 1 byte overflow maybe?
[05:16:36] <thetruthisoutthe> i have programmed the device many hundred times
[05:18:24] <thetruthisoutthe> but it didn't overflow at 255, the counter value was even 350, then got more, and then got less, it was unconsistent
[05:40:37] <RikusW> could be buggy eeprom wrinting in avrdude
[05:41:07] <RikusW> try editing avrdude.conf to use byte instead of page eeprom writing
[05:47:01] <thetruthisoutthe> good thing i don't really have to know the programming cycle count
[05:47:17] <thetruthisoutthe> was just thinking it would be nice to know
[08:23:02] <thetruthisoutthe> when debugmode breaks things :(
[08:24:30] <thetruthisoutthe> i can't place #if #elseif in interrupt routine?
[08:28:47] <jadew`> sure you can, those are preprocessors, they get compiled before the actual compiling starts
[08:31:17] <thetruthisoutthe> i'm getting weird errors
[08:31:27] <twnqx> then you did something wrong.
[08:31:55] <twnqx> (aren't we all heartless people)
[08:31:56] <thetruthisoutthe> like when i accidentally wrote #if #elseif #endif with elseif condition left blank
[08:32:40] <jadew`> and what's the problem?
[08:32:44] <jadew`> that sounds about right
[08:32:54] <jadew`> #elseif expects a condition
[08:33:22] <thetruthisoutthe> chaged #if debugmode == 0
[08:33:27] <thetruthisoutthe> #else
[08:33:30] <thetruthisoutthe> #endif
[08:33:35] <thetruthisoutthe> and it worked i think
[08:33:54] <thetruthisoutthe> problem? i have no idea
[08:34:27] <thetruthisoutthe> my interrupts are getting insane when i set debugmode 2 now
[08:34:51] <thetruthisoutthe> nested ATOMIC_BLOCK collision ?
[08:35:16] <thetruthisoutthe> used ATOMIC_RESTORESTATE
[08:36:23] <jacekowski> thetruthisoutthe: use #ifdef
[08:37:07] <thetruthisoutthe> how is that better than using #define debugmode 0 ?
[08:37:21] <thetruthisoutthe> (and i have 3 debug modes now)
[08:39:43] <jacekowski> ahm ok
[08:51:04] <thetruthisoutthe> can a structure like this cause problems? ATOMIC_BLOCK(ATOMIC_RESTORESTATE) { ATOMIC_BLOCK(ATOMIC_RESTORESTATE) { } }
[09:37:08] <Casper> thetruthisoutthe: I beleive that it should be fine
[09:37:43] <thetruthisoutthe> i always find the hidden bugs ;/
[09:38:01] <thetruthisoutthe> something is not right
[09:38:37] <thetruthisoutthe> when i change a define and it breaks everything that does not sound all right
[09:40:08] <Casper> thetruthisoutthe: do you use -O3 ?
[09:40:15] <thetruthisoutthe> eerm
[09:40:33] <thetruthisoutthe> no, currently -os
[09:40:43] <Casper> ok
[09:40:55] <thetruthisoutthe> CFLAGS =-g -std=c99 -Os -Wall -mcall-prologues -mmcu=$(MCU)
[09:40:58] <Casper> -O3 is known to cause issues
[09:41:06] <Casper> it tend to over optimise
[09:42:01] <thetruthisoutthe> that like to make some large code
[09:42:10] <Casper> "oh it do push r3; push r3... pop r3; pop r3;.... that is twice the job, let's do push r3.... pop r3 !"
[09:42:43] <thetruthisoutthe> it can cause problems when it alters the sequency
[09:42:46] <thetruthisoutthe> e
[09:42:59] <Casper> I prefer -O2 than -Os
[09:43:17] <thetruthisoutthe> but if i turn off debug mode then it works
[09:43:52] <thetruthisoutthe> i have seen this before, turning ON debug mode makes code work, but not turning OFF
[09:44:17] <Casper> debug code add code and delays
[09:44:25] <thetruthisoutthe> hm yes
[09:44:27] <Casper> sometime it "fix" some timing issues
[09:44:38] <thetruthisoutthe> but i think this should not matter
[09:44:53] <thetruthisoutthe> though i know 5us skew can make my code bad
[09:44:59] <Casper> but when you have weird bug
[09:45:05] <Casper> check for stack overflow
[09:45:34] <thetruthisoutthe> static void set_rgb_led( uint8_t value )
[09:45:34] <thetruthisoutthe> {
[09:45:34] <thetruthisoutthe> ATOMIC_BLOCK(ATOMIC_RESTORESTATE) {
[09:45:34] <thetruthisoutthe> PORTD = ( PORTD & ~((1<<red_led)|(1<<green_led)|(1<<blue_led)) ) |
[09:45:34] <thetruthisoutthe> (( (value&1) << red_led ) | ( ((value>>1) & 1) << green_led ) | ( ((value>>2)&1) << blue_led ));
[09:45:36] <thetruthisoutthe> }//
[09:45:38] <thetruthisoutthe> }
[09:45:52] <thetruthisoutthe> i have inserted many of this in my code in debug modes
[09:46:13] <thetruthisoutthe> and core is ticking at 8MHz
[09:46:41] <thetruthisoutthe> i don't see how will this cause >5us delays
[09:47:34] <thetruthisoutthe> or mess up interrupts
[09:50:07] <Casper> ther delay may be normal
[09:50:42] <Casper> 5us@8Mhz = 40 cycles
[09:51:15] <thetruthisoutthe> yeah
[09:52:17] <Casper> ((value>>2)&1) << blue_led
[09:52:22] <Casper> that may be expensive too
[09:52:36] <thetruthisoutthe> eerm, should i use atomic block too when reading eeprom?
[09:52:43] <Casper> what is the value of blue_led?
[09:53:07] <thetruthisoutthe> PORTD0
[09:53:08] <Casper> because that cause that many bitshift instructions
[09:53:22] <thetruthisoutthe> zero now
[09:53:30] <Casper> ok, so zero shifting
[09:53:37] <Casper> btw
[09:53:58] <Casper> 1<<blue_led and x<<blue_led do not produce the same code at all
[09:54:18] <thetruthisoutthe> well i use that to translate bitt positions
[09:54:33] <Casper> and atomic)_BLOCK is only needed if you need to make sure that your interrupts won't mess up things
[09:54:58] <thetruthisoutthe> i was just feeling comfortable with BGR bits in order
[09:55:14] <Casper> ex: when you read a 16 bits value, when your interrupt update some value that your code use
[09:55:24] <Casper> or when you have sensitive timing
[09:55:35] <thetruthisoutthe> i used it because interrupts mangle with portd too
[09:55:47] <thetruthisoutthe> and led is connected to that port too
[09:55:51] <Casper> ok
[09:56:10] <Casper> just wanted to be sure that you knew what it was for :D
[09:56:15] <thetruthisoutthe> yeah
[09:56:54] <thetruthisoutthe> it does something like sregtmp=sreg; cli; codeblock; sreg=sregtmp;
[10:41:23] <ambro718> why would reading an input pin always return zero even if the pin is high?
[10:42:07] <ambro718> the Pin Change Interrupt works for this pin, but just fetching ((PORTA & (1 << PA0)) does not
[10:43:01] <tzanger> do you want PINA not PORTA
[10:43:17] <tzanger> PINx = voltage on pin, PORTx = latched output value for pin
[10:43:41] <ambro718> oh lol, yes, stupid me
[13:07:54] <kobsu> we are splitting off 10pcs old Aery32 rev0 boards for postages only (5e)... join #aery32 and pm me if interested in
[13:31:12] <skroon> hi all
[13:58:25] <skroon> I sometimes see libraries talking about software uart vs hardware uart
[13:58:59] <skroon> but the software versions also use the UART register etc, so I was wondering what is the difference between hard vs software uart?
[13:59:34] <OndraSter__> they lie?
[13:59:45] <skroon> is it perhaps that the hardware versions, use interrupt driven instead of polling the register?
[13:59:46] <Tom_itx> software uart would be 2 io pins
[13:59:48] <skroon> OndraSter__: ;-)
[13:59:52] <asteve> 2 io piins
[13:59:54] <Tom_itx> with software driving them
[13:59:54] <asteve> more like
[14:00:00] <asteve> (pin drop)
[14:00:02] <asteve> *zing*
[14:00:05] <Tom_itx> zong
[14:00:07] <skroon> ahh, riht
[14:00:09] <skroon> zang
[14:00:16] <Tom_itx> zoom zoom
[14:00:56] <asteve> now the mazda's are about the skyactiv
[14:00:57] <skroon> so what's the difference then between two pin uart, and ... 4pin? uart
[14:01:04] <Tom_itx> and not as efficient as hardware uart
[14:01:12] <Tom_itx> 2 pins
[14:01:17] <asteve> *zing*
[14:01:19] <Tom_itx> handshaking
[14:01:28] <Tom_itx> dtr dsr
[14:02:35] <skroon> is that like rs232 then perhaps?
[14:07:32] <Tom_itx> that's kinda what uart is about
[14:07:46] <Tom_itx> except for the voltage levels
[15:02:50] <madcat1990> Guys, yesterday I played around with an ATMega328P, and everything worked seamlessly and easily. Thank you for all your hard work!
[15:04:53] <thetruthisoutthe> tzanger<= i like PINA :)
[15:05:28] <thetruthisoutthe> [172857] <tzanger> do you want PINA not PORTA < i prefer PINA ^^
[15:06:03] <inkjetunit> PORTB isn't that bad either.
[15:06:39] <thetruthisoutthe> eerm, who knows how windows handles ps2 keyboard ?
[15:06:59] <thetruthisoutthe> something working on linux why won't work on windows ?
[15:07:27] <thetruthisoutthe> ( a keyboard )
[15:09:53] <RikusW> megal0maniac_afk:
http://www.netram.co.za/Pages/ordering-info.html
[15:10:27] <specing> thetruthisoutthe: PS/2 is not hotplug, you have to reboot
[15:10:31] <thetruthisoutthe> :(
[15:10:43] <thetruthisoutthe> but i plugged another keyboard in it and that worked
[15:11:35] <thetruthisoutthe> windows didn't reset the keyboard, and it had set up another id ?
[15:11:51] <thetruthisoutthe> haven't tried rebooting yet
[15:12:18] <RikusW> in particular ps2 mice
[15:12:30] <thetruthisoutthe> so i can only use a similar keyboard on windows without a reboot ?
[15:13:11] <RikusW> specing: I see overseas mail is ZAR6.60 so still have that m32u2 ?
[15:13:29] <tzanger> PS/2 is not hotplug. *sometimes* it works, most times it doesn't, and once in a while it'll blow the port or the keyboard.
[15:17:28] <theBear> most time it works, but once in a while it blows up
[15:18:10] <RikusW> specing: I still have a U2S blank pcb
[15:19:15] <specing> RikusW: I have exams ;)
[15:21:07] <specing> 0.55 Euro is quite cheap, what gives?
[15:23:13] <RikusW> its and envelope max 5mm thick
[15:23:51] <RikusW> specing: thats only shipping
[15:38:11] <Badaboom> Hello
[15:38:29] <Badaboom> I need help with a MAX7219 to AVR'
[15:41:58] <jadew`> spi
[15:42:40] <Badaboom> jadew: is there a test you can do with it to see if its working or not?
[15:43:08] <jadew`> to test the SPI interface?
[15:43:11] <Badaboom> I have it connected and just cant seem to get past 88888888
[15:43:12] <jadew`> do you have a logic analyzer?
[15:43:16] <Badaboom> no the display
[15:43:26] <Badaboom> no
[15:43:30] <jadew`> ah
[15:44:29] <jadew`> if it's 8888 and it's wired properly, it's most likely what you're sending over SPI
[15:44:35] <Badaboom> Here it is in a nutshell, i have a attiny2313 hooked to the max7219 and an out of 8 dig
[15:45:01] <Badaboom> so my code is screwed up?
[15:45:20] <jadew`> probably, or the SPI data lines are not wired properly
[15:45:40] <jadew`> or, you haven't configured the SPI peripheral correctly, in the avr
[15:45:54] <Badaboom> for example when it writes to the chip i get all kinds of stuff lately
[15:46:12] <Badaboom> like now it reads p88
[15:51:09] <jadew`> Badaboom, what mode are you using the SPI in?
[15:51:25] <Badaboom> one sec
[15:51:27] <jadew`> by the looks of it, the chip you're using expects to use mode 0
[15:51:47] <Badaboom> SPI_PORT |= (1 << SPI_CLK_PIN) | (1 << SPI_MOSI_PIN);
[15:52:10] <jadew`> that's not the mode
[15:52:53] <jadew`> the mode is set by writting to the SPCR register
[15:53:45] <Badaboom> is there a good tutorial on spi for the attiny2313?
[15:54:02] <jadew`> ah, wait, this is attiny
[15:54:03] <jadew`> forgot
[15:54:05] <Badaboom> i think i need to start there
[15:54:39] <jadew`> yeah, I don't know, do a google search, if you find nothing, I'll help you out and write a tutorial too
[15:55:19] <Badaboom> ty,, i spent all night with this, had to make my own breakout board for the max7219 as it came in an so package
[15:55:48] <jadew`> oh, I think there's a dip one too
[15:55:58] <jadew`> at least that's how it seemed like from the datasheet
[15:56:09] <Badaboom> there is, but this is what i got as samples form maxim so
[15:56:13] <jadew`> yep, there's also a dip one
[15:56:17] <Badaboom> yep
[15:56:18] <jadew`> got it
[15:56:28] <Badaboom> its ok,, ive got that part:)
[15:56:43] <Badaboom> just need to make them talk and im in business
[15:57:30] <jadew`> well, I still have 20 more minutes of work, so if you can't find anything by then I'll look into it
[15:58:08] <Badaboom> ty so much
[16:14:56] <jadew`> Badaboom, have you checked AVR319?
[16:15:08] <Badaboom> no
[16:15:25] <jadew`> take a look, it also has sample code
[16:15:31] <Badaboom> kk
[16:15:46] <sabesto> dont think the 2313 has hw spi
[16:16:01] <jadew`> sabesto, it has some hybrid thingie
[16:16:13] <jadew`> software SPI with some hw help
[16:16:16] <sabesto> maybe the usart can be used as spi?
[16:16:25] <sabesto> yeah, the usi
[16:16:36] <jadew`> the hw help comes in the form of automatically shifting the output and toggling the clock, when you tell it to
[16:19:08] <jadew`> doesn't look very straigh forward, that's for sure
[16:19:15] <Badaboom> not at all:)
[16:19:54] <Badaboom> one of the things i read just now is DO NOT use the miso mosi lines
[16:20:09] <Badaboom> some of the stuff i read last night said to do so
[16:20:18] <jadew`> why not use them?
[16:20:24] <jadew`> that's what they're for
[16:20:41] <Badaboom> hmm,, the isp wont be effected?
[16:20:54] <jadew`> shouldn't be
[16:21:11] <Badaboom> I had problems when programming it too
[16:21:16] <jadew`> sometimes it is tho, but most of the times it's not
[16:21:54] <jadew`> if you make a project that doesn't use SPI and you can spare those 3 lines, sure, leave them open
[16:22:06] <thetruthisoutthe> do you often use pgmspace ?
http://www.nongnu.org/avr-libc/user-manual/pgmspace.html
[16:22:15] <twnqx> i do
[16:22:23] <jadew`> me too
[16:22:27] <thetruthisoutthe> that frees up the somewhat limited amount of ram
[16:22:52] <twnqx> but remember it's read only :P
[16:23:02] <twnqx> good for strings and config tables, not much else
[16:23:03] <thetruthisoutthe> yea, for text strings it is definitely ok
[16:23:20] <thetruthisoutthe> and led flashing patterns?
[16:23:30] <sabesto> i've burned myself 2 times on chips with higher pin count where ISP was not the mosi/miso pins
[16:23:48] <twnqx> i'd consider that a config table
[16:23:49] <sabesto> like the mega128
[16:24:10] <twnqx> but i also throw megabytes of flash memory via SPI on my cute avrs
[16:24:26] <thetruthisoutthe> :)
[16:24:49] <thetruthisoutthe> micro SD-card?
[16:25:08] <twnqx> not in this case, just a so8 chip
[16:25:18] <Badaboom> I actually made a microsd breakout :)
[16:25:42] <Badaboom> used an old cellphone sdcard reader
[16:25:46] <sabesto> microsd+ribboncable
[16:25:59] <sabesto> + solder :P
[16:26:02] <Badaboom> lol
[16:26:34] <twnqx> like this?
http://imageshack.us/a/img96/9854/pirateh.jpg
[16:26:37] <Badaboom> well hell, i had to breakout that so package the 7219 came in last night
[16:26:39] <twnqx> (to the left)
[16:27:31] <Badaboom> what is that?
[16:27:39] <twnqx> because ribbon cables for 1.27mm are... prohibitively expensive :X
[16:27:41] <Tabaliah> Found Max7219C - now I gotta find a display or two.
[16:28:22] <twnqx> Badaboom: my breakout solution for standard so8 chips :P
[16:28:23] <Badaboom> Tabaliah: they also sent me 6915's
[16:28:37] <Badaboom> twnqx: ahh i see
[16:28:58] <twnqx> buspirate compatible pinout so i just can plug the chip in there
[16:29:12] <Badaboom> thats pretty clever
[16:29:35] <twnqx> i am not the only one with the idea
[16:29:44] <Badaboom> mine involved etching and soldering pins:(
[16:30:00] <twnqx> i leave the etching to companies that know what they do :P
[16:30:01] <Badaboom> but hey,, its in the breadboard:)
[16:30:12] <Badaboom> lol
[16:31:21] <twnqx> and soldering i don't mind, just finished the third (and last) of my dual port CAN boards
[16:31:33] <Badaboom> So when i was reading this driver can also be used to drive 64 leds,, makes sense
[16:31:36] <twnqx> next time i won't order three sets of components for fear of ruining one...
[16:31:54] <Badaboom> lol
[16:32:29] <twnqx> i never had 100% success with TSSOP before!
[16:32:43] <Badaboom> yeah,, those are tricky
[16:32:59] <twnqx> no... not really
[16:33:06] <Badaboom> lots of flux?
[16:33:14] <twnqx> none needed
[16:33:17] <Badaboom> hmm
[16:33:23] <twnqx> 0.35mm solder wire
[16:33:26] <Badaboom> ahh
[16:33:27] <twnqx> 1.6mm tip
[16:33:32] <Badaboom> u use a scope?
[16:33:33] <thetruthisoutthe> http://imageshack.us/a/img96/9854/pirateh.jpg <<< main.c:1328:50: warning: label 'http' defined but not used
[16:33:36] <thetruthisoutthe> :)
[16:33:36] <twnqx> nah
[16:33:51] <thetruthisoutthe> you can put a link in your C file with only a warning
[16:34:06] <twnqx> lol
[16:34:20] <l9> anyone that has an idea why my ubuntu and eclipse dosent work with avdude? I get an file not found error... :(
[16:34:36] <twnqx> __attribute__ ((unused) before that should silence the warning!
[16:35:03] <twnqx> )) of course
[16:35:29] <twnqx> l9: because it's avrdude!
[16:36:09] <l9> yeah i know forgot a R
[16:36:16] <l9> avrdude: ser_open(): can't open device "/dev/ttyUSB0": Permission denied
[16:36:22] <twnqx> did you install it? does it work on the cli?
[16:36:33] <twnqx> well yes
[16:36:53] <twnqx> do ls -l /dev/ttyUSB0, see what group it belongs to
[16:37:12] <twnqx> add add your user to that group
[16:37:43] <Badaboom> jadew: this is where i found that bit on NOT using the miso mosi lines
http://playground.arduino.cc/Code/USI-SPI
[16:38:28] <l9> hmm that i havent done... :) thanks i have been googling this for hours now :/
[16:39:38] * twnqx goes back to procrastinating while being scared of building custom tranformers
[16:42:33] <l9> twnqx thanks a million that solved my problem :D 4 hours well spendt on the computer :P
[16:42:47] <twnqx> you're welcome
[16:45:59] <jadew`> Badaboom, again, it's highly dependent on what you're doing there
[16:46:09] <jadew`> in your case, I'm pretty sure you're fine using it for ISP
[16:53:02] <Badaboom> rgr
[16:53:13] <Badaboom> sorry,, jumped in the shower
[16:56:30] <Badaboom> one example i was following they used a display line connected to what i believe to be iset since there was no actuall schematic and it made sense due to the ability to change the intensity
[16:56:50] <Badaboom> or brightness
[17:06:32] <Badaboom> jadew: are u still there?
[17:12:16] <jadew> yeah
[17:13:28] <Badaboom> so im following that setup as far as the spi, does that look ok to use?
[17:13:46] <jadew> which one?
[17:14:19] <Badaboom> http://playground.arduino.cc/Code/USI-SPI
[17:14:56] <jadew> yeah, looks ok
[17:15:34] <Badaboom> k
[17:28:42] <Badaboom> where the h--- is the latch supposed to go?
[17:28:52] <Badaboom> on the max7219 that is?
[18:04:06] <jadew> Badaboom, I'm having a hard time getting SPI to work with USI, it worked the first time, now, with basically the same code doesn't want to work anymore
[18:04:18] <Badaboom> hmm
[18:04:41] <Badaboom> I really appreciate you trying, im having a tough time obviously
[18:04:59] <jadew> I'll give it 10 more minutes, if I can't get it to work, I'll have to leave it for tomorrow
[18:05:16] <Badaboom> np
[18:05:49] <Badaboom> is there a more prefered chip to use for this?
[18:06:23] <jadew> a mega one
[18:06:29] <Badaboom> rgr
[18:06:30] <jadew> but I'm sure it can be done with this one too
[18:06:57] <Badaboom> yeah,, not to much in the way of sample codes,, i looked already,,lol
[18:07:31] <jadew> I'll dig on it, I always wanted to get stuff working with USI
[18:07:47] <Badaboom> kk
[18:08:04] <Badaboom> It looks like a very efficient way to use the avr
[18:20:53] <jadew> hah, got it working
[18:21:06] <jadew> had to read the datasheet carefully
[18:22:28] <Badaboom> oh?
[18:22:41] <jadew> do you have the datasheet open?
[18:22:49] <Badaboom> ,, gmme 2 sec
[18:23:10] <Badaboom> rgr, open
[18:23:22] <jadew> pin configuration
[18:23:49] <jadew> and tell me what lines are you using? SCK / MISO / MOSI and pin numbers
[18:24:40] <Badaboom> 19 sck 18 miso 17 mosi
[18:24:59] <jadew> alright... that's wrong
[18:25:03] <Badaboom> ahhh
[18:25:17] <jadew> I had the same "ahh" lol
[18:25:21] <Badaboom> lol
[18:25:31] <jadew> the USI uses DO as MOSI
[18:25:35] <jadew> and DI as MISO
[18:26:04] <Badaboom> so reversed?
[18:26:07] <jadew> yep
[18:26:09] <Badaboom> wtf
[18:26:10] <Badaboom> lol
[18:26:16] <jadew> damn stupid
[18:26:19] <Badaboom> yeah
[18:26:24] <Badaboom> no wonder
[18:26:28] <jadew> let me know if it works for you
[18:26:32] <Badaboom> rgr
[18:26:55] <jadew> I'll give you my code in a moment, for reference
[18:27:10] <jadew> well, you can use it
[18:27:22] <jadew> but it's not really polished
[18:27:34] <jadew> like I didn't add a way to set the frequency, but that shouldn't be hard
[18:29:15] <Badaboom> yeah,, mine sucks
[18:29:23] <Badaboom> its not doiny anything
[18:29:38] <jadew> how do you know that?
[18:29:50] <Badaboom> no display or anything now
[18:29:58] <Horologium> MOSI= master out slave in...DO= data out.
[18:30:10] <Horologium> MISO = master in slave out...DI = data in.
[18:30:19] <Badaboom> yep
[18:30:23] <Badaboom> sck same
[18:30:24] <jadew> Horologium, that's what you might think
[18:30:27] <jadew> but no
[18:30:36] <jadew> PB6 (MISO/DO/PCINT6)
[18:30:41] <jadew> PB5 (MOSI/DI/SDA/PCINT5)
[18:30:54] <jadew> the MISO / MOSI labels are probably there just for ISP
[18:31:00] <Horologium> probably.
[18:31:08] <jadew> but still pretty dumb
[18:31:11] <Horologium> just the USI on that chip, eh?
[18:31:17] <jadew> yep
[18:31:41] <jadew> Badaboom:
http://eenoob.com/download/usi/2313-usi-spi.zip
[18:31:49] <Badaboom> rgr
[18:32:11] <jadew> the code just sends decimal 10 over SPI then waits for a bit and does it again
[18:32:21] <jadew> you'll have to controll /CS by yourself
[18:33:13] <jadew> you know how /CS works, right?
[18:33:30] <Badaboom> yes
[18:33:37] <jadew> cool
[18:33:39] <jadew> let me know if it works
[18:33:43] <Badaboom> ty very much
[18:33:46] <Badaboom> rgr
[18:33:52] <jadew> np
[18:34:57] <jadew> I'll make a nicer one tomorrow, hopefully supporting all 4 modes + configurable frequency (again, that's pretty simple)
[18:35:09] <Badaboom> very cool
[18:38:37] <jadew> proof that it's working:
http://eenoob.com/download/usi/2313-usi-spi_1.png
[18:39:24] <Badaboom> yup,, its good,, now i have my night cut out
[18:39:42] <jadew> did you get any results?
[18:39:48] <Badaboom> yes
[18:39:55] <jadew> awesome
[18:41:25] <jadew> that arduino code was useful too, cuz it confirmed the way it works, not the most clear example tho
[18:41:59] <Badaboom> yeah,, but this is a breakthru for me:)
[18:42:22] <jadew> :)
[18:42:49] <jadew> I should go to bed, gonna have some blood work done in the morning
[18:42:51] * jadew shivers
[18:42:54] <Badaboom> lol
[18:42:58] <Badaboom> good luck and ty
[18:43:22] <jadew> thanks
[18:43:23] <jadew> np
[18:43:25] <jadew> night
[18:43:37] <Badaboom> take care\
[20:27:03] <ambro718> lol, my AVR runs even if the quartz is inserted into the wrong holes on the broadboard, so there is no electrical contact with the quartz
[20:27:42] <ambro718> I can insert the wires one row off on each leg of the quarts
[20:27:58] <Tom_itx> maybe it's running off the internal osc and you don't know it
[20:28:19] <ambro718> no, because it stops running when I remove the quartz, and it also runs at the right frequency
[20:33:21] <Casper> ambro718: that just show you how shitty breadboards are
[20:34:24] <ambro718> yeah :D
[20:39:28] <Tom_itx> if you put them in ajacent pins wouldn't they be on some other io pins?
[20:41:18] <ambro718> huh?
[20:45:27] <tzanger> induction? capacitive coupling maybe
[20:45:28] <Badaboom> So as i mentioned earlier i found out one of my problems in my circuit:(
[20:45:43] <tzanger> those breadboards have insane coupling
[20:46:02] <Badaboom> tzanger: I just went thru that
[20:46:33] <tzanger> I didn't see it in the scrollback
[20:47:02] <Badaboom> sorry,, i posted it in another ch
[20:47:06] <Badaboom> oops
[20:47:28] <Badaboom> I had a timing issue related to capacitance
[20:47:51] <Badaboom> breadboards arent really the way to go for highspeed:(
[21:55:28] <sabesto> OndraSter__: found out anything about the kodak thingie?
[21:56:16] <Tom_itx> what kodak thingy?
[21:56:55] <sabesto> kodak thermal printer of some sorts with no info
[21:57:10] <Tom_itx> oh
[21:58:50] <sabesto> sony it was:
http://www.ipernity.com/doc/26252/4316824/in/keyword/339593/self
