Closed majenkotech closed 9 years ago
This is because for some reason the original bootloader was written in such a way that all requests succeed even if they're not implemented. There is no way of knowing if an instruction has been implemented or not.
Now who the heck would have done that. Cheeky bastard.
*Brian
On Mon, Mar 9, 2015 at 9:28 AM, Matt Jenkins notifications@github.com wrote:
This is because for some reason the original bootloader was written in such a way that all requests succeed even if they're not implemented. There is no way of knowing if an instruction has been implemented or not.
— Reply to this email directly or view it on GitHub https://github.com/chipKIT32/PIC32-avrdude-bootloader/pull/14#issuecomment-77863011 .
:)
Just waiting on Serge to accept my pic32prog pull request and recompile the binaries, and then we can have high speed bootloader access on the boards with lots of flash (Wi-FIRE), yet full backwards compatibility with existing boards.
Oh, so sweet.
*Brian
On Mon, Mar 9, 2015 at 9:58 AM, Matt Jenkins notifications@github.com wrote:
:)
Just waiting on Serge to accept my pic32prog pull request and recompile the binaries, and then we can have high speed bootloader access on the boards with lots of flash (Wi-FIRE), yet full backwards compatibility with existing boards.
— Reply to this email directly or view it on GitHub https://github.com/chipKIT32/PIC32-avrdude-bootloader/pull/14#issuecomment-77869056 .
The baud rate change code now sends back the same baud rate that you requested so you can check if the change code is implemented in the bootloader or not.