Closed GoogleCodeExporter closed 9 years ago
A good part of how optiboot stays small is that it doesn't have a complete list
of commands that are "legal" bootloader commands. It had the few that it
recognizes, and everything else it just says "yes, I did that."
http://code.google.com/p/arduino/issues/detail?id=368
(https://github.com/WestfW/Arduino/commit/e81c1123b624b6cac7da018c9c786700f3152b
c9 ) added a feature where if there are uart errors (ie speed mismatch), the
sketch will be started, so if the sketch operates at different than 115200, you
should be OK.
I could probably add a check for "carriage return" (which is common in many
apps, but not used by the bootloader protocol) and treat that as "quit" - that
might fit. Do you think it would be sufficient?
Original comment by wes...@gmail.com
on 24 Jan 2012 at 6:21
Thanks for the fast answer.
Unfortunately the stuff that comes in the serial port immediately after warm
start is a steady stream of binary, not text. And because it is a radio link it
does need to operate at 115200.
Is there no space to just increment a recognised packet counter, and if after,
say, 10 seconds, this counter is very low as a percentage of total characters
received, start the sketch?
Original comment by justinbe...@gmail.com
on 24 Jan 2012 at 8:04
Actually, looking more closely, it SHOULD be starting the sketch if it receives
any unrecognized command that is not immediately followed by a "space" (0x20).
Do you know what you binary data stream looks like?
Original comment by wes...@gmail.com
on 24 Jan 2012 at 4:21
you are probably right please close the issue I was told the problem was with
optiboot but now it seems it is just with stk500v2 boot loader so thus issue
should not have been lodged. sorry!
Original comment by justinbe...@gmail.com
on 24 Jan 2012 at 9:52
Closed as requested; never was an optiboot issue.
Original comment by wes...@gmail.com
on 5 Jan 2013 at 5:47
Original issue reported on code.google.com by
justinbe...@gmail.com
on 24 Jan 2012 at 1:40