Back
[04:04:27] <malinus> vsync, lol'd
[04:49:34] <antto> http://oneweekwonder.blogspot.co.uk/2014/07/bootjacker-amazing-avr-bootloader-hack.html <- much wow
[09:40:44] <vsync> even the electronics channel is better than this, 9 out of 10 times
[12:11:33] <t4nk218> hi
[15:01:52] <Jordan_U> How can I determine what value I should pass to eeprom_write_dword()? I only need to store one 32 bit value, and I won't be writing this value many times (so no wear leveling needed). Can I just pass 0 to write to the start of the eeprom data address space? If I did want to write more than just 32 bits, how would I determine the first and last addresses in the eeprom address space? Is it just 0 to the size of eeprom data space size foun
[15:14:39] <Jordan_U> I guess the "proper" solution, for my case at least, is to declare a "uint32_t EEMEM my_nv_var" and pass that to eeprom_write_dword() and eeprom_read_dword().
[17:34:30] <malinus> Jordan_U, yes, that makes it easier
[17:35:25] <malinus> Jordan_U, as far as I understand, the compiler will just pick some random (probably not random) address value, but it makes it easier to keep track of them
[17:35:44] <malinus> Jordan_U, I'm just writing to address 1 or so (but I'm also just storing one byte)