Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
mtb-example-xmc-vadc-emux/README.md
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
261 lines (143 sloc)
13.9 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# XMC™ MCU: VADC EMUX | |
This code example demonstrates the VADC capability to drive a external multiplexer automatically by emux output pins in XMC™ MCU. The successful completion of EMUX control in sequence mode is indicated by observing the waveform from EMUX output pins which changes automatically in the sequence 7,6,5,4,3,2,1,0,7,6 | |
## Requirements | |
- [ModusToolbox™ software](https://www.infineon.com/modustoolbox) v3.1 | |
- Board support package (BSP) minimum required version for: | |
- XMC™ MCU: v2.2.0 | |
- [SEGGER J-Link software](https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack) | |
- Programming language: C | |
- Associated parts: All [XMC™ MCU](https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/) parts | |
## Supported toolchains (make variable 'TOOLCHAIN') | |
- GNU Arm® embedded compiler v10.3.1 (`GCC_ARM`) - Default value of `TOOLCHAIN` | |
## Supported kits (make variable 'TARGET') | |
- [XMC1200 boot kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc12_boot_001/) (`KIT_XMC12_BOOT_001`) | |
- [XMC1300 boot kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc13_boot_001/) (`KIT_XMC13_BOOT_001`) | |
- [XMC1400 boot kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc14_boot_001/) (`KIT_XMC14_BOOT_001`) | |
- [XMC4200 Platform2Go kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc_plt2go_xmc4200/) (`KIT_XMC_PLT2GO_XMC4200`) | |
- [XMC4300 relax EtherCAT kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc43_relax_ecat_v1/) (`KIT_XMC43_RELAX_ECAT_V1`) | |
- [XMC4400 Platform2Go kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc_plt2go_xmc4400/) (`KIT_XMC_PLT2GO_XMC4400`) | |
- [XMC4500 relax kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc45_relax_v1/) (`KIT_XMC45_RELAX_V1`) - Default value of `TARGET` | |
- [XMC4700 relax kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc47_relax_v1/) (`KIT_XMC47_RELAX_V1`) | |
- [XMC4800 relax EtherCAT kit](https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc48_relax_ecat_v1/) (`KIT_XMC48_RELAX_ECAT_V1`) | |
## Hardware setup | |
This example uses the board's default configuration. See the kit user guide to ensure that the board is configured correctly. | |
## Software setup | |
This example requires no additional software or tools. | |
## Using the code example | |
### Create the project | |
The ModusToolbox™ tools package provides the Project Creator as both a GUI tool and a command line tool. | |
<details><summary><b>Use Project Creator GUI</b></summary> | |
1. Open the Project Creator GUI tool. | |
There are several ways to do this, including launching it from the dashboard or from inside the Eclipse IDE. For more details, see the [Project Creator user guide](https://www.infineon.com/ModusToolboxProjectCreator) (locally available at *{ModusToolbox™ install directory}/tools_{version}/project-creator/docs/project-creator.pdf*). | |
2. On the **Choose Board Support Package (BSP)** page, select a kit supported by this code example. See [Supported kits](#supported-kits-make-variable-target). | |
> **Note:** To use this code example for a kit not listed here, you may need to update the source files. If the kit does not have the required resources, the application may not work. | |
3. On the **Select Application** page: | |
a. Select the **Applications(s) Root Path** and the **Target IDE**. | |
> **Note:** Depending on how you open the Project Creator tool, these fields may be pre-selected for you. | |
b. Select this code example from the list by enabling its check box. | |
> **Note:** You can narrow the list of displayed examples by typing in the filter box. | |
c. (Optional) Change the suggested **New Application Name** and **New BSP Name**. | |
d. Click **Create** to complete the application creation process. | |
</details> | |
<details><summary><b>Use Project Creator CLI</b></summary> | |
The 'project-creator-cli' tool can be used to create applications from a CLI terminal or from within batch files or shell scripts. This tool is available in the *{ModusToolbox™ install directory}/tools_{version}/project-creator/* directory. | |
Use a CLI terminal to invoke the 'project-creator-cli' tool. On Windows, use the command-line 'modus-shell' program provided in the ModusToolbox™ installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ tools. You can access it by typing "modus-shell" in the search box in the Windows menu. In Linux and macOS, you can use any terminal application. | |
The following example clones the "[VADC EMUX](https://github.com/Infineon/mtb-example-xmc-vadc-emux)" application with the desired name "MyVADCEMUX" configured for the *KIT_XMC45_RELAX_V1* BSP into the specified working directory, *C:/mtb_projects*: | |
``` | |
project-creator-cli --board-id KIT_XMC45_RELAX_V1 --app-id mtb-example-xmc-vadc-emux --user-app-name MyVADCEMUX --target-dir "C:/mtb_projects" | |
``` | |
The 'project-creator-cli' tool has the following arguments: | |
Argument | Description | Required/optional | |
---------|-------------|----------- | |
`--board-id` | Defined in the <id> field of the [BSP](https://github.com/Infineon?q=bsp-manifest&type=&language=&sort=) manifest | Required | |
`--app-id` | Defined in the <id> field of the [CE](https://github.com/Infineon?q=ce-manifest&type=&language=&sort=) manifest | Required | |
`--target-dir`| Specify the directory in which the application is to be created if you prefer not to use the default current working directory | Optional | |
`--user-app-name`| Specify the name of the application if you prefer to have a name other than the example's default name | Optional | |
> **Note:** The project-creator-cli tool uses the `git clone` and `make getlibs` commands to fetch the repository and import the required libraries. For details, see the "Project creator tools" section of the [ModusToolbox™ tools package user guide](https://www.infineon.com/ModusToolboxUserGuide) (locally available at {ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf). | |
</details> | |
### Open the project | |
After the project has been created, you can open it in your preferred development environment. | |
<details><summary><b>Eclipse IDE</b></summary> | |
If you opened the Project Creator tool from the included Eclipse IDE, the project will open in Eclipse automatically. | |
For more details, see the [Eclipse IDE for ModusToolbox™ user guide](https://www.infineon.com/MTBEclipseIDEUserGuide) (locally available at *{ModusToolbox™ install directory}/docs_{version}/mt_ide_user_guide.pdf*). | |
</details> | |
<details><summary><b>Visual Studio (VS) Code</b></summary> | |
Launch VS Code manually, and then open the generated *{project-name}.code-workspace* file located in the project directory. | |
For more details, see the [Visual Studio Code for ModusToolbox™ user guide](https://www.infineon.com/MTBVSCodeUserGuide) (locally available at *{ModusToolbox™ install directory}/docs_{version}/mt_vscode_user_guide.pdf*). | |
</details> | |
<details><summary><b>Command line</b></summary> | |
If you prefer to use the CLI, open the appropriate terminal, and navigate to the project directory. On Windows, use the command-line 'modus-shell' program; on Linux and macOS, you can use any terminal application. From there, you can run various `make` commands. | |
For more details, see the [ModusToolbox™ tools package user guide](https://www.infineon.com/ModusToolboxUserGuide) (locally available at *{ModusToolbox™ install directory}/docs_{version}/mtb_user_guide.pdf*). | |
</details> | |
## Operation | |
1. Connect the board to your PC using a micro-USB cable through the debug USB connector. | |
2. Program the board using one of the following: | |
<details><summary><b>Using Eclipse IDE</b></summary> | |
1. Select the application project in the Project Explorer. | |
2. In the **Quick Panel**, scroll down, and click **\<Application Name> Program (JLink)**. | |
</details> | |
<details><summary><b>In other IDEs</b></summary> | |
Follow the instructions in your preferred IDE. | |
</details> | |
<details><summary><b>Using CLI</b></summary> | |
From the terminal, execute the `make program` command to build and program the application using the default toolchain to the default target. The default toolchain is specified in the application's Makefile but you can override this value manually: | |
g ``` | |
make program TOOLCHAIN=<toolchain> | |
``` | |
Example: | |
``` | |
make program TOOLCHAIN=GCC_ARM | |
``` | |
</details> | |
3. Connect VADC EMUXx0, EMUXx1, EMUXx2 pins to selection lines of external multiplexer or observe the behaviour using logic analyser. | |
**Figure 1. EMUX pins output** | |
![](images/vadc_emux.png) | |
## Debugging | |
You can debug the example to step through the code. | |
<details><summary><b>In Eclipse IDE</b></summary> | |
Use the **\<Application Name> Debug (JLink)** configuration in the **Quick Panel**. For details, see the "Program and debug" section in the [Eclipse IDE for ModusToolbox™ user guide](https://www.infineon.com/MTBEclipseIDEUserGuide). | |
</details> | |
<details><summary><b>In other IDEs</b></summary> | |
Follow the instructions in your preferred IDE. | |
</details> | |
## Design and implementation | |
The EMUX pins of the VADC is connected to selection line of the external multiplexer. | |
The output of the external multiplexer is connected to VADC GROUP 0 CHANNEL 1 | |
The output of the VADC is printed via debug UART which can be verified with a serial monitor. | |
### Resources and settings | |
The project uses a custom *design.modus* file because the following settings were modified in the default *design.modus* file. | |
**Figure 2. USIC (UART) settings** | |
![](images/uart-settings-1400.jpg) | |
**Figure 3. UART Tx pin settings** | |
![](images/tx-pin-settings-1400.jpg) | |
**Figure 4. UART Rx pin settings** | |
![](images/rx-pin-settings-1400.jpg) | |
<br> | |
## Related resources | |
Resources | Links | |
-----------|---------------------------------- | |
Code examples | [Using ModusToolbox™ software](https://github.com/Infineon/Code-Examples-for-ModusToolbox-Software) on GitHub | |
Device documentation | [XMC1000 family datasheets](https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/32-bit-xmc1000-industrial-microcontroller-arm-cortex-m0/#document-group-myInfineon-49) <br> [XMC1000 family technical reference manuals](https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/32-bit-xmc1000-industrial-microcontroller-arm-cortex-m0/#document-group-myInfineon-44) <br> [XMC4000 family datasheets](https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/32-bit-xmc4000-industrial-microcontroller-arm-cortex-m4/#document-group-myInfineon-49) <br> [XMC4000 family technical reference manuals](https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/32-bit-xmc4000-industrial-microcontroller-arm-cortex-m4/#document-group-myInfineon-44) | |
Development kits | [XMC™ eval boards](https://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-cortex-m/#boards) | |
Libraries on GitHub | [mtb-xmclib-cat3](https://github.com/Infineon/mtb-xmclib-cat3) – XMC™ peripheral driver library (XMCLib) | |
Tools | [Eclipse IDE for ModusToolbox™ software](https://www.infineon.com/modustoolbox) – MModusToolbox™ software is a collection of easy-to-use libraries and tools enabling rapid development with Infineon MCUs for applications ranging from wireless and cloud-connected systems, edge AI/ML, embedded sense and control, to wired USB connectivity using PSoC™ Industrial/IoT MCUs, AIROC™ Wi-Fi and Bluetooth® connectivity devices, XMC™ Industrial MCUs, and EZ-USB™/EZ-PD™ wired connectivity controllers. ModusToolbox™ incorporates a comprehensive set of BSPs, HAL, libraries, configuration tools, and provides support for industry-standard IDEs to fast-track your embedded application development. | |
<br> | |
## Document history | |
Document title: *CE239241* - *XMC™ MCU: VADC EMUX* | |
Version | Description of change | |
------- | --------------------- | |
1.0.0 | New code example | |
1.1.0 | Updated design.modus file for KIT_XMC45_RELAX_V1 BSP | |
<br> | |
------ | |
All other trademarks or registered trademarks referenced herein are the property of their respective owners. | |
© 2023-2024 Infineon Technologies AG | |
All Rights Reserved. | |
### Legal disclaimer | |
The information given in this document shall in no event be regarded as a guarantee of conditions or characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any information regarding the application of the device, Infineon Technologies hereby disclaims any and all warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual property rights of any third party. | |
### Information | |
For further information on technology, delivery terms and conditions and prices, please contact the nearest Infineon Technologies Office (www.infineon.com). | |
### Warnings | |
Due to technical requirements, components may contain dangerous substances. For information on the types in question, please contact the nearest Infineon Technologies Office. | |
Infineon Technologies components may be used in life-support devices or systems only with the express written approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system or to affect the safety or effectiveness of that device or system. Life support devices or systems are intended to be implanted in the human body or to support and/or maintain and sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other persons may be endangered. | |
------------------------------------------------------------------------------- |