#avr | Logs for 2013-02-07

Back
[00:00:01] <TechIsCool> patch
[00:03:43] <theBear> oh, i wouldn't know about output options on there... i wonder if it's a message about running an old or 32bit program, perhaps you can test by running some generic command or something that doesan't expect feedback
[00:04:22] <TechIsCool> theBear I can also try it in amel studio and it say please verify device selection, interface settings, target power and connections to target device
[00:07:36] <theBear> yeah, that sounds like a generic "avrdude gave an error or response we don't recognise" message to me
[00:07:52] <TechIsCool> I know
[00:07:53] <theBear> does it tell you the cmdline it used to cause that
[00:08:55] <TechIsCool> http://pastebin.com/auQJ4Pbf
[00:08:58] <jadew> ah, it's about the emulator mode
[00:09:11] <jadew> it is illegal!
[00:09:22] <TechIsCool> http://pastebin.com/auQJ4Pbf
[00:09:37] <TechIsCool> jadew: thanks for stating the obvious
[00:11:53] <jadew> TechIsCool, is it saying anything else after that?
[00:12:04] <jadew> it appears to be a response from avrdragon
[00:12:53] <jadew> it should say something like Illegal emulator mode JTAG/Xmega
[00:13:11] <TechIsCool> jadew: http://pastebin.com/auQJ4Pbf
[00:13:21] <TechIsCool> line 76 is where it starts
[00:16:25] <theBear> i say 59/60 is the problem
[00:16:42] <theBear> ooh, caused by 56
[00:16:59] <TechIsCool> hmm
[00:17:04] <theBear> which appears to be caused by 48
[00:17:21] <jadew> it just seems like they're talking a different language
[00:17:54] <theBear> it kinda looks like it's trying to jtag rather than program
[00:18:00] <jadew> most likely avrdude's fault
[00:18:03] <theBear> unless dragon programs via jtag
[00:18:06] <theBear> and i agree with jade
[00:18:10] <TechIsCool> it does but no
[00:18:23] <TechIsCool> hmm
[00:18:43] <theBear> it does but no ? no no no, that doesn't make sense
[00:18:48] <TechIsCool> sorry
[00:19:05] <TechIsCool> I would have thought that if it was specificed as dragon_pdi it would only use pdi
[00:19:06] <theBear> and i mean english sense, not technical sense :)
[00:19:12] <TechIsCool> I understand
[00:19:20] <theBear> you'd think so, but the log clearly says it's doing jtag stuff
[00:19:36] <TechIsCool> is there a newer version then 5.11?
[00:19:55] <jadew> theBear, I think there are more interfaces / protocols implemented in the same piece of code
[00:20:17] <jadew> like stk500v2 doing a lot more than it should
[00:20:17] <theBear> or maybe it's talking jtag to the dragon, judging from the start of the messages
[00:20:23] <TechIsCool> What does Got error setting up PDI mode. Device is not suppored in this emulator mode. Debugger command setParameter failed mean
[00:20:35] <TechIsCool> thats what hapeens when I try atmelstudio6
[00:21:24] <jadew> TechIsCool, can dragon do pdi?
[00:21:29] <TechIsCool> yes
[00:21:43] <theBear> that soudns like it's saying either pdi or your chip isn't supported in the mode it is talking, perhaps because it's opening in jtag mode then trying to pdi, for example
[00:22:11] <theBear> or perhaps because your chip doesn't do or isn't connected for jtag and the dragon is in jtag mode
[00:22:27] <TechIsCool> the chip does not support anything but pdi so no jtag
[00:23:26] <jadew> call atmel, tell them they suck
[00:23:31] <TechIsCool> lol
[00:24:54] <jadew> http://pastebin.com/M9UNktQE
[00:25:18] <theBear> hmm, is your avrdude.conf standard and recent enough for that version/firmware dragon ?
[00:25:44] <TechIsCool> theBear: I am running what I believe to be the most reason version of avrdude
[00:25:57] <theBear> i said avrdude.conf
[00:27:45] <jadew> night
[00:28:02] <theBear> day
[00:28:09] <theBear> :) cya
[00:28:10] <TechIsCool> :)
[00:29:42] <TechIsCool> theBear: I ssee why it is trying jtag since its listed as aplicable for the atxmega32a4 So I created a listing that has the atxmega32a4u listed as pdi only and it still seems to get the same responce
[00:31:04] <theBear> hmm, it's a step in the right direction.. you actually looked for a chip that is very similar to yours ? it might not be the one with the closest p/n... and you checked the other config parameters make sense for your chip ?
[00:33:08] <TechIsCool> the only difference between the atxmega32a4 and the u is that they changed the way adc works and update the usb side nothing else. Which means avrdude had it typed wrong since it never supported jtag
[00:33:45] <theBear> you sure ? a lot of avrs support jtag at some level, and those are pretty fancy ones
[00:34:07] <TechIsCool> I am sure this is one of the few that don't. Confirmed that before making the boards.
[00:34:49] <theBear> you asked the web ?
[00:35:06] <TechIsCool> clawson says "The ATxmega A4U doesn't support JTAG."
[00:35:18] <TechIsCool> not yet on avrfreak should though
[00:36:06] <theBear> i dunno who clawson is, but i wouldn't consider him to be authoritive... tho i meant re: the programming issues
[00:36:17] <theBear> surely someone has tried to program that chip with a dragon
[00:36:35] <TechIsCool> they have but it seems flaky
[00:36:48] <TechIsCool> http://www.avrfreaks.net/index.php?name=PNphpBB2&file=printview&t=118076&start=0
[00:37:18] <theBear> once i wake up i got stuff to do, i aint gonna start reading irc links :)
[00:37:28] <TechIsCool> np
[01:17:56] <TechIsCool> OndraSter_: You around
[01:51:28] <Vutral> he
[01:51:31] <Vutral> someone tried dithering ?
[01:51:34] <Vutral> atmega328p !?
[03:40:44] <OndraSter_> TechIsCool, yes
[04:15:14] <Grievre> ok UART question: If I pull the serial line low and just keep it there for a long time, the AVR will read one all-zero byte with a frame error
[04:15:25] <Grievre> will it read more all-zero bytes after that or will it not read any more until I let it go high again?
[04:18:52] <OndraSter_> it needs start and stop bits
[05:44:09] <iSaleK> tomatto: Did you manage to make the circuit work? :)
[06:04:11] <tomatto> iSaleK: hi, yes it looks like it is working, but i have there ground loops issua perhaps
[06:04:45] <iSaleK> tomatto: What circuit did you use? :)
[06:06:23] <tomatto> iSaleK: that on page 77 :). i was wondering about what is double rolloff for
[06:07:03] <iSaleK> What is rolloff? (I don't know that term in english) :)
[06:07:13] <iSaleK> I'm glad that it is working/semiworking :)
[06:08:03] <tomatto> iSaleK: now do some rectifier for it i suppose
[06:21:28] <iSaleK> Can anyone suggest me a good simulator with component models?
[06:21:57] <iSaleK> For simulating Op amps, transistors, caps, electrolytic caps, diodes, LEDs and etc.... ?
[06:22:48] <inflex> pspice?
[06:23:48] <theBear> rolloff is kinda, the end of a curve, like what you get with a filter outside the passband
[06:24:02] <theBear> maybe double rolloff means 12db/oct
[06:37:25] <iSaleK> Is there a windows version of pspice?
[06:37:53] <iSaleK> And yes, double rollof means 2xloss/decade(octave)
[06:38:02] <iSaleK> *rolloff
[06:41:42] <theBear> that's a pretty shitty term for it... rolloff is rolloff... it has no defined curve outside of a specific rating/measurement
[11:25:47] <sabesto> anyone seen this error before? "Invoking: AVR32/GNU C Compiler : (AVR_32_bit_GNU_Toolchain_3.4.0_332) 4.4.3 make: *** Access is denied.
[11:25:50] <sabesto> "
[11:26:13] <sabesto> compiling avr8/asm works fine, avr32 doesnt compile
[11:26:24] <sabesto> tried running AS6 as admin
[11:29:30] <specing> your permissions are f*cked
[11:29:47] <specing> Try Linux
[11:29:55] <sabesto> helpful
[11:30:07] <jadew> I was about to suggest: try Windows
[11:31:13] <specing> alsi 3.4.0 is ancient
[11:31:21] <specing> I use 4.8.0
[11:40:54] <sabesto> avg was the problem
[11:52:25] <Steffanx> Toolchain version != gcc version specing :P
[11:52:30] <Steffanx> but 4.4.3 is also old :)
[13:21:42] <TechIsCool> anyone around that has a dragon that works with pdi?
[13:22:17] <asteve> I am around but do not have a dragon
[13:22:22] <asteve> I don't know if that information helps you
[13:23:06] <TechIsCool> :) I have an issue where I can't seem to get my atxmega32a4u to repsond to pdi commands it will not respond to atmelstudio or avrdude
[13:28:53] <DrLuke> oh god I need help, for some reason programming fuses failed, and now I don't know what fuses are programmed on an avr
[13:29:00] <DrLuke> I can't remove it though, it's soldered on a board
[13:29:09] <DrLuke> is there anything I can do?
[13:29:21] <TechIsCool> DrLuke: More information is needed. Chip and Programmer used
[13:29:45] <DrLuke> avrisp mkII clone, atmega1284p, error was: 20:08:42: [ERROR] Internal error: null sent as device context when trying to tear down programming session.
[13:29:51] <DrLuke> I can't talk to the device anymore
[13:31:34] <TechIsCool> I have never seen that error but someone else might have. Just stick around a bit. Also what OS and version of avrdude are you using
[13:31:52] <DrLuke> I am using avrstudio 6 and windows 8
[13:32:05] <TechIsCool> 32 bit or 64bit
[13:32:21] <DrLuke> 64-bit, and I think I found the error
[13:32:29] <DrLuke> one of the crystal caps thombstoned
[13:32:33] <TechIsCool> You have been able to program the device before
[13:32:44] <DrLuke> yes, while it was running on the internal oscillator
[13:32:48] <DrLuke> I switched it to external crystal
[13:32:55] <DrLuke> I'll fix that cap really quick
[13:33:31] <TechIsCool> abcminiuser: You know your website is down correct?
[13:33:48] <abcminiuser> What?!
[13:33:59] <abcminiuser> Son of a bitch
[13:34:21] <TechIsCool> abcminiuser: you run http://fourwalledcubicle.com correct?
[13:34:28] <abcminiuser> Yeah
[13:34:32] <abcminiuser> When did that happen I wonder
[13:35:00] <TechIsCool> I can't resolve it. I live in Washington State and I use google 8.8.8.8 and 8.8.4.4 for dns
[13:35:11] <abcminiuser> Yeah dead for me too
[13:35:12] <abcminiuser> Damn
[13:35:46] <TechIsCool> can someone else find his site?
[13:35:55] <abcminiuser> Crap the actual DNS entry is missing
[13:35:55] <TechIsCool> if so it could be dns but I know I was on it last night
[13:36:02] <TechIsCool> What
[13:36:34] <TechIsCool> abcminiuser: Correct http://mxtoolbox.com/SuperTool.aspx?action=a%3afourwalledcubicle.com
[13:37:17] <DrLuke> techiscool: fixing the cap didn't do the trick :(
[13:37:36] <abcminiuser> Server is up at 223.130.24.80 so it's just the DNS
[13:37:55] <TechIsCool> Intresting you have flashed fuses before with this computer. Only reason I ask is that I have had nothing but problems with my dragon and windows 8. I used my latop that still on 7
[13:38:42] <TechIsCool> DrLuke: ^
[13:38:59] <DrLuke> yes
[13:39:24] <DrLuke> it was on another equal board
[13:39:28] <DrLuke> this one is freshly soldered
[13:39:38] <DrLuke> I think somehow the power went out while programming
[13:40:47] <TechIsCool> abcminiuser: It is dns only I added a local record and it resolves just fine
[13:40:59] <abcminiuser> Yeah what the christ is going on
[13:41:39] <TechIsCool> Check with the hosting company and see if they lost a top level dns server.
[13:42:50] <abcminiuser> GODDAMIT
[13:42:55] <abcminiuser> Angus didn't renew
[13:45:05] <abcminiuser> Hopefully he'll come online soon and fix
[13:48:18] <Tom_itx> abcminiuser i found a data sheet for the at90s4414
[13:48:58] <abcminiuser> Oh?
[13:49:07] <abcminiuser> I got confused looks when I mentioned it around the office
[13:49:47] <Tom_itx> i bet
[13:50:02] <Tom_itx> forget to pay your isp?
[14:03:59] <tandoori> i am confused about the pin and port addresses
[14:04:13] <tandoori> they are separate addresses but on the same pin, right?
[14:06:05] <dirty_d> yea
[14:06:29] <dirty_d> its been a while since ive done anything, but i think pin is input, nd port is output
[14:08:58] <Steffanx> Until you write to pin, then you toggle outputs ( with most newer devices ) :D
[14:09:12] <Steffanx> *toggle the pin
[14:11:27] <Tom_itx> tandoori look at the internal logic diagram of an avr and you will see
[14:16:24] <tandoori> oh i think i see what i did. i think i confused the settings of the pins for input and output
[14:36:19] <TechIsCool> So I have been trying to talk with my dragon to a atxmega32a4u and it reads to voltage but not the signature. I have a scope and connected it to the reset line and the data line. Reset is pulled low and then data is sent but nothing happens except an illegal exception. http://techiscool.com/Pictures/Forum_Images/PCB%20Design/NewFile0.bmp
[14:36:37] <TechIsCool> Channel 1 is the reset line while channel 2 is the data line
[14:41:33] <monode> what is the best way - or is there some sort of "holy grail" solution - to do debouncing, and figure out short/long/combined and double-click keypresses, along with an event loop?
[14:43:15] <monode> right now I'm doing a very simple method <<1 a per button buffer, |=1 if the button is pressed, detect if the buffer == 0xFF (8 transitions), a timer runs at 12.5ms, so the buttons are debounced at 100ms. The timer handles the buttons and the transitions (old vs new state) and feeds the data into a circular buffer which I like to call the keyboardEventBuffer, and consume it from main()
[14:43:44] <monode> however, I'm not sure what would be an efficient way to detect combined keypresses or long ones
[15:12:08] <OndraSter> TechIsCool, with 40pf between clk and reset?
[15:12:18] <TechIsCool> OndraSter: Yes
[15:12:27] <TechIsCool> wait
[15:12:30] <TechIsCool> clk and reset
[15:12:34] <TechIsCool> not gnd and reset?
[15:12:42] <OndraSter> err
[15:12:44] <OndraSter> clk = reset, sorry lol
[15:12:49] <OndraSter> yes, gnd and clk (reset)
[15:12:53] <TechIsCool> yes
[15:12:55] <OndraSter> hmm
[15:12:57] <OndraSter> weird
[15:13:03] <OndraSter> it works for me with 128a4u after that "patch"
[15:13:06] <TechIsCool> do you have that video that you shot
[15:13:11] <OndraSter> ?
[15:13:15] <OndraSter> I shot somebody?
[15:13:26] <TechIsCool> [13:15:01] <OndraSterver> http://clip2net.com/s/2gxWK
[15:13:40] <OndraSter> uh
[15:13:43] <OndraSter> where did you find that?
[15:13:51] <TechIsCool> logs from tom-itx
[15:13:52] <OndraSter> I don't know what is supposed to be there
[15:13:59] <OndraSter> that is a very, very old screenshot that has been deleted already
[15:14:01] <OndraSter> or video
[15:14:05] <TechIsCool> alrigh
[15:14:07] <OndraSter> do you have any description what it is supposed to be?
[15:14:07] <TechIsCool> t
[15:14:24] <TechIsCool> [13:13:20] <OndraSterver> HOLY COW
[15:14:26] <TechIsCool> [13:13:25] <OndraSterver> I connected scope to SCK pin
[15:14:28] <TechIsCool> [13:13:30] <OndraSterver> and it read signature just fine ?!
[15:14:29] <TechIsCool> [13:13:35] <OndraSterver> I have GOT to make video of that
[15:14:34] <OndraSter> heh
[15:14:36] <OndraSter> that was screenshot then
[15:14:38] <OndraSter> from as6
[15:14:43] <TechIsCool> ah ok
[15:14:45] <OndraSter> showing that it read calibration rows or something
[15:14:53] <OndraSter> but it was ringing issue
[15:15:02] <OndraSter> the 20+pF on the scope fixed it
[15:15:07] <TechIsCool> hmm
[15:15:16] <OndraSter> I *have* to ask - are you connecting it the right way?
[15:15:21] <OndraSter> using the ISP connector on the dragon?
[15:15:23] <OndraSter> not the JTAG
[15:15:27] <TechIsCool> yes
[15:15:33] <OndraSter> weeird
[15:16:12] <TechIsCool> I will go over it one more time to make sure but voltage is read correctly and I get this on a scope. http://techiscool.com/Pictures/Forum_Images/PCB%20Design/NewFile0.bmp
[15:16:20] <TechIsCool> yellow is the reset line and blue is data
[15:16:44] <TechIsCool> but I thought that the rst/clk was supposed to be a square wave not just a line
[15:17:00] <OndraSter> shouldn't be the yellow one jumping around?
[15:17:06] <OndraSter> indeed it is
[15:17:27] <TechIsCool> OndraSter: the square wave is generated by the dragon or the avr
[15:17:41] <OndraSter> dragon of course is the master
[15:18:39] <TechIsCool> so if I connect my scope directly to the reset/clk line I should see a square wave
[15:18:43] <TechIsCool> let me try that
[15:18:48] <OndraSter> indeed you should
[15:22:44] <monode> i hear good things happen if you touch the PSU or main chip on the avr dragon
[15:22:53] <OndraSter> eh
[15:23:05] <OndraSter> I get burned if I touch the master? slave? atmega
[15:23:11] <OndraSter> it gets really hot :P
[15:23:22] <monode> heh
[15:23:28] <OndraSter> I am tempted by JTAGICE3, it is now only $99
[15:23:31] <monode> i heard/read several reports where it burned out
[15:23:35] <TechIsCool> OndraSter: http://techiscool.com/Pictures/Forum_Images/PCB%20Design/dgjFile1.bmp
[15:23:43] <OndraSter> bmp? :(
[15:23:46] <TechIsCool> that is without a device connected
[15:23:51] <TechIsCool> sorry pulled it off a scope
[15:23:55] <OndraSter> ok
[15:24:09] <OndraSter> that is the clk (reset) line?
[15:24:13] <TechIsCool> yes
[15:24:22] <OndraSter> do you have your schematic and board layout somewhere?
[15:24:28] <TechIsCool> yes
[15:24:47] <TechIsCool> https://github.com/TechIsCool/10w_RGB_LED
[15:24:54] <TechIsCool> let me know if you want it in pdf or something else
[15:25:04] <OndraSter> presumably eagle files?
[15:25:15] <TechIsCool> they are
[15:26:57] <OndraSter> hmm
[15:27:05] <OndraSter> it seems ok
[15:27:23] <OndraSter> is the reset high or low when you hook it up to the chip and try reading it?
[15:27:32] <TechIsCool> reset is high
[15:27:39] <TechIsCool> then it gets pulled down
[15:28:43] <OndraSter> hmmm
[15:28:48] <OndraSter> can't think of anything else really
[15:30:26] <tandoori> i have a question about clock signals
[15:31:07] <tandoori> so, when this datasheet talks about the 'rising edge', that means when the clock is brought from low to high, right? or is it low-high-low?
[15:31:16] <OndraSter> TechIsCool, why is the polygon below the chip +3v3? :o
[15:31:29] <OndraSter> rising = _|-
[15:31:33] <OndraSter> falling = -|_
[15:31:36] <dioxide> eising edge is the slope from low to high
[15:31:59] <dioxide> rising*
[15:32:22] <TechIsCool> um because it worked. lol
[15:32:30] <TechIsCool> not to say it was the brightest idea
[15:33:35] <tandoori> i still dont get that, can you explain it in reference to my example?
[15:33:59] <OndraSter> rising = low to high
[15:34:20] <tandoori> so set the pin to 0 and then to 1, right?
[15:34:24] <OndraSter> yes
[15:34:40] <tandoori> do i have to bring it back down to 0 again? or can i move on?
[15:35:01] <OndraSter> depends on the device
[15:35:02] <OndraSter> check datasheet
[15:35:17] <tandoori> i have read this datasheet a hundred times
[15:35:23] <tandoori> tells me nothing about that
[15:35:53] <OndraSter> then you are reading it wrong :)
[15:36:02] <tandoori> my code reflects what is in the function table, but all the lights on the shift register are on
[15:36:07] <OndraSter> or bad chip maker
[15:36:17] <OndraSter> who cannot do proper datasheets
[15:36:25] <monode> you need to slaughter the sacrificial goat
[15:36:37] * tandoori frowns again
[15:36:39] <monode> also, make sure you compile your code on a tuesday that's a multiple of 3
[15:36:50] <dioxide> if it does something on the rising edge, and you only need one shot, then you shouldnt have to continue the clock unless youre reading something out of it
[15:36:50] <OndraSter> :)
[15:37:14] <monode> actually, I think that's what's needed to compile PHP
[15:37:25] <OndraSter> that's what's needed to *use* PHP
[15:39:57] <tandoori> hmm i think i know what i am doing wrong
[15:40:12] <tandoori> clock pins need to be set to OUTPUT, right?
[15:40:12] <tandoori> heh
[15:40:21] <tandoori> i have them set as input :(
[15:40:29] <OndraSter> ohh lol
[15:40:30] <OndraSter> happens
[15:40:45] <OndraSter> the worse part is when you fix it and it still does not work
[15:41:15] <tandoori> true, true
[15:43:04] <monode> there's a saying here - practice is when it works, but you don't know why; theory is when you know how it should work, but it doesn't.
[15:43:27] <monode> my circuits, however, combine theory with practice - they don't work and i have no idea why
[15:43:33] <dioxide> im partial to fwitiw
[15:44:04] <OndraSter> :)
[15:44:17] <OndraSter> fwitiw?
[15:44:23] <dioxide> f with it till it works
[15:44:42] <OndraSter> ah
[15:44:43] <OndraSter> I like that
[15:48:54] <monode> professional circuit bending.
[15:49:25] <monode> sort of like a minesweeper consultant / solitaire expert
[15:50:09] <monode> so, how do you guys do special keypress detection? (double click, long clicks, combinations, etc)
[15:51:08] <dioxide> i havent had reason to use it yet
[15:51:24] <dioxide> intresting problem
[15:51:48] <tandoori> hmm. i dont think this is evaluating properly. if (((foo >> x) & 0x01)), where x is a for loop counter value from 0 to 7
[15:52:03] <monode> minimizing extra hardware while till providing some sort of menus
[15:52:11] <tandoori> that is supposed to check every bit in that byte and return 0 or 1
[15:52:35] <tandoori> mind you, foo = byte
[15:52:47] <monode> I like !!(foo >> x)
[15:53:13] <tandoori> huh
[15:53:16] <monode> the absurdity of statements C allows you is mind bending.
[15:53:41] <monode> it's a double negation, which, unlike anything != 0 may or may not be 1, will always return 1.
[15:53:43] <tandoori> thats a not-not?
[15:53:49] <dirty_d> tandoori, i think thats ok
[15:53:52] <monode> that would be a yes-yes.
[15:54:03] <tandoori> monode: that is evil
[15:54:06] <monode> and yeah, your statement looks fine.
[15:54:21] <monode> it isn't if you want a one liner to pull a single bit and remove its mask
[15:54:39] <tandoori> hmm
[15:54:48] <tandoori> okay i will rewrite this and see if it works this time
[15:54:49] <tandoori> hehe
[15:55:14] <monode> I needed it only in one case, and could be solved with less obfuscation, but someone in ##electronics suggested it once, and it applied.. so..
[15:55:49] <TechIsCool> OndraSter: It works with every pin except my voltage pin as soon as i connect it it has issues
[15:57:24] <monode> tandoori: don't forget to check hardware stuff. shadow PINs and enable pullups if needed, or set your DDRs to output, or make intermediate registers volatile, if that's supposed to run in an ISR and it's written somewhere else, and whatnot...
[15:58:08] <monode> on the topic of more sillynesses, why does avrgcc emit a warning if main is int
[15:58:12] <monode> isn't*
[15:58:39] <monode> the only usable purpose I see in that is wasting 2 more words of program memory to satisfy some absurd standard that doesn't apply in a bare metal situation
[16:01:42] <tandoori> this circuit doesn't work
[16:01:48] <tandoori> im not sure what else to do
[16:01:51] <tandoori> except to give up
[16:01:59] <monode> fuck with it till it works
[16:02:01] <tandoori> ive checked everything
[16:02:10] <monode> also, details? i don't think i have the backlog
[16:10:13] <tandoori> oh im sorry i was reading the datasheet
[16:10:36] <tandoori> i dont understand this line 'when the output enable input is high, the outputs are in high impedance state
[16:12:33] <specing> monode: -Wno-main
[16:12:47] <monode> well yes, but.. why?
[16:13:10] <specing> Because standard. And GCC is following it
[16:13:37] <monode> tandoori: that sounds wrong..
[16:14:08] <monode> does a kernel's main loop also have a return value?
[16:15:36] <tandoori> monode: this is from a serial in -parallel out 595 shift register
[16:16:17] <monode> oh. you need to drive the OE line low then.
[16:16:24] <monode> driving it high disables the outputs.
[16:16:35] <monode> (if memory serves me well)
[16:16:46] <monode> think of it as output disable, or negated output enable
[16:17:52] <tandoori> ugh i cant even tell if this circuit is on
[16:18:02] <tandoori> i need to add more leds for the buttons
[16:18:03] <tandoori> lol
[16:18:12] <specing> monode: Go check it out
[16:33:57] <RikusW> monode: a piece of key handling code I wrote in a hurry early (04:00) one morning http://pastebin.com/a8U1qk0P
[16:34:20] <RikusW> there was a piezo alarm on B0
[16:34:51] <RikusW> it only needed power via a transistors on B0
[16:35:01] <RikusW> so I didn't have to generate any tone
[16:37:37] <tandoori> ...i think this 597 is broken
[16:44:29] <john_f> is there a vbus pin on the atemga16u2? I don't see it in the pinout but it is referenced in the powering options.
[16:45:15] <RikusW> no
[16:45:28] <RikusW> only 16u4 iirc
[16:45:48] <RikusW> and at90usb64/128 6/7
[16:46:10] <OndraSter> vbus = usb ;D
[16:46:14] <OndraSter> ph
[16:46:16] <OndraSter> oh
[16:46:16] <OndraSter> nvm
[16:46:20] <OndraSter> I read it as atmega162
[16:46:31] <john_f> so I should leave the usb +5v disconnected when using a battery power supply?
[16:47:12] <john_f> as that is the only place it goes in that configuration
[16:48:53] <john_f> strange they used the wrong graphic in the datasheet
[16:51:35] <RikusW> there is UVcc
[16:53:00] <john_f> that is tied to the 3.3v from the battery/regulator.
[16:53:26] <RikusW> UVcc needs USB 5V iirc
[16:53:51] <RikusW> the mega16U2 datasheet shows a few powering option circuits
[16:54:26] <john_f> yeah that is what I am reading, one option doesn't connect it to usb
[16:54:56] <john_f> it bypasses the internal regulator
[17:14:11] <DrLuke> hey, so a power loss during fuse programming may lead to bricking, right?
[17:16:06] <RikusW> chances are slim
[17:16:10] <DrLuke> crap
[17:16:15] <DrLuke> so I bricked my board
[17:16:15] <RikusW> fuses program really fast
[17:16:16] <DrLuke> that sucks
[17:16:23] <DrLuke> well, I got this error message: 20:08:42: [ERROR] Internal error: null sent as device context when trying to tear down programming session
[17:16:35] <RikusW> try supplying a clock to XT1 ?
[17:16:37] <DrLuke> after that I couldn't talk to it anymore, I set it to an external crystal
[17:16:55] <RikusW> external clock or external crystal ?
[17:16:58] <DrLuke> crystal
[17:17:01] <DrLuke> 8 MHz
[17:17:05] <DrLuke> it worked on a different board
[17:17:16] <RikusW> what value caps ?
[17:17:36] <DrLuke> 18 pF
[17:17:42] <DrLuke> as the caps' datasheet says
[17:17:45] <RikusW> should be ok
[17:17:51] <DrLuke> works on another board
[17:18:10] <RikusW> you could try loading PORT++ on some avr then connect PORT0 to the XT1 pin
[17:18:14] <RikusW> it might revive it
[17:18:20] <DrLuke> :S
[17:18:23] <DrLuke> ok
[17:18:39] <RikusW> the SPI clock needs to the 5 times lower than system clock...
[17:18:53] <RikusW> at the very least 4 times
[17:19:11] <DrLuke> yeah I'll set it to the minimum speed
[17:19:16] <RikusW> tried connecting via JTAG yet ?
[17:19:34] <RikusW> hopefully you didn't change SPIEN...
[17:24:15] <DrLuke> RikusW: no luck :/
[17:24:21] <DrLuke> got no jtag broken out
[17:25:04] <RikusW> tqfp ?
[17:25:25] <DrLuke> worse, qfn
[17:25:46] <RikusW> ugh
[17:26:19] <DrLuke> well
[17:26:39] <DrLuke> I won't get around trying to desolder it and add a new avr
[17:27:02] <DrLuke> and if that fails, desolder the dc-dc converter, as that's the only thing stopping me from making a new board :P
[17:27:06] <DrLuke> (I ran out of ICs)
[17:27:29] <DrLuke> it's just a shame, this is the most beautiful board I ever made
[17:27:58] <DrLuke> *sniff*
[17:31:27] * RikusW got some yageo YC158 chip resistors, 1206 but 5x2 pins
[18:02:03] <Tom_itx> DrLuke, single sided?
[18:02:16] <DrLuke> Tom_itx ?
[18:02:31] <Tom_itx> the qfn you need to remove
[18:02:55] <DrLuke> are there double sided qfns?
[18:03:03] <DrLuke> or what do you mean (it's an atmega1284p)
[18:03:50] <Tom_itx> <DrLuke> I won't get around trying to desolder it and add a new avr
[18:04:00] <Tom_itx> is the board single sided?
[18:04:06] <DrLuke> no, it's a double sided board
[18:04:13] <Tom_itx> components on both sides?
[18:04:21] <DrLuke> only one side
[18:04:25] <Tom_itx> any thru hole components?
[18:04:33] <DrLuke> only the isp header
[18:04:41] <DrLuke> but it's on the other side
[18:04:45] <DrLuke> so I can just throw it on the hotplate
[18:04:45] <Tom_itx> set it on a clothes iron on high and pick the part off when it gets hot
[18:04:52] <Tom_itx> or that
[18:05:01] <DrLuke> that's how I soldered it in the first place :P
[18:05:13] <Tom_itx> carry on...
[18:05:45] <DrLuke> I'll probably need to apply some flux though
[18:08:55] <TechIsCool> Tom_itx: you got a second to talk about my pdi chip issue?
[18:11:18] <TechIsCool> OndraSter: http://techiscool.com/Pictures/Forum_Images/PCB%20Design/einrvle1.bmp
[18:28:09] <OndraSter> TechIsCool, what is what?
[18:28:28] <TechIsCool> Yellow is the data, Blue is reset/clk
[18:28:45] <TechIsCool> but I still get the same errors
[18:29:09] <TechIsCool> I am now thinking it could be a bad chip or I distroyed it somehow
[18:29:15] <OndraSter> hmm
[18:29:19] <OndraSter> how long cable are you using?
[18:29:37] <OndraSter> although that should not matter, I am using either very long (30cm) or short (10cm) and it works with both
[18:29:45] <TechIsCool> 12 inches
[18:29:54] <OndraSter> 25cm*
[18:29:56] <TechIsCool> 30 cm
[18:29:58] <OndraSter> oh
[18:29:59] <OndraSter> yes
[18:30:06] <OndraSter> hmm hmmm
[18:30:21] <OndraSter> if you are sure you have not swapped clock and data then I do not have any ideas left
[18:30:30] <OndraSter> try adding the 40pf even to the other line
[18:30:40] <OndraSter> I soldered them right on the header on the board
[18:30:43] <OndraSter> from the bottom
[18:30:58] <OndraSter> or just hold it there if you have regular PTH one
[18:35:49] <OndraSter> http://arduino.cc/forum/index.php/topic,21780.0.html
[18:35:50] <OndraSter> oh dear god
[18:39:51] <TechIsCool> OndraSter: http://techiscool.com/Pictures/Forum_Images/PCB%20Design/3ewFile1.bmp That is with .4F is what my dvm says which should be 40pF right
[18:41:26] <OndraSter> 0.4F?!
[18:41:27] <OndraSter> uh
[18:41:36] <TechIsCool> no no uF
[18:41:37] <OndraSter> that would be either 400pF or 400nF or something
[18:41:42] <TechIsCool> I think
[18:41:49] <OndraSter> 0.4uF = 400nF
[18:41:53] <OndraSter> != 40pF
[18:42:49] <RikusW> that will kill any signal....
[18:43:15] <TechIsCool> FAIL they are these LOL http://www.mouser.com/ProductDetail/AVX/08055C104JAT4A/?qs=%2fha2pyFadugABdYl%252bpvDCfe%252b7s2XCj7JlYpauezfDy0MimO%252babstOQ%3d%3d
[18:43:53] <TechIsCool> but I just touched them there
[18:43:58] <OndraSter> 100nF
[18:44:02] <TechIsCool> lol :(
[18:44:04] <OndraSter> that is 3 orders of magnitude bigger
[18:44:32] <TechIsCool> so I am looking for a 22 pF right
[18:44:39] <OndraSter> 40 - 60pF
[18:44:40] <TechIsCool> or 1 40 pF
[18:44:43] <OndraSter> 22pF was not enough for me
[18:44:46] <OndraSter> so I added second one there
[18:44:50] <TechIsCool> ok
[18:45:03] <TechIsCool> let me dig through my parts bin most likely won't have one
[18:45:07] <TechIsCool> but maybe get lucky
[18:51:50] <OndraSter> gn
[18:59:18] <TechIsCool> OndraSter: all I have is 1nf
[18:59:19] <TechIsCool> OndraSter: all I have is 1nF
[19:32:02] <RikusW> thats too much I'd say
[20:20:09] <TechIsCool> I know
[21:35:47] -pratchett.freenode.net:#avr- [freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp
[22:39:48] <TechIsCool> I am back
[22:40:34] <RifRaf> there goes the peaceful neighbourhood
[22:40:49] <TechIsCool> RifRaf: LOL