Back
[00:48:52] <heuiou890> hii
[00:49:02] <Casper> o/
[01:46:07] <rtcg72a> Hi, has anyone programmed avr devices from the raspberry pi before? does anyone know a thing or two about the linuxspi module?
[05:18:33] <guanche> guys, have you ever happened to wind wire arround a magnet? I wonder what would be the difference between it and the same winding arround and iron core, if willing to make another magnet pass perpendicular to the core
[05:18:40] <guanche> in terms of electricity generation
[13:44:05] <stanreg> I'm looking for some guidance as to what approaches would be preferable. Thinking of using: AVR + ext. flash mem. (i2c) + Wifi shield (ESP8266).
[13:44:05] <stanreg> Goal is: (1) AVR creates a filesystem (fat12?) on the ext. flash mem. (2) AVR continuously monitors/logs on the ext. flash mem. in a .dat file. (3) AVR scans for a preconfigured WiFi AP by using the ESP8266. Upon finding the AP, it connects to it, and then sets up an FTP server hosting the filesystem.
[13:44:05] <stanreg> What would be the most foolproof path to accomplishing this?
[13:50:46] <Casper> the hardest part for your project is the ftp server
[13:51:41] <Casper> so start by that
[13:53:40] <LeoNerd> FTP? It isn't 1970 any more
[13:53:50] <LeoNerd> Use HTTP PUT. It's much nicer and simpler
[14:43:53] <stanreg> LeoNerd, pardon my noobiness, by HTTP PUT, you mean to say that I can list the files on the FS onto an HTTP page, and then provide them as the user clicks on a downloadable link?
[14:44:11] <stanreg> And that is simpler than an ftp?
[14:45:08] <LeoNerd> Definitely
[14:45:15] <Tom_itx> i do
[14:45:23] <LeoNerd> FTP requires two socket connections; doesn't even standardise a way to list files
[14:45:28] <LeoNerd> FTP needs to die already
[14:45:41] <Tom_itx> naw
[14:45:50] <Tom_itx> let's keep it alive for posterity
[16:12:54] <tpw_rules> what are the three GPIOR in the i/o space?
[16:13:06] <tpw_rules> on the attiny85v. they link to the page abotu the regsiter file
[16:13:54] <Xark> tpw_rules: Sounds like GPIO?
[16:14:08] <tpw_rules> they aren't PIN or PORT
[16:14:24] <tpw_rules> do they just not apply to the tiny?
[16:19:52] <LeoNerd> I've often wondered about those myself
[16:20:02] <tpw_rules> seems like it's just extra space for you to do whatever with
[16:20:02] <LeoNerd> I don't think they're attached to any hardware
[16:21:23] <tpw_rules> welp that's good news. i can shave a cycle off my interrupt re-vector routine
[16:21:40] <LeoNerd> :)
[16:22:14] <Xark> Hmm "In the I/O space, it is possible to directly manipulate individual bits in addresses $00 up to $1F. In the ATtiny24, this includes GPIOR0, GPIOR1, and GPIOR2, which an avr-gcc developer is free to manually allocate however (s)he sees fit.
[16:22:16] <Xark> It also includes several special-function registers. The developer may determine that some of those special-function registers control peripheral features that (s)he doesn't intend to use. However, modifying some of those registers may cause unintended side-effects. (For example, consider the PRR register, located at address $00). After careful consideration, the developmer may determine...
[16:22:17] <Xark> ...that some of those registers may be modifiable without causing unintended side effects. The developer is then free to use any of those unused registers to allocate additional bit-addressable variables."
[16:22:41] <tpw_rules> what's wrong with cbr and sbr
[16:22:55] <tpw_rules> they're faster
[16:23:38] <tpw_rules> oh i guess not in tinyavr
[16:23:42] <tpw_rules> tinyavr == attiny right?
[16:30:11] <Xark> tpw_rules: Sounds like you can from attiny pdf "I/O Registers within the address range 0x00 - 0x1F are directly bit-accessible using the SBI and CBI instructions. In these registers, the value of single bits can be checked by using the SBIS and SBIC instructions"
[16:35:55] <tpw_rules> well you can also do sbrc
[16:36:13] <tpw_rules> i'm not sure what the advantage of i/o registers is unless you've run out of regular ones
[16:37:23] <Xark> tpw_rules: Yeah, that seems to be the consensus.
[16:37:47] <Xark> Not super useful unless you are desperate for a few bit flags.
[16:38:04] <LeoNerd> But more likely on a tiny
[16:39:14] <Xark> Yeah, not "useless". :)
[19:09:44] <chrime> Hi everyone
[19:15:35] <Lambda_Aurigae> hi chrime
[20:15:58] <chrime> how's everything going ?
[20:17:48] <chrime> hi asteve