XMC™ MCU: DAC sine wave

This code example demonstrates the usage of the DAC peripheral of the XMC™ MCU.

This example uses two of the five available DAC configurations. It generates an analog sine wave at the DAC0 output and a static analog voltage at the DAC1 output. The frequency and duration of the sine waves are adjusted to play an audio at the DAC0 output.

View this README on GitHub.

Provide feedback on this code example.

Requirements

ModusToolbox™ software v3.0
SEGGER J-Link software
Programming language: C
Associated parts: All XMC™ MCU parts

Supported toolchains (make variable 'TOOLCHAIN')

GNU Arm® embedded compiler v10.3.1 (GCC_ARM) - Default value of TOOLCHAIN
Arm® compiler v6.16 (ARM)
IAR C/C++ compiler v9.30.1 (IAR)

Supported kits (make variable 'TARGET')

XMC4700 relax kit (KIT_XMC47_RELAX_V1) - Default value of TARGET
XMC4200 Platform2Go kit (TARGET_KIT_XMC_PLT2GO_XMC4200)
XMC4300 relax EtherCAT kit (TARGET_KIT_XMC43_RELAX_ECAT_V1)
XMC4400 Platform2Go kit (TARGET_KIT_XMC_PLT2GO_XMC4400)
XMC4500 relax kit (TARGET_KIT_XMC45_RELAX_V1)
XMC4800 relax EtherCAT kit (TARGET_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 and open it using one of the following:

In Eclipse IDE for ModusToolbox™ software

Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox™ Application). This launches the Project Creator tool.
Pick a kit supported by the code example from the list shown in the Project Creator - Choose Board Support Package (BSP) dialog.

When you select a supported kit, the example is reconfigured automatically to work with the kit. To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can use the Library Manager to select or update the BSP and firmware libraries used in this application. To access the Library Manager, click the link from the Quick Panel.

You can also just start the application creation process again and select a different kit.

If you want to use the application 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.
In the Project Creator - Select Application dialog, choose the example by enabling the checkbox.
(Optional) Change the suggested New Application Name.
The Application(s) Root Path defaults to the Eclipse workspace which is usually the desired location for the application. If you want to store the application in a different location, you can change the Application(s) Root Path value. Applications that share libraries should be in the same root path.
Click Create to complete the application creation process.

For more details, see the Eclipse IDE for ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mt_ide_user_guide.pdf).

In command-line interface (CLI)

ModusToolbox™ software provides the Project Creator as both a GUI tool and the command line tool, "project-creator-cli". The 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™ software 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™ software installation instead of a standard Windows command-line application. This shell provides access to all ModusToolbox™ software 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 "project-creator-cli" tool has the following arguments:

Argument	Description	Required/optional
`--board-id`	Defined in the `<id>` field of the BSP manifest	Required
`--app-id`	Defined in the `<id>` field of the CE 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

The following example will clone the "DAC Sine Wave" application with the desired name "FceCrc" configured for the KIT_XMC47_RELAX_V1 BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id KIT_XMC47_RELAX_V1 --app-id mtb-example-xmc-dac-sine --user-app-name DacSine --target-dir "C:/mtb_projects"

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™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mtb_user_guide.pdf).

In third-party IDEs

Note: Only VS code is supported.

Follow the instructions from the In command-line interface (CLI) section to create the application, and import the libraries using the make getlibs command.
Export the application to a supported IDE using the make <ide> command.

For a list of supported IDEs and more details, see the "Exporting to IDEs" section of the ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mtb_user_guide.pdf).

Follow the instructions displayed in the terminal to create or import the application as an IDE project.

Operation

Connect the board to your PC using a micro-USB cable through the debug USB connector.
Program the board using Eclipse IDE for ModusToolbox™ software:
1. Select the application project in the Project Explorer.
2. In the Quick Panel, scroll down, and click <Application Name> Program (JLink).
Confirm that the kit generates an analog sine wave on the DAC0 output and a static analog value on the DAC1 output. Observe the output frequency and duration of the sine wave varying with time.
Connect a speaker to the DAC0 output to listen to the audio.

Note: The DAC can directly drive a 5-kOhm/50-pF terminated load. For XMC4000 MCU family devices - P14.8 (DAC0), P14.9 (DAC1).

Debugging

You can debug the example to step through the code. In the IDE, use the <Application Name> Debug (JLink) configuration in the Quick Panel. For more details, see the "Program and Debug" section in the Eclipse IDE for ModusToolbox™ software user guide.

Design and implementation

This example shows the working of the DAC peripheral of the XMC™ MCU. Initially, the following arrays are defined: 'melody[ARRAY_SIZE]' and 'beats[ARRAY_SIZE]'. The 'melody[ARRAY_SIZE]' array defines new frequencies. Frequencies defined by R in this array are outside the audible range and act as pauses in the melody being played. R is of type "const" and is predefined in the code. The 'beats[ARRAY_SIZE]' array defines the number of function calls after which the frequency will be updated. This defines the duration and pause times in the melody being played.

Two DAC channels, DAC0 and DAC1, are configured in the following structures: 'ch_config0' and 'ch_config0'. Sine wave pattern is used in the pattern mode of DAC.

Finally, the interrupt handler for 'Systick' periodically calls the 'DAC_Update()' function. The 'DAC_Update()' function updates the DAC frequency after each function call. In this function, each frequency value in 'melody[index]' denotes a musical note to be played. Value in 'beats[index]' determines the duration for which each note must be played.

Resources	Links
Code examples	Using ModusToolbox™ software on GitHub
Device documentation	XMC4000 MCU family datasheets XMC4000 MCU family technical reference manuals
Development kits	XMC™ MCU eval boards
Libraries on GitHub	mtb-xmclib-cat3 – XMC™ MCU peripheral library (XMCLib) and docs
Tools	Eclipse IDE for ModusToolbox™ software – ModusToolbox™ software is a collection of easy-to-use software and tools enabling rapid development with Infineon MCUs, covering applications from embedded sense and control to wireless and cloud-connected systems using AIROC™ Wi-Fi and Bluetooth® connectivity devices.

Other resources

Infineon provides a wealth of data at www.infineon.com to help you select the right device, and quickly and effectively integrate it into your design.

For XMC™ MCU devices, see 32-bit XMC™ Industrial microcontroller based on Arm® Cortex®-M.

Document history

Document title: CE232580 - XMC™ MCU: DAC sine wave

Version	Description of change
1.0.0	New code example
1.0.1	Updated README
1.1.0	Added support for new kits
2.0.0	Updated to support ModusToolbox™ software v3.0. This CE is not backward compatible with previous versions of ModusToolbox™ software.
2.1.0	Added support for DAC personality

All other trademarks or registered trademarks referenced herein are the property of their respective owners.

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.

infineon / mtb-example-xmc-dac-sine Goto Github PK

mtb-example-xmc-dac-sine's Introduction

mtb-example-xmc-dac-sine's People

Contributors

Watchers

Recommend Projects

Recommend Topics

Recommend Org