Getting Started With the CCM Development Kit


Infineon offers a CCM development kit containing a single AIROC™ CCM module which you can connect to any PC. It is designed to help you walk through the main capabilities of the CCM product, including:

  • CIRRENT™ Cloud ID for effortless, secure cloud authentication using the device certificate pre-programmed into the CCM module

  • Wi-Fi onboarding with additional assistance from the CIRRENT™ mobile app for testing, and a mobile app SDK which simplifies development of your own app

  • Secure and reliable full network stack, including Wi-Fi, TCP/IP, HTTP, MQTT, TLS, and other networking features

  • The ability to send secure and reliable Over-The-Air (OTA) firmware updates for CCM firmware

  • Optional use of CIRRENT™ IoT Network Intelligence (INI) for monitoring and managing your CCM fleet and monitoring connectivity reliability

  • Robust AT command set compatible with AWS IoT ExpressLink, making it easy to connect your host to the cloud

This getting started section walks you through the following:

  1. Steps required to bind your CCM developer kit to an Infineon Account for access to CIRRENT™ Cloud ID

  2. Steps to get your CCM developer kit online

  3. Getting your CCM developer kit connected to your AWS account


We recommend that you follow the complete getting started guide including setting up a CIRRENT(TM) account so you can test sending and data from your AWS IoT Core instance. However, we offer a Quick Evaluation Flow which enables you to rapidly test your unit. You can read more about the quick evaluation flow here.

Kit Contents

The IFW956810 CCM evaluation kit consists of an IFW56810 single-band Wi-Fi 4 Cloud Connectivity Manager module with powerful processing capability, a PCB antenna, an FTDI chip for the USB to serial interface, and an 8x2 pin header.


Bind your CCM developer kit to your CIRRENT™ Cloud ID account

CIRRENT™ Cloud ID provides the secure cloud-based device authentication that helps you to give your products secure and effortless access to your Product Cloud. This process works based on a unique device certificate embedded into every CCM module. These device certificates are pre-populated in CIRRENT™ Cloud ID. To get started with your developer kit you first need to bind your CCM developer kit to your CIRRENT™ Cloud ID account, which confirms ownership of the device.


CIRRENT™ Cloud ID is an Infineon service and you access Cloud ID using your Infineon account. If you do not already have an Infineon account, you need to register one first. Follow the instructions here.

Binding your CCM developer kit to a Cloud ID account is simple. The unique device ID is embedded in the QR code printed on your developer kit module. Simply scan the QR code located on the module, or use your browser and retype the URL printed below the QR code.


The QR code will redirect you to the Infineon website. If if you already have a CIRRENT™ Cloud ID account, you can simply select the Cloud ID account you want to bind your developer kit to. Alternatively, click Create Account to create a new CIRRENT™ account.


You can use the CCM development kit independent of an Infineon Account and independent of CIRRENT™ services by pulling the Device Certificate from your device directly using an AT command, and manually provisioning your device in your cloud using that certificate.

You can learn more about CIRRENT™ accounts here , and you can learn more about Cloud ID here .

Getting the CCM module online

Verify that your CCM module is registered with the CIRRENT™ Cloud ID

Your kit is already bound (registered) to your CIRRENT account when you registered your kit through the quick start guide provided along with the kit. If you landed on this page without following the quick start guide, see the document provided along with your kit. You can now observe that your CCM module is registered with CIRRENT™ Cloud ID by checking the device binding in CIRRENT™ Cloud ID:

  1. Log in to your Infineon account at and if prompted select the CIRRENT Account you used to register your device.

  2. On the Infineon OSTS home page, select CIRRENT Cloud ID, you will be redirected to the Cloud ID Binding page.

  3. Choose your account number as follows:

  4. You should see your device listed on the page.


You need to first successfully bind your developer kit to your CIRRENT™ account if you want to use CIRRENT™ Cloud ID to automatically provision your developer kit to your AWS account.

Connect the CCM module to your PC

The PC can be used as a host for evaluation. AT commands can be sent through a serial terminal on the PC to the IFW956810 CCM kit.

