PSOC™ 6 MCU: XENSIV™ 60 GHz radar presence detection

This code example demonstrates Infineon's radar presence detection sensor solution for human presence sensing within a configurable distance using the XENSIV™ BGT60TR13C and BGT60UTR11AIP 60 GHz radar sensors. This solution provides extremely high accuracy in detecting both micro and macro motions, enabling efficient user interaction with devices.

The code example utilizes a special optimization mechanism to demonstrate the switching between different radar device configurations on the fly. Depending on the application use case, you can switch between two or more radar configurations. For example, you can switch from a radar device configured for presence detection to gesture control based on certain conditions within the user application (e.g., the range bin information of the detected target).

The code example demonstrates how the presence detection application can benefit from using power-saving features enabled through dynamic reconfiguration. The present example takes an advantage of the opportunity to save power by reconfiguring the radar sensor to slow down the frame rate. This is particularly beneficial, especially when running in the MICRO_IF_MACRO mode. This mechanism is detailed in the Optimization mechanism section.

View this README on GitHub.

Provide feedback on this code example.

Requirements

ModusToolbox™ v3.5 or later (tested with v3.5)
Board support package (BSP) minimum required version: 4.0.0
Programming language: C
Associated parts: All PSOC™ 6 MCU parts

Supported toolchains (make variable 'TOOLCHAIN')

GNU Arm® Embedded Compiler v11.3.1(GCC_ARM) – Default value of TOOLCHAIN
Arm® Compiler v6.22 (ARM)
IAR C/C++ Compiler v9.50.2 (IAR)

Supported kits (make variable 'TARGET')

Rapid IoT Connect Developer Kit (CYSBSYSKIT-DEV-01) – Default value of TARGET
XENSIV™ BGT60TR13C Embedded Kit (KIT-BGT60TR13C-EMBEDD)
PSOC™ 6 AI Evaluation Kit (CY8CKIT-062S2-AI)

Hardware setup

XENSIV™ BGT60TR13C Connected Sensor Kit

The XENSIV™ KIT_CSK_BGT60TR13C is a comprehensive development kit consisting of:

Rapid IoT Connect Developer Kit CYSBSYSKIT-DEV-01
XENSIV™ BGT60TR13C Radar Wing EVAL_BGT60TR13C_WING

Figure 1. XENSIV™ BGT60TR13C CSK

To set up the kit:

Ensure that EVAL_BGT60TR13C_WING is mounted on the top of the CYSBSYSKIT-DEV-01 kit through the pin headers
Connect the CYSBSYSKIT-DEV-01 to your PC using the provided Micro USB cable through the KitProg3 USB connector
For optimal performance of the presence detection application, place the KIT_CSK_BGT60TR13C kit at a fixed location, such as the corner of a room

XENSIV™ BGT60UTR11AIP Connected Sensor Kit

The XENSIV™ KIT_CSK_BGT60UTR11AIP is a comprehensive development kit consisting of:

Rapid IoT Connect Developer Kit CYSBSYSKIT-DEV-01
XENSIV™ BGT60UTR11AIP Radar Wing EVAL_60UTR11AIP_WING

Figure 2. XENSIV™ BGT60UTR11AIP CSK

To set up the kit:

Ensure that EVAL_60UTR11AIP_WING is mounted on the top of the CYSBSYSKIT-DEV-01 kit through the pin headers
Connect the CYSBSYSKIT-DEV-01 to your PC using the provided Micro USB cable through the KitProg3 USB connector
For optimal performance of the presence detection application, place the KIT_CSK_BGT60UTR11AIP kit at a fixed location, such as the corner of a room

XENSIV™ BGT60TR13C Embedded Kit

Figure 3. KIT-BGT60TR13C-EMBEDD kit

Connect the KIT-BGT60TR13C-EMBEDD kit to your PC using the provided Micro USB cable through the KitProg3 USB connector
For optimal performance of the presence detection application, place the KIT-BGT60TR13C-EMBEDD kit at a fixed location, such as the corner of a room

PSOC™ 6 AI Evaluation Kit

