<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Freertos on Carmine Noviello</title><link>https://www.carminenoviello.com/tags/freertos/</link><description>Recent content in Freertos on Carmine Noviello</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 22 Jun 2015 05:50:14 +0000</lastBuildDate><atom:link href="https://www.carminenoviello.com/tags/freertos/index.xml" rel="self" type="application/rss+xml"/><item><title>Running FreeRTOS on a STM32Nucleo using a free GCC/Eclipse toolchain</title><link>https://www.carminenoviello.com/2015/06/22/running-freertos-stm32nucleo-free-gcceclipse-toolchain/</link><pubDate>Mon, 22 Jun 2015 05:50:14 +0000</pubDate><guid>https://www.carminenoviello.com/2015/06/22/running-freertos-stm32nucleo-free-gcceclipse-toolchain/</guid><description>&lt;p&gt;Using a micro like the STM32F4, able to run up to 160Mhz, with 512Kb of flash and about 100k of RAM, without using an operating system is a nonsense. Although it&amp;rsquo;s perfectly possible to use some forms of cooperative scheduling to execute firmware activities, basically this not convenient especially when dealing with low level events related to hardware (eg. interrupt handling) and aspects related to synchronization. As long as your firmware starts to grow, you&amp;rsquo;ll need constructs to synchronize firmware activities, like queues or semaphores. Moreover, especially when dealing with low-power devices, a busy spin (while(some condition);) it&amp;rsquo;s not the best solution if you have to fight with mAh.&lt;/p&gt;</description></item></channel></rss>