Before you connect the CCM module to your PC ensure that pin 3 to pin 4, pin 5 to pin 6, pin 9 to pin 10 and pin 11 to pin 12 of header J60 are closed as shown in the figure below. J61 must be connected in position 1 and 2.


Connect the IFW956810 Single-band Wi-Fi 4 Cloud Connectivity Manager evaluation kit to your PC using either the Type-C connector or Type-A male to Type-C female cable.


Run a serial terminal to communicate with the kit over USB by choosing the higher of the two enumerated COM ports with the following configuration:

Baud rate:








Flow control


Local Echo


End of Line

Line Feed

If you’re not sure how to connect to your CCM developer kit using a serial terminal you can view the Setting up a serial terminal on your PC section for more details. Once you open the serial terminal, type:

AT+CONF? About

in the serial terminal. You should see a response

OK Infineon - IFW56810

Connect the CCM module to Wi-Fi

The CCM module has a built-in Wi-Fi onboarding process that works over Bluetooth® LE or SoftAP and which relies on an app available in the Android and iOS app stores. You can use this app to connect your CCM module to your Wi-Fi network.

First, download and install the CIRRENT™ Wi-Fi onboarding app from Google Play Store for Android or iOS App Store for iOS on your mobile phone. The following QR codes link to the relevant app for your mobile device:



_images/gsd-4.png _images/gsd-5.png

To activate the Wi-Fi onboarding process on the CCM module type the following command in the serial terminal on your PC:


You should receive this response from the module:


Open the CIRRENT™ Wi-Fi onboarding app. You can skip the sign in. From the menu, select Configuration and then choose BLE onboarding for the best experience. Follow the onscreen instructions and enter your Wi-Fi router’s SSID and password.

When you complete these steps type the following in the serial terminal to ensure verify your connection to Wi-Fi:


You should see a you should see a response:

OK Ping received in x ms

That means that your CCM module has successfully connected to your Wi-Fi network.

If you prefer to configure Wi-Fi networking using AT commands you can do so by typing two commands into your terminal application. First, set the SSID you want to connect to. In our example, the SSID is “MyWorWiFI”:


Next, set the password for your WiFi network. In our example below, the password is “uMCjc3DB”:

AT+CONF Passphrase=uMCjc3DB


Your local router’s SSID and passphrase are stored securely inside the IFW56810 CCM module. While the SSID can be retrieved later (e.g. for debugging purposes), any attempt to retrieve the passphrase will return an error.

Getting the CCM Connected to Your AWS Account

How the CCM module interacts with AWS

The Infineon AIROC™ IFW56810 CCM is pre-configured to work with AWS IoT Core. To connect your CCM developer kit to your AWS account, you’ll need to connect your CIRRENT™ account to your AWS account so that new devices are automatically provisioned to your AWS account using CIRRENT™ Cloud ID. Follow the instructions in the CIRRENT™ Cloud ID documentation.

Alternatively, you can configure a single CCM module’s device certificate manually in your AWS account by downloading the device certificate from the CIRRENT™ Console, and then creating a Thing in your AWS account, using the certificate you just downloaded.

However, CIRRENT™ Cloud ID simplifies the process of connecting the kit to your AWS developer account. This method eliminates several manual steps that need to be performed otherwise. Learn more about the Cloud ID solution here.

At a high level, the CIRRENT™ Cloud performs the following functions to connect your CCM developer kit to your AWS account:

  1. Binds your kit to your CIRRENT™ account. In this guide, you completed the binding step before you connected the CCM module to your PC. In production, you would incorporate the binding step into your workflow.

  2. Provisions the AWS resources for the kit on your AWS account. That includes a Thing, which is the AWS cloud representation of a physical device. It also includes the device certificate which securely links the CCM device to the CIRRENT™ Cloud and to an AWS Thing, as well as creating and associating AWS IoT Thing access policies.

  3. The CIRRENT™ Cloud pulls the AWS endpoint from your AWS account and automatically pushes it to the CCM module. This enables the module to connect to your AWS development account.

