<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stm32nucleo on Carmine Noviello</title><link>https://www.carminenoviello.com/tags/stm32nucleo/</link><description>Recent content in Stm32nucleo on Carmine Noviello</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 28 Aug 2016 16:15:28 +0000</lastBuildDate><atom:link href="https://www.carminenoviello.com/tags/stm32nucleo/index.xml" rel="self" type="application/rss+xml"/><item><title>Adding ethernet connectivity to a STM32-Nucleo</title><link>https://www.carminenoviello.com/2015/08/28/adding-ethernet-connectivity-stm32-nucleo/</link><pubDate>Fri, 28 Aug 2015 05:23:37 +0000</pubDate><guid>https://www.carminenoviello.com/2015/08/28/adding-ethernet-connectivity-stm32-nucleo/</guid><description>&lt;p&gt;One drawback of the Nucleo ecosystem is the lack of a version with ethernet connectivity or a dedicated shield officially supported by ST. There are 90 different STM32 MCUs available that provide an Ethernet MAC interface (this means that only an external ethernet transceiver - also called &lt;em&gt;phyter&lt;/em&gt; - and few other things are required to bring your MCU to the IoT world). STM32Cube (the HAL officially supported by ST) also provides support for &lt;a href="http://savannah.nongnu.org/projects/lwip/"&gt;lwIP&lt;/a&gt; stack. But, all the current Nucleo boards are designed with a MCU without an Ethernet interface (I think that the main reason is that only two STM32 MCUs with Ethernet MAC are available in LQFP-64 package and the Nucleo boards are designed to be pin-to-pin compatible between its releases - L0, F1, etc). This means that without a dedicated expansion shield it is impossible to add network connectivity to our Nucleo. And this is a sin considering what that MCU can do.&lt;/p&gt;</description></item><item><title>BlueNRG shield for STM32 Nucleo</title><link>https://www.carminenoviello.com/2015/03/08/bluenrg-shield-stm32-nucleo/</link><pubDate>Sun, 08 Mar 2015 15:32:51 +0000</pubDate><guid>https://www.carminenoviello.com/2015/03/08/bluenrg-shield-stm32-nucleo/</guid><description>&lt;p&gt;I recently received during a ST training day a sample of the X-NUCLEO-IDB04A1 shield. This shield is based on the BlueNRG network processor from ST and it allows to create Bluetooth Low Energy (BLE) applications using an Arduino compatible developing board. Obviously, ST designed the software for this shield to be used mainly with its Nucleo range of developing boards. In fact, all necessary libraries and examples needed to use this shield are designed to run on Nucleo-L0 and Nucleo-F4 boards using their respective HAL. However, ST still doesn&amp;rsquo;t provide official support to free GCC/Eclipse toolchains (an this is a pity&amp;hellip;), and it&amp;rsquo;s a little bit tricky to use ST demo files and BlueNRG HAL without using a commercial IDE supported by ST (IAR, TrueSTUDIO, etc).&lt;/p&gt;</description></item><item><title>How to use STM32 Nucleo serial port</title><link>https://www.carminenoviello.com/2015/03/02/how-to-use-stm32-nucleo-serial-port/</link><pubDate>Mon, 02 Mar 2015 07:17:28 +0000</pubDate><guid>https://www.carminenoviello.com/2015/03/02/how-to-use-stm32-nucleo-serial-port/</guid><description>&lt;p&gt;As we have seen in the previous tutorial about this new developing board from ST, the STM32 Nucleo provides an integrated ST Link v2.1 interface. ST Link is mainly designed to allow flashing of target MCU trough the mini-USB interface. But, it provides at least another really useful feature: a Virtual COM port. When you install the ST-Link drivers, a new device appears in your hardware devices list: the ST-Link Virtual COM port.&lt;/p&gt;</description></item><item><title>Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part III</title><link>https://www.carminenoviello.com/2015/01/16/setting-gcceclipse-toolchain-stm32nucleo-part-iii/</link><pubDate>Fri, 16 Jan 2015 07:12:39 +0000</pubDate><guid>https://www.carminenoviello.com/2015/01/16/setting-gcceclipse-toolchain-stm32nucleo-part-iii/</guid><description>&lt;aside class="callout callout--info" role="note" aria-label="Note"&gt;&#10; &lt;p class="callout__title"&gt;Note&lt;/p&gt;&#10; &lt;div class="callout__content"&gt;&lt;p&gt;&lt;strong&gt;Please, read carefully.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Thanks to the feedbacks I have received, I reached to the conclusion that it&amp;rsquo;s really hard to cover a topic like this one in the room of a blog post. So, I started writing a book about the STM32 platform. In the free book sample you can find the whole complete procedure better explained. You can download it &lt;a href="https://leanpub.com/mastering-stm32"&gt;from here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;/aside&gt;&#10;&#10;&lt;p&gt;Let&amp;rsquo;s recap what we&amp;rsquo;ve done in the two previous parts of this series. In the &lt;a href="https://www.carminenoviello.com/?p=998" title="Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part I"&gt;first part&lt;/a&gt; we&amp;rsquo;ve configured Eclipse and GCC to build applications for the ARM-Cortex platform. We&amp;rsquo;ve used the GNU ARM Eclipse plug-ins to generate a minimal yet working example (a simple blinking LED app) for our STM32 Nucleo board. Next, we&amp;rsquo;ve used the CubeMX tool from ST to generate the right initialization code for our Nucleo. Lastly, we used ST-Link Utility to upload generated binary code on the target MCU. In the &lt;a href="https://www.carminenoviello.com/?p=1256" title="Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part II"&gt;second part&lt;/a&gt; we&amp;rsquo;ve taken a deeper look in the debug topic. We&amp;rsquo;ve configured OpenOCD and GDB to allow step-by-step execution of our application on the Nucleo target MCU.&lt;/p&gt;</description></item><item><title>Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part II</title><link>https://www.carminenoviello.com/2015/01/07/setting-gcceclipse-toolchain-stm32nucleo-part-2/</link><pubDate>Wed, 07 Jan 2015 14:13:50 +0000</pubDate><guid>https://www.carminenoviello.com/2015/01/07/setting-gcceclipse-toolchain-stm32nucleo-part-2/</guid><description>&lt;aside class="callout callout--info" role="note" aria-label="Note"&gt;&#10; &lt;p class="callout__title"&gt;Note&lt;/p&gt;&#10; &lt;div class="callout__content"&gt;&lt;p&gt;&lt;strong&gt;Please, read carefully.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Thanks to the feedbacks I have received, I reached to the conclusion that it&amp;rsquo;s really hard to cover a topic like this one in the room of a blog post. So, I started writing a book about the STM32 platform. In the free book sample you can find the whole complete procedure better explained. You can download it &lt;a href="https://leanpub.com/mastering-stm32"&gt;from here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;/aside&gt;&#10;&#10;&lt;p&gt;In the &lt;a href="https://www.carminenoviello.com/?p=998" title="Setting up a GCC/Eclipse toolchain for STM32Nucleo – Part I"&gt;first part&lt;/a&gt; of this series we&amp;rsquo;ve successfully setup a minimal yet working tool-chain to develop applications for the STM32 family (we&amp;rsquo;ve especially focused on STM32Nucleo developing board). We&amp;rsquo;ve based the tool-chain over the Eclipse IDE and the GCC cross-compiler for ARM Cortex platform. We&amp;rsquo;ve also created a test project (a simple blinking LED) and uploaded it on our Nucleo using the ST-Link Utility.&lt;/p&gt;</description></item><item><title>Setting up a GCC/Eclipse toolchain for STM32Nucleo - Part I</title><link>https://www.carminenoviello.com/2014/12/28/setting-gcceclipse-toolchain-stm32nucleo-part-1/</link><pubDate>Sun, 28 Dec 2014 17:09:33 +0000</pubDate><guid>https://www.carminenoviello.com/2014/12/28/setting-gcceclipse-toolchain-stm32nucleo-part-1/</guid><description>&lt;aside class="callout callout--info" role="note" aria-label="Note"&gt;&#10; &lt;p class="callout__title"&gt;Note&lt;/p&gt;&#10; &lt;div class="callout__content"&gt;&lt;p&gt;&lt;strong&gt;Please, read carefully.&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;Thanks to the feedbacks I have received, I reached to the conclusion that it&amp;rsquo;s really hard to cover a topic like this one in the room of a blog post. So, I started writing a book about the STM32 platform. In the free book sample you can find the whole complete procedure better explained. You can download it &lt;a href="https://leanpub.com/mastering-stm32"&gt;from here&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;/aside&gt;&#10;&#10;&lt;p&gt;I recently got in my hands a new development board from STMicroelectronics: STM32Nucleo. It&amp;rsquo;s a development board based on the STM32 MCU and it is compatible with the Arduino UNO pinout. This means that it&amp;rsquo;s possible to use the hundreds of shields available for the Arduino. However this is true in theory, since the most important aspect of Arduino&amp;rsquo;s world is the software (based on libraries, examples, and so on) made for this popular platform.&lt;/p&gt;</description></item></channel></rss>