Figure 4. CY8CKIT-062S2-AI kit

Connect the CY8CKIT-062S2-AI to your PC using the provided Micro USB cable through the KitProg3 USB connector
For optimal performance of the presence detection application, place the CY8CKIT-062S2-AI kit at a fixed location, such as the corner of a room

Software setup

See the ModusToolbox™ tools package installation guide for information about installing and configuring the tools package.

Install a terminal emulator if you do not have one. Instructions in this document use Tera Term.

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.

Use Project Creator GUI

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 (locally available at {ModusToolbox™ install directory}/tools_{version}/project-creator/docs/project-creator.pdf)
On the Choose Board Support Package (BSP) page, select a kit supported by this code example. See Supported kits

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

Use Project Creator CLI

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 "XENSIV™ 60GHz Radar Presence Detection" application with the desired name "XENSIV 60GHz Radar Presence Detection" configured for the CYSBSYSKIT-DEV-01 BSP into the specified working directory, C:/mtb_projects:

project-creator-cli --board-id CYSBSYSKIT-DEV-01 --app-id mtb-example-ce241611-xensiv-60ghz-radar-presence-detection --user-app-name XENSIV 60GHz Radar Presence Detection--target-dir "C:/mtb_projects"

The 'project-creator-cli' tool has the following arguments:

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

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

Open the project

After the project has been created, you can open it in your preferred development environment.

Eclipse IDE

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

Visual Studio (VS) Code

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

Arm® Keil® µVision®

Double-click the generated {project-name}.cprj file to launch the Keil® µVision® IDE.

For more details, see the Arm® Keil® µVision® for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_uvision_user_guide.pdf).

IAR Embedded Workbench

Open IAR Embedded Workbench manually, and create a new project. Then select the generated {project-name}.ipcf file located in the project directory.

For more details, see the IAR Embedded Workbench for ModusToolbox™ user guide (locally available at {ModusToolbox™ install directory}/docs_{version}/mt_iar_user_guide.pdf).

Command line

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

Operation

XENSIV™ BGT60TR13C Connected Sensor Kit

Open a terminal program and select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud
Program the board using one of the following:
Using Eclipse IDE
1. Select the application project in the Project Explorer
2. In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3_MiniProg4)
In other IDEs

Follow the instructions in your preferred IDE.
Using CLI

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:
```
make program TARGET=<BSP> TOOLCHAIN=<toolchain>
```
Example:
```
make program TARGET=CYSBSYSKIT-DEV-01 TOOLCHAIN=GCC_ARM
```

XENSIV™ BGT60UTR11AIP Connected Sensor Kit

Open radar_device_config.h file
Edit the definition of the CONNECTED_RADAR_DEVICE macro from DEVICE_BGT60TR13C to DEVICE_BGT60UTR11
Save the file and close
Open a terminal program and select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud
Program the board using one of the following:
Using Eclipse IDE
1. Select the application project in the Project Explorer
2. In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3_MiniProg4)
In other IDEs

Follow the instructions in your preferred IDE.
Using CLI

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:
```
make program TARGET=<BSP> TOOLCHAIN=<toolchain>
```
Example:
```
make program TARGET=CYSBSYSKIT-DEV-01 TOOLCHAIN=GCC_ARM
```

XENSIV™ BGT60TR13C Embedded Kit

The KIT-BGT60TR13C-EMBEDD kit requires an external programmer, such as MiniProg4 that uses the SWD interface.

Figure 5. MiniProg4

Set the proper jumpers on switches S3 and S5 by closing pins 1 and 2, and opening pins 3 and 4

Figure 6. Switch 3 and 5 position
Connect the KIT-BGT60TR13C-EMBEDD kit SWD interface with the programmer. Then, plug the USB cables for the board and for the programmer to power on both
Open a terminal program and select a COM port where the board is connected (not the MiniProg4 port). Set the serial port parameters to 8N1 and 115200 baud
Program the board using one of the following:
Using Eclipse IDE
1. Select the application project in the Project Explorer
2. In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3_MiniProg4)
Using CLI

