STM 8 and STM32
#1
Posted 14 April 2012 - 09:09 AM
#2
Posted 14 April 2012 - 10:37 AM
#3
Posted 14 April 2012 - 11:18 AM
#4
Posted 18 July 2012 - 01:09 PM
Hi Andy,
We will initially be supporting STM8S003F3/STM8S103F3 (20TSSOP) along with the STM8S003K3/STM8S103K3 (32LQFP) chips.
Once the new standardized virtual io firmware is working well there, we'll add support for the stm32 micros (at least stm32f2/f4) and then we can look into additional STM8S modules, AVRs, etc.
That said, in theory the code from STM8S003F3/K3 should be portable to other STM8S chips (and STM32F2 and F4 can use pretty much the same code as each other too). So you're welcome to choose the best chip for the virtual IO (and any other co-proc tasks) you need.
Chris
Hey Chris
I got my netduino go which contain STM32F4 in main board while STM32F2 in shield board and in every post i am reading about STM8. I want to access registers of STM32F4 but i am not getting which header file do i have to include,which extra file i have to add in my visual studio project for accessing main board controller registers.
For example i want to run hardware timer(TIM2 of STM32F4),i saw one post mentioning about inclusion of stm8 header file,is it worth to add 8 bit micro controller file for 32 bit controller. I am so much confused please help me.
Thanks for your last help
#5
Posted 18 July 2012 - 06:43 PM
Hey Chris
I got my netduino go which contain STM32F4 in main board while STM32F2 in shield board and in every post i am reading about STM8. I want to access registers of STM32F4 but i am not getting which header file do i have to include,which extra file i have to add in my visual studio project for accessing main board controller registers.
For example i want to run hardware timer(TIM2 of STM32F4),i saw one post mentioning about inclusion of stm8 header file,is it worth to add 8 bit micro controller file for 32 bit controller. I am so much confused please help me.
Thanks for your last help
In the .NetMF (.Net Micro Framework) access to the registers is not directly available, you could write some native code to allow you access via the managed code. To do that you'd have to compile your own firmware for the Go. The Go is intended to be used with Modules which are communicated with via SPI.
When you talk EE use small words, I'm just a Software Developer
My Blog/Site and Everything Else
If my post helped you please consider pressing the "Like This" button in the bottom right-hand corner.
Oh my. So many things, so little money!!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users