Source code examples for LPC1114, LPC2103, STM32 and STM32CL available in Download > ARM > Examples were joined by two new projects, written for "super-fast high-end" MCUs - one for STM32F4 (new chips from ST, Cortex-M4F core with integrated floating point unit, 168MHz) and second one for LPC1769 (Cortex-M3, 120MHz).

These examples are both configured for linaro toolchain. In case of STM32F4 example it is not possible to use CodeSourcery toolchain, because it lacks libraries supporting floating point coprocessor. LPC1769 example - due to lack of high-end fancy stuff in Cortex-M3 core - can be used on any toolchain available.

STM32F4 example is configured for STM32F4DISCOVERY board, which has an embedded ST-LINK/V2 interface, so for debugging it requires development version of OpenOCD, from these available on this website in Download > Software > OpenOCD dev - at least from February 2012 (OpenOCD 0.6.0-dev-120229143915 / 0.6.0-dev-00448-gc59a441 or 64-bit version) - previous versions, including "stable" 0.5.0, don't support this interface.

It's also a good idea to remind that for proper operation of the examples GNU Coreutils have to be installed in the system (Windows installer is available in Download > Software > Coreutils). This information is provided above the examples, but some people miss it anyway... (; This time it is even more important, as Windows package of linaro toolchain does not contain make executable. It is also worth noting that Coreutils and toolchain must not be installed in a path that contains brackets (so "Program Files (x86)" in 64-bit systems is out of the question).

Taking the occasion, I'll also write that STM32F4DISCOVERY modules (and other...) can be bought from DISTORTEC for a very good price, better (that means "lower") than on allegro! If someone would be interested in buying one of these (of course with a receipt / invoice) - contact me here or there (; .

Yesterday, on the first day of February, on a very frosty Wednesday (-20deg in the morning!), my firm named DISTORTEC started. The profile of business activity is obviously obvious - electronics (; . There is already a domain and temporary website - www.distortec.com (or .pl). People / companies interested in cooperation are invited to contact me, but if you're interested in buying an ARM JTAG described on this page (currently available "in stock", only Polish description at the moment) feel free to contact me too. The purchase of JTAGs (or any future products [there are many ideas]) or services will be documented by VAT invoice, so (in case of companies) the expense reduces income and VAT tax can be deducted. For now - since there is no web shop available at this moment - you can reach me via e-mail address This e-mail address is being protected from spambots. You need JavaScript enabled to view it .

Keep your fingers crossed and - as usual - stay tuned! (;

W ramach krótkiego wstępu, powiem tylko, że osobiście nie polecam używania biblioteki standardowej dla STM32 (STM32F10x Standard Peripherals Library), z kilku powodów, z których najważniejszym jest to, że tak czy siak nie ominie nas przeczytanie manuala dla danego układu i zrozumienie zasady działania i konfiguracji danego układu peryferyjnego, więc po co dokładać sobie do tego jeszcze dokumentację biblioteki? Z biblioteką ale bez zrozumienia danego układu peryferyjnego nic nie zrobimy, w odwrotnej "konfiguracji" (bez biblioteki, z wiedzą) - można zrobić wszystko co się tylko chce. Generalnie większość zarzutów względem tej biblioteki zebrana została w tym temacie na forum elektrody.

Nie da się jednak zaprzeczyć, że są osoby dla których możliwość użycia tej biblioteki jest ważna i do nich właśnie kierowany jest ten artykuł.

After year and a half of silence I've finally decided to update example project for ARM core microcontrollers a bit. I have absolutely no idea why I waited for so long... Since last update some details of Eclipse configuration changed, so an update was definitely recommended (;

On this occasion a new example for STM32 Connectivity Line devices - STM32F105x i STM32F107x joins the group. Because the clock system in this devices is way more advanced (not to say "strange") than in "normal" STM32s, the function which calculates four parameters (two dividers and two multipliers) for two PLLs is a bit... longish (; However it does set highest achievable frequency with given quartz crystal resonator.

Main changes are configuration updates for new versions of OpenOCD (0.5.0), Eclipse (Indigo SR1) and GDB Hardware Debugging plugin (7.0.0.201109151620). In STM32 projects I've added function to configure GPIO pins mode. There are not many "visible" changes, that's why the version changes only from 1.2.0 to 1.2.1.

Example projects enjoy unflagging popularity, the most popular one - stm32_blink_led - was downloaded almost 5000 times! You can download updated versions from Download > ARM > Examples.

Almost one and a half year passed since last stable OpenOCD release... During this time 0.4.0 Windows installer was downloaded from this website over 16000 times and packages with development versions from this period - over 5000 times.

This time Windows version of the application was published - just as development versions - as a compressed .zip archive, not as .msi installer - I hope this won't be a problem for you, it's easier and faster to create such package instead of playing with installers (; . In Download > Software > OpenOCD you can download 32- and 64-bit version. Extract anywhere and you are ready to go (;

You can find highlights of major changes in NEWS file associated with this release in OpenOCD repository. There are not many of them, because this release should be treated as a stable update, without any revolutionary changes.

What next? The most anticipated feature - SWD (Serial Wire Debug) interface support, two-wire interface used in most recent Cortex chips - is in advanced stage. While you could use both "classic" JTAG and "modern" SWD in "bigger" chips like STM32 or LPC17xx, the smallest chips - like LPC11xx - can be debugged only via SWD. You can find more details on OpenOCD mailing list. Let's hope that test versions will be available soon! Stay tuned!