-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update SMC bootloader tools #56
Update SMC bootloader tools #56
Conversation
73a5ed5
to
788aadf
Compare
788aadf
to
8ee8e8b
Compare
@stefan-b-jakobsson ready for review. I did a quick test on my machine, seems like the tools still works. |
There's a dead link to the Flash manipulation tools in doc/update-guide.md under heading "In-system update of the bootloader". |
I tested the new flash tools. They work fine as far as I can tell. I also tested to do an SMC update after updating the bootloader. One small thing I think I remember from some discussion. The dump tool prints the command you can use to save the bootloader to disk. If I remember correctly, the end address should be the actual end address + 1. |
Well spotted. Fixed. |
I have updated the BSAVE commands to include the last byte |
I think there's still a dead link in update-guide.md, at line 124. It refers to the file flash-manipulation.md that has been renamed. |
Well spotted, again. Fixed. |
This PR updates the SMC bootloader tools and information. This is mostly to include changes made in the zip version added here #53 (comment) , but, the instructions are also reorganized and cleaned up a bit.
Main changes are that these tools are better together with bootloader v3, and, they add a warning if the user attempts to e.g. install bootloader v2 if bootloader v3 is installed, causing a significant risk of bricking the x16.
Also, I took the liberty to add the pre-built bootloader .BIN files from existing bootloaders to this repo, causing that files are in one place, and that there are fewer risks involved with e.g. renaming the files.