Rowley crossworks free download

This time, I decided to create a project and have it managed by the git source control software. Furthermore, I have made it available in a public repository so that others can use it and so that I can easily clone or download a copy as a starter. Upgrading settings or library versions is now trackable and I will be able to go back and check out previous versions if needed.

Rather than retain the complicated folder structure used by the ST Standard Peripheral Libraries, it just copies all of the CMSIS headers into one place and all the library files into another. Now there are fewer paths to keep track of and everything is much neater. The version of Crossworks used for this project is 2. Crossworks does not use a makefile or linker script for its builds. This is a little annoying and reduces the general usefulness of the starter project for other development environments.

Still, I have listed the project settings below so that you can see how everything is configured. This just gives more memory so it is unlikely to be a big problem in most cases.

The STM32F4 devices are all reasonably similar. The internal oscillator on the STM32F4 is used because I want the project to be more portable and there is no need for any better accuracy in my project.

The processor is running at 72MHz as a reasonable compromise between performance and current consumption. On the micromouse, it is turned on at the start of every systick event and turned off at the end. That way the brightness of the LED serves as a guide to system load and if it is ever on or off continuously, I know the code has crashed.

Here I just toggle the LED at each tick. A global boolean, crashed, lets me override the status LED behaviour and will be useful elsewhere in the micromouse code.

There is also a software timing-loop delay function that can count off microseconds. This is a bit counter so it will not overflow for over hours. Plenty for my purposes. By default, Crossworks eliminates unused code so it is safe to allow all the libraries to be built.

Only the functions used by the program will be included in the binary image downloaded to the target. The stack for the STM32F4 is set to a size of The default stack size in Crossworks is only bytes which is pretty small. These STM32F4 devices have a lot of available memory so there is no reason to be mean.

This is needed in any production code or the startup routines will sit in an endless loop, waiting for the debugger to connect. I define it for both debug and release configurations just because it annoys me otherwise.

However, doing do may be the reason why, sometimes, I am unable to get easy control of the target. I cannot help but feel this is a bit of a hack but I am sure there is good reason for it. It would be a shame not to use it or, worse, to forget to turn it on and wonder why the code ran so poorly.

On the subject of floating point, I have enabled the use of floating point in printf. While many frown upon printf and its related functions for their bloat and slowness, this is a fast processor with plenty of code memory.

Note that printf is useless without a way to get characters off the chip but that is a problem for another post.

By the time you read this, I may have sorted that out. As will getchar , putchar and others. I like my code to be kept reasonably neat and tidy so I have a copy of astyle installed on my desktop machine.

Crossworks allows an external executable to be called at several stages during the build. I call astyle just before the link. It runs through all the files and reformats them according to my preferred style. This is very handy when you are using a source control system as it is pretty annotying to have the repository filled with whitespace changes. Of course, you probably do not have astyle installed so you will want to remove this option. Sorry for your loss.

For some reason, Crossworks does not assume anything at all about project include directories and will not be able to find header files even if they are in the same folder as the source files. To make all that happy, the following three paths are added to the user include directories:. There is no option to convert or import a GCC linker script. I think the messages are just defined in case when there is a error.

The program itself does not give any message, just a perfect build and I did had error befor, when I was creating the linker script. Just take al look to the configuration itself please. Is that a standard linker file? If so I doubt there is anything wrong with it. Are you building for the Olimex board? Try if you are able to debug with gdb, if so, then something is wrong with my hardware what i doubt. Like i said; all the files of freertos in crossworks is standard, accept the linker script.