> What is the correct procedure for starting development?
I'm always amazed by this kind of questions, as if there was no life before Eclipse and my plug-ins.
the correct procedure for starting development is to start with an empty folder, and with your editor of choice to create the make files and all files required for your project.
if you decide to use Eclipse managed projects, you do not need to worry about the make files, they are generated for you; start with a new project, add files to it and tell Eclipse where the source files are, where the include files are and what options to use for the build.
or you can use a template and manually configure it to match your needs.
> this MDK project can not be compiled stright away. So what is the purpose of this packs items?
the CMSIS Packs are a marketing gimmick from ARM, to make you use MDK. the provided examples are generally not portable.
the only useful files I could find were the SVD files, that drive the Peripheral Viewer during debugging.
> Do I have to modidy all 6 subdir.mk
no, these files are generated with each build.
Well, regarding your answer to the first question I think that asking that inside a GNU MCU forum has implicitly the idea of using your plugin.
I followed your answers in other questions and found that your eclipse examples are available for F0 and F4 but not for F3.
I'm currently following a procedure described by Allen in https://www.element14.com/community/message/238877/l/re-guidelines-for-integrating-cubemx-code#238877 and also I'll follow the steps described in How to quickly import a STM32CubeMX project . However this are steplists given by other users, not official documentation. When I made this post, I was asking for some kind of pdf or website where I could find all this procedures that for sure have already been answered many times, and thus I guess there's some docs.
Thanks for your time and work,
yes, the point is that with or without the plug-ins, you should anyway know how to do it by hand, and the plug-ins should be only a convenience, to save you some typing/clicking.
as for the cubemx integration, I already have a solution that was used with some µOS++ tests, but if the suggestions you found worked for you, they should be ok; I know that many consider cubemx a big pain in the rear, but personally I think that generating the initialisations automatically is worth the effort to learn and integrate it.
the plan for the future templates is to create the cubemx files and then using cubemx to generate the init code. this does not fit very well into my requirement that all projects must be also generated from scriptable environments, but for gui based environments they should be fine.
I'm new to ARM development and thus I don't now the procedure.
After some struggling, I wasn't able to blink a single LED. Can you please post the link to these instructions you mentioned?
Thanks for your answer. After some struggling I finally decided to try OPENSTM32 SW. In about an hour I got a board blinking. Thanks for your time. It's a pitty that such a large work you did can not be used as easily as the other.
Good luck with your projects!
If it is the line of products that I think it is, look for an entry CPU32. The Freescale parts from that series were commonly used in engine controllers and it is quite likely to provide your solution. The other means would be just to use 68000 as the selection.
> Freescale ... 68000 ...
I don't see how this is relevant for a STM32F3 project.
I recently installed GNU MCU plugin for eclipse. I also created a project, here came the first problem, as I own a STM32F334 dev board but the project creator didn't allow this dev board nor didn't have my MCU (STM32F334R8) available for chossing when creating the project. I simply selected stm32f30X. I compiled and flashed this first blinky project and... surprise it didn't work. Of course my config must be wrong, LED pin config and/or clock config and even other items I didn't think about. I also came through the Packs Manager and found some items named after my dev board, like:
This item looks just perfect, however somewhere I saw that this MDK project can not be compiled stright away. So what is the purpose of this packs items? Maybe looking at them and copying?
Also I was able to open some device config headers:
Is this file intended to be swapped with my initial stm32f30x.h? Is there any possibility to select all this Packs Manager installed modules from the project creator wizard?
So as you see I need some guidance in what are the steps to be performed to get a working blinky project with a target device different from the wizard available devices, as seen:
EDIT: I got
from Packs Manager and copied to the folders within the (). Now I think I have to modify the makefile in order to define the proper variables to be used in cmsis_device.h. Do I have to modidy all 6 subdir.mk or is there any better way of doing it?
Thank you very much for your support,