Restrictive check of protocol / flash timeouts #6

Open
opened 2020-01-03 17:20:18 +01:00 by razzor · 0 comments
Owner

When issue #5 is implemented, there is no longer a need to have an 1s timeout after which twiboot executes the application.

Currently this timeout is disabled after the first valid protocol message.
Instead use it as a protocol guard and reset (not disable) the timeout after each protocol message.

When issue #5 is implemented, there is no longer a need to have an 1s timeout after which twiboot executes the application. Currently this timeout is disabled after the first valid protocol message. Instead use it as a protocol guard and reset (not disable) the timeout after each protocol message.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: razzor/twiboot#6
No description provided.