<Haohmaru>
hm, is that thing where the address is accessed from the debugger with an extra offset of 0x100 only for the DSU or for all peripherals?!
<Haohmaru>
User : 151 199 options.c:52 configuration_output_handler(): 0x41004012: 0b31
<Haohmaru>
is this hex?!
<Haohmaru>
0b31
<PaulFertser>
Haohmaru: no offset should be applied anywhere
<Haohmaru>
okay, so if 0b31 is hex, i guess it worked, but something else isn't right
<Haohmaru>
i've set bootloader protection, and now i can't flash a new bootloader :/
<Haohmaru>
does the "program <elf>" command do any resets?
<PaulFertser>
Haohmaru: yes, "reset init" before starting
<Haohmaru>
well, crap then
<Haohmaru>
any way to not do that?
<PaulFertser>
Haohmaru: manual "flash write_image" but why? reset init is meant to be bringing the target into a flashable state.
<Haohmaru>
because bootloader protection
<Haohmaru>
a bootloader region can be configured from the "fuses" anything from 8KB to 120KB from the beginning of flash
<Haohmaru>
then it's protected.. there's a "temporary" "BootProtDisable" NVM command, which unprotects it temporarily.. that's what i was doing with mwh commands
<Haohmaru>
but if "program" resets the chip - it reloads the boot protection settings from the fuses
<Haohmaru>
so i should use the flash syntax? i had this earlier