HD44780 based LCD<\/strong><\/h1>\nIn lesson 6 you have seen how to interface an I2C-based LCD to the STM32F05x. If you rather use a 14\/10-bit HD44780 interface, then check out the following example project. It implements a HD44780 driver on top of the STM standard peripheral driver library.<\/p>\n
STM32F05x\u00a0HD44780 example code<\/a><\/p>\nLIS302D\u00a0accelerometer<\/strong><\/h1>\nAn other I2C example is provided for the LIS302D accelerometer. The example shows how to setup the hardware and howto read and write from the internal registers. It uses the standard peripheral driver library, but as a reference, in comments the CMSIS implementation is shown.<\/p>\n
STM32F05x\u00a0LIS302D example code<\/a><\/p>\nAssembly programming<\/strong><\/h1>\nSome projects require parts of it to be written in assembly. This example shows how this can be done in Keil uVision in two ways. The first is how to write external functions in a *.s file and shows how parameters are passed.\u00a0The second one shows how to use inline assembly and how C-variables can be referenced.
\nBoth example programs run on the STM32F0Discovery board. For debugging the simulator is enabled by default.<\/p>\n
STM32F05x\u00a0ASM example code<\/a><\/p>\n74HC595 drivers<\/strong><\/h1>\nOne way to expand the I\/O’s of a project is using a serial in and parallel out shift register like the 74HC595<\/a>. This example project shows two targets that implement a driver for the 74HC595. The first target implements the driver with toggling GPIO pins, often called ‘bit-banging’. The second target implements the driver using the SPI interface. The beauty of this example is that the main routine remains the same, because both drivers implement the same Application Programming Interface (API)!<\/p>\nSTM32F05x 74HC595 example code<\/a><\/p>\nCustom Hardware<\/strong><\/h1>\nThis lesson gives an example where the STM32F051R8T6 microcontroller is used on a custom PCB and how it can be programmed using the SWD interface which is available on the STM32F0-Discovery board.<\/p>\n
![\"STM32F05x](\"https:\/\/ese.han.nl\/~harends\/wpsite\/wp-content\/uploads\/2014\/02\/STM32F05x-custom-hardware-schematic1-300x199.png\")
<\/a><\/p>\nSTM32F05x custom hardware lesson<\/a>
\nSTM32F05x custom hardware example code<\/a><\/p>\nUsing the High Speed Internal (HSI) 8 MHz oscillator<\/strong><\/h1>\nThe STM32F05x microcontroller has three clock sources:
\n– High Speed Internal (HSI) 8 MHz RC oscillator clock
\n– High Speed External (HSE) oscillator clock
\n– Phase-Locked Loop (PLL) clock<\/p>\n
The STM32F0-Discovery board firmware examples all use an 8 MHz HSE clock as an input for the PLL to get the microcontroller to clock at 48 MHz. This setup is done in the file ‘system_stm32f0xx.c’.
\nThis example has an updated version of this file so it sets up the HSI as an input for the PLL and still clock the microcontroller at 48 MHz. Care must be taken however, because the exact internal RC oscillator frequency varies depending on variations in temperature and operating voltage.\u00a0This new file has been generated with the Clock Configuration Tool for STM32F0xx Microcontrollers<\/a>.<\/p>\nSTM32F05x HSI example code<\/a><\/p>\nStarting a new project<\/strong><\/h1>\nAll lessons provide an example project for \u03bcVision. This lesson describes in a nutshell how to start a new project in \u03bcVision.<\/p>\n
STM32F05x\u00a0new project lesson<\/a><\/p>\nTips for debugging<\/strong><\/h1>\nWhen you try to watch the value of a variable during a debug session, you might see the following message instead of it’s actual value: <out of scope><\/strong>
\nThis most likely means that this variable has been optimized out by the compiler and is in fact not in scope of the debugger (see this link<\/a> for detailed information about optimization levels and debugging in Keil uVision).<\/p>\nThere are several things you can do:
\n– lower the optimization level.
\n– declare the variable you would like to watch static.<\/p>\n
In the following example, the variable has been declared static. When you watch this variable in a ‘Watch window’, it’s value is updated live during runtime.
\nBTW. Did you know you can also see live the values of all registers in the System Viewer Windows?<\/em>
\nHappy debugging \ud83d\ude42
\n![\"debugging\"](\"https:\/\/ese.han.nl\/~harends\/wpsite\/wp-content\/uploads\/2015\/06\/debugging-300x164.png\")
<\/a><\/p>\nOne more debugging tip.<\/em> Did you know the STM32F0 microcontroller features four breakpoints<\/strong> and two watchpoints<\/strong>? When you set more in uVision unexpected behavior (like unable to step through the source code) might be experienced. So be sure to not use more break- and watchpoints then supported by the microcontroller.<\/p>\n
\n<\/div>\n","protected":false},"excerpt":{"rendered":"This page contains even more topics that are not explicitly part of the lessons. Bit manipulation Manipulating individual bits in registers is important in microcontroller programming. A detailed discussion of bitwise operators is presented here: Bit manipulation HD44780 based LCD … Continue reading
LIS302D\u00a0accelerometer<\/strong><\/h1>\nAn other I2C example is provided for the LIS302D accelerometer. The example shows how to setup the hardware and howto read and write from the internal registers. It uses the standard peripheral driver library, but as a reference, in comments the CMSIS implementation is shown.<\/p>\n
STM32F05x\u00a0LIS302D example code<\/a><\/p>\nAssembly programming<\/strong><\/h1>\nSome projects require parts of it to be written in assembly. This example shows how this can be done in Keil uVision in two ways. The first is how to write external functions in a *.s file and shows how parameters are passed.\u00a0The second one shows how to use inline assembly and how C-variables can be referenced.
\nBoth example programs run on the STM32F0Discovery board. For debugging the simulator is enabled by default.<\/p>\n
STM32F05x\u00a0ASM example code<\/a><\/p>\n74HC595 drivers<\/strong><\/h1>\nOne way to expand the I\/O’s of a project is using a serial in and parallel out shift register like the 74HC595<\/a>. This example project shows two targets that implement a driver for the 74HC595. The first target implements the driver with toggling GPIO pins, often called ‘bit-banging’. The second target implements the driver using the SPI interface. The beauty of this example is that the main routine remains the same, because both drivers implement the same Application Programming Interface (API)!<\/p>\nSTM32F05x 74HC595 example code<\/a><\/p>\nCustom Hardware<\/strong><\/h1>\nThis lesson gives an example where the STM32F051R8T6 microcontroller is used on a custom PCB and how it can be programmed using the SWD interface which is available on the STM32F0-Discovery board.<\/p>\n
<\/a><\/p>\nSTM32F05x custom hardware lesson<\/a>
\nSTM32F05x custom hardware example code<\/a><\/p>\nUsing the High Speed Internal (HSI) 8 MHz oscillator<\/strong><\/h1>\nThe STM32F05x microcontroller has three clock sources:
\n– High Speed Internal (HSI) 8 MHz RC oscillator clock
\n– High Speed External (HSE) oscillator clock
\n– Phase-Locked Loop (PLL) clock<\/p>\n
The STM32F0-Discovery board firmware examples all use an 8 MHz HSE clock as an input for the PLL to get the microcontroller to clock at 48 MHz. This setup is done in the file ‘system_stm32f0xx.c’.
\nThis example has an updated version of this file so it sets up the HSI as an input for the PLL and still clock the microcontroller at 48 MHz. Care must be taken however, because the exact internal RC oscillator frequency varies depending on variations in temperature and operating voltage.\u00a0This new file has been generated with the Clock Configuration Tool for STM32F0xx Microcontrollers<\/a>.<\/p>\nSTM32F05x HSI example code<\/a><\/p>\nStarting a new project<\/strong><\/h1>\nAll lessons provide an example project for \u03bcVision. This lesson describes in a nutshell how to start a new project in \u03bcVision.<\/p>\n
STM32F05x\u00a0new project lesson<\/a><\/p>\nTips for debugging<\/strong><\/h1>\nWhen you try to watch the value of a variable during a debug session, you might see the following message instead of it’s actual value: <out of scope><\/strong>
\nThis most likely means that this variable has been optimized out by the compiler and is in fact not in scope of the debugger (see this link<\/a> for detailed information about optimization levels and debugging in Keil uVision).<\/p>\nThere are several things you can do:
\n– lower the optimization level.
\n– declare the variable you would like to watch static.<\/p>\n
In the following example, the variable has been declared static. When you watch this variable in a ‘Watch window’, it’s value is updated live during runtime.
\nBTW. Did you know you can also see live the values of all registers in the System Viewer Windows?<\/em>
\nHappy debugging \ud83d\ude42
\n<\/a><\/p>\nOne more debugging tip.<\/em> Did you know the STM32F0 microcontroller features four breakpoints<\/strong> and two watchpoints<\/strong>? When you set more in uVision unexpected behavior (like unable to step through the source code) might be experienced. So be sure to not use more break- and watchpoints then supported by the microcontroller.<\/p>\n
\n<\/div>\n","protected":false},"excerpt":{"rendered":"This page contains even more topics that are not explicitly part of the lessons. Bit manipulation Manipulating individual bits in registers is important in microcontroller programming. A detailed discussion of bitwise operators is presented here: Bit manipulation HD44780 based LCD … Continue reading
Assembly programming<\/strong><\/h1>\nSome projects require parts of it to be written in assembly. This example shows how this can be done in Keil uVision in two ways. The first is how to write external functions in a *.s file and shows how parameters are passed.\u00a0The second one shows how to use inline assembly and how C-variables can be referenced.
\nBoth example programs run on the STM32F0Discovery board. For debugging the simulator is enabled by default.<\/p>\n
STM32F05x\u00a0ASM example code<\/a><\/p>\n74HC595 drivers<\/strong><\/h1>\nOne way to expand the I\/O’s of a project is using a serial in and parallel out shift register like the 74HC595<\/a>. This example project shows two targets that implement a driver for the 74HC595. The first target implements the driver with toggling GPIO pins, often called ‘bit-banging’. The second target implements the driver using the SPI interface. The beauty of this example is that the main routine remains the same, because both drivers implement the same Application Programming Interface (API)!<\/p>\nSTM32F05x 74HC595 example code<\/a><\/p>\nCustom Hardware<\/strong><\/h1>\nThis lesson gives an example where the STM32F051R8T6 microcontroller is used on a custom PCB and how it can be programmed using the SWD interface which is available on the STM32F0-Discovery board.<\/p>\n
<\/a><\/p>\nSTM32F05x custom hardware lesson<\/a>
\nSTM32F05x custom hardware example code<\/a><\/p>\nUsing the High Speed Internal (HSI) 8 MHz oscillator<\/strong><\/h1>\nThe STM32F05x microcontroller has three clock sources:
\n– High Speed Internal (HSI) 8 MHz RC oscillator clock
\n– High Speed External (HSE) oscillator clock
\n– Phase-Locked Loop (PLL) clock<\/p>\n
The STM32F0-Discovery board firmware examples all use an 8 MHz HSE clock as an input for the PLL to get the microcontroller to clock at 48 MHz. This setup is done in the file ‘system_stm32f0xx.c’.
\nThis example has an updated version of this file so it sets up the HSI as an input for the PLL and still clock the microcontroller at 48 MHz. Care must be taken however, because the exact internal RC oscillator frequency varies depending on variations in temperature and operating voltage.\u00a0This new file has been generated with the Clock Configuration Tool for STM32F0xx Microcontrollers<\/a>.<\/p>\nSTM32F05x HSI example code<\/a><\/p>\nStarting a new project<\/strong><\/h1>\nAll lessons provide an example project for \u03bcVision. This lesson describes in a nutshell how to start a new project in \u03bcVision.<\/p>\n
STM32F05x\u00a0new project lesson<\/a><\/p>\nTips for debugging<\/strong><\/h1>\nWhen you try to watch the value of a variable during a debug session, you might see the following message instead of it’s actual value: <out of scope><\/strong>
\nThis most likely means that this variable has been optimized out by the compiler and is in fact not in scope of the debugger (see this link<\/a> for detailed information about optimization levels and debugging in Keil uVision).<\/p>\nThere are several things you can do:
\n– lower the optimization level.
\n– declare the variable you would like to watch static.<\/p>\n
In the following example, the variable has been declared static. When you watch this variable in a ‘Watch window’, it’s value is updated live during runtime.
\nBTW. Did you know you can also see live the values of all registers in the System Viewer Windows?<\/em>
\nHappy debugging \ud83d\ude42
\n<\/a><\/p>\nOne more debugging tip.<\/em> Did you know the STM32F0 microcontroller features four breakpoints<\/strong> and two watchpoints<\/strong>? When you set more in uVision unexpected behavior (like unable to step through the source code) might be experienced. So be sure to not use more break- and watchpoints then supported by the microcontroller.<\/p>\n
\n<\/div>\n","protected":false},"excerpt":{"rendered":"This page contains even more topics that are not explicitly part of the lessons. Bit manipulation Manipulating individual bits in registers is important in microcontroller programming. A detailed discussion of bitwise operators is presented here: Bit manipulation HD44780 based LCD … Continue reading
\nBoth example programs run on the STM32F0Discovery board. For debugging the simulator is enabled by default.<\/p>\n
74HC595 drivers<\/strong><\/h1>\nOne way to expand the I\/O’s of a project is using a serial in and parallel out shift register like the 74HC595<\/a>. This example project shows two targets that implement a driver for the 74HC595. The first target implements the driver with toggling GPIO pins, often called ‘bit-banging’. The second target implements the driver using the SPI interface. The beauty of this example is that the main routine remains the same, because both drivers implement the same Application Programming Interface (API)!<\/p>\nSTM32F05x 74HC595 example code<\/a><\/p>\nCustom Hardware<\/strong><\/h1>\nThis lesson gives an example where the STM32F051R8T6 microcontroller is used on a custom PCB and how it can be programmed using the SWD interface which is available on the STM32F0-Discovery board.<\/p>\n
<\/a><\/p>\nSTM32F05x custom hardware lesson<\/a>
\nSTM32F05x custom hardware example code<\/a><\/p>\nUsing the High Speed Internal (HSI) 8 MHz oscillator<\/strong><\/h1>\nThe STM32F05x microcontroller has three clock sources:
\n– High Speed Internal (HSI) 8 MHz RC oscillator clock
\n– High Speed External (HSE) oscillator clock
\n– Phase-Locked Loop (PLL) clock<\/p>\n
The STM32F0-Discovery board firmware examples all use an 8 MHz HSE clock as an input for the PLL to get the microcontroller to clock at 48 MHz. This setup is done in the file ‘system_stm32f0xx.c’.
\nThis example has an updated version of this file so it sets up the HSI as an input for the PLL and still clock the microcontroller at 48 MHz. Care must be taken however, because the exact internal RC oscillator frequency varies depending on variations in temperature and operating voltage.\u00a0This new file has been generated with the Clock Configuration Tool for STM32F0xx Microcontrollers<\/a>.<\/p>\nSTM32F05x HSI example code<\/a><\/p>\nStarting a new project<\/strong><\/h1>\nAll lessons provide an example project for \u03bcVision. This lesson describes in a nutshell how to start a new project in \u03bcVision.<\/p>\n
STM32F05x\u00a0new project lesson<\/a><\/p>\nTips for debugging<\/strong><\/h1>\nWhen you try to watch the value of a variable during a debug session, you might see the following message instead of it’s actual value: <out of scope><\/strong>
\nThis most likely means that this variable has been optimized out by the compiler and is in fact not in scope of the debugger (see this link<\/a> for detailed information about optimization levels and debugging in Keil uVision).<\/p>\nThere are several things you can do:
\n– lower the optimization level.
\n– declare the variable you would like to watch static.<\/p>\n
In the following example, the variable has been declared static. When you watch this variable in a ‘Watch window’, it’s value is updated live during runtime.
\nBTW. Did you know you can also see live the values of all registers in the System Viewer Windows?<\/em>
\nHappy debugging \ud83d\ude42
\n<\/a><\/p>\nOne more debugging tip.<\/em> Did you know the STM32F0 microcontroller features four breakpoints<\/strong> and two watchpoints<\/strong>? When you set more in uVision unexpected behavior (like unable to step through the source code) might be experienced. So be sure to not use more break- and watchpoints then supported by the microcontroller.<\/p>\n
\n<\/div>\n","protected":false},"excerpt":{"rendered":"This page contains even more topics that are not explicitly part of the lessons. Bit manipulation Manipulating individual bits in registers is important in microcontroller programming. A detailed discussion of bitwise operators is presented here: Bit manipulation HD44780 based LCD … Continue reading
STM32F05x 74HC595 example code<\/a><\/p>\n This lesson gives an example where the STM32F051R8T6 microcontroller is used on a custom PCB and how it can be programmed using the SWD interface which is available on the STM32F0-Discovery board.<\/p>\n STM32F05x custom hardware lesson<\/a> The STM32F05x microcontroller has three clock sources: The STM32F0-Discovery board firmware examples all use an 8 MHz HSE clock as an input for the PLL to get the microcontroller to clock at 48 MHz. This setup is done in the file ‘system_stm32f0xx.c’. STM32F05x HSI example code<\/a><\/p>\n All lessons provide an example project for \u03bcVision. This lesson describes in a nutshell how to start a new project in \u03bcVision.<\/p>\n STM32F05x\u00a0new project lesson<\/a><\/p>\n When you try to watch the value of a variable during a debug session, you might see the following message instead of it’s actual value: <out of scope><\/strong> There are several things you can do: In the following example, the variable has been declared static. When you watch this variable in a ‘Watch window’, it’s value is updated live during runtime. One more debugging tip.<\/em> Did you know the STM32F0 microcontroller features four breakpoints<\/strong> and two watchpoints<\/strong>? When you set more in uVision unexpected behavior (like unable to step through the source code) might be experienced. So be sure to not use more break- and watchpoints then supported by the microcontroller.<\/p>\n This page contains even more topics that are not explicitly part of the lessons. Bit manipulation Manipulating individual bits in registers is important in microcontroller programming. A detailed discussion of bitwise operators is presented here: Bit manipulation HD44780 based LCD … Continue reading Custom Hardware<\/strong><\/h1>\n
<\/a><\/p>\n
\nSTM32F05x custom hardware example code<\/a><\/p>\nUsing the High Speed Internal (HSI) 8 MHz oscillator<\/strong><\/h1>\n
\n– High Speed Internal (HSI) 8 MHz RC oscillator clock
\n– High Speed External (HSE) oscillator clock
\n– Phase-Locked Loop (PLL) clock<\/p>\n
\nThis example has an updated version of this file so it sets up the HSI as an input for the PLL and still clock the microcontroller at 48 MHz. Care must be taken however, because the exact internal RC oscillator frequency varies depending on variations in temperature and operating voltage.\u00a0This new file has been generated with the Clock Configuration Tool for STM32F0xx Microcontrollers<\/a>.<\/p>\nStarting a new project<\/strong><\/h1>\n
Tips for debugging<\/strong><\/h1>\n
\nThis most likely means that this variable has been optimized out by the compiler and is in fact not in scope of the debugger (see this link<\/a> for detailed information about optimization levels and debugging in Keil uVision).<\/p>\n
\n– lower the optimization level.
\n– declare the variable you would like to watch static.<\/p>\n
\nBTW. Did you know you can also see live the values of all registers in the System Viewer Windows?<\/em>
\nHappy debugging \ud83d\ude42
\n<\/a><\/p>\n
\n