Closed mahiuchun closed 8 years ago
fwiw, see this project, started about the same time: https://github.com/afaerber/stlink
+1 for STM8 support. I have recently purchased a STM8AF/STM8AL Discovery kit and it uses STlinkV2 but all st- binaries here say they cannot connect to the board. Apparently, the driven chip (the STM8) uses SWD so it should work with the same framework as STM32s, even if the shipped data is different (different instruction set et al.).
I'm pretty sure the STM8 uses SWIM not SWD.
Support would be nice, but I expect it's going to be a bit different.
+1 for this issue.
+1 for supporting STM8S
+1 for STM8 support with SWIM.
I think SWIM can be supported, but we need to update firmware for F103 (ST-LINK debugger).
I think there is not a very high need for STM8. Because nobody seems to gets their hands dirty to integrate the old https://github.com/afaerber/stlink code for STM8 support as most people are using 32-bit controllers. The current structure of the texane/stlink library is not well organised and needs alot of love to actual support both STM8 and STM32.
As mentioned by the guy who have give a shot to program STM8 has discussed the following: https://github.com/afaerber/stlink/issues/2#issuecomment-94290520
As most texane/stlink
users program STM32 controllers and there is no high need for STM8 I will close this as nobody stands up to integrate/investigate it. The STM8 core is a custom SoC/uC and has nothing todo with the STM32 ARM cores M0/M0+/M3/M4/M7. Most code inside the project is based around the STM32 controllers.
That's unfortunate... +1
+1 to STM8 support
STM8: http://www.st.com/web/en/catalog/mmc/FM141/SC1244
It may be yet another MCU family that is "inaccessible" from Linux or Mac OS X :(
Fortunately, STM8 shares ST-LINK with STM32. So I guess some of the work here may be reused.
I'm new to STM8 also. And I don't want to be merely a free rider of FOSS. I post this issue hoping that it can raise some interest of STM8 from other people.