Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob

ModusToolbox™ version 2.x tools known issues – KBA236147

ModusToolbox™ version 2.x tools known issues – KBA236147

Community Manager
Community Manager
Community Manager
1000 replies posted First like given 750 replies posted

Community Translation: ModusToolbox™ バージョン 2.x ツールの既知の問題 – KBA236147

Version: *B

Question: What are the known issues with the various ModusToolbox™ tools?

 Answer: The sections in this document provide known issues and workarounds for various tools from the ModusToolbox™ version 2.x tools package release notes. Some of these issues may apply to version 3.x tools, but they are not included in the 3.x release notes, because they are not new issues.

  1. Installation
  2. Project Creator
  3. Proxy
  4. Building/programming/debugging
  5. Eclipse IDE
  6. Library Manager
  7. Device Configurator
  8. CAPSENSE™ Tuner


1    Installation




On Windows, when using various tools, the following error displays:

ERROR:fatal: unable to access 'http://git-ore.aus.cypress.com/repo-staging/device-db/': error setting certificate verify locations: CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none

This is a conflict issue with Cygwin when you set the environment variable:


Only administrators (or accounts with SeCreateSymbolicLinkPrivilege) can create native symbolic links. Since the ModusToolbox™ installer does not run with elevated privileges for per-user installation, it fails to construct the symbolic links required by the modus-shell tool.

To resolve these errors, do the following:

  1. Uninstall the ModusToolbox™ tools package.
  2. Remove the CYGWIN environment variable.
  3. Restart the system.
  4. Re-install the ModusToolbox™ tools package.


After updating from macOS Mojave to Big Sur, the previously installed version of ModusToolbox™ reports various errors in the Eclipse IDE and other tools.

This issue is likely caused by Xcode not being updated properly.

Re-install ModusToolbox™ tools package. See the installation guide as needed.

Re-install x-code; run:
xcode-select --install


On common Linux distributions, the serial UART ports (usually /dev/ttySx or /dev/ttyUSBx devices) belong to the root user and to the dialout and plugdev groups. Standard users are not allowed to access these devices.

An easy way to allow the current user access to the Linux machine's serial ports is by adding the user to the dialout or plugdev group. This can be done using the following command:

$sudo usermod -a -G dialout,plugdev $USER

Note For this command to take effect, the user must log out and then log back in.


2    Project Creator




Using the Project Creator Target IDE feature, the application that was exported to a third-party IDE doesn’t work in that IDE.

There are limitations to the export process. For example, IAR and µVision are not supported in macOS or Linux. In other cases, you need to update configuration settings in the third-party IDE. Refer to the "Export to IDEs" chapter in the ModusToolbox™ tools package user guide for more details.


In the default case, project creation and library updates require internet access. In some cases, using a VPN may adversely affect the time required for these operations due to a delay in DNS server response times for external IP addresses such as github.com.

If you experience issues such as this, project creation and library update times can be improved by disabling the VPN connection during those operations.

To determine if this is an issue for you, open a terminal window and enter "nslookup github.com". If the response is not immediate, then you may benefit from disabling your VPN connection.


When trying to create a new project you may not see any BSPs or applications to select, as well as the following error message:

Unable to open file at http://github.com/Infineon/mtb-super-manifest/raw/v2.X/mtb-super-manifest-fv2.xml

Some boards and applications may be missing. Check the console for a detailed error message.

Verify that you have a network connection and see the instructions in the Installation problem section above concerning proxy settings.

This may also be caused by your work environment not having access to GitHub. Refer to KBA230953 for details on how to work around this problem.


3   Proxy




When trying to create a new project, you may see the following error message:

Unable to open file at http://github.com/Infineon/mtb-super-manifest/raw/v2.X/mtb-super-manifest.xml.

Some boards and apps may be missing. Check the logfile for a detailed error message.

This can happen if you are behind a firewall and do not have your proxy settings configured. You must set your HTTP_PROXY and HTTPS_PROXY environment variables or use the Proxy Helper tool from the Settings menu. You can also find it in:



In some cases, incorrect proxy settings in the Project Creator or Library Manager tool can prevent the proxy server settings from being edited to correct values.

Run the Proxy Helper tool from the Settings menu to reset the proxy mode to direct. The tool is also located in:



For example:

./proxy-helper --config set mode=direct



4     Building/programming/debugging




On Windows 11, the KitProg3 UART driver is not certified, and this causes issues for the UART interface, CAPSENSE™ Tuner, and CyBridge for the StopBits, ParityType, DataBits, and BaudRates parameters.

As a short-term solution, manually install the Windows 10 driver:

In the Device Manager under the Ports tab, find USB Serial Device item (COMX).

Right-click on it and select Update driver > Browse my computer for drivers

Navigate to the appropriate driver:

The path for the drivers is <ModusToolbox™ Install_DIR>/tools_3.0/kp-firmware/drivers/.

Select either KitProg3 or MiniProg4, then the UART option, then Win10 and Win10x64.

Click Next > and then Close.

This issue will be resolved in a future release.


When using VS Code with Cortex-Debug v0.4.5, some operations may not work on Linux and macOS via FTDI, KitProg3, or MiniProg4 programmers, with messages indicating that the USB device is busy. The J-Link probe is not impacted.

This can happen for various operations (Program, Erase, Launch, Attach) when executed a second time, due to Cortex-Debug not terminating the OpenOCD process.

Manually terminate the OpenOCD process and switch versions of Cortex-Debug from v0.4.5 to v0.4.4, v0.4.6, or later.

This issue is tracked on GitHub: https://github.com/Marus/cortex-debug/issues/493



When launching a debug session, execution does not halt at main() on PSoC™ 64 devices with J-Link/SEGGER debug tools. This may happen on virtual or slow PCs, or when the communication interface (SWD, JTAG) speed =< 100k Hz.

Add small delay at the very beginning of Reset_Handler so the J-Link will have enough time to halt the CPU before starting execution of the application. A delay of 100 ms should be sufficient in most cases. Example of a simple delay loop in Reset_Handler:

/* 1<<22 corresponds to 4M so loop should take approx. 12M cycles */
mov   r0, #1
lsl   r0, #22
    subs  r0, #1
    bne   debug_delay
    bl Cy_OnResetUser
    cpsid i


When trying to debug a FreeRTOS AWS project in the Eclipse IDE when connected via the MiniProg4 probe, you might see the following messages the ModusToolbox™ Console:

"Failed to write memory at <address>"

"Error: Write failure during wipe of variable: uxTopUsedPriority at <address>"

These messages can be safely ignored.


Sometimes the J-Link 'Program' configuration for CYW43907/CYW53907 devices may fail if executed after an 'Erase' operation on macOS/Linux. This is caused by an issue in the J-Link script used for these devices.

Turn the devices' power supply off and on, and then try the 'Program' configuration again.


Programming the S25FS512S external memory device mounted on the CYW9P62S1-43012EVB-01 kit might not work if SFDP auto-detection is selected in the QSPI Configurator.

This is caused by corrupted SFDP table in this memory.

Select "S25FS512S" instead of "Auto detect SFDP" for the memory slot in the QSPI Configurator.


After programming a PSoC™ 4 device, the following message displays:

Polling target psoc4.cpu failed, try to reexamine

None. You can safely ignore this message. This might occur if the SWD is disconnected after the reset.


The ModusToolbox™ build process stops at some points, such as during auto-discovery, and it takes longer than other times.

This is likely due to anti-virus software scanning various ModusToolbox™ directories. To resolve this, change your anti-virus settings to exclude the following as appropriate for your installation (where ~ is your home directory):

  • Installation directory (e.g., ~/ModusToolbox/)
  • Settings directory (e.g., ~/.modustoolbox/)
  • Applications directories (e.g., ~/MyExamples/)
  • Eclipse IDE workspace directory (e.g., ~/mtw/)


While debugging an application built with the GCC toolchain, some breakpoints cannot be reached as the application code referenced by the breakpoints is inlined.

The GDB behavior described above has no functional impact on the application execution.

Switch the optimization level from -Og (default in the CONFIG=Debug mode) to -O0, by editing the application Makefile:


Changing the optimization flag to -O0 may impact the application behavior or memory usage. We recommend disabling the compiler optimizations only for debugging purposes.


PSoC™ 64 "Secure Boot" MCUs do not support the programming and debugging via JTAG interface.  It is because of the specifics of PSoC™ 64 MCUs - JTAG pins are configured after unpredictable amount of time after what causes a lot of warnings during programming via JTAG. 

Use SWD interface with PSoC™ 64 "Secure Boot" MCUs in Eclipse and VS Code IDEs


Unable to acquire PSoC™ 4 target with J-Link probe if target is in PROTECTED state. J-Link probe does not support device acquisition in Test Mode. This prevents invocation of SROM API making it impossible to re-program or erase the chip in PROTECTED state.

The workaround is to unprotect/erase the chip using MiniProg4 or KitProg3 probe.


A "Failed to read memory at <address>" message may appear in "Memory View" of the Eclipse IDE when connected via the MiniProg4 probe and try to read memory from invalid address.

You can safely ignore this error


In VS Code, "Exception has occurred" error might appear when you execute Attach launch configuration. Such errors started to be visible in VS Code - 1.53.2.

You can safely ignore this error.


In VS Code, "Failed to launch undefined GDB Server: Timeout." error might appear if to launch Debug J-Link launch configuration with KIT_XMC47_RELAX_V1 after several 'step over', 'step into' operations during the previous Debug session what was stopped.

Re-run the launch configuration again after failure


In VS Code, the J-Link launch configuration does not stop at Reset_Handler after ‘Restart’, but at some other line of code.

For PSoC™ 6 MCUs, this is associated with any "monitor" command in GDB. For example, if you press the Restart button, the Cortex-Debug plugin sends "monitor halt" and "monitor reset" commands to the GDB causing GDB to go out-of-sync with the target.

GDB does not know what the "monitor xxx" command does. It does not expect that "monitor reset" will change the state of the target.

For XMC™ and PSoC™ 4 MCUs, such behavior is caused by the using "Cortex M0" target for PSoC™ 4 and "Cortex-M4" for XMC™ devices as the workaround for other issue with Attach in SEGGER SW.

Step through code to enter the Reset_Handler.






When attempting to Program/Debug with Miniprog4 or J‑Link probes in JTAG mode, the tool displays errors similar to the following:


These errors are likely caused by the device being in sleep mode. Open the Device Configurator, and set the System Idle Power Mode setting to 'Active' to turn off DeepSleep mode. JTAG is not available in sleep mode.

Alternately, use SWD to acquire the target, and then switch to JTAG.


If an application includes multiple BSPs that span major version numbers (for example, v1.x and v2.x) as local dependencies, there will be build conflicts. This is because of changes in the names of the BSP's dependencies.

There are two options:

  1. The application can be updated to use the new MTB flow with the BSPs (and dependencies) marked as shared.
  2. All local BSPs within an application must have the same major version number. Once the application is updated to only have a single major version of the BSP, any of the dependent libraries that were pulled down by the removed BSP version need to be removed from the application. This includes removing any .lib or .mtb files. The problematic dependencies that must be removed include the following:
  • 1.x BSP dependencies: psoc6pdl, psoc6hal
  • 2.x BSP dependencies: mtb-pdl, mtb-hal


KitProg3 and J-Link launch configurations do not work when you change the build configuration from Debug to Release or vice-versa. This applies to the Eclipse IDE for ModusToolbox™ and Visual Studio (VS) Code.

Launch configurations contain the path to the executable, and that changes for each build configuration.

After you change from Debug to Release or vice-versa, click the "Generate Launches" command in the Quick Panel.

You can alternately run the following command to create new launch configurations:

  • make eclipse for Eclipse IDE for ModusToolbox™
  • make vscode for VS Code

Be aware that this option overwrites any changes you may have made to the configurations.


On macOS for a PSoC™ 64 "Secure Boot" or PSoC™ 6A project, using the Eclipse IDE for ModusToolbox™, the "Attach" launch configuration fails every second time it is used:

for an RTOS-based project

if "Attach" is launched when the target is halted on breakpoint

Reset the device each time you run the "Attach" configuration.



For the Arm Cortex CM4 core, some code in main() executes before the debugger stops at start 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 start of main() and you start debugging.

If you observe this issue, and it affects your application, put a delay loop at the start of main() to allow time for debugging subsystem initialization. The following code tests for the presence of the debugger before entering the delay loop:

int main(void)
    /* If an active debugger is detected, give it some time to execute SYSRESETREQ
    * otherwise, the application runs before the debugger is fully operational */
    if (CoreDebug->DHCSR &

See KBA231071 for details.



Junk characters might be observed in a UART terminal during programming of the connected kit or after programming is completed.

Clear UART buffers after programming is completed.


On some occasions, the Eclipse IDE will fail to run launch configurations with various errors, such as:

"XXX has encountered a problem. Debug session already started. Terminate the first one before restarting"

Depending on the steps taken prior to launching a configuration, there are several reasons this may occur. The easiest way to resolve the issue is to restart Eclipse.


There is a programming error for our platforms that connect via FTDI on macOS Catalina. The boards include:

  • CYW920819EVB-02
  • CYW920820EVB-02
  • CYW920719B2Q40EVB-01
  • CYW920721B2EVK-01
  • CYW920721B2EVK-02
  • CYW920721B2EVK-03
  • CYW989820EVB-01
  • CYW920706WCDEVAL
  • CYW920735Q60EVB-01

This only happens in macOS Catalina 10.15.5 because of a serial port detection error. The macOS Catalina FTDI driver is missing the necessary device identification information.

To resolve this issue, update to macOS Catalina 10.15.6 or newer.



A "JTAG-DP STICKY ERROR" message may appear in the IDE when connected via the JTAG interface of a MiniProg4 probe in CMSIS-DAP HID mode.

You can safely ignore this error, or switch the MiniProg4 to CMSIS-DAP bulk mode.


JTAG performance on MiniProg4 may be significantly slower than SWD.

There is no workaround except using the SWD interface if JTAG performance is not acceptable.


You must manually reset after programming PSoC™ 6 kits when using GDB SEGGER + Jlink + JTAG interface.

Update each of the following Launch Configurations under the Debugger tab. In the Device Name field, delete the "_tm" suffix.

  • "<app-name> Erase (JLink)"
  • "<app-name> Program (JLink)"


Starting from KitProg3 v2.10, when KitProg3 is in CMSIS-DAP Bulk mode, it is not possible to debug and use USB-I2C/SPI bridging (for example, in the CAPSENSE™ Tuner, Bridge Control Panel) at the same time. This affects Windows OS only. It does not affect Linux or macOS users.

If you would like to use debug and USB-I2C/SPI bridging at the same time, there are two possible workarounds:

  • If performance for programming and debug is not critical, switch KitProg3 to CMSIS-DAP HID mode via the fw-loader utility. Firmware Loader is installed with ModusToolbox™ software, and is available separately on GitHub.
  • If you need faster performance for programming and debug, use the onboard KitProg3 for programming purposes and MiniProg4 for bridging purposes or vice versa. Both devices can be in CMSIS-DAP bulk mode.

Details are in KBA231025.



Starting from KitProg3 v2.10, in some cases Windows 7 does not recognize the KitProg3 bridge. So, the USB-I2C/SPI bridge devices are not available in either CMSIS-DAP HID or CMSIS-DAP bulk mode.

Install a digitally signed driver manually from the Windows Update Catalog. Follow steps from KBA231026.



In Linux OS, with KitProg3 in CMSIS-DAP HID mode, a debug session in ModusToolbox™ software can be destroyed if you use the Firmware Loader --device-list command while debugging. This is limitation of hidapi library used on Linux.

MacOS and Windows OSs are not impacted.

If you have a debug session running, don't use the firmware loader tool.



KitProg3 v2.10 or later is installed as part of the ModusToolbox™ 2.2 or later tools package. This version of KitProg3 will not work with PSoC™ Creator 4.3 or PSoC™ Programmer 3.28.7.

If you updated your kit to KitProg3 v2.10 and wish to use the kit with PSoC™ Creator 4.3 and PSoC™ Programmer 3.28.7, get a previous version of fw-loader (with an earlier version of KitProg3) and update the kit. The fw-loader tool is available here:


If this is not urgent, you can wait for a newer PSoC™ Programmer version with support for KitProg3 v2.10, expected soon.


5   Eclipse IDE




When renaming a multi-core application in the Eclipse IDE, the core processor subprojects become regular folders instead of project folders.

Right-click on each of the core processor folders and select Import as Project. Each folder will become a project folder with the appropriate name.


For some applications, the Configurations window shows duplicate launch configurations.

Use the launches on the Quick Panel, which filters launch configurations and hides duplicates.

Note that the duplicate configurations in the Configurations window is native Eclipse behavior.


In the Eclipse IDE you can open multiple, separate Terminals (for example Terminal, Terminal 1, Terminal 2, etc.). However, if you close the original, primary Terminal, the tool does not allow you to open any new separate Terminals. Instead new Terminals open as sub-tabs within the selected Terminal.


To fix this issue, reset the Perspective using Window > Perspective > Reset Perspective.


Sometimes when importing an application using the Eclipse IDE, a message displays stating the following:

Unable to add the shared library project at "<workspace_location>/mtb_shared" to the workspace. That project is for reference only; functionality is not affected.

This message can be safely ignored.


For some macOS machines running on M1 processors, the Eclipse IDE may fail to start with a message such as:

"ModusToolbox™ quit unexpectedly."

The message details also state that the "attachment of code signature supplement failed."

This problem occurs any time that Eclipse was last opened in an empty workspace prior to a reboot. After the reboot, the application fails to start.

Run the following command in the /Applications/ModusToolbox/ide_x.y/ModusToolbox.app directory:

xattr -dr com.apple.quarantine *

Note:  You may have to adjust the path if you installed ModusToolbox™ in a non-default location.

When complete, launch the Eclipse IDE again. This workaround works for all cases so far discovered.


In the updated Eclipse IDE for this release, the News tab has been removed. However, it may appear if you open an older release application in the updated IDE. If so, it may contain an error message like:

"Unable to access the news site. Please check your internet connection then click on the button below to try again."

The web page that provided content to the News tab is no longer maintained. You can safely ignore the message about site access.

If you want to remove the News tab from this workspace, select Window > Perspective > Reset Perpective...


Some BTSDK projects imported in the Eclipse IDE on macOS and Linux fail to build.

If an existing project is exported from Eclipse using File > Export > General > Archive File, and then the resultant .zip file is imported into another workspace using File > Import > General > Existing Projects into Workspace, any files that had the executable permission bit set in the original project will have the executable bit stripped in the new imported project.

This can vary from project to project, but can include executables necessary to the build process, which can cause the imported project to fail to build, or other possible side effects depending on what executables may be in the archive.

Identify what files were executable in the original project (pre-export) and then manually fix them in the new imported project with the following terminal command:

chmod +x <filename>


For projects that use external resources located outside of the application directory root (such as mtb_shared, wiced_btsdk, or 3rd-party libraries), some IDE code browsing and analysis features (such as resolving includes or opening object declarations for objects and headers located in those external resources) may not be usable or show unresolved includes immediately after project creation.

These will be resolved after building the project, as the IDE parses the output messages from the build to find paths to those resources.


On macOS Catalina, some IDE GUI windows/elements do not display correctly in some cases.

Resize the window or scroll to fix the display problem. In some cases, use the Refresh option.

We are investigating these issues and will address them in a future release.


If you delete the shared library directory (named mtb_shared, by default) from disk and then regenerate it using make getlibs or the Library Manager, the directory will not be restored properly for use in the Eclipse IDE.

This is because several files required by the Eclipse IDE are not restored as they were when the application was created.

Note:             You can delete the mtb_shared directory at any time because it can be recreated. You might do this when sharing the application, for example. The shared library directory only contains files that are already controlled and versioned, so you should NOT check it into a revision control system.

After regenerating the mtb_shared directory and assorted libraries, open the Eclipse IDE and follow these steps:

  1. Delete the mtb_shared directory shown in the IDE Project Explorer. Do NOT select the check box "Delete project contents on disk" (if you do, you will have to regenerate it again).
  2. Select File > Import > C/C++ > Existing Code as Makefile Project and click Next >.
  3. Under Existing Code Location, click Browse…, navigate to the application's root directory, select the mtb_shared directory, and click Select Directory.
  4. Under Toolchain for Indexer Settings, select ARM Cross GCC.
  5. Click Finish.
  6. After the import completes, build the application.


On Windows, when building a project and/or programming the device, the IDE reports one or more errors similar to the following:

*** fatal error - cygheap base mismatch detected - 0x18032C408/0x18032D408

This occurs because you likely have multiple versions of Cygwin in your build environment path. The IDE uses a version of Cygwin in the ModusToolbox™ installation directory. Remove the instance of "C:\cygwin64\bin" from your path.


Markdown (*.md) files do not render correctly in the IDE. For example, tables do not show rows and columns. Also, the IDE may show an error for the file such as:

"Cannot resolve element with id 'figure-1'".

This is a known issue with viewing markdown files in Eclipse. Various rendering errors can be safely ignored. We recommend using an external editor, such as Visual Studio Code or Typora to view markdown files.


When creating a new application, the IDE attempts to open any found readme.md files. Occasionally (and randomly), some of these files are opened in an external text editor instead of in the IDE.

This appears to be an Eclipse bug with no workaround. However, since *.md files do not render well in Eclipse (as noted above), you should use an external editor, such as Visual Studio Code or Typora, and set that editor as the default.


Sometimes, the Eclipse "egit" plugin locks directories. This prevents the Library Manager from removing BSPs/libraries from these locked directories. When this happens, you will see an error message in the Library Manager console indicating that permission is denied for removing a particular directory.

Before running the Library Manager from the Eclipse IDE, right-click on the project and select Team > Disconnect. When you are done with the Library Manager, go to Team > Share Project and select the correct project to reconnect.

Note Various projects may be set up differently, and the process to use the Team options will vary as well.


The IDE Project >Build Configurations > Active menu item to set Debug or Release mode is non-functional. This is due to the project's Makefile.

To set Debug or Release mode, edit the project's Makefile, which contains the following:

# Default build configuration. Options include:
# Debug   -- build with minimal
optimizations, focus on debugging.
# Release -- build with full optimizations


If you include external directories/files in your application, the Eclipse IDE will occasionally unselect your application project in the Project Explorer. However, it will leave the Launch section populated with links in the Quick Panel. Using those Launch links may result in a reported error of "Could not resolve cy_prj_path."

To resolve this, click on the appropriate project for your application in the Project Explorer, and then click on the Launch link again.


6     Library Manager




Issue using a VPN.

See Project Creator.


After running the Library Manager, the files shown in the Eclipse IDE Project Explorer are not updated.

To see the updated files, click on the project in the IDE Project Explorer and press [F5] to refresh the Eclipse view.


Opening multiple instances of the Library Manager at the same time for the same application could cause confusion and indeterminate states in applications.

Do not open multiple instances of the Library Manager for the same application. This issue will be addressed in a later release.


Sometimes when you click Update in the Library Manager, the tool will begin to process your request and then appear to freeze.

Terminate the Library Manager and relaunch it. This issue will be addressed in a future release.


When you remove a library item, the Library Manager deletes the associated directory from the "libraries" directory (typically this is called "libs"). On Windows, if there are any processes that have a lock on that directory, or a file in that directory, the directory removal will not work completely. The Library Manager will remove most of the directory contents and will also mark the library item as removed.

To remove the library completely, you must release the lock on the directory or file, and then manually delete the directory. The steps to release the lock depend entirely on the process that is holding the lock. Common scenarios include:

A command-line prompt is in that directory. In this case, "cd" to a different directory.

A text editor has a file from that directory open. In this case, close the file in the text editor. Depending on the text editor, you may have to exit the entire text editor.

The Eclipse git "egit" plugin has a lock on the directory. In this case, exit and restart the ModusToolbox™ Eclipse IDE.

In all cases, once the lock is removed you must remove the associated directory from the libraries directory before the Library Manager will be able to work with that particular library again.


7    Device Configurator




On macOS machines, there is an issue with the the Device Configurator Create Design dialog where you cannot select the desired MCU device from the list with the mouse. When you type in a partial part number, a drop-down menu displays various part numbers that match the value you typed. However, you cannot select the one you want with the mouse.

To select the desired device, either type the complete part number in the field or use the arrow keys on the keyboard.

This is a known Qt bug (third-party company), which has been reported.


For ModusToolbox™ 2.x applications using PSoC™ 4 devices, if you open the application using ModusToolbox™ version 3.x, the Device Configurator (version 4.0) may show various errors with various types of connections, such as SAR ADC SOC Input, TCPWM Start/Stop/Capture/Count/Reload Signal, DMA Channel Trigger Input or connections between pins over Digital Input and Digital Output.

Select new signals for the invalid connections to resolve the issues.


For ModusToolbox™ 2.x applications using PSoC™ 4 or PSoC™ 6 devices, if you open the application using ModusToolbox™ version 3.x, the Device Configurator (version 4.0) may show "Resource overused" errors in some cases where the pin's Digital Input, Digital Output, and Analog parameters are set at the same time.

Select new signals for the invalid connections to resolve the issues.


8   CAPSENSE™ Tuner




If using the UART communication interface, a low packet-transferring rate may cause the CAPSENSE™ Tuner to disconnect due to a data-reading timeout error.

You can resolve this using either of these solutions:

Increase the UART communication baud rate.

Increase the value of the uartSingleReadTimeout parameter available in the tuner INI file.

You can find the tuner INI file as follows:



HOME/Library/Application Support/Infineon_Technologies_AG\ModusToolbox



First comment on KBA 10 questions asked First comment on blog

Please consider to use the latest version of ModusToolbox™  available at https://www.infineon.com/cms/en/design-support/tools/sdk/modustoolbox-software/

If 2.x version has to be used, and seeing some issue, please post the issue/question as a new thread in this community, or contact your local Infineon representatives.