sysmocom
/
openblt
11
0
Fork 0
Code Issues Pull Requests Releases Activity

Refs# 312. Restructured the modules in the OpenBLT doxygen documentation. 

git-svn-id: https://svn.code.sf.net/p/openblt/code/trunk@259 5dc33758-31d5-4daf-9ae8-b24bf3d40d73
This commit is contained in:
Frank Voorburg 2017-05-23 17:01:20 +00:00
parent 71449427e3
commit d6046d1598
83 changed files with 476 additions and 97 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
Doc/doxygen/images/OpenBLT/openblt_architecture.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 76 KiB

11
Target/Demo/ARM7_LPC2000_Olimex_LPC_L2294_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARM7_LPC2000_Olimex_LPC_L2294_GCC User Program
\brief User Program.
\ingroup ARM7_LPC2000_Olimex_LPC_L2294_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:arm7_lpc2000.
*/

5
Target/Demo/ARM7_LPC2000_Olimex_LPC_L2294_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARM7_LPC2000_Olimex_LPC_L2294_GCC Demo for Olimex LPC-L2294/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex LPC-L2294 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://feaser.com/openblt/doku.php?id=manual:demos:olimex_lpc_l2294_gcc.
*/

11
Target/Demo/ARMCM0_STM32F0_Discovery_STM32F051_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM0_STM32F0_Discovery_STM32F051_GCC User Program
\brief User Program.
\ingroup ARMCM0_STM32F0_Discovery_STM32F051_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm0_stm32.
*/

4
Target/Demo/ARMCM0_STM32F0_Discovery_STM32F051_GCC/demo.dox
View File

@ -1,8 +1,10 @@
/**
\defgroup ARMCM0_STM32F0_Discovery_STM32F051_GCC Demo for STM32F0-Discovery/GCC
\ingroup Demos
\brief Preconfigured programs for the STM32F0-Discovery board and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:stm32f0_discovery_gcc.
*/

11
Target/Demo/ARMCM0_STM32F0_Discovery_STM32F051_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM0_STM32F0_Discovery_STM32F051_IAR User Program
\brief User Program.
\ingroup ARMCM0_STM32F0_Discovery_STM32F051_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm0_stm32.
*/

5
Target/Demo/ARMCM0_STM32F0_Discovery_STM32F051_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM0_STM32F0_Discovery_STM32F051_IAR Demo for STM32F0-Discovery/IAR
\ingroup Demos
\brief Preconfigured programs for the STM32F0-Discovery board and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:stm32f0_discovery_iar.
*/

11
Target/Demo/ARMCM0_STM32F0_Nucleo_F091RC_GCC/Prog/prog.dox
View File

@ -1,5 +1,14 @@
/**
\defgroup Prog_ARMCM0_STM32F0_Nucleo_F091RC_GCC User Program
\brief User Program.
\ingroup ARMCM0_STM32F0_Nucleo_F091RC_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm0_stm32.
*/

4
Target/Demo/ARMCM0_STM32F0_Nucleo_F091RC_GCC/demo.dox
View File

@ -1,8 +1,10 @@
/**
\defgroup ARMCM0_STM32F0_Nucleo_F091RC_GCC Demo for Nucleo-F091RC
\ingroup Demos
\brief Preconfigured programs for the Nucleo-F091RC and the GNU ARM GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:nucleo_f091rc_gcc.
*/

11
Target/Demo/ARMCM0_XMC1_XMC1400_Boot_Kit_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM0_XMC1_XMC1400_Boot_Kit_GCC User Program
\brief User Program.
\ingroup ARMCM0_XMC1_XMC1400_Boot_Kit_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm0_xmc1.
*/

5
Target/Demo/ARMCM0_XMC1_XMC1400_Boot_Kit_GCC/demo.dox
View File

@ -1,9 +1,10 @@
/**
\defgroup ARMCM0_XMC1_XMC1400_Boot_Kit_GCC Demo for XMC1400 Boot Kit/GCC
\ingroup Demos
\brief Preconfigured programs for the Infineon XMC1400 Boot Kit board and the Dave 4
development environment, which is based on the ARM GCC toolchain.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:infineon_xmc1400_boot_kit_gcc.
*/

11
Target/Demo/ARMCM0_XMC1_XMC1400_Boot_Kit_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM0_XMC1_XMC1400_Boot_Kit_IAR User Program
\brief User Program.
\ingroup ARMCM0_XMC1_XMC1400_Boot_Kit_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm0_xmc1.
*/

5
Target/Demo/ARMCM0_XMC1_XMC1400_Boot_Kit_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM0_XMC1_XMC1400_Boot_Kit_IAR Demo for XMC1400 Boot Kit/IAR
\ingroup Demos
\brief Preconfigured programs for the Infineon XMC1400 Boot Kit board and the IAR compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:infineon_xmc1400_boot_kit_iar.
*/

11
Target/Demo/ARMCM3_EFM32_Olimex_EM32G880F128STK_Crossworks/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_EFM32_Olimex_EM32G880F128STK_Crossworks User Program
\brief User Program.
\ingroup ARMCM3_EFM32_Olimex_EM32G880F128STK_Crossworks
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_efm32.
*/

5
Target/Demo/ARMCM3_EFM32_Olimex_EM32G880F128STK_Crossworks/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_EFM32_Olimex_EM32G880F128STK_Crossworks Demo for Olimex EM-32G880F128-STK/Crossworks
\ingroup Demos
\brief Preconfigured programs for the Olimex EM-32G880F128-STK and the Crossworks IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_em32g880f128stk_crossworks.
*/

11
Target/Demo/ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC User Program
\brief User Program.
\ingroup ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_efm32.
*/

5
Target/Demo/ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_EFM32_Olimex_EM32G880F128STK_GCC Demo for Olimex EM-32G880F128-STK/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex EM-32G880F128-STK and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_em32g880f128stk_gcc.
*/

11
Target/Demo/ARMCM3_EFM32_Olimex_EM32G880F128STK_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_EFM32_Olimex_EM32G880F128STK_IAR User Program
\brief User Program.
\ingroup ARMCM3_EFM32_Olimex_EM32G880F128STK_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_efm32.
*/

5
Target/Demo/ARMCM3_EFM32_Olimex_EM32G880F128STK_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_EFM32_Olimex_EM32G880F128STK_IAR Demo for Olimex EM-32G880F128-STK/IAR
\ingroup Demos
\brief Preconfigured programs for the Olimex EM-32G880F128-STK and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_em32g880f128stk_iar.
*/

11
Target/Demo/ARMCM3_LM3S_EK_LM3S6965_Crossworks/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_LM3S_EK_LM3S6965_Crossworks User Program
\brief User Program.
\ingroup ARMCM3_LM3S_EK_LM3S6965_Crossworks
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_lm3s.
*/

5
Target/Demo/ARMCM3_LM3S_EK_LM3S6965_Crossworks/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_LM3S_EK_LM3S6965_Crossworks Demo for Texas Instruments EK-LM3S6965/Crossworks
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments EK-LM3S6965 and the Crossworks IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:ek_lm3s6965_crossworks.
*/

11
Target/Demo/ARMCM3_LM3S_EK_LM3S6965_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_LM3S_EK_LM3S6965_GCC User Program
\brief User Program.
\ingroup ARMCM3_LM3S_EK_LM3S6965_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_lm3s.
*/

5
Target/Demo/ARMCM3_LM3S_EK_LM3S6965_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_LM3S_EK_LM3S6965_GCC Demo for Texas Instruments EK-LM3S6965/GCC
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments EK-LM3S6965 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:ek_lm3s6965_gcc.
*/

11
Target/Demo/ARMCM3_LM3S_EK_LM3S6965_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_LM3S_EK_LM3S6965_IAR User Program
\brief User Program.
\ingroup ARMCM3_LM3S_EK_LM3S6965_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_lm3s.
*/

5
Target/Demo/ARMCM3_LM3S_EK_LM3S6965_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_LM3S_EK_LM3S6965_IAR Demo for Texas Instruments EK-LM3S6965/IAR
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments EK-LM3S6965 and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:ek_lm3s6965_iar.
*/

11
Target/Demo/ARMCM3_LM3S_EK_LM3S8962_Crossworks/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_LM3S_EK_LM3S8962_Crossworks User Program
\brief User Program.
\ingroup ARMCM3_LM3S_EK_LM3S8962_Crossworks
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_lm3s.
*/

5
Target/Demo/ARMCM3_LM3S_EK_LM3S8962_Crossworks/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_LM3S_EK_LM3S8962_Crossworks Demo for Texas Instruments EK-LM3S8962/Crossworks
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments EK-LM3S8962 and the Crossworks IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:ek_lm3s8962_crossworks.
*/

11
Target/Demo/ARMCM3_LM3S_EK_LM3S8962_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_LM3S_EK_LM3S8962_GCC User Program
\brief User Program.
\ingroup ARMCM3_LM3S_EK_LM3S8962_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_lm3s.
*/

5
Target/Demo/ARMCM3_LM3S_EK_LM3S8962_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_LM3S_EK_LM3S8962_GCC Demo for Texas Instruments EK-LM3S8962/GCC
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments EK-LM3S8962 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:ek_lm3s8962_gcc.
*/

11
Target/Demo/ARMCM3_LM3S_EK_LM3S8962_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_LM3S_EK_LM3S8962_IAR User Program
\brief User Program.
\ingroup ARMCM3_LM3S_EK_LM3S8962_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_lm3s.
*/

5
Target/Demo/ARMCM3_LM3S_EK_LM3S8962_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_LM3S_EK_LM3S8962_IAR Demo for Texas Instruments EK-LM3S8962/IAR
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments EK-LM3S8962 and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:ek_lm3s8962_iar.
*/

11
Target/Demo/ARMCM3_STM32F1_Nucleo_F103RB_GCC/Prog/prog.dox
View File

@ -1,5 +1,14 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Nucleo_F103RB_GCC User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Nucleo_F103RB_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Nucleo_F103RB_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Nucleo_F103RB_GCC Demo for Nucleo-F103RB
\ingroup Demos
\brief Preconfigured programs for the Nucleo-F103RB and the GNU ARM GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:nucleo_f103rb_gcc.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32H103_Crossworks/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32H103_Crossworks User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32H103_Crossworks
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32H103_Crossworks/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32H103_Crossworks Demo for Olimex STM32-H103/Crossworks
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-H103 and the Crossworks IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32h103_crossworks.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32H103_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32H103_GCC User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32H103_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32H103_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32H103_GCC Demo for Olimex STM32-H103/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-H103 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32h103_gcc.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32H103_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32H103_IAR User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32H103_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32H103_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32H103_IAR Demo for Olimex STM32-H103/IAR
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-H103 and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32h103_iar.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_Crossworks/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32P103_Crossworks User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32P103_Crossworks
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_Crossworks/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32P103_Crossworks Demo for Olimex STM32-P103/Crossworks
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-P103 and the Crossworks IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32p103_crossworks.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32P103_GCC User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32P103_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32P103_GCC Demo for Olimex STM32-P103/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-P103 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32p103_gcc.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32P103_IAR User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32P103_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32P103_IAR Demo for Olimex STM32-P103/IAR
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-P103 and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32p103_iar.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_Keil/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimex_STM32P103_Keil User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimex_STM32P103_Keil
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimex_STM32P103_Keil/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimex_STM32P103_Keil Demo for Olimex STM32-P103/Keil
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-P103 and the Keil MDK toolchain.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32p103_keil.
*/

11
Target/Demo/ARMCM3_STM32F1_Olimexino_STM32_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F1_Olimexino_STM32_GCC User Program
\brief User Program.
\ingroup ARMCM3_STM32F1_Olimexino_STM32_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32.
*/

5
Target/Demo/ARMCM3_STM32F1_Olimexino_STM32_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F1_Olimexino_STM32_GCC Demo for Olimexino-STM32/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimexino-STM32 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimexino_stm32_gcc.
*/

11
Target/Demo/ARMCM3_STM32F2_Olimex_STM32P207_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM3_STM32F2_Olimex_STM32F207_GCC User Program
\brief User Program.
\ingroup ARMCM3_STM32F2_Olimex_STM32F207_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm3_stm32f2.
*/

5
Target/Demo/ARMCM3_STM32F2_Olimex_STM32P207_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM3_STM32F2_Olimex_STM32F207_GCC Demo for Olimex STM32-P207/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-P207 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32p207_gcc.
*/

11
Target/Demo/ARMCM4_STM32F3_Nucleo_F303K8_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_STM32F3_Nucleo_F303K8_GCC User Program
\brief User Program.
\ingroup ARMCM4_STM32F3_Nucleo_F303K8_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_stm32f3.
*/

5
Target/Demo/ARMCM4_STM32F3_Nucleo_F303K8_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM4_STM32F3_Nucleo_F303K8_GCC Demo for Nucleo-F303K8
\ingroup Demos
\brief Preconfigured programs for the Nucleo-F303K8 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:nucleo_f303k8_gcc.
*/

11
Target/Demo/ARMCM4_STM32F4_Olimex_STM32E407_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_STM32F4_Olimex_STM32E407_GCC User Program
\brief User Program.
\ingroup ARMCM4_STM32F4_Olimex_STM32E407_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_stm32.
*/

5
Target/Demo/ARMCM4_STM32F4_Olimex_STM32E407_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM4_STM32F4_Olimex_STM32E407_GCC Demo for Olimex STM32-E407/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-E407 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32e407_gcc.
*/

11
Target/Demo/ARMCM4_STM32F4_Olimex_STM32E407_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_STM32F4_Olimex_STM32E407_IAR User Program
\brief User Program.
\ingroup ARMCM4_STM32F4_Olimex_STM32E407_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_stm32.
*/

5
Target/Demo/ARMCM4_STM32F4_Olimex_STM32E407_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM4_STM32F4_Olimex_STM32E407_IAR Demo for Olimex STM32-E407/IAR
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-E407 and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32e407_iar.
*/

11
Target/Demo/ARMCM4_STM32F4_Olimex_STM32P405_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_STM32F4_Olimex_STM32P405_GCC User Program
\brief User Program.
\ingroup ARMCM4_STM32F4_Olimex_STM32P405_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_stm32.
*/

5
Target/Demo/ARMCM4_STM32F4_Olimex_STM32P405_GCC/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM4_STM32F4_Olimex_STM32P405_GCC Demo for Olimex STM32-P405/GCC
\ingroup Demos
\brief Preconfigured programs for the Olimex STM32-P405 and the GCC compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:olimex_stm32p405_gcc.
*/

11
Target/Demo/ARMCM4_TM4C_DK_TM4C123G_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_TM4C_DK_TM4C123G_IAR User Program
\brief User Program.
\ingroup ARMCM4_TM4C_DK_TM4C123G_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_tm4c.
*/

5
Target/Demo/ARMCM4_TM4C_DK_TM4C123G_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM4_TM4C_DK_TM4C123G_IAR Demo for Texas Instruments DK-TM4C123G/IAR
\ingroup Demos
\brief Preconfigured programs for the Texas Instruments DK-TM4C123G and the IAR Embedded Workbench IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:dk_tm4c123g_iar.
*/

11
Target/Demo/ARMCM4_XMC4_XMC4700_Relax_Kit_GCC/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_XMC4_XMC4700_Relax_Kit_GCC User Program
\brief User Program.
\ingroup ARMCM4_XMC4_XMC4700_Relax_Kit_GCC
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_xmc4.
*/

5
Target/Demo/ARMCM4_XMC4_XMC4700_Relax_Kit_GCC/demo.dox
View File

@ -1,9 +1,10 @@
/**
\defgroup ARMCM4_XMC4_XMC4700_Relax_Kit_GCC Demo for XMC4700 Relax Kit/GCC
\ingroup Demos
\brief Preconfigured programs for the Infineon XMC4700 Relax Kit board and the Dave 4
development environment, which is based on the ARM GCC toolchain.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:infineon_xmc4700_relax_kit_gcc.
*/

11
Target/Demo/ARMCM4_XMC4_XMC4700_Relax_Kit_IAR/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_ARMCM4_XMC4_XMC4700_Relax_Kit_IAR User Program
\brief User Program.
\ingroup ARMCM4_XMC4_XMC4700_Relax_Kit_IAR
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:armcm4_xmc4.
*/

5
Target/Demo/ARMCM4_XMC4_XMC4700_Relax_Kit_IAR/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup ARMCM4_XMC4_XMC4700_Relax_Kit_IAR Demo for XMC4700 Relax Kit/IAR
\ingroup Demos
\brief Preconfigured programs for the Infineon XMC4700 Relax Kit board and the IAR compiler.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:infineon_xmc4700_relax_kit_iar.
*/

11
Target/Demo/HCS12_Evbplus_Dragon12p_CodeWarrior/Prog/prog.dox
View File

@ -1,7 +1,16 @@
/**
\defgroup Prog_HCS12_Evbplus_Dragon12p_CodeWarrior User Program
\brief User Program.
\ingroup HCS12_Evbplus_Dragon12p_CodeWarrior
\brief User Program.
\details The intention of the demo user program is two-fold. (1) To test the
bootloader, you need some sort of firmware to see if you can perform a
firmware update with the bootloader. This program can be used for this
purpose. (2) To make firmware programmable by the bootloader, a few
adjustments to the firmware are required. The demo user program serves as an
example for how these adjustments can be implemented. Additional details on
this subject can be found in the port specifics documentation, which is
available at:
https://www.feaser.com/openblt/doku.php?id=manual:ports:hcs12.
*/

5
Target/Demo/HCS12_Evbplus_Dragon12p_CodeWarrior/demo.dox
View File

@ -1,8 +1,9 @@
/**
\defgroup HCS12_Evbplus_Dragon12p_CodeWarrior Demo for Dragon12-plus/CodeWarrior
\ingroup Demos
\brief Preconfigured programs for the EVBplus Dragon12-plus and the CodeWarrior IDE.
\details Refer to http://feaser.com/openblt/doku.php?id=manual:demos
for detailed getting started instructions.
\details For detailed getting started instructions, refer to:
https://www.feaser.com/openblt/doku.php?id=manual:demos:evbplus_dragon12p_codewarrior.
*/

18
Target/Demo/demos.dox Normal file
View File

@ -0,0 +1,18 @@
/**
\defgroup Demos Bootloader Demos
\brief Preconfigured demo programs.
\details Each demo consists of a bootloader and user program. The bootloader can be
tested by performing a firmware udpate using the supplied user program.
Refer to https://www.feaser.com/openblt/doku.php?id=manual:demos for an
overview of all available demo programs.
The easiest way to get started with the bootloader is by obtaining a low
cost development board with on-chip debugger, for which a demo is available.
For example one of the ST STM32 Nucleo boards. Getting to know that
bootloader and how it works is much easier once you have it running. Then
porting it to your own microcontroller system will go smoother. If you'd
like assistance or outsource the integration of the bootloader on your
system, feel free to contact Feaser (http://www.feaser.com).
*/

1
Target/Source/ARM7_LPC2000/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARM7_LPC2000 Target ARM7 LPC2000
\ingroup Ports
\brief Target dependent code for the ARM7 LPC2000 microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARM7 LPC2000 microcontroller family.

1
Target/Source/ARMCM0_STM32F0/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM0_STM32F0 Target ARMCM0 STM32F0
\ingroup Ports
\brief Target dependent code for the ARMCM0 STM32F0 microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM0 STM32F0 microcontroller family.

1
Target/Source/ARMCM0_XMC1/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM0_XMC1 Target ARMCM0 XMC1
\ingroup Ports
\brief Target dependent code for the ARMCM0 XMC1xxx microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM0 XMC1xxx microcontroller family.

1
Target/Source/ARMCM3_EFM32/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM3_EFM32 Target ARMCM3 EFM32
\ingroup Ports
\brief Target dependent code for the ARMCM3 EFM32 microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM3 EFM32 microcontroller family.

1
Target/Source/ARMCM3_LM3S/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM3_LM3S Target ARMCM3 LM3S
\ingroup Ports
\brief Target dependent code for the ARMCM3 LM3S microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM3 LM3S microcontroller family.

1
Target/Source/ARMCM3_STM32F1/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM3_STM32F1 Target ARMCM3 STM32F1
\ingroup Ports
\brief Target dependent code for the ARMCM3 STM32F1 microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM3 STM32F1 microcontroller family.

1
Target/Source/ARMCM3_STM32F2/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM3_STM32F2 Target ARMCM3 STM32F2
\ingroup Ports
\brief Target dependent code for the ARMCM3 STM32F2xx microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM3 STM32F2xx microcontroller family.

1
Target/Source/ARMCM4_STM32F3/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM4_STM32F3 Target ARMCM4 STM32F3
\ingroup Ports
\brief Target dependent code for the ARMCM4 STM32F3 microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM4 STM32F3 microcontroller family.

1
Target/Source/ARMCM4_STM32F4/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM4_STM32F4 Target ARMCM4 STM32F4
\ingroup Ports
\brief Target dependent code for the ARMCM4 STM32F4 microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM4 STM32F4 microcontroller family.

1
Target/Source/ARMCM4_TM4C/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM4_TM4C Target ARMCM4 TM4C
\ingroup Ports
\brief Target dependent code for the ARMCM4 TM4C microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM4 TM4C microcontroller family.

1
Target/Source/ARMCM4_XMC4/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_ARMCM4_XMC4 Target ARMCM4 XMC4
\ingroup Ports
\brief Target dependent code for the ARMCM4 XMC4xxx microcontroller family.
\details This module implements the bootloader's target dependent part for the
ARMCM4 XMC4xxx microcontroller family.

1
Target/Source/HCS12/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_HCS12 Target HCS12
\ingroup Ports
\brief Target dependent code for the Freescale HCS12 microcontroller family.
\details This module implements the bootloader's target dependent part for the
Freescale HCS12 microcontroller family.

1
Target/Source/TRICORE_TC1798/target.dox
View File

@ -1,5 +1,6 @@
/**
\defgroup Target_TRICORE_TC1798 Target Tricore TC1798
\ingroup Ports
\brief Target dependent code for the Tricore TC1798 microcontroller family.
\details This module implements the bootloader's target dependent part for the
Tricore TC1798 microcontroller family.

10
Target/Source/ports.dox Normal file
View File

@ -0,0 +1,10 @@
/**
\defgroup Ports Bootloader Ports
\brief Target dependent code.
\details The bootloader targets contain the microcontroller and compiler dependent
parts of the bootloader. They are grouped per microcontroller family. This is
the part that needs to be newly developed when porting the bootloader to a
new microcontroller family.
*/

6
Target/Source/readme.dox
View File

@ -11,12 +11,18 @@ The software program's architecture is divided into 4 major categories, namely t
application code (App), target independent code (Core), target dependent code
(Target), and compiler specific code (Comp).
\image html openblt_architecture.png
\image latex openblt_architecture.png
To configure and fine-tune the bootloader for integration in your product, all you have
to do is take the demo bootloader project for the microcontroller and compiler you are
using, and (optionally) modify just the application code (App) to fit your needs. This
typically involves changing the configuration header file (blt_conf.h) and the
implementation of the hook functions (hooks.c).
For more in-depth information behind the design of the OpenBLT bootloader, you can visit:
https://www.feaser.com/openblt/doku.php?id=manual:design.
\section copy Copyright and Licensing
\verbatim
----------------------------------------------------------------------------------------