Timeline for Add serial interface to ST-link clone
Current License: CC BY-SA 4.0
30 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2020 at 18:39 | history | edited | JRE | CC BY-SA 4.0 |
edited title
|
| Aug 30, 2020 at 18:32 | history | edited | Araneus0390 | CC BY-SA 4.0 |
added 323 characters in body; edited title
|
| Jun 30, 2020 at 12:00 | history | tweeted | twitter.com/StackElectronix/status/1277934944854163456 | ||
| Jun 28, 2020 at 22:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 27, 2020 at 13:50 | answer | added | GB - AE7OO | timeline score: 1 | |
| May 21, 2020 at 12:04 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 18, 2020 at 15:23 | answer | added | RCinFLA | timeline score: 1 | |
| Jun 4, 2019 at 21:38 | comment | added | Sven | Have you tried connecting pc13 to 3v3? It seems that pin is used to identify the version of the st link hardware. | |
| Feb 28, 2019 at 0:44 | comment | added | Chris Stratton | Honestly it would be worth just sitting down and re-implementing an ST-LINK in open source form. Most of the building blocks are there, but the ST-LINK scheme makes more efficient use of USB full speed than the published-source CMSIS-DAP one does, and it would be nice to have the VCP without the silly mass storage thing. And we could drive whichever pin those cute little dongles erroneously wire the target reset to, rather than having to do micro surgery on each one... | |
| Feb 27, 2019 at 23:32 | history | edited | Araneus0390 | CC BY-SA 4.0 |
added 501 characters in body
|
| Feb 27, 2019 at 23:01 | history | edited | Araneus0390 | CC BY-SA 4.0 |
added 17 characters in body
|
| Feb 27, 2019 at 22:18 | comment | added | Chris Stratton | @YehorPererva - no, that pin merely control the USB enumeration resistor to let the upgrade bootloader etc work (vs tying it permanently). It is not a mode pin for the STLINK firmware to have or not have the VCP port. That is rather determined by the firmware variant loaded. | |
| Feb 27, 2019 at 21:35 | comment | added | Araneus0390 | @duskwuff - I'm checking for traces and comparing with original ST-Link schematic on Nucleo boards. Looks like to enable the VCP, the microcontroller on ST-Link needs to provide the signal from pin 38 to start enumerating com-port. In my clone this pin is just floating. I think this is end of this "investigation" | |
| Feb 27, 2019 at 21:15 | history | edited | Araneus0390 | CC BY-SA 4.0 |
added 21 characters in body
|
| Feb 27, 2019 at 21:13 | comment | added | user39382 | @YehorPererva Using a STM32F101 instead of a '103 is a common "hack" in cheap ST-Link devices. The silicon in the two parts is identical, and the USB transceiver usually works. | |
| Feb 27, 2019 at 21:13 | comment | added | Eugene Sh. | That's simple and was told here several times - if the pins are not connected, they have no use supported by the firmware. These clone makers are cutting costs as much as it is possible. | |
| Feb 27, 2019 at 21:12 | comment | added | Araneus0390 | @duskwuff - looks like it is not a case with my clone. And, I think other problem is that my clone is made with STM32F101, meanwhile ST-Link from Nucleo is made with STM32F103 | |
| Feb 27, 2019 at 21:10 | comment | added | Araneus0390 | @ElliotAlderson - I can't find documentation for clone. | |
| Feb 27, 2019 at 20:51 | comment | added | Chris Stratton | If the VCP device isn't showing up on the host computer already (or at least in the descriptors), soldering wires won't do any good because the firmware you have in there does not support this. | |
| Feb 27, 2019 at 20:41 | comment | added | user39382 | @MarcusMüller Some of the embedded variants of the ST-Link v2 support VCP. Convincing this one that it's on the right kind of board may be tricky, though. | |
| Feb 27, 2019 at 20:23 | comment | added | Marcus Müller | electronics.stackexchange.com/a/321455/64158 says no, ST Link v2 doesn't have a USB-UART port | |
| Feb 27, 2019 at 20:22 | comment | added | Eugene Sh. | @ElliotAlderson Ah, these are for virtual COM port. Got it. | |
| Feb 27, 2019 at 20:22 | comment | added | Eugene Sh. | @YehorPererva I know what ST-Link is. But I don't think the serial TX/RX are playing any role in programming. | |
| Feb 27, 2019 at 20:21 | comment | added | Elliot Alderson | Soldering wires onto pins won't do you any good unless the software on your ST-link clone supports those pins and emulates a serial port over USB. Do you have any reason to believe that it does? What does the documentation for your clone say? | |
| Feb 27, 2019 at 20:21 | history | edited | Marcus Müller | CC BY-SA 4.0 |
deleted 11 characters in body
|
| Feb 27, 2019 at 20:21 | comment | added | Araneus0390 | ST-link is programming/debugging tool for STM32 microcontrollers. And they are compatible with official firmware for original ST-Link from STMicroelectronics. | |
| Feb 27, 2019 at 20:19 | history | edited | Araneus0390 | CC BY-SA 4.0 |
edited body
|
| Feb 27, 2019 at 20:15 | review | First posts | |||
| Feb 28, 2019 at 3:11 | |||||
| Feb 27, 2019 at 20:13 | comment | added | Eugene Sh. | What this link is used for? In any case. these "clones" are not necessarily having the same firmware as the original. So it might be the case that there is no support for it in the firmware (whatever this support is for..). | |
| Feb 27, 2019 at 20:11 | history | asked | Araneus0390 | CC BY-SA 4.0 |