/**
  @page Lib_DEBUG_Example  Lib_DEBUG Example
  
  @verbatim
  ******************** (C) COPYRIGHT 2015 STMicroelectronics *******************
  * @file    Lib_DEBUG/Lib_DEBUG_Example/readme.txt 
  * @author  MCD Application Team
  * @version V1.1.3
  * @date    15-December-2021
  * @brief   Description of the Lib_DEBUG Example.
  ******************************************************************************
  *
  * Copyright (c) 2015 STMicroelectronics.
  * All rights reserved.
  *
  * This software is licensed under terms that can be found in the LICENSE file
  * in the root directory of this software component.
  * If no LICENSE file comes with this software, it is provided AS-IS.
  *
  ******************************************************************************
   @endverbatim

@par 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 stm32f30x_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 stm32f30x_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 use it only when debugging the application and to
remove it from the final application code.


@par Directory contents

  - Lib_DEBUG/Lib_DEBUG_Example/stm32f30x_conf.h     Library Configuration file
  - Lib_DEBUG/Lib_DEBUG_Example/stm32f30x_it.c       Interrupt handlers            
  - Lib_DEBUG/Lib_DEBUG_Example/stm32f30x_it.h       Interrupt handlers header file
  - Lib_DEBUG/Lib_DEBUG_Example/main.c               Main program 
  - Lib_DEBUG/Lib_DEBUG_Example/main.h               Header for main.c module
  - Lib_DEBUG/Lib_DEBUG_Example/stm32f30x_ip_dbg.c   Provides all STM32F30x peripherals pointers initialization 
  - Lib_DEBUG/Lib_DEBUG_Example/stm32f30x_ip_dbg.h   Header for stm32f30x_ip_dbg.c module
  - Lib_DEBUG/Lib_DEBUG_Example/system_stm32f30x.c   STM32F30x system source file

@note The "system_stm32f30x.c" is generated by an automatic clock configuration 
      system and can be easily customized to your own configuration. 
      To select different clock setup, use the "STM32F30x_Clock_Configuration_V1.0.0.xls" 
      provided with the AN4152 package available on <a href="http://www.st.com/internet/mcu/family/141.jsp">  ST Microcontrollers </a>

      
@par Hardware and Software environment

  - This example runs on STM32F303xC and STM32F303xE Devices.
  
  - This example has been tested with STMicroelectronics STM32303C-EVAL (STM32F30x)
    evaluation board and can be easily tailored to any other supported device 
    and development board.

  - STM32303C-EVAL Set-up
       - Connect a null-modem female/female RS232 cable between the DB9 connector 
         CN8(when USART1 (EVAL_COM1) is used) and PC serial port.      

  - Hyperterminal configuration:
    - Word Length = 8 Bits
    - One Stop Bit
    - No parity
    - BaudRate = 115200 baud
    - flow control: None 


@par 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
   Projects\STM32F30x_StdPeriph_Templates
 - Open your preferred toolchain
 - Add the following files to the project source list
   - Utilities\STM32_EVAL\STM32303C_EVAL\stm32303c_eval.c
   - "stm32f30x_ip_dbg.c"
 - Rebuild all files and load your image into target memory
 - Run the example

@note Known Limitations
      This example retargets the C library printf() function to the Hyperterminal
      (C library I/O redirected).
      TrueSTUDIO Lite version does not support I/O redirection, and instead
      have do-nothing stubs compiled into the C runtime library. 
      To use printf() with TrueSTUDIO Professional version, just include the
      TrueSTUDIO Minimal System calls file "syscalls.c" provided within the toolchain.
      It contains additional code to support printf() redirection. 


 */
