![]() This is one of the issues an all-serial-non-re-enumerating boot loader can solve, I hope – with the help of the IWDG watchdog: ![]() This may also imply that anyone using a different USB mode such as HID or MEM disk will run into this same issue. Yes, serial USB has to be running & attached for it to pick up a reset request (I’ll call it “The Maple Trick”). ![]() I’m reporting this here, though it touches on another thread, about having to call Serial.begin() in the sketch – viewtopic.php?f=3&t=703 If all of this is indeed the case, it could be a very interesting avenue to explore IMO, but for some reason there seems to be no recent development going on in this area, at least not any I could find. Lastly, the use of the Atmel STK protocol in this driver means that “avrdude” might be all that’s needed to upload firware. In particular, it looks like this approach avoids the need for any driver setup and config files on Windows, Mac OSX, and Linux, and that even pulsing D+ for a reattach may no longer be necessary, since the USB connection remains of the same type. The interesting bit is that this might avoid the DFU vs VCP (serial) complexity. Has anyone explored this serial-only USB boot loader, as alternative for the DFU approach?įurther developments, but still relatively old:
0 Comments
Leave a Reply. |