Re: Strategy for permament extended/EUI64 address writing and updating in atusb

[Werner Almesberger <werner@almesberger.net>]

Stefan Schmidt wrote:
> 2) The firmware can issue a MCU reset after the address was written
> which would force a USB reset and re-enumerate.

Or just copy EEPROM content to RAM on application start ("reset")
and on USB bus reset, and make the application that writes the
EEPROM do a USB bus reset.

That way, the address won't change while the device is in active
use, no matter how often you write to the EEPROM. And a USB bus
reset is supposed to reset the whole dependency chain anyway, so
that should be a safe moment for propagating the address change.

Oh, and for completeness, a plan B could be to attach the address
to the application binary (so you read it from Flash, not EEPROM).
Then you could use DFU. But you'd be trading one can of worms for
another one.

> The perfect solution would be to have this done [...]

Yup, once time travel finally becomes mainstream, engineers will
laugh about our clumsy work-arounds ;-)

- Werner