You are likely playing with your MDK-ARM uVision4 IDE with default examples provided by the ST firmware. But each time you try to change something you see a message saying that the project is read only. Therefor in this tutorial we will create our own project by copying an example provided in order to customize it. All the tutorial will use the STM32F3-DISCOVERY board but it should of course work with other boards. ...
If you already had some difficulties to install the IAR Embedded Workbench, let me explain how to get a time limited or a code size limited license. This tutorial will help you to remove this kind of error when trying build a project without a license: Fatal Error[LMS001]: No license found. Use the IAR License Manager to resolve the problem.[LicenseCheck:2.13.8.154, RMS:3.4.2.0085, Feature:ARM.EW.COMPILER, Version:1.00] Not so hard, but setting up IDEs is sometimes not so easy. ...
In this tutorial we will see errors discovered by playing with the IDE uVision4 MDK-Lite. Of course detailed errors and solutions are provided and will be added if more errors would be found. Simple and easy, so let’s get started. Unknow target connected If, when you tried to download code to flash memory, you encountered this error: Unknow target connected from the Debugger - Cortex-M Error popup. And just after a new popup saying: ...
Before going mad, by installing a STM32 board on your Windows OS, let’s see how to install it with a simple way. If you asked yourself what was going on, don’t worry, you are not alone in this case. Let’s see how to resolve this problem with this tutorial. How it works EDIT: here’s maybe the weird but working solution if you’ve more than one USB connection. Plug your device into your first USB connector; Install the driver; Remove your device from your first USB connector; Plug your device into your second USB connector; Oh miracle it works! ———– come back to others solutions. ...
In a previously STM32F103ZE-SK’s tutorial we created a program to initialize and enable all GPIOs on the board. This time, we will just initialize and enable default LEDs of the board, the LCD screen and the buzzer. Making them blinking. That’s why we disable the GPIO D, E and G. Indeed, there is no peripheral of LED, LCD or buzzer types on those ports. So the code is the same, except that the badprogInitOnlyBoardDefault() function is replaced with badprogInitAllGPIO(). ...
You probably won’t use directly this code, but it’s always interesting to know how to initialize all pins and activate them. So let’s see how to do this, in this STM32F103ZE-SK tutorial. We are of course free to plug or weld LEDs on some ports in order to see then blink. Explanation In the example below, an array of GPIOs is created in order to handle them easily in the code. ...
In this STM32F103ZE-SK tutorial we are going to see how to use the User button of the board by turning on and off the LCD screen. The LCD screen is on the GPIO B peripheral and on the GPIO_Pin_5 port. The User button is on the GPIO G and on the GPIO_Pin_8 port. Explanation We have: PB5 -> LCD PG8 -> User button The lightToMe() function initializes both GPIO B and G, being respectively the LCD screen and the User button. ...