From the terminal, execute:
```
make program TARGET=KIT-BGT60TR13C-EMBEDD TOOLCHAIN=GCC_ARM
```

PSOC™ 6 AI Evaluation Kit

Open a terminal program and select the KitProg3 COM port. Set the serial port parameters to 8N1 and 115200 baud
Program the board using one of the following:
Using Eclipse IDE
1. Select the application project in the Project Explorer
2. In the Quick Panel, scroll down, and click <Application Name> Program (KitProg3_MiniProg4)
In other IDEs

Follow the instructions in your preferred IDE.
Using CLI

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:
```
make program TARGET=<BSP> TOOLCHAIN=<toolchain>
```
Example:
```
make program TARGET=CY8CKIT-062S2-AI TOOLCHAIN=GCC_ARM
```

Successful programming

Upon successful programming, the application starts automatically and displays the confirmation message "XENSIV 60 GHz Radar Presence Detection" on the UART terminal.

Ensure that the kit LED blinks at approximately 1 Hz.

Error message

If the mounted radar wing board does not match the enabled radar device configurations, an error message will be displayed on the UART terminal, indicating a configuration mismatch.

Figure 7. Terminal output wrong configurations

Open radar_device_config.h file
Edit the definition of the CONNECTED_RADAR_DEVICE macro for the mounted radar device
Save the file and close
Reprogram the board

Terminal outputs

The information that is printed out is in the following format:
[INFO] Radar state Range bin Time stamp
Current presence state, Current radar setting, New radar setting

Figure 8. Terminal output choosing different configurations

Table 1. Terminal outputs

Parameters	Event type	Description
Radar state	Macro presence	Presence event detected
Range bin	2	Maximum range bin
Time stamp	'4298'	Relative time in ms
Current presence state	0	0: Macro 1: Micro 2: Absence
Current radar setting	10 Hz	10 Hz: Low frame rate 200 Hz: High frame rate
New radar setting	macro/micro	Depends on the detection

Note: Time Stamp is relative to the boot time, which means that when the application boots up first, the time counting starts from 0 ms.

Conversion of range bin to range in meters can be done by using the following relation:

R (range in meters) = (xensiv_radar_presence_get_bin_length() * config.max_range_bin)

For example: If xensiv_radar_presence_get_bin_length() = 0.325, R = 0.325 * 2 = 0.66 m

Sensor information and LEDs

XENSIV™ BGT60TR13C Connected Sensor Kit

For the KIT_CSK_BGT60TR13C kit, the radar task is suspended if the radar wing board is not connected to the feather kit. The sensor initialization process is indicated by blinking the red LED (CYBSP_USER_LED). The red LED (CYBSP_USER_LED) on the CYSBSYSKIT-DEV-01 kit blinks when the system is operational (ready state).

The LED on the KIT_CSK_BGT60TR13C kit uses the following color codes to indicate different events:

Table 2. Events and LED indication KIT_CSK_BGT60TR13C

LED color	Event type	Description
Red	`XENSIV_RADAR_PRESENCE_STATE_MACRO_PRESENCE`	Presence event detected
Red	`XENSIV_RADAR_PRESENCE_STATE_MICRO_PRESENCE`	Presence event detected
Green	`XENSIV_RADAR_PRESENCE_STATE_ABSENCE`	Absence event detected

XENSIV™ BGT60UTR11AIP Connected Sensor Kit

For the KIT_CSK_BGT60UTR11AIP kit, the radar task is suspended if the radar wing board is not connected to the feather kit. The sensor initialization process is indicated by blinking the red LED (CYBSP_USER_LED). The red LED (CYBSP_USER_LED) on the CYSBSYSKIT-DEV-01 kit blinks when the system is operational (ready state).

The LED on the KIT_CSK_BGT60UTR11AIP kit uses the following color codes to indicate different events:

Table 3. Events and LED indication KIT_CSK_BGT60UTR11AIP