The CIRRENT™ Cloud ID workflow we describe above demonstrates the ease of securely connecting a product to the Product Cloud. Because the CIRRENT™ Cloud is preloaded with the device certificate of all AIROC™ CCM modules you no longer need to manage device certificates on the production line. Instead, device certificates are managed in CIRRENT™ Cloud ID.


If you are unable to complete the process of connecting your AWS account to CIRRENT™ Cloud ID using the steps described below you can connect your device directly to your AWS instance using the AWS flow.

Get connected to AWS

You need to follow a few steps to ensure you’re able to interact with your AWS developer account while using the CIRRENT™ Cloud ID flow for device onboarding. The following diagram illustrates the process:


You’ve already confirmed that the CCM kit successfully binded to your Cloud ID account in previous sections. We’ll now outline the steps you need to take to set up your AWS instance so that you can connect your CCM kit to your Product Cloud.

  1. Execute the CloudFormation template

  2. Create a Product Cloud API

  3. Provision and prepare to connect the kit to your AWS account.

Execute Cloud Formation Template

Executing a CloudFormation template creates a stack in the AWS CloudFormation service. The template for creating the AWS resources needed to connect the IFW956810 evaluation kit to AWS IoT Core is already created by Infineon and stored in Amazon S3 storage. This stack establishes a channel of back-end device communication between your CIRRENT™ account and your AWS account. You need to execute the CloudFormation template only once per AWS account in a region.

The same stack can be reused to provision multiple kits to the AWS account in that region. You need to execute the CloudFormation template only once per AWS account in a region. Do the following to execute the Infineon-provided CloudFormation template:

  1. Click on the following link to execute the CloudFormation template. By default, the link uses the us-west-1 region:

    You can change the region in which you want to execute this template by changing the region=us-west-1 in this link to your required region. See Choosing a Region in the AWS documentation.

  2. You should now be on the Create Stack page in the AWS CloudFormation service, and the Infineon CloudFormation template should be preloaded. Click Next.

    Dashboard 2
  3. On the Step 2 page, retain all parameters at their default values, and click Next.

  4. On the Step 3 page, retain all parameters at their default values, and click Next.

  5. Select all the boxes as shown below to provide permissions to access the resources required by the CloudFormation template.

    Dashboard 2
  6. Click Create stack.

  7. Wait for up to five minutes for the stack creation to complete.

    Dashboard 2

    This stack creates the AWS infrastructure that enables provisioning the required AWS Product Cloud resources when your CCM-equipped product authenticates itself via CIRRENT™ Cloud ID.

  8. Click Outputs.

    The output of the stack that you created is shown on this page. Note the details as you will be required to enter it in the next section when you create a Product Cloud API endpoint in CIRRENT™ Cloud ID.

    Dashboard 2

Create a Product Cloud API

Your next step is to link your AWS account to Cloud ID so the CIRRENT™ Cloud service can communicate with your AWS developer account. To configure your first cloud API with Cloud ID, navigate to back to Infineon OSTS. Select CIRRENT™ Cloud ID, and navigate to the Provisioning tab. Click on Add Cloud API. You’ll be presented with a dialog box where you need to complete your Product Cloud API details. In setting up your Product Cloud API, ensure that you select AWS in the Create Cloud API dialog box:

Dashboard 2

Next, configure the fields using the valued obtained when you triggered the AWS CloudFormation template, as follows:

  • Account ID. This is your Amazon Web Services account identifier.

  • API Gateway ID. Here, enter the API gateway ID you have set up.

  • Region. Select the AWS region your AWS service operates in.

  • Stage. Provide the name of the stage in your deployment that you want to use for this API link.


You have now added your AWS-based Product Cloud to CIRRENT™ Cloud ID and can now provision devices bound to your Cloud ID account directly into your Product Cloud.

Provision and Prepare

When new devices are bound to your account, they will be automatically configured in your AWS account, but for this first device you will need to initiate the provisioning manually. To provision follow these steps:

  1. On the Infineon OSTS landing page, click on CIRRENT™ Cloud ID. Click on the Binding menu link:

  2. Click the Edit button.

  3. Click the drop-down list in the API Endpoint column.

  4. Choose the Product Cloud API created in the previous section.

  5. Click Save.

  6. Click the Provision now button


