Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pinaraf
Copy link
Contributor

@pinaraf pinaraf commented Feb 14, 2020

Add support for the STLink-2.1 when flashed with no mass storage

Since STLink 2.33.25, it is possible to flash the STLink in two modes:
− STM32 Debug + VCP
− STM32 Debug + Mass storage + VCP

When flashed in the first mode, the device id changes, but the behaviour remains the same.
This commit thus introduces support for this new device id. Also, fix broken installation by including the stm32.h file while I'm at it.

Since STLink 2.33.25, it is possible to flash the STLink in two modes:
- STM32 Debug + VCP
- STM32 Debug + Mass storage + VCP

When flashed in the first mode, the device id changes, but the behaviour
remains the same.
This commit thus introduces support for this new device id.
@pinaraf pinaraf force-pushed the fix-stlink-no-mass-storage branch from 326ec19 to 0f293fd Compare February 14, 2020 19:00
@pinaraf pinaraf changed the title Fix stlink no mass storage Fix stlink support with no mass storage Feb 14, 2020
@Nightwalker-87 Nightwalker-87 added this to the v1.5.2 milestone Feb 19, 2020
@Nightwalker-87
Copy link
Member

@pinaraf: Thx for your contribution!

@Nightwalker-87 Nightwalker-87 linked an issue Apr 9, 2020 that may be closed by this pull request
5 tasks
@Nightwalker-87
Copy link
Member

This PR has been manually merged with commit 8cd3069.

@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

stlink does not see the Nucleo programmer with changed type

2 participants