Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
I am starting to work on STM-32F103C8T6 can someone guide me if coding on STM cube IDE is better (in terms of ease and effectiveness) than integrating it with Arduino IDE
For comemrcial product development I would think your better off
sticking with ST IDE :
1) Part is ARM based and with ARM widely sold by various vendors industry
backed corporate support more robust.
2) Becuse of 1) varients abound with the peripheral makeup, everything
from simple M0 type parts up to dual core.
3) Vendors support their IDE libraries usually quite well, its their business. Arduino
open source and testing and upgrades always a bit of a crap shoot.
4) ARM core docs superb, Arduino.....OK.....
5) Need to transport ST design into FPGA solutions robbust, Arduino eh .....?
6) ARM core performance generally no comparison to Arduino.
For comemrcial product development I would think your better off
sticking with ST IDE :
1) Part is ARM based and with ARM widely sold by various vendors industry
backed corporate support more robust.
2) Becuse of 1) varients abound with the peripheral makeup, everything
from simple M0 type parts up to dual core.
3) Vendors support their IDE libraries usually quite well, its their business. Arduino
open source and testing and upgrades always a bit of a crap shoot.
4) ARM core docs superb, Arduino.....OK.....
5) Need to transport ST design into FPGA solutions robbust, Arduino eh .....?
6) ARM core performance generally no comparison to Arduino.
When choosing a bare metal platform I often consider checking if the selected uC part is supported by Proteus simulator; many here will curse this tool but it helped me a lot many times.
With this tool it is possible to simulate the interaction of the firmware with the hardware ( to a certain extent ), quite often being possible to code with no need of the hardware at each compilation. If I'm not mistaken, they provide support for some parts of the STM, not sure whether the STM8 or STM32 family.
Sorry for not elaborating further, just to avoid distracting from the original topic.
I recently did a button reading project using STM32 where in Proteus and to my surprise, it didn't work, I wasted a lot of time trying to find the error, which in fact didn't exist. When testing on physical hardware, the source code was worked perfectly.
So you should pay attention to some points like that.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
