STM8S-DISCOVERY - KIT
#1
Posted 12 May 2012 - 07:24 PM
#2
Posted 12 May 2012 - 07:28 PM
#3
Posted 12 May 2012 - 07:32 PM
#4
Posted 12 May 2012 - 07:47 PM
#5
Posted 12 May 2012 - 09:04 PM
Mike,Great stuff cheers both. Good thing it's a UK reseller too!
Have a look at RS Components web site - that board is £6.12 ex VAT at RS. You will have to pay shipping and VAT but it should still work out a little cheaper.
Regards,
Mark
To be or not to be = 0xFF
Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life
Follow @nevynuk on Twitter
#6
Posted 12 May 2012 - 09:36 PM
#7
Posted 13 May 2012 - 02:46 PM
Total BOCS Traveled Distance: 9708 miles | States Visited: 5
Track the Box
#8
Posted 15 May 2012 - 08:48 PM
--
Asbjørn
#9
Posted 15 May 2012 - 11:06 PM
I find there are more of these discovery boards, stm8l also, and two stm32 boards, which of all are recomended if one want for 32 and 8 chip?
And for using the swim connector, is it only to plug cables into it, and go?, or does one need other components? (seems to remember talk about stlink/2?
I want to buy various of these to try to learn about these, but wanted to be sure what to get so I can try to order most in one go.
AFAIK there are 3 Discovery boards which are most applicable to Netduino GO development:
- The STM8SDiscovery kit which features a MCU in the same series as the ones used on the RGB LED module and Pot Module in the GO! starter kit.
- The STM32F0Discovery kit, Chris announced today that the network and SD card modules would be using the same family MCU
- The STM32F4Discovery kit which features a MCU in the same series as the one on the main GO! board.
All of the discovery boards can also be used a programmer/debugger as well I believe..
#10
Posted 16 May 2012 - 09:51 AM
I've not used them much yet, but the one warning I'd give is that the toolchain for the STM8 is more of a pain to set up, including waiting a few days for a trial activation key from Cosmic for their C compiler.
Neither the STM8 or STM32 is particularly well documented for a newbie to get up and running. We're so spoiled with the Netduino and Visual Studio. When I have time (always the excuse) and if someone doesn't beat me to it, I might knock up an idiot's guide to getting started and compiling the ST demo code and writing blinky from scratch.
#11
Posted 16 May 2012 - 11:03 AM
The IAR development environment is a doddle to set up. Works straight out of the box with no additional components required. The Kickstart version is free but only allows applications up to 8K.I've not used them much yet, but the one warning I'd give is that the toolchain for the STM8 is more of a pain to set up, including waiting a few days for a trial activation key from Cosmic for their C compiler.
This is an understatement - information out there is scarce!Neither the STM8 or STM32 is particularly well documented for a newbie to get up and running. We're so spoiled with the Netduino and Visual Studio. When I have time (always the excuse) and if someone doesn't beat me to it, I might knock up an idiot's guide to getting started and compiling the ST demo code and writing blinky from scratch.
I've written some blog posts covering getting started with IAR and the STD Peripheral Library for the STM8S and also the Atollic environment for the STM32.
Interrupts
Setting up an interrupt handler.
Using Timers
Using a timer to generate a regular clock signal.
Connecting the IDE to the STM8S003
Using the ST-Link/V2 to connect the STM8S003 on breadboard to the IAR IDE.
First Project For STM8S
Creating your first project using the IAR IDE for the STM8S using the STD Peripheral Library.
STM32 Discovery Board - First Impressions
First attempt at writing a simple program using the Atollic development environment.
Arron Chapman has also written a couple of posts:
PWM
Generating a PWM signal from the STM8S.
Getting Started/Toggling a Pin
Toggling a pin using direct register access on the STM8S.
Hope people find these useful,
Mark
To be or not to be = 0xFF
Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life
Follow @nevynuk on Twitter
#12
Posted 16 May 2012 - 11:11 AM
AFAIK the on-board programmer is limited to a particular protocol (e.g. SWD-only, SWIM-only) and supports only selected microcontroller family. ST-LINK/V2 is an universal JTAG/SWD/SWIM programmer for all STM8 and STM32 devices.I'm not sure what advantage a separate ST-LINK/V2 debugger has over the one that's included on the dev boards for half the price
#13
Posted 16 May 2012 - 11:29 AM
I'm not sure what advantage a separate ST-LINK/V2 debugger has over the one that's included on the dev boards
I think some of the discovery boards can only be used as a debugger or a dev board but not at the same time, I might be totally wrong...
Plus i think the embedded ones on the discovery boards are constrained to a smaller selection of chips, whilst the stand alone debugger works with all STM8 and STM32's, but for most people a discovery board would be all that is needed...
For me personally I like having a little box that is dedicated to debugging/programming as I tend to want to debug something just as I have everything breadboarded up on a separate project, although that could be avoided if I would only concentrate on one thing at a time, ah well
When I have time (always the excuse) and if someone doesn't beat me to it, I might knock up an idiot's guide to getting started and compiling the ST demo code and writing blinky from scratch.
I too am contemplating doing something similar, as time is the ever present issue, might make sense to collaborate?
Nak.
#14
Posted 16 May 2012 - 01:38 PM
AFAIK there are 3 Discovery boards which are most applicable to Netduino GO development:
- The STM8SDiscovery kit which features a MCU in the same series as the ones used on the RGB LED module and Pot Module in the GO! starter kit.
- The STM32F0Discovery kit, Chris announced today that the network and SD card modules would be using the same family MCU
- The STM32F4Discovery kit which features a MCU in the same series as the one on the main GO! board.
Thanks, ordered all three, and the stlink/v2 due to some comments further down in the thread.
Will be interresting to try these.
--
Asbjørn
#15
Posted 16 May 2012 - 03:08 PM
I totally agree. With built-in support for SWIM debugging and supporting 8KB of flash on the STM8S chips...it's a great free resource. We've purchased the full AVR version for some of our Zigbee work...it's a nice toolset.The IAR development environment is a doddle to set up. Works straight out of the box with no additional components required. The Kickstart version is free but only allows applications up to 8K.
Not Visual Studio nice, but a lot better than others that we've tried.
Wow, those are NICE Mark. Thanks for writing those up, they should be really helpful to folks getting started with STM8S.I've written some blog posts covering getting started with IAR and the STD Peripheral Library for the STM8S and also the Atollic environment for the STM32.
Chris
#16
Posted 16 May 2012 - 08:14 PM
Thanks, just trying to help.Wow, those are NICE Mark. Thanks for writing those up, they should be really helpful to folks getting started with STM8S.
I've just added a new post on the SPI problems I had at the weekend.
Regards,
Mark
To be or not to be = 0xFF
Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life
Follow @nevynuk on Twitter
#17
Posted 17 May 2012 - 12:32 PM
I've read this a few places, but can't actually find a device that would need JTAG over SWD (for STM32) or SWIM (for STM8). The only advantage I can see is that you have one debugger in a nice plastic case rather than trailing wires from an embedded ST-LINK/V2 on one of the discovery boards.AFAIK the on-board programmer is limited to a particular protocol (e.g. SWD-only, SWIM-only) and supports only selected microcontroller family. ST-LINK/V2 is an universal JTAG/SWD/SWIM programmer for all STM8 and STM32 devices.
#18
Posted 17 May 2012 - 01:00 PM
If I am not mistaken, ST-LINK/V2 on STM32F4 Discovery board supports only SWD, so it cannot be used to program STM8 over SWIM, similarly ST-LINK on STM8S Discovery supports only SWIM, so it cannot be used to program STM32 over SWD. I have not examined the hardware in detail, so I don't know if it is just simple limitation like pins not broken out or for example a different firmware...I've read this a few places, but can't actually find a device that would need JTAG over SWD (for STM32) or SWIM (for STM8).
#19
Posted 17 May 2012 - 01:36 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users