Provisioning via the Product Cloud API performs two functions. First, it creates the Thing for your device in the AWS Console and attaches the related policy and device certificate. It also pulls the AWS endpoint required by the device to connect to your AWS account and pushes it to the device so that the device connects to the AWS Cloud automatically. Retrieving the AWS endpoint from the CIRRENT Cloud is a one time step. The device connects to the endpoint immediately during subsequent connection attempts.

Connect to the AWS IoT Core

Enter the following command in the serial terminal to establish a secure connection to the AWS IoT Core:


The device will eventually connect to the AWS IoT Core and you will receive the message:


Next, run the following command:


Wait for a minute or two while the device pulls the endpoint from the CIRRENT Cloud and connects to the AWS IoT Core.


The above AT command will replace the default endpoint used for quick evaluation flow with your AWS account endpoint and automatically switches the connection to the new endpoint.

You can verify the endpoint present in the device using the following AT command

AT+CONF? Endpoint

Connect and interact with the AWS Cloud

Now that you’ve linked your AWS account with Cloud ID you can use the MQTT client in the AWS IoT Console to monitor the communication between your evaluation kit and the AWS Cloud.

  1. Navigate to the AWS IoT Console (

  2. In the navigation pane, select Test and then click MQTT Test Client.

  3. In Subscribe to a topic panel, enter #, and then click Subscribe.

Once the kit is connected to Wi-Fi, it will automatically connect to the AWS IoT Core. You will receive “OK 1 CONNECTED” in the serial terminal once the device is connected to the AWS IoT Core.

Sending and receiving data

Now that your device is connected you’re able to send and receive data from your AWS IoT Core account. To send data, you must first configure a topic. Each topic name has an associated topic number, e.g. 1, and is associated with a descriptive name, e.g. MyPubTopic. You configure a topic using this command:

AT+CONF Topic1=/MyPubTopic

You then send data by publishing text to the topic you just configured:

AT+SEND1 Hello World!

Where the “1” in “Topic1” refers to the topic number, where MyPubTopic is a string of your choice, and the “1” in SEND1 refers to the topic number again.

After a short time, you will receive the message “OK”. You should see the “Hello World!” message appearing on the AWS IoT Console under MyPubTopic. To receive data, you’ll need to subscribe to a topic. Here is an example:

Create a new topic, topic number 2 with label /MySubTopic, using the following command:

AT+CONF Topic2=/MySubTopic

Next, subscribe to topic number 2:


In your AWS IoT Consoler, select the MQTT test client and type /MySubTopic in Topicfiler. Click Subscribe. Navigate to the Publish to a topic tab and type /MySubTopic in the Topic name field. Keep the “Hello from the AWS IoT Console” message. Click Publish.

On your serial terminal, enter the following command to receive avilable messages on topic 2:


You will receive the message

“OK Hello from the AWS IoT Console”

Connect directly to AWS

We strongly recommend that you connect your AIROC™ IFW56810 to your AWS cloud using Cloud ID as described above as Cloud ID is central to the functionality of the AIROC™ IFW56810. However, we provide the following instructions as an alternative way to connect the AIROC™ IFW56810.

Configure the AWS Thing

Open the AWS IoT Console. From the left pane, select Manage, and then select Things. Click Create Things. On the Create things page, select Create Single Thing, and then click Next. In the terminal application, type the following command:

AT+CONF? ThingName

Copy the returned string (a sequence of alphanumeric characters) from the terminal. On the console, on the Specify Thing properties page, paste the copied string from the terminal into the Thing Name field under Thing Properties. Retain the ThingName as you will need it in the next step. Leave other fields at their default values, and then click Next.

Configure device certificate

First, you need to prepare the device certificate. In the terminal application, type the following command:

AT+CONF? Certificate

You will receive the device certificate in PEM format as part of the response. Copy the returned string (a longer sequence of alphanumeric symbols), and save it into a text file on your host machine as “ThingName.cert.pem”. Replace “ThingName” with the name of the Thing obtained after you executed AT+CONF? ThingName in the previous section.

Next, you need to attach the device certificate to the Thing. On the Configure device certificate page in the AWS Console, select Use my certificate, and then choose CA is not registered with AWS IoT. Under Certificate, select Choose File and find ThingName.cert.pem file you created, replacing “ThingName” with the name of the Thing obtained in the previous section. Under Certificate Status, select Active. Click Next.

You now need to attach policies to the certificate. Click Create to create a policy. This opens a new tab. Enter the policy name (e.g., “IoTDevPolicy”) and click Advanced mode. Copy the following section into the console:

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "*", "Resource": "*" } ] }

