Skip to content
Permalink
master
Switch branches/tags

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-i2c-master-slave/README.md

Go to file
 
 
Cannot retrieve contributors at this time
XMC™ MCU: I2C master and slave Requirements Supported toolchains (make variable 'TOOLCHAIN') Supported kits (make variable 'TARGET') Hardware setup Software setup Using the code example Operation Design and implementation Debugging Resources and settings Related resources Other resources Document history Legal disclaimer Information Warnings
224 lines (131 sloc) 14.7 KB
Raw Blame
Open in GitHub Desktop

XMC™ MCU: I2C master and slave

This code example demonstrates the implementation of an I2C master and an I2C slave using the Universal Serial Interface Channel (USIC) module available in XMC™ MCUs. It configures one USIC module as the I2C master and another as the I2C slave on the same XMC™ MCU using the Device Configurator. The I2C master module sends commands to the I2C slave module to toggle the LEDs present on the XMC™ development kit.

You must make the connection between the I2C master and the I2C slave externally.

Requirements

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')

Hardware setup

Prepare your board for the example by interconnecting the SDA master to the SDA slave and the SCL master to the SCL slave. You need a 4.7-kohm pull-up to VDD for each.

See the kit user guide to ensure that the board is configured correctly. To prepare other boards, see the following USIC channel configuration:

Board name Master SCL Master SDA Slave SCL Slave SDA
KIT_XMC11_BOOT_001 2.11 1.2 2.0 2.1
KIT_XMC12_BOOT_001 2.11 2.10 0.8 1.0
KIT_XMC13_BOOT_001 1.3 1.2 2.0 1.0
KIT_XMC14_BOOT_001 1.8 2.12 0.8 2.11
KIT_XMC_PLT2GO_XMC4200 3.0 2.5 0.11 2.14
KIT_XMC43_RELAX_ECAT_V1 2.4 2.5 0.8 1.5
KIT_XMC_PLT2GO_XMC4400 3.0 2.5 0.11 2.14
KIT_XMC45_RELAX_V1 0.11 0.5 5.2 5.0
KIT_XMC48_RELAX_ECAT_V1 6.2 3.13 5.2 5.0

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

  1. Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox™ Application). This launches the Project Creator tool.

  2. 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.

  3. In the Project Creator - Select Application dialog, choose the example by enabling the checkbox.

  4. (Optional) Change the suggested New Application Name.

  5. 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.

  6. 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}/ide_{version}/docs/mtb_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.

This 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 "I2C master and slave" application with the desired name "I2cMasterSlave" configured for the KIT_XMC14_BOOT_001 BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id KIT_XMC14_BOOT_001 --app-id mtb-example-xmc-i2c-master-slave --user-app-name I2cMasterSlave --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.

  1. Follow the instructions from the In command-line interface (CLI) section to create the application, and import the libraries using the make getlibs command.

  2. 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).

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

Operation

  1. Prepare your board as described in the Hardware setup section.

  2. Connect the board to your PC using a micro-USB cable through the debug USB connector.

  3. 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).

  4. Check whether the LED toggles every ~500 ms, which confirms that commands are sent by the I2C master and are received by the I2C slave.

Design and implementation

The following occurs in the code example:

  1. Inside main(), the example is initialized:

    • The master and slave interfaces are initialized using personalities.

    • Interrupt priority is set for the receive event of the I2C slave.

    • SysTimer is initialized to call SysTick_Handler every 1 ms.

  2. Inside SysTick_Handler:

    • The I2C master interface sends commands to the I2C slave interface every 500 ms (see #define I2C_MASTER_SEND_TASK_MS in main.c) to toggle an LED.

  3. Inside I2C slave:

    • The receive interrupt routine processes the commands sent from the I2C master to the I2C slave.

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™ user guide.

Resources and settings

The project uses the default design.modus file.


Related resources

Resources Links
Code examples Using ModusToolbox™ software on GitHub
Device documentation XMC1000 family datasheets
XMC4000 family datasheets
XMC1000 family technical reference manuals
XMC4000 family technical reference manuals
Development kits XMC™ 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: CE232573 – XMC™ MCU: I2C master and slave

Version Description of change
1.0.0 New code example
1.1.0 Added support for more kits
2.0.0 Updated to support ModusToolbox™ software v3.0; CE will not be backward compatible with previous versions of ModusToolbox™ software
2.1.0 Added support for more kits

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

© 2022 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.