#avr Logs

Jul 05 2019

12:01 AM rue_mohr: you know you can just write to UBBR0?
12:06 AM rue_mohr: you should also use macros for setting, clearing and checking bits
12:09 AM rue_mohr: 'U' is a better test character, because its 01010101
12:09 AM rue_mohr: you can read the frequency of it and know if your clock is out
01:04 AM nohit: he is using macros, are you blind
01:06 AM nohit: _BV() is a built-in macro
02:04 AM Maya-sama is now known as Miyu
02:13 AM arti_ is now known as arti
07:47 AM salcedo: nohit: i was setting baud rate incorrectly
09:24 AM salcedo: nohit: so that was utterly pointless. but i can turn LEDs on and off using brainfuck now :)
09:25 AM salcedo: the first few general purpose registers that start at address 0 aren't used by gcc
09:26 AM salcedo: so they make for good temp vars. to write to io registers, move data pointer up to register's mem location and write to it.
02:33 PM day__ is now known as day
02:43 PM day__ is now known as day
03:26 PM rue_mohr: _BV isn't a set/reset macro, its a macro for (1<<n)
03:52 PM nohit: so the macros you use are the right ones and everybody should use them ?
04:31 PM LeoNerd: I use the _BV() macro a lot yes
04:31 PM LeoNerd: Except oddly, much less on the new 1-series chips.. the header files seem to have a lot more constants already pre-built for that
04:43 PM nohit: yeah
04:43 PM nohit: so does xmegas
04:43 PM LeoNerd: The 1-series ATtinies are kinda just really small xmegas
04:45 PM nohit: yep
04:51 PM nohit: i wonder how the Qt licensing works for closed source embedded linux applications
07:42 PM rue_mohr: I"m not saying dont use _BV, I'm saying to avoid foo &= ~(_BV(n))
07:42 PM rue_mohr: because tooo often people screw it up, and ClearBit(foo, n) is more readable
08:03 PM vmt: CamelCase is so win32
08:23 PM rue_mohr: oh_do_you_prefer_stupid_long_names_with_underscores = Maybe;
11:33 PM day__ is now known as day