LED color	Event type	Description
Red	`XENSIV_RADAR_PRESENCE_STATE_MACRO_PRESENCE`	Presence event detected
Red	`XENSIV_RADAR_PRESENCE_STATE_MICRO_PRESENCE`	Presence event detected
Green	`XENSIV_RADAR_PRESENCE_STATE_ABSENCE`	Absence event detected

XENSIV™ BGT60TR13C Embedded Kit

There is no user LED for the KIT-BGT60TR13C-EMBEDD kit to indicate the sensor initialization or operational process.

The LED indicates different events with different colors as follows:

Table 4. Events and LED indication for KIT-BGT60TR13C-EMBEDD

LED color	Event type	Description
Red	`XENSIV_RADAR_PRESENCE_STATE_MACRO_PRESENCE`	Presence event detected
Red	`XENSIV_RADAR_PRESENCE_STATE_MICRO_PRESENCE`	Presence event detected
Green	`XENSIV_RADAR_PRESENCE_STATE_ABSENCE`	Absence event detected

PSOC™ 6 AI Evaluation Kit

The CY8CKIT-062S2-AI kit features LEDs that indicate different events through a color-coded system. The LEDs and their corresponding events are:

Table 5. Events and LED indication for CY8CKIT-062S2-AI kit

LED color	Event type	Description
Red (LED1)	`XENSIV_RADAR_PRESENCE_STATE_MACRO_PRESENCE`	Presence event detected
Red (LED1)	`XENSIV_RADAR_PRESENCE_STATE_MICRO_PRESENCE`	Presence event detected
Red (LED2)	`XENSIV_RADAR_PRESENCE_STATE_ABSENCE`	Absence event detected

Configuration parameters

You can configure the application parameters using the options provided on the terminal as follows:

Press Enter to switch from work to settings mode

Type help and press Enter to see a list of configurable parameters as shown in Figure 9

Figure 9. Configuration mode

The following table lists the configurable parameters with valid values:

Table 6. Presence detection algorithm configuration parameters

Key	Default value	Valid values
set_max_range (m)	2.0	0.66 – 5.0
set_macro_threshold	0.5	0.5 – 2.0
set_micro_threshold	12.5	0.2 – 50.0
set_bandpass_filter	disable	enable/disable
set_decimation_filter	disable	enable/disable
set_mode	micro_if_macro	macro_only/micro_only/micro_if_macro/micro_and_macro
verbose	disable	Enable detailed status to be updated for every second
board_info	–	Board information
config	–	Solution configuration information

Note the following:

Micro motions: Detecting small movements such as finger gestures or small head movements in a typical smart home environment. These include working on a laptop or keyboard, or normal breathing, and blinking of the eyes in sitting or standing positions (in line of sight)
Macro motions: Detecting major movements into or through the field of view (motion detection)

Note 1: Macro and micro threshold parameters can be adjusted to achieve different levels of sensitivity. The following table summarizes three different levels. For example, high sensitivity means that the solution is more sensitive to smaller movements. You can set any threshold values based on your use case requirement

Note 2: If you want to see the data to be printed continuously in the serial terminal, enable the verbose

Table 7. Sensitivity levels with corresponding threshold setting

Sensitivity	Macro threshold value	Micro threshold value
High	0.5	12.5
Medium	1.0	25
Low	2.0	50

Type the command name with the required value and press Enter

If the parameter update is successful, "ok" is displayed; otherwise "command not recognized" or "invalid value" is printed

For details, see the XENSIV™ Radar Presence API Reference Guide.

Debugging

You can debug the example to step through the code.

In Eclipse IDE

Use the <Application Name> Debug (KitProg3_MiniProg4) configuration in the Quick Panel. For details, see the "Program and debug" section in the Eclipse IDE for ModusToolbox™ user guide.

Note: (Only while debugging) On the CM4 CPU, some code in main() may execute before the debugger halts at the beginning of main(). This means that some code executes twice – once before the debugger stops execution, and again after the debugger resets the program counter to the beginning of main(). See PSOC™ 6 MCU: Code in main() executes before the debugger halts at the first line of main() to learn about this and for the workaround.

In other IDEs

Follow the instructions in your preferred IDE.

