Back
[00:17:05] <_ami_> sabor: ok, i shall read that too.
[00:18:40] <sabor> _ami_: "18.4 data modes" on page 171 in my version of the datasheet
[00:19:14] <sabor> nice drawings there :)
[00:34:48] <_ami_> sabor: indeed, nice drawings.
[00:35:07] <_ami_> best thing is separate drawing for each spi modes.
[00:35:08] <_ami_> :)
[00:35:26] <_ami_> spi wiki page has that too.. but all merged together. not that nice. :)
[02:39:19] <carabia> sup software nerds
[02:42:05] <Casper> shhhh don't yell! people are sleeping here!
[02:42:06] <Casper> :D
[02:52:52] <Frans-Willem> Any idea why my USBASP has no trouble reading things from my AtMega8, but refuses to write ?
[03:05:38] <carabia> Why's megal0maniac never around anymore
[03:06:42] <carabia> And who was that farmer from south africa
[03:27:45] <skz81> <_ami_> python binding are also pretty good. >> I was browsing the docs and came to this conclusion ! My feeling, by reading examples, is that trying to code plain C on a problem that is fondamentally Obect Oriented lead to bleeding-eye code
[03:28:31] <skz81> I mean, function naming, etc... C++ gives syntax candy about that, so does python
[03:31:18] <skz81> <Lambda_Aurigae> setting up my new lappy with a full java and java3d dev environment to try to make a simplified open source game like kerbal space program. >> you maybe should try a real game engine... I don't know Java3d, but starting from 3D primitive will make you re-invent the wheel !
[03:37:27] <theBear> Frans-Willem, err, you effed a fuse ?
[03:47:21] <_ami_> skz81: thats true
[03:47:57] <_ami_> Frans-Willem: whats the error are you getting?
[03:50:21] <carabia> skz81: "simplified" might be an indicator of said project being done for learning purposes
[03:50:22] <_ami_> why few tech blogger post their code as image. is n't it cumbersome for both reader and blogger?
[03:50:39] <_ami_> one example:
https://rpidev.wordpress.com/
[03:51:59] <carabia> too long didn't read, it was software, ergo not real engineering
[04:38:52] * skz81 slaps carabia with a large trout
[04:56:12] <sabor> _ami_: it protects against code theft ;)
[07:45:39] <megal0maniac> carabia: I'm still here
[07:45:45] <megal0maniac> Just on power saving mode :P
[07:45:52] <megal0maniac> And RikusW is the farmer dude
[12:40:22] <DexterLB> If I'm reading the datasheet correctly, the ATTiny2313A can have only one 16-bit PWM (there is no timer mode with a 0xFFFF top, so the only way is to make the second OCR register be a top)
[12:40:26] <DexterLB> Am I correct?
[16:47:28] <rue_shop3> DexterLB, sounds right
[16:47:39] <rue_shop3> there is usually 1 16 bit timer and a few 8 bits
[16:47:42] <rue_shop3> BUT
[16:47:53] <rue_shop3> sometimes the one 16 bit timer will have a few channels
[16:50:13] <LeoNerd> Some of the bigger newer ones have more 16 bits
[16:50:20] <LeoNerd> mega328PB has three of them
[21:09:01] <rue_shop3> I think the m238 has the most channels I'v seen for a non-smt chip
[21:22:55] <pseudosin> do I need to add impedance on the T3-T5 pins for a 2560, or is it built into the TC? couldn't find in the datasheet any reference one way or another
[21:33:55] <Tom_itx> is that for the alternate crystal or what?
[21:34:39] <pseudosin> it's the external input for timer/counter 3-5
[21:36:04] <Tom_itx> can't help with that one
[21:36:21] <Tom_itx> more than likely it's built in
[21:37:05] <pseudosin> yeah, kind of what I figured, the datasheet only shows the logic diagram for it though
[21:37:27] <pseudosin> couldn't find anything about tolerances
[21:37:45] <Tom_itx> even in the back on the graphs?
[21:39:37] <pseudosin> yeah, nothing specific unless it's just treated as a gpio
[21:39:49] <Tom_itx> probably