i think the boot loader defines a timeout where if it doesn't get commands for x seconds it signs out.
without knowing this timeout we are stuck in a world where random delays in sending commands could cause the bootloader to stop stk500 and resume normal serial. to the user this would look like stk500 timeouts forever. i have had this issue with avrdude.
we need to keep track of this timeout and make sure that the bootloader is in stk500 mode when commands are sent. ideally we keep track of programming mode and page offset so we can reset state as if nothing happened if the bootloader signs out.
i think the boot loader defines a timeout where if it doesn't get commands for x seconds it signs out.
without knowing this timeout we are stuck in a world where random delays in sending commands could cause the bootloader to stop stk500 and resume normal serial. to the user this would look like stk500 timeouts forever. i have had this issue with avrdude.
we need to keep track of this timeout and make sure that the bootloader is in stk500 mode when commands are sent. ideally we keep track of programming mode and page offset so we can reset state as if nothing happened if the bootloader signs out.