Fix JLink SPI Dumping Tool #999
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview & Major Changes
This PR fixes the following issue: #998
The SPI flash dumping tool was unsuccessful on certain PODs that were in a particular bricked state. The PODs were less so "bricked", but in some sort of loop. This fix addresses that corner case by halting the POD before injecting the "flash forensics" firmware blob.
Testing
To test, run the command on a POD connected via JLink.
iotile hw --port 'jlink:device=nrf52' connect_direct 1 debug dump_memory --out_path spi_dump.bin --memory_region external --pause TrueIt may take a minute to download the entire flash.