STM32F0xx Standard Peripherals Firmware Library: Lib_DEBUG Example

STM32F0xx Standard Peripherals Library

previous page next page
Lib_DEBUG Example 
  ******************** (C) COPYRIGHT 2014 STMicroelectronics *******************
  * @file    Lib_DEBUG/Lib_DEBUG_Example/readme.txt 
  * @author  MCD Application Team
  * @version V1.4.0
  * @date    24-July-2014
  * @brief   Description of the Lib_DEBUG Example.
  ******************************************************************************
  *
  * Licensed under MCD-ST Liberty SW License Agreement V2, (the "License");
  * You may not use this file except in compliance with the License.
  * You may obtain a copy of the License at:
  *
  *        http://www.st.com/software_license_agreement_liberty_v2
  *
  * Unless required by applicable law or agreed to in writing, software 
  * distributed under the License is distributed on an "AS IS" BASIS, 
  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  * See the License for the specific language governing permissions and
  * limitations under the License.
  *
  ******************************************************************************
Example Description

This example demonstrates how to declare a dynamic peripherals pointers used for Debug mode.

To use Debug mode you have to add the stm32f0xx_ip_dbg.c file to your application. This creates a pointer to the peripheral structure in SRAM. Debugging consequently becomes easier and all register settings can be obtained by dumping a peripheral variable.

When the "USE_FULL_ASSERT" label is uncommented (in stm32f0xx_conf.h file), the assert_param macro is expanded and run-time checking is enabled in the firmware library code. The run-time checking allows checking that all the library functions input value lies within the parameter allowed values.

The associated program simulates wrong parameter passed to library function and the source of the error is printed on Hyperterminal (through USART).

Note:
The Debug mode increases the code size and reduces the code performance. For this reason, it is recommended to used it only when debugging the application and to remove it from the final application code.
Directory contents
Note:
The "system_stm32f0xx.c" is generated by an automatic clock configuration tool and can be easily customized to meet user application requirements. To select different clock setup, use the "STM32F0xx_Clock_Configuration_VX.Y.Z.xls" provided with the AN4055 package available on ST Microcontrollers
Hardware and Software environment
  • This example runs on STM32F0xx devices.
  • This example has been tested with STMicroelectronics STM320518-EVAL and STM32072B-EVAL including respectively STM32F051R8T6 and STM32F072VBT6 devices and can be easily tailored to any other supported device and development board
  • STM320518-EVAL Set-up
    • Connect a null-modem female/female RS232 cable between the DB9 connector CN7 and PC serial port.
  • STM32072B-EVAL Set-up
    • Connect a null-modem female/female RS232 cable between the DB9 connector CN10 and PC serial port.
  • Hyperterminal configuration:
    • Word Length = 8 Bits
    • One Stop Bit
    • No parity
    • BaudRate = 115200 baud
    • flow control: None
How to use it ?

In order to make the program work, you must do the following :

  • Copy all source files from this example folder to the template folder under Project
  • Open your preferred toolchain
  • Select STM32F051 workspace
  • If the used device is STM32F051R8T6 choose STM32F051 project
    • Add the following files to the project source list
  • If the used device is STM32F072VBT6 choose STM32F072 project
    • Add the following files to the project source list
  • Rebuild all files and load your image into target memory
  • Run the example

© COPYRIGHT STMicroelectronics

STM32L1xx Standard Peripherals Library: Footer

 

 

 For complete documentation on STM32 Microcontrollers visit www.st.com/STM32

 

previous page start next page