Click Create.

Note: The examples in this document are intended only for development environments. All devices in your end product must have credentials with privileges that authorize only intended actions on specific resources. The specific permission policies can vary for your use case. Identify the permission policies that best meet your business and security requirements.

Configure endpoint

  1. In the AWS IoT Console, choose Settings, and then copy your account endpoint string under Device data endpoint.

  2. Type the following AT command in the serial terminal to configure the endpoint:

AT+CONF Endpoint

Where Endpoint is the endpoint copied in step 1. The above step replaces the configured default endpoint used for evaluating the quick connect flow. Enter the following command in the serial terminal to establish a secure connection to the AWS IoT Core if you followed AWS flow


After a few seconds, the device will connect to the AWS IoT Core and you will receive the message


Further exploration

With your CCM module now connected to your Product Cloud you can try out the different capabilities of the product. Here are a few suggestions:

  • Run an Over-the-Air firmware update process

  • Try out other CCM Commands

Test CCM low power mode

Before trying out the low-power modes, ensure that the IFW56810 CCM evaluation kit is not connected to Wi-Fi. To disconnect the device. enter the following command in the serial terminal:


System sleep mode

To put the IFW56810 CCM evaluation kit to sleep mode for a particular duration, enter the following command:

AT+SLEEP <Sleep time in seconds>

Enter the following command to put the device in system sleep mode indefinitely untill it receives an external interrupt:


In sleep mode the device stays in sleep state until it receives an external interrupt. An external interrupt can be triggered through sending an AT command or by deasserting the INT pin.

Deep sleep mode

Enter the following command to put the device in deep sleep mode:


When deep sleep mode is activated the device will stay in deep sleep state until the device is reset (using RST pin) or is deasserting the INT pin.

Setting up a serial terminal on your PC


The following instructions are only for a Windows PC.

The IFW956810 CCM evaluation kit should be recognized by your PC as soon as you connect it. If the device is not recognized, see the troubleshooting section.

Determine the COM port number

Once you’ve connected your device, open Windows Device Manager. If your device was recognized you will notice new COM ports appearing in Windows Device Manager. You need to use Windows Device Manager to determine the COM port number assigned to your CCM kit, as below:



You need to choose the higher of the two COM port numbers, in this example it would be COM29.

Serial terminal settings

Next, you need to configure your serial terminal. The example below uses Tera Term, which you can download here, but you can use another suitable serial terminal.

  1. Open your terminal

  2. Find the higher of the COM port numbers assigned by Windows to your CCM evaluation kit, as described in the previous section

  3. Select Set Up, and Serial port.

  4. Configure the settings as shown in the screenshot below

  5. Select Set Up, and Terminal.

  6. Do the following:

    • Set End of Line as Line Feed.

    • Enable Local Echo to view the commands that you type on the terminal.

  7. Once you open the serial terminal, type the following command into the serial terminal:

AT+CONF? About

You should see a response

OK Infineon - IFW56810

Troubleshooting the CCM Kit

Choosing a COM port where two ports were enumerated when the kit is connected

The IFW956810 CCM evaluation kit has a FT2232H chip capable of supporting USB to dual-channel UART (USB serial converter A and USB serial converter B). Only the second of the two, USB serial converter B, is configured to enable USB-to-UART conversion. Therefore, use the higher-number COM port among the enumerated COM ports to communicate with the kit.

Device is not recognised

If the device is not recognized, you need to install the FTDI USB to UART Bridge Virtual Communication Port drivers from this link.

Diagnosing errors when commands are entered

For example, if:




