Writing new documentations.

Author: suikan4github

Doxyfile

@@ -1252,46 +1252,6 @@ USE_HTAGS              = NO
 
 VERBATIM_HEADERS       = YES
 
-# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the
-# clang parser (see:
-# http://clang.llvm.org/) for more accurate parsing at the cost of reduced
-# performance. This can be particularly helpful with template rich C++ code for
-# which doxygen's built-in parser lacks the necessary type information.
-# Note: The availability of this option depends on whether or not doxygen was
-# generated with the -Duse_libclang=ON option for CMake.
-# The default value is: NO.
-
-CLANG_ASSISTED_PARSING = NO
-
-# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS
-# tag is set to YES then doxygen will add the directory of each input to the
-# include path.
-# The default value is: YES.
-# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
-
-CLANG_ADD_INC_PATHS    = YES
-
-# If clang assisted parsing is enabled you can provide the compiler with command
-# line options that you would normally use when invoking the compiler. Note that
-# the include paths will already be set by doxygen for the files and directories
-# specified with INPUT and INCLUDE_PATH.
-# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
-
-CLANG_OPTIONS          =
-
-# If clang assisted parsing is enabled you can provide the clang parser with the
-# path to the directory containing a file called compile_commands.json. This
-# file is the compilation database (see:
-# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the
-# options used when the source files were built. This is equivalent to
-# specifying the -p option to a clang tool, such as clang-check. These options
-# will then be passed to the parser. Any options specified with CLANG_OPTIONS
-# will be added as well.
-# Note: The availability of this option depends on whether or not doxygen was
-# generated with the -Duse_libclang=ON option for CMake.
-
-CLANG_DATABASE_PATH    =
-
 #---------------------------------------------------------------------------
 # Configuration options related to the alphabetical class index
 #---------------------------------------------------------------------------

docs/BAREMETAL.md

@@ -0,0 +1,34 @@
+# Building for the bare metal target
+
+In this file, we explain how to build your code for the bare metal target. 
+In this case, the word bare metal means the Raspberry Pi Pico or Pico2. 
+
+We see two ways to build 
+- CLI ( Command Line Interface )
+- VS Code ( Visual Studio Code )
+
+## Configuration and building on CLI
+To build the program for the Raspberry Pi Pico, run the following commands : 
+```sh
+cmake -B build -S . \
+-DCMAKE_C_COMPILER=/usr/bin/arm-none-eabi-gcc \
+-DCMAKE_CXX_COMPILER=/usr/bin/arm-none-eabi-g++
+cmake --build build --target all
+```
+
+In the case you want to build the program for the Raspberry Pi Pico2, you need to define the variables PICO_PLATFORM and PICO_BOARD. 
+
+```sh
+cmake -B build -S . \
+-DPICO_PLATFORM=rp2350 -DPICO_BOARD=pico2 \
+-DCMAKE_C_COMPILER=/usr/bin/arm-none-eabi-gcc \
+-DCMAKE_CXX_COMPILER=/usr/bin/arm-none-eabi-g++ 
+cmake --build build --target all
+```
+
+## Configuration and building on VS Code
+![](../image/cmake-ext.png)
+![](../image/selecting-kit.png)
+## How to run the application
+
+## How to run the test

docs/WINLIN.md

@@ -0,0 +1,26 @@
+# Building for the bare metal target
+
+In this file, we explain how to build your code for the bare metal target. 
+In this case, the word bare metal means the Raspberry Pi Pico or Pico2. 
+
+We see two ways to build 
+- CLI ( Command Line Interface )
+- VS Code ( Visual Studio Code )
+
+## Configuration and building on CLI
+
+```sh
+cmake -B build -S . \
+-DCMAKE_C_COMPILER=gcc \
+-DCMAKE_CXX_COMPILER=g++
+cmake --build build --target all
+```
+
+
+
+
+## Configuration and building on VS Code
+
+## How to run the application
+
+## How to run the test