Allow Windows builds using Visual Studio. #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I mentioned in the Readme file, I am currently building using the Visual Studio 2022 release and probably
needed to install the WDK.
Also need to build for x86.
Note: This started off with has some of my experimental stuff for working with CircuitPython to see why their
sketches wipe out the Filesystem that is installed at the 1MB address
So some of the debug stuff is still in this version
teensy_loader_cli.c -
-d option dumps the ranges of memory that the .hex file is setup to upload to.
-f option filled holes in memory ranges with 0s. Can/should probably remove this as this turned out
not the reason why everything was erased
@PaulStoffregen - I decided to do a PR back to you to see if this is something you wish to pull in. Note: we could remove the extras -d -f stuff if desired. It helped figure out what was going on with CircuitPython, but others may not need. Although sort of nice to see the ranges of where things are loaded