The Attiny needs some time after it reboots for the microcontroller to have fully booted and configured its peripherals. Previously, this was reboot time was being measured incorrectly because it was starting the timeout from after when GPIO toggling messages were queued with the domain socket rather than when we got a confirmed response. As a result, the 150 ms timeout was completing only about 70ms after the reset line was pulled low. This PR makes the rebooting time more accurate to what's going on with the hardware.
The Attiny needs some time after it reboots for the microcontroller to have fully booted and configured its peripherals. Previously, this was reboot time was being measured incorrectly because it was starting the timeout from after when GPIO toggling messages were queued with the domain socket rather than when we got a confirmed response. As a result, the
150ms timeout was completing only about 70ms after the reset line was pulled low. This PR makes the rebooting time more accurate to what's going on with the hardware.