First, make sure that you have typed the command correctly. If you’ve entered the command correctly, make a note of the error code and refer to this guide for details of the error code, which will point you to the cause.

Onboarding fails when using the CIRRENT™ mobile onboarding app

Verify that you enabled CONFMODE using the AT+CONFMODE command

ERR 14 UNABLE TO CONNECT received when using the AT+CONNECT command

The AT+CONNECT command first connects to Wi-Fi if not already connected, and then connects to the AWS IoT Core. If the command fails, first check that the WiFi connection is active, and that you have entered the right Wi-Fi details. Type the following command to verify whether the kit connects to Wi-Fi:


If the connection is successful, the device will respond with

OK Received ping response in <ping latency ms>

If the Wi-Fi connection test is successful but you still have no connectivity with your AWS account, first check the AWS IoT connection, and then check that the device certificate successfully uploaded to the AWS IoT Core.

ERR14 5 UNABLE TO CONNECT MQTT device authentication failure error for the AT+CONNECT command

The AT+CONNECT command first connects to Wi-Fi if not already connected and then connects to the AWS IoT Core. If you receive the

ERR14 5 UNABLE TO CONNECT MQTT device authentication failure

error you should try the following steps

  1. Check Your AWS endpoint.

  2. Check the device certificate uploaded to the AWS IoT Core and the device certificate present in the CCM device.

Changing the Wi-Fi network the device is connected to

To change the Wi-Fi network your device is connected to you first need to disconnect the device form the network using the following command on the serial terminal:


Next, follow the steps in the “Get Connected with AWS” section to enter new Wi-Fi credentials.

Steps to follow if CIRRENT(TM) Cloud ID connectivity to AWS is not working

These steps will help you to verify whether the device is waiting for the endpoint from the CIRRENT™ Cloud after the device is connected to Wi-Fi To complete the following you needed to onboard the device using the CIRRENT™ Cloud flow. Follow these steps if you do not receive an “OK 1 CONNECTED” response from the device.

Check if a Thing is present in the AWS IoT Console for your device

  1. Run the following command in the serial terminal to get the ThingName of your device.

    AT+CONF? ThingName
  2. Open the AWS IoT Console.

  3. From the left pane, select Manage, and then select Things.

  4. Note the Name of the Thing.

The ThingName shown on the serial terminal and the AWS IoT Console must be the same.

Check for a job in the CIRRENT™ Console

This job should be for sending the endpoint to your device. Do the following:

  1. In the Infineon OSTS Console, navigate to Services and Tools and CIRRENT™ Device Management.

  2. Click the Jobs tab, and review that the following columns for your new job is logged under the Jobs tab:

    • Action: ccm_config

    • Action Details: Endpoint should be the same as your AWS account endpoint. In the AWS IoT Console, choose Settings, check the endpoint under Device data endpoint.

    • Created Time: This should be the current time when you clicked Provision now in the CIRRENT™ Console.

    • Status: Active

    • Device IDs: Note the value in the Device ID field.

Check the pending state of the job

Do the following if a new job is available for your device.

  1. In the Infineon OSTS Console, navigate to Services and Tools and CIRRENT™ Device Management.

  2. Click the Jobs tab, and do the following:

    • Type the device ID noted in the previous section in the Device ID text box as Infineon_device ID.

    • Under the Pending Jobs section, verify that the Job ID, Action, and Action Details are the same as shown in the previous section.

After sending the AT command AT+CLOUD_SYNC in the serial terminal, the job will move from the “Pending” section to the jobs list, and the Result column will display Success and the Status column should show Completed. If execution of any of the above steps didn’t match the expectation as mentioned, check the Product Cloud API details and repeat the steps in Provision and prepare to connect the kit to your AWS account. Execute the following commands in the serial terminal if steps in Provision and prepare to connect the kit to your AWS account were completed after connecting to Wi-Fi.


Device registration with Cloud ID service failed

This message appears after connecting to Wi-Fi. The cause depends on the method of connection used. There is an error in the provisioning step. Do the following:

  1. Redo Step Provision and prepare to connect the kit to your AWS account

  2. Execute the following command in the serial terminal to pull the endpoint to the device after connecting to Wi-Fi.