Skip to content

Fix svl script #137

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 6 commits into from
Mar 9, 2020
Merged

Fix svl script #137

merged 6 commits into from
Mar 9, 2020

Conversation

nseidle
Copy link
Member

@nseidle nseidle commented Feb 28, 2020

This adds back serial exception printing.

It also adds a few helper texts:

image

Below - when COM is valid but the target fails to respond to the 'enter bootload' command.
image

Below - verbose output when COM is valid but target fails to respond:
image

@nseidle nseidle mentioned this pull request Feb 28, 2020
Closed
@oclyke
Copy link
Contributor

oclyke commented Mar 2, 2020 •
edited
Loading

@nseidle Thanks!

  • Seems to be a typo in Bin file blank.bin does notexits
  • When the target fails to enter bootload mode... this could also mean that the SVL is not running on the board. Should we add a message like Verify right COM port is selectedand that your board has the SVL bootloader (or is that TMI for the user?

@nseidle
Copy link
Member Author

nseidle commented Mar 3, 2020

Good typo eyes. Fixed. And I'm not opposed to it.

Fixes in place. I added a version number to verbose output. Exe has been compiled.

image

@oclyke oclyke merged commit 48b563c into master Mar 9, 2020
@oclyke oclyke deleted the fix_svl_script branch March 9, 2020 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nseidle @oclyke