Design and implementation

Resources and settings

This application uses a modular approach to build a presence application combining a radar driver and presence algorithm library and the following components:

Figure 10. Application overview

The radar configuration parameters are generated from a PC tool and saved in radar_settings.h file. For more details, see the XENSIV™ BGT60TRxx Radar API Reference Guide.

After initialization, the application runs in an event-driven way. The radar interrupt is used to notify the MCU, which retrieves the raw data into a software buffer and then triggers the main task to normalize and feed the data to the presence library.

Figure 11. Application execution

Optimization mechanism

This code example uses a special optimization mechanism to demonstrate the switching between different radar device configurations:

Low frame rate is sufficient for macro movement detection
High frame rate is required for micro movement detection

Therefore, in the default presence detection mode of MICRO_IF_MACRO, the radar device can be configured with a low frame rate by default and only reconfigured with a high frame rate configuration when it is expected to perform micro detection. By implementing such a mechanism, the application benefits from some power-savings.

In the processing task, the optimization object is initialized with the reconfiguration function pointer. The application then runs the presence algorithm normally. The evaluation for the reconfiguration of the radar device is performed in two cases:

The application receives a request to change the presence detection mode (e.g., from MACRO_ONLY to MICRO_IF_MACRO)
A change in the presence detection state occurs (e.g., from absence to macro detected)

The radar device reconfiguration involves rewriting the radar registers with a new set of values, reconfiguring the radar FIFO limit, and restarting the radar frame

Figure 12. Radar activity

Configuration logic

The following configuration logic (see Figure 12) is deployed in the evaluation process when the application is operating in MICRO_IF_MACRO mode.

If the radar is currently configured with a low frame rate and has detected a macro presence, it can detect a micro presence. Therefore, the radar needs to be reconfigured with a high frame rate
If the radar is currently configured with a high frame rate and has detected a macro presence instead of a micro presence, the radar can be reconfigured with the low frame rate to save power
If the radar is currently configured with a high frame rate and there is no presence detected (absence), the radar can be reconfigured with a low frame rate to detect a macro presence

Table 8. Switching to MICRO_IF_MACRO mode

Radar current state	Last detected state	Radar new mode
Low frame rate	MACRO	High frame rate
High frame rate	MACRO	High frame rate
High frame rate	ABSENCE	Low Frame rate

Adding different configurations

Each radar configuration is a structure containing a pointer to a register list, the number of registers, and the FIFO limit. To use a radar configuration suitable for your application, perform these steps:

In optimization_list.h file, edit or add to the existing configurations (i.e., optimizations_list[] and optimization_type_e) in the code example.
Provide the new configuration register list per the example given in radar_high_framerate_config.h and radar_low_framerate_config.h files. You can use the XENSIV™ BGT60TRxx Radar Sensor to generate the register list.

typedef struct {
    uint32_t *reg_list;
    uint8_t reg_list_size;
    uint32_t fifo_limit;
} optimization_s;

optimization_s optimizations_list[] = {
    {
        register_list_macro_only,
        XENSIV_BGT60TRXX_CONF_NUM_REGS_MACRO,
        NUM_SAMPLES_PER_FRAME * 2
    },
    {
        register_list_micro_only,
        XENSIV_BGT60TRXX_CONF_NUM_REGS_MICRO,
        NUM_SAMPLES_PER_FRAME * 2
    },
    {
        register_list_user_config,
        XENSIV_BGT60TRXX_CONF_NUM_REGS_USER_CONFIG,
        NUM_SAMPLES_PER_FRAME * 2
    }
};

typedef enum {
    CONFIG_LOW_FRAME_RATE_OPT,
    CONFIG_HIGH_FRAME_RATE_OPT,
    CONFIG_USER_CONFIG_OPT,
    CONFIG_UNINITIALIZED = 64
} optimization_type_e;

Optimizer API

Table 9. API functions

API function	Description
`radar_config_optimizer_init`	Initializes optimization component. Requires a pointer to the radar reconfiguration function
`radar_config_optimizer_set_operational_mode`	Saves the new mode to which you want to switch. This function is called during mode selection in the CLI
`radar_config_optimize`	Switches to the new mode. The new list of registers is chosen and saved into the radar, depending on the selected mode and last presence event
`radar_config_get_current_optimization`	Returns the current chosen optimization mode: low or high frame rate

Table 10. Application resources

Resource	Alias/object	Purpose
UART (HAL)	cy_retarget_io_uart_obj	UART HAL object used by Retarget-IO for the Debug UART port
SPI (HAL)	spi	SPI driver to communicate with radar sensor
GPIO (HAL)	CYBSP_USER_LED	User LED
GPIO (HAL)	CYBSP_USER_LED_RED	User LED
GPIO (HAL)	CYBSP_USER_LED_GREEN	User LED
GPIO (HAL)	CYBSP_USER_LED_BLUE	User LED

Related resources

Resources	Links
Application notes	AN228571 – Getting started with PSOC™ 6 MCU on ModusToolbox™ AN215656 – PSOC™ 6 MCU dual-core system design AN124642 – Presence detection solution using XENSIV™ KIT_CSK_BGT60TR13C 60 GHz radar
Code examples	Using ModusToolbox™ on GitHub
Device documentation	PSOC™ 6 MCU datasheets PSOC™ 6 technical reference manuals
Development kits	Select your kits from the Evaluation board finder.
Libraries on GitHub	sensor-xensiv-bgt60trxx – Driver library to interface with the XENSIV™ BGT60TRxx 60 GHz FMCW radar sensors xensiv-radar-presence – Presence library to detect human presence using XENSIV™ BGT60TR13C sensor-dsp – Sensor-DSP library to provide signal processing functions for sensor applications mtb-pdl-cat1 – PSOC™ 6 Peripheral Driver Library (PDL) mtb-hal-cat1 – Hardware Abstraction Layer (HAL) library retarget-io – Utility library to retarget STDIO messages to a UART port
Middleware on GitHub	psoc6-middleware – Links to all PSOC™ 6 MCU middleware
Tools	ModusToolbox™ – ModusToolbox™ 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.

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 more information about connected sensor kit, see IoT sensor platform.

Document history

Document title: CE241611 – PSOC™ 6 MCU: XENSIV™ 60 GHz radar presence detection

Version	Description of change
1.0.0	New code example
1.1.0	Changes in readme and support for MTB 3.5

All referenced product or service names and trademarks are the property of their respective owners.

The Bluetooth® word mark and logos are registered trademarks owned by Bluetooth SIG, Inc., and any use of such marks by Infineon is under license.

PSOC™, formerly known as PSoC™, is a trademark of Infineon Technologies. Any references to PSoC™ in this document or others shall be deemed to refer to PSOC™.

© Cypress Semiconductor Corporation, 2025. This document is the property of Cypress Semiconductor Corporation, an Infineon Technologies company, and its affiliates ("Cypress"). This document, including any software or firmware included or referenced in this document ("Software"), is owned by Cypress under the intellectual property laws and treaties of the United States and other countries worldwide. Cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragraph, grant any license under its patents, copyrights, trademarks, or other intellectual property rights. If the Software is not accompanied by a license agreement and you do not otherwise have a written agreement with Cypress governing the use of the Software, then Cypress hereby grants you a personal, non-exclusive, nontransferable license (without the right to sublicense) (1) under its copyright rights in the Software (a) for Software provided in source code form, to modify and reproduce the Software solely for use with Cypress hardware products, only internally within your organization, and (b) to distribute the Software in binary code form externally to end users (either directly or indirectly through resellers and distributors), solely for use on Cypress hardware product units, and (2) under those claims of Cypress's patents that are infringed by the Software (as provided by Cypress, unmodified) to make, use, distribute, and import the Software solely for use with Cypress hardware products. Any other use, reproduction, modification, translation, or compilation of the Software is prohibited.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS DOCUMENT OR ANY SOFTWARE OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. No computing device can be absolutely secure. Therefore, despite security measures implemented in Cypress hardware or software products, Cypress shall have no liability arising out of any security breach, such as unauthorized access to or use of a Cypress product. CYPRESS DOES NOT REPRESENT, WARRANT, OR GUARANTEE THAT CYPRESS PRODUCTS, OR SYSTEMS CREATED USING CYPRESS PRODUCTS, WILL BE FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR THEFT, OR OTHER SECURITY INTRUSION (collectively, "Security Breach"). Cypress disclaims any liability relating to any Security Breach, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any Security Breach. In addition, the products described in these materials may contain design defects or errors known as errata which may cause the product to deviate from published specifications. To the extent permitted by applicable law, Cypress reserves the right to make changes to this document without further notice. Cypress does not assume any liability arising out of the application or use of any product or circuit described in this document. Any information provided in this document, including any sample design information or programming code, is provided only for reference purposes. It is the responsibility of the user of this document to properly design, program, and test the functionality and safety of any application made of this information and any resulting product. "High-Risk Device" means any device or system whose failure could cause personal injury, death, or property damage. Examples of High-Risk Devices are weapons, nuclear installations, surgical implants, and other medical devices. "Critical Component" means any component of a High-Risk Device whose failure to perform can be reasonably expected to cause, directly or indirectly, the failure of the High-Risk Device, or to affect its safety or effectiveness. Cypress is not liable, in whole or in part, and you shall and hereby do release Cypress from any claim, damage, or other liability arising from any use of a Cypress product as a Critical Component in a High-Risk Device. You shall indemnify and hold Cypress, including its affiliates, and its directors, officers, employees, agents, distributors, and assigns harmless from and against all claims, costs, damages, and expenses, arising out of any claim, including claims for product liability, personal injury or death, or property damage arising from any use of a Cypress product as a Critical Component in a High-Risk Device. Cypress products are not intended or authorized for use as a Critical Component in any High-Risk Device except to the limited extent that (i) Cypress's published data sheet for the product explicitly states Cypress has qualified the product for use in a specific High-Risk Device, or (ii) Cypress has given you advance written authorization to use the product as a Critical Component in the specific High-Risk Device and you have signed a separate indemnification agreement.
Cypress, the Cypress logo, and combinations thereof, ModusToolbox, PSoC, CAPSENSE, EZ-USB, F-RAM, and TRAVEO are trademarks or registered trademarks of Cypress or a subsidiary of Cypress in the United States or in other countries. For a more complete list of Cypress trademarks, visit www.infineon.com. Other names and brands may be claimed as property of their respective owners.

Name		Name	Last commit message	Last commit date
Latest commit History 2 Commits
deps		deps
images		images
source		source
.cyignore		.cyignore
.gitignore		.gitignore
.mtbqueryapi		.mtbqueryapi
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
xensiv_radar_presence.c		xensiv_radar_presence.c
xensiv_radar_presence.h		xensiv_radar_presence.h

License

Infineon/mtb-example-ce241611-xensiv-60ghz-radar-presence-detection

Folders and files

Latest commit

History

Repository files navigation

PSOC™ 6 MCU: XENSIV™ 60 GHz radar presence detection

Requirements

Supported toolchains (make variable 'TOOLCHAIN')

Supported kits (make variable 'TARGET')

Hardware setup

Software setup

Using the code example

Create the project

Open the project

Operation

XENSIV™ BGT60TR13C Connected Sensor Kit

XENSIV™ BGT60UTR11AIP Connected Sensor Kit

XENSIV™ BGT60TR13C Embedded Kit

PSOC™ 6 AI Evaluation Kit

Successful programming

Terminal outputs

Sensor information and LEDs

XENSIV™ BGT60TR13C Connected Sensor Kit

XENSIV™ BGT60UTR11AIP Connected Sensor Kit

XENSIV™ BGT60TR13C Embedded Kit

PSOC™ 6 AI Evaluation Kit

Configuration parameters

Debugging

Design and implementation

Resources and settings

Optimization mechanism

Configuration logic

Adding different configurations

Optimizer API

Related resources

Other resources

Document history

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Languages

Packages