# Project Name: Mcu_ModeDemo

---

## Function description

**Mcu_ModeDemo** is designed to demonstrate the operation of the Mcu module in different modes. The modules involved in this example include Resource, Platform, Mcu, GPT, Port, Det, Dio, and EcuM. The DEMO uses LPTMR as the wake-up source. It utilizes PTB4, PTB5, PTE8 as the output pin, allowing the LED connected to PTB4, PTB5, PTE8 to indicate the current state of the example. **Ultimately**, this achieves the transition between different modes of the chip. 

❗If in MCAL_ENABLE_USER_MODE_SUPPORT mode, the interrupt priority of the wake-up source needs to be set to 0, otherwise the Mcu may not wake up normally due to the masking of the interrupt priority.

The pins used are:

| Pin  | Purpose |
| :--: | :-----: |
| PTB4 |  LED_B  |
| PTB5 |  LED_G  |
| PTE8 |  LED_R  |

LED Status in Different Modes:

|   Mode    |  LED_R  |  LED_G  |  LED_B  |
| :-------: | :------ | :------ | :------ |
|    RUN    | STD_ON  | STD_ON  | STD_ON  |
|   SLEEP   | STD_ON  | STD_ON  | STD_OFF |
| DEEPSLEEP | STD_ON  | STD_OFF | STD_ON  |
|  STANDBY  | STD_ON  | STD_OFF | STD_OFF |
| POWERDOWN | STD_OFF | STD_OFF | STD_OFF |

---

## Setup

+ ***Step1***: Open the Mcu_Demo.yct with the YCT tool, config the toolchain per your required(by default, the VS code + GCC are used)
+ ***Step2***：Generate the codes， you can change the configurations if needed(to adapt to your own HW design), if so, please ensure all the modifications are OK with no any errors exist before generating the code.
+ ***Step3***: Open the generated project with VS code/IAR/Keil IDE per your selected.
+ ***Step4***: Compile the project, power on the EVB and download it to the EVB via the available debugger, such as a J-Link debugger probe.
+ ***Step5***: At last, enjoy the demo example.

---

## Hardware requirement
+ **EVB**: YTM32B1MD1-EVB-Q100-Rev.A/B
+ **Debugger**: J-Link HW v9 or later with YUNTU `YTM32B1MD1` patch(support package) installed.

**Note**: Please check the version number at the bottom of the EVB. If it is `YTM32B1MD1-EVB-Q100-Rev.A/B`, please use the example projects ending with `_RevA` for `Icu_Demo`.
---

## Software requirement

+ **Config & Code Generation Tool**
  + **MCAL**: Yuntu Config Tool(YCT) v2.7.0 or later version
+ **Compiler Toolchain**
  + **GCC**: GNU GCC v10.3 or later version
  + **Keil/MDK**: ARM Keil/MDK v5.36 or later version(`armclang v6.18.2` is recommended to be used as the compiler)
  + **IAR**: IAR v9.50 or later version
  + **VS Code**: Microsoft Visual Studio Code IDE v1.76 or later version(C/C++ support, GNU toolchain, CMake v3.25, ninja, Cortex-Debug extensions installation required)
+ **Debugger driver**
    + **J-Link**: SEGGER J-Link v7.82 or later version, YUNTU `YTM32B1MD1` patch(support package) installation required.
    + **Ozone Debugger tool**: SEGGER Ozone v3.28 or later version.

    ***Note***: **YTM32B1MD1** patch install required which can be obtained via **YCT** or contact ***YUNTU sales/FAE team***.

---