Add device provider for STM32 Nucleo development boards. #141
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
The two identifiers given for these boards are based on the ST-Link V2 attached to Nucleo F4/L4 series boards when set to both Debug+VCP and Debug+Mass storage+VCP modes available for selection from the STLinkUpgrade utility.
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.
Add new device provider and allow auto-detection of device path for STM32 Nucleo development boards.
This creates a new option of "Nucleo" in the drop-down menu for "Device type". The two USB identifiers given for these boards are based on the ST-Link V2 attached to Nucleo F4/L4 series boards when set to both Debug+VCP and Debug+Mass storage+VCP modes available for selection from the STLinkUpgrade utility. These USB identifiers allow the serial port to be detected automatically.