Back
[06:16:16] <GeneralStupid> Hi
[06:16:34] <GeneralStupid> i still have the problem, that i cant write and read to my SPI flash chip
[06:19:07] <GeneralStupid> I write with cs=0, writeEnable, cs=1, cs=0, PageWrite, 0x00, 0x00, 0x00, 0x24, 0x42, cs=1 Wait for WIP
[06:19:34] <GeneralStupid> I read with cs=0, Read, 0x00, 0x00, 0x00
[06:19:39] <GeneralStupid> cs = 1 :D
[06:25:25] <Lambda_Aurigae> http://www.atmel.com/Images/Atmel-2585-Setup-and-Use-of-the-SPI_ApplicationNote_AVR151.pdf
[06:26:32] <GeneralStupid> Lambda_Aurigae: that dosnt help. Iam using ASF. and my logic analyzer tells me that the data transmission works
[06:26:46] <GeneralStupid> Lambda_Aurigae: i think its more a problem in my understanding of SPI Flash chips -.-
[06:26:51] <Lambda_Aurigae> https://sites.google.com/site/qeewiki/books/avr-guide/spi
[06:27:00] <Lambda_Aurigae> oh.
[06:27:06] <Lambda_Aurigae> can't help you with the asf thing
[06:27:25] <GeneralStupid> but with SPI flashes?
[06:27:42] <GeneralStupid> do i have to set CS to 1 before reading?
[06:27:56] <GeneralStupid> (cs =1; wait; cs=0 ; read ...)
[06:27:59] <Lambda_Aurigae> have you read the datasheet for the particular chip you are trying to read?
[06:28:31] <LeoNerd> Generally you hold CS low for the entire transaction
[06:28:52] <LeoNerd> Normally SPI chips are active-low on the CS line; so you keep it high normally and drop it low to actually address the chip
[06:28:56] <Lambda_Aurigae> it is Chip Select after all.
[06:28:58] <LeoNerd> Keep it low for the entire transaction, then raise it at the end
[06:29:16] <Lambda_Aurigae> also called Slave Select or SS on some documents.
[06:29:47] <GeneralStupid> LeoNerd: i tried that with reading the status registers... it turns out that i have to cs=0, write enable, cs=1 , cs=0, read status register, ....
[06:29:59] <Lambda_Aurigae> and that document should help as it shows the same thing.
[06:30:42] <Lambda_Aurigae> still need to know the exact chip you are working with to look at the datasheet in case it has some odd interface requirement
[06:30:44] <GeneralStupid> Lambda_Aurigae: your right... it tells me exactly what i figured out by trying...
[06:30:54] <GeneralStupid> https://4donline.ihs.com/images/VipMasterIC/IC/FASL/FASLS03757/FASLS03757-1.pdf?hkey=EF798316E3902B6ED9A73243A3159BB0
[06:31:13] <GeneralStupid> its a s25FL-116
[06:33:06] <Lambda_Aurigae> according to the command protocol on page 19 you pull CS low,,,send command,,,and read data,,then pull CS high.
[06:34:54] <Lambda_Aurigae> which is what it looks like you are doing.
[06:35:32] <GeneralStupid> yes :( maybe there is a problem at the programming part. I will check that once again.
[06:35:52] <LeoNerd> GeneralStupid: that sounds like two separate SPI transactions then
[06:36:28] <Lambda_Aurigae> looks like 3...write enable, page write, and read
[06:36:47] <Lambda_Aurigae> page 21 has the timing diagrams
[06:37:00] <Lambda_Aurigae> and, I gotta go take wifey to hospital..surgery day.
[06:38:58] <_ami_> Lambda_Aurigae: what happened? all good?
[06:39:22] <Lambda_Aurigae> all good
[06:39:31] <Lambda_Aurigae> she had gastric sleeve surgery last october.
[06:39:41] <Lambda_Aurigae> lost 130 pounds in a year and a half.
[06:39:52] <_ami_> wow!
[06:39:55] <Lambda_Aurigae> now she is having the extra skin and fat on her tummy removed.
[06:40:09] <Lambda_Aurigae> will lose another 15 to 20 pounds in skin and subcutaneous fatty deposits today.
[06:40:22] <Lambda_Aurigae> will have lost half herself by the time it's done.
[06:40:40] <Lambda_Aurigae> this surgery will be kinda painful afterwards though and she will be out of work for 3 to 6 weeks.
[06:41:31] <Lambda_Aurigae> at least ksp 1.2.1 is out! I'll have something to do while waiting at the hospital today.
[06:41:36] <_ami_> surgery scares shit out of me.
[06:41:47] <GeneralStupid> Lambda_Aurigae: thanks for help
[06:46:26] <GeneralStupid> omg -.- what a mistake
[06:49:55] <GeneralStupid> it works :)
[06:50:30] <Lambda_Aurigae> what'd you do?
[06:50:34] <Lambda_Aurigae> we aren't leaving yet.
[06:50:38] <Lambda_Aurigae> another 10 minutes or so.
[06:54:22] <GeneralStupid> first i returned a pointer were i want to return a value -.-
[06:54:39] <GeneralStupid> second i thought i was using page program, but i used page write -.-
[06:55:47] <GeneralStupid> -.-
[06:58:25] <_ami_> its always good practice to share code snippet sometimes.
[06:58:45] <GeneralStupid> but asf scares most people -.-
[06:59:36] <Lambda_Aurigae> working with asf is next to impossible without atmel studio
[06:59:42] <Lambda_Aurigae> and atmel studio won't run on linux.
[06:59:47] <Lambda_Aurigae> and I refuse to run windows
[06:59:53] <GeneralStupid> i know-.- i hardly learned that
[07:00:08] <LeoNerd> Yah; I just don't bother with it. avr-gcc/avrdude/etc.. for me :)
[07:00:10] <LeoNerd> Works just fine
[07:00:15] <Lambda_Aurigae> I have to use windows at work.
[07:00:25] <Lambda_Aurigae> refuse to do so at home for fun.
[07:00:28] <GeneralStupid> iam doing a lot with fpga and matlab at work... so windows is a good choice for that
[07:00:42] <GeneralStupid> iam at work right now -.-
[07:01:18] <GeneralStupid> the xilinx matlab <-> fpga bridge is a PITA under windows and impossible to use under linux
[07:01:57] <Lambda_Aurigae> oooo...2 cops shot and killed in des moines last night.
[07:02:25] <Lambda_Aurigae> ambushed, shot in their cars.
[07:02:57] <GeneralStupid> united states?
[07:03:02] <GeneralStupid> sounds like the us :D
[07:10:30] <skz81> GeneralStupid, sounds like Iowa is in the US, yeah :) :p
[07:10:36] <skz81> https://www.rt.com/usa/365059-des-moines-police-ambush/
[07:13:25] <skz81> << Des Moines PD have paired up their officers as a precaution ... >> I believed US PD officiers were ALWAYS paired... To much Hollywood bullshits in my head ?
[07:22:25] <GeneralStupid> hm in germany they are always paired AFAIK
[07:24:15] <GeneralStupid> i think having too many weapons around is a problem (its only an advantage in a "the walking dead" szenario)
[07:32:49] <Snert_> they pair the noob with the experienced.
[07:33:08] <Snert_> and tons of weapons is a most excellent way to have it.
[07:33:32] <Snert_> a citizen with a gun is a cop's best friend.
[07:36:21] <GeneralStupid> normally the executive should be the only ones which are allowed to be violent by the judicial... (and only if it is ok by the legislative) so... in a perfect world there is no need for a weapon
[08:52:40] <Snert_> when the logic fails late at night at a concert and you find yourself getting shot at - Well.......
[09:06:25] <bss36504> specing: VFD isnt a bad idea. I don't know much about how they work, at least not at a low level. I understand the general block diagram of them though.
[09:08:24] <bss36504> lochs: H-bridge might be easier. I'd still want to have a feedback mechanism for speed control etc., but that might be an easier project than a BLDC driver. At the very least, all the students should know about H-Bridge control by that point
[09:30:44] <specing> bss36504: I haven't found any open hardware designs for >100W stuff
[09:31:11] <specing> bss36504: the closest thing is Vedder's ESC for up to 60V 1.5 kW BLDC
[09:34:56] <daey> GeneralStupid: i love when the pro gun guys pull out the statistics that show that more guns dont mean more crime... yeah no shit the 10th gun per head doesnt increase the crimerate :P
[09:35:06] <Casper> thing get more and more complex as you go up in size, and the tiny issue become a major one... plus, not everyone have access to big ones
[09:55:55] <GeneralStupid> daey: that makes no difference, no :D
[09:58:03] <bss36504> Well it's the age-old argument of "guns dont kill people, people kill people". Of course, the counter argument is, "people predisposed to violence who have little-to-no restrictions to firearms are more likely to get them and use them, ergo, we should restrict gun access" to which the argument is "if youre a criminal and want a gun, you'll get it n
[09:58:04] <bss36504> o matter what the law is"
[09:58:06] <bss36504> Note, I
[09:58:21] <bss36504> Not trying to start a debate here, btw
[10:03:59] <specing> you should fix your society to produce less criminals
[10:04:13] <LeoNerd> fewer
[10:06:38] <bss36504> lol ^
[10:06:40] <bss36504> I agree
[10:06:48] <bss36504> I'm not savvy enough to even know where to begin.
[10:08:25] <bss36504> Do you begin with education? With quality of life through heathcare/housing? How do you remove the impression (or literal fact, as the case may be) of oppression against various demographics?
[10:27:14] <GeneralStupid> is it a problem to use two i²c ports at once?
[10:27:23] <LeoNerd> ?
[10:28:17] <GeneralStupid> i already use TWIC and now i want to add TWIE and if i try to write something on TWIE my device hangs
[10:28:45] <GeneralStupid> i stepped through the code but actually that doesnt help me... a lot of asf code -.-
[10:30:05] <GeneralStupid> and there is no action on the I²C bus
[10:30:16] <LeoNerd> First of all: which chip?
[10:30:24] <LeoNerd> Not that many AVR chips even have more than one I²C controller
[10:30:41] <GeneralStupid> xmega a3u 192 -.-
[10:32:12] <GeneralStupid> it has two i2c interfaces
[10:35:27] <LeoNerd> Ah OK
[10:35:34] <LeoNerd> So they should be entirely independent
[10:37:09] <GeneralStupid> yes... maybe its an asf problem again
[10:37:24] <GeneralStupid> i already had a LOT OF fun with their "documentation"
[10:40:13] <GeneralStupid> ok ok
[10:40:41] <GeneralStupid> please dont laugh at me (again) ... my pcb is too small... it looks like there is anything directly under that pin ... (so i cannot connect my la there)
[10:41:22] <LeoNerd> I've not yet used a chip with two I²Cs
[10:41:38] <LeoNerd> Well,.. actually I have started playing with the 328PB, but I haven't used the second I²C unit yet
[10:42:19] <GeneralStupid> yes but this sucks. i cannot debug AND it does not configure the chip :) im sill gettin 20Mhz out of that PLL
[10:56:22] <skz81> <LeoNerd> Well,.. actually I have started playing with the 328PB, but I haven't used the second I²C unit yet >> huhu ! Be careful, you maybe temptated to link some ardweeny stuff into your project...
[10:56:35] <LeoNerd> Doubt it
[10:56:37] <LeoNerd> I don't usually :)
[10:56:41] <skz81> Or even end coding inside the IDE :p
[10:56:50] <LeoNerd> (Except that one time I needed a USB-CDC driver in a hurry)
[10:57:00] <LeoNerd> I should get around to fiddling with LUFA
[10:57:11] <skz81> ho sorry, didn't notice the 'B', sorry
[10:57:59] <LeoNerd> Yah; the B is the killer bit there ;)
[10:58:39] <skz81> to my "joke", yep. Don't know any arduino hardware with the 328PB on it :)
[10:59:09] <LeoNerd> My board
[10:59:24] <LeoNerd> I sell a 328PB-based variant of the Nano
[10:59:34] <LeoNerd> I.e. 16MHz xtal, USB-UART bridge.. similar shape too
[10:59:49] <LeoNerd> https://www.tindie.com/products/leonerd/atmega328pb-development-board/
[11:00:16] <LeoNerd> The pins aren't in the same place though because fundamentally there's more of them, so something has to change
[11:01:30] <skz81> USB is for powering only, or you can flash the device / do UART comm through it ?
[11:01:45] <LeoNerd> It's on UART, same as the other boards
[11:02:06] <LeoNerd> It ships with Optiboot, so you can reflash it over that as well
[11:02:07] <skz81> ha yes found the interface chip, under the PCB
[11:02:15] <LeoNerd> I use both sides :)
[11:02:44] <LeoNerd> Infact next version of this board might have to be a 4 layer, so I can squeeze in some solderbridge pads to do UART pin routing on the bottom
[11:02:58] <LeoNerd> Could be nice to route CTS/RTS/DTR/DSR onto IO pins
[11:05:19] <skz81> <LeoNerd> Could be nice to route CTS/RTS/DTR/DSR onto IO pins >> What feature would it enable ?
[11:05:31] <aandrew> nah
[11:05:37] <LeoNerd> Software control of the handshaking lines
[11:05:41] <aandrew> don't worry about CTS/RTS/DTR/DSR unless you need them
[11:05:44] <LeoNerd> sometimes it's nice to get some sort of control signal out of it
[11:05:59] <aandrew> In 25 years I've never needed them. :-)
[11:06:01] <LeoNerd> aandrew: ohyes, by default they wouldn't be connected. but they'd be routable by some solder pads on the bottom *if* you wanted them
[11:06:09] <aandrew> oh
[11:06:11] <aandrew> yes
[11:06:17] <aandrew> that's a fantastic idea
[11:06:21] <aandrew> especially on any prototype. you never know
[11:06:31] <aandrew> and put a zero ohm resistor between CTS/RTS and DSR/DTR that you can depop if needed
[11:06:47] <skz81> ha okay, just in case of need, nice :)
[11:06:56] <LeoNerd> E.g. you can use CTS/RTS for outofband signalling
[11:07:15] <bss36504> LeoNerd: How did you manage the tri-color logo?
[11:08:03] <LeoNerd> A blue marker pen ;)
[11:08:09] <LeoNerd> A sharpie, no less
[11:08:50] <bss36504> Oh ok, I wondered if that was the case
[11:09:49] <LeoNerd> silkscreen and soldermask make two colours but the blue is just a pen.
[11:12:44] <GeneralStupid> is it possible to use SPI pins as GPIO ?
[11:13:43] <LeoNerd> If you turn off the SPI unit first, sure
[11:14:17] <LeoNerd> Except for the occasional pin like e.g. the XTAL1/XTAL2 pins on some of the bigger AVRs, every IO pin can be a generic dumb GPIO pin if you turn off the peripheral unit(s) otherwise attached to it
[11:14:19] <GeneralStupid> but where is the pins name? :) i only got PIN0_bm to PIN7_bm
[11:33:05] <cehteh> datasheet ftw
[11:38:46] <skz81> GeneralStupid, what are << PIN0_bm to PIN7_bm >> ? ASF specific syntax ?
[11:39:20] <LeoNerd> << is C's numerical bitshift operator
[12:07:38] <bss36504> Do you guys think a smart mirror with facial rec would be bad for a bathroom mirror?
[12:07:59] <GeneralStupid> skz81: yes :D
[12:08:20] <GeneralStupid> skz81: but i realized that our PCB guy already planned a debug LED to the blackfin...
[12:08:31] <GeneralStupid> so i "just" have to program that blackfin LED :D
[12:08:46] <GeneralStupid> that thing is a bit more complex (first view)
[12:08:52] <skz81> <LeoNerd> << is C's numerical bitshift operator : hu, sorry but here I used them as double-quote. Maybe too franchy notation
[12:09:01] <LeoNerd> Ah
[12:10:52] <skz81> <bss36504> Do you guys think a smart mirror with facial rec would be bad for a bathroom mirror? >> with facial recognition ? Why in a bathroom ?
[12:12:42] <bss36504> Well, the first mirror I look in, and the only one I look in every day is my bathroom mirror. Seems like a good place for a smart mmirror. Then I thought, gee it would be cool if it could detect who the person was looking at it, and serve up customized info.
[12:12:56] <bss36504> would probably need facial rec, but then I thought "camera + bathroom = bad"
[12:14:10] <bss36504> Not so much a problem for me, or even people who trust me, but connecting a device to the internet that has a camera into my bathroom is...concerning to say the least.
[12:14:32] <skz81> Yeap, probably not the most "pratical" idea, then :p your guest won't be happy with that
[12:14:37] <skz81> (and family, too)
[12:15:03] <bss36504> Too bad too, since it's pretty a pretty neat idea I think
[12:15:48] <skz81> Install some mirror in you hall, next to the door, so you can look at your beautiful hats
[12:16:11] <bss36504> ha
[12:17:16] <bss36504> Ignoring the privacy concerns, it would be super cool to get customized weather, calendar events, look at emails, etc whilst brushing your teeth, without having to login or anything
[12:19:24] <skz81> I like rather to <<meditate>> in my bathroom, so it's not really for me, but I agree some would find it cool.
[12:19:38] <skz81> you still have a vapour problem though
[12:20:00] <bss36504> There must be an antifog glass
[12:20:16] <skz81> or need some warming glass or hydrophobic coating
[12:20:56] <bss36504> yeah that's what I was thinking. I'd assume hydrophobic is easier to come by, without having to get something custom manufactured.
[12:21:05] <skz81> never saw "antifog" mirror, with or without electronic in it, so far...
[12:21:16] <bss36504> But, if the coating wears off in a short time it wouldnt be very good
[12:21:58] <bss36504> https://www.rainx.com/product/for-the-home/rain-x-bathroom-mirror-anti-fog/#.WBoaCLMY1_I
[12:22:06] <bss36504> TMYK
[12:22:11] <skz81> Yeah, you can coat with soap, ie. wash your mirror, I observed it lowers fog on it, but does not last very long :) :) :)
[12:24:28] <bss36504> On the other hand, since you're already packing a bunch of electronics into it, it wouldn't be too much of a stretch to do a humidity+temp sensor and heat the glass
[12:25:04] <bss36504> just spanning some thin nichrome over the back would probably do the trick, like in a car's back windscreen
[13:36:38] <SomeT> How do I add a timer to this code
http://hastebin.com/bexojaqiga.ino that stops, starts and sets the time on user input? (I just started learning)
[13:37:00] <cehteh> :D
[13:37:33] <SomeT> haha
[13:38:09] <SomeT> seriously need to do this shortly haha
[13:38:15] <SomeT> I know how to write a timer in C
[13:38:26] <SomeT> or C++ even its just implementing it into the right functions and such
[13:38:38] <cehteh> you want the hardware do the timekeeping
[13:38:42] <cehteh> and not mess with it
[13:39:05] <cehteh> basically start one timer at startup and keep it spinning
[13:39:34] <cehteh> then have a function to query the actual time in whatever unit (ticks?) you want
[13:40:43] <cehteh> everything else then becomes simple arithmetic, store the time when you start a timer, get the current time minus the start time gives you the time elapsed since then etc
[13:40:48] <SomeT> so when you say at startup that would go in function void setup()
[13:41:11] <SomeT> I was thinking more just do a loop
[13:41:21] <SomeT> then do two seperate functions to set and stop the time
[13:41:22] <cehteh> doesnt matter how you name it, setup/loop is arduinoism, usually a program starts in main
[13:41:23] <SomeT> or one function
[13:41:58] <cehteh> arduino has a main hidden somewhere which initializes everything , calls the users setup and then calls loop() in a loop (and some more stuff)
[13:42:21] <cehteh> what do you want to do with the timer?
[13:42:38] <SomeT> literally, just start, stop and set
[13:42:54] <cehteh> like a stopwatch?
[13:43:51] <cehteh> in arduino you can just use the millis() function to query time, it overflows every so much days (30 somewhat i think) but prolly ok for you
[13:44:17] <SomeT> yes exactly like a stopwatch
[13:44:46] <SomeT> ah nice
[13:44:49] <SomeT> https://www.arduino.cc/en/Reference/Millis
[13:44:55] <cehteh> just use millis -> back to #arduino :D
[13:45:35] <SomeT> why back?
[13:45:36] <SomeT> lol
[13:45:58] <cehteh> because thats arduino stuff and you can do it like i saied with simple arithmetic then
[13:46:18] <SomeT> ah fair enough
[13:47:19] <cehteh> doing fancier things with the timers may become more complicated, like implementing the millis() on your own, or call functions at specified times etc
[13:47:49] <LeoNerd> Prettymuch every AVR program Iwrite ends up gaining some sort of timer/delay/alarm scheduler ability in the mainloop
[13:48:27] <SomeT> lemme try and write it
[13:48:32] <SomeT> then I will see what happens
[13:50:32] <cehteh> the timer of my mµOS got somewhat complex :)
[13:50:50] <cehteh> scheduler with priority queue etc
[13:57:02] <SomeT> ok I can't figure this out
[13:57:03] <SomeT> lol
[13:57:11] <SomeT> everything I try contradicts another functionj
[13:57:21] <SomeT> mainly just copying and pasting from:
https://www.arduino.cc/en/Reference/Millis
[13:58:41] <cehteh> i dont like arduino much, ok for simple quick and dirty things, but for reliable software you beter use something else
[13:59:38] <LeoNerd> Ya most definitely
[13:59:48] <LeoNerd> for one thing, nobody in Arduino generally has any idea how to write nonblocking code
[13:59:59] <LeoNerd> Because apparently everyone is afraid of interrupts
[14:00:38] <cehteh> of course when you do it their way then i would be scared of interrupts too
[14:01:13] <cehteh> loads of wrapers and stuff .. digitalWrite is costly, often using floats etc
[14:01:16] <SomeT> can someone show me an example of how to implement this timer into my code please? not just I want the easy way (being honest) but this allows me to learn how its done and also ask more precise follow up questions in my studies
[14:01:35] <SomeT> like I got a feeling I will be sitting here all night else haha
[14:03:21] <cehteh> ah
https://github.com/arduino/Arduino/blob/master/hardware/arduino/avr/cores/arduino/wiring.c#L65
[14:03:26] <cehteh> .. racy :D
[14:04:21] <cehteh> SomeT: some global unsigned long start; .... then in loop when you read "start" or whatever from serial you do start = now;
[14:04:37] <LeoNerd> cehteh: that's not racy
[14:04:40] <LeoNerd> It turns off interrupts
[14:04:58] <SomeT> can you show me how? ;)
[14:04:59] <cehteh> and when stopped (read for serial?) you just print(now-start)
[14:05:04] <SomeT> I dunno where to even paste that code lol
[14:05:13] <cehteh> LeoNerd: it is because of that :)
[14:05:58] <cehteh> ah moment .. no its ok
[14:06:05] <cehteh> millis is calcualted in the ISR
[14:06:41] * SomeT is about to bash his head into the wall, lol
[14:06:48] <SomeT> What even is ISR?
[14:07:02] <bss36504> some dingus on electronics.se tried to tell someone to use floating point divides only in a microcontroller. I made sure to shut that down quickly
[14:07:08] <bss36504> SomeT: Interrupt service routine
[14:07:11] <cehteh> interrupt service routine
[14:07:17] <SomeT> ah makes sense, lol
[14:07:41] <bss36504> So the timer is capable of interrupting the main CPU thread, causing it too jump to an Interrupt Service Routine.
[14:07:47] <cehteh> SomeT: then dont say you know C and C++ :D
[14:07:49] <bss36504> inside the ISR, you can add code of your own
[14:08:08] <bss36504> In this case you will just want to increment a volatile global int at each call
[14:08:22] <cehteh> but .. beware of all kinds of side effects and crap .. told ya on #arduino, dont try
[14:08:23] <bss36504> then your main "thread" can access this variable
[14:08:45] <SomeT> when I said I knew it
[14:08:52] <SomeT> I know it until about pointer level
[14:08:57] <SomeT> sorry I thought I mentioned that
[14:09:08] <cehteh> thats nothing to do with pointers :D
[14:09:13] <SomeT> I know
[14:09:19] <cehteh> we talking about basic logic here
[14:09:22] <SomeT> I have learned the basics, except for arrays in C lol
[14:09:32] <SomeT> yes but its the messy code
[14:09:39] <cehteh> you meant you have learned C except the basics?
[14:09:53] <SomeT> lets just say I have learned nothing, lol ;)
[14:10:02] <cehteh> ok we getting closer
[14:10:20] * SomeT is a blank slate
[14:10:32] <SomeT> ok I know millis is a function
[14:10:40] <cehteh> well first you need formally define what your program shall do
[14:10:40] <SomeT> when I put said function into my code
[14:10:42] <SomeT> it does not work
[14:10:54] <bss36504> Are you coding for arduino?
[14:10:59] <bss36504> in the arduino IDE?
[14:11:07] <SomeT> ok, so a timer, that stops, starts, and sets the time
[14:11:10] <SomeT> yes I am
[14:11:12] <cehteh> i send him here because he pasted some native code in #arduino :D
[14:11:23] <bss36504> oh, thanks for that cehteh ;)
[14:11:24] <cehteh> so better we talk that over in arduino
[14:11:40] <SomeT> am I in the right channel? lolk
[14:11:41] <cehteh> copy pasted
[14:13:12] <bss36504> Well id say iif you are trying something in arduino that isnt related to AVR then you should ask over there. Its not that we cant help you, its that we dont like arduino :)
[14:14:23] <cehteh> its even not that i dont like it. its good for what its meant for, but thats all, and that is not so much
[15:39:54] <woz> existing design with atmega64 running at 5V. Works at 8MHz. Changed resonator to 16MHz and nothing seems to work right
[15:45:22] <LeoNerd> What was it using for a clock at 8MHz?
[15:59:01] <bss36504> did you update the fuse settings?
[16:07:37] <lochs> woz: did you set F_CPU to 16000000?
[21:17:58] <woz> bss36504 LeoNerd: updated fuse settings. traced problems down to an assembly I2C bitbanger that made hardcoded assumptions about clock ticks meaning a specific amount of time.
[22:00:08] <lochs> woz: well then it really wasn't "nothing seems to work"