Software Forum Discussions
Browse the Community
ModusToolbox™
The ModusToolbox™ forum includes discussions regarding multi-platform development tools and a comprehensive suite of GitHub-hosted firmware libraries accompanied by thoroughly tested code example applications.
DAVE™
PSoC™ Creator & Designer
Discussion forum regarding PSoC Creator & Designer Software topics.
Wi-Fi Bluetooth for Linux
AURIX™ Development Studio
The AURIX™ Development Studio is a free of charge Integrated Development Environment (IDE) for the TriCore™-based AURIX™ microcontroller family. It is a comprehensive development environment, including Eclipse IDE, C-Compiler, Multi-core Debugger, Infineon low-level driver (iLLD), with no time and code-size limitations that enables editing, compiling, and debugging of application code. Combined with numerous code example projects, the IDE can be used to evaluate the powerful architecture of the AURIX™ microcontroller family. It supports Microsoft Windows 10 as a host operating system (OS).
Featured Discussions
Hi infineon Team,
A few days ago, ModusToolbox can still open normally, but today the following problems occur, how to solve.
ERROR:there was an error retreiving the asset 'https://github.com/Infineon/device-db' commit 'release-v4.9.0' - fatal: unable to access 'https://mirror.ghproxy.com/https://github.com/Infineon/device-db/': Failed to connect to mirror.ghproxy.com port 443 after 2237 ms: Connection refused
ERROR:Global asset download of device-db loading completed with error.
ERROR:The asyncStepComplete failed for LoadFlag DEVICE_DB.
Show Less
When I try to create a new project with Project Creator I get an error getting device_db:
I have all the environment variable set up as suggested by the installation guide :
unfortunately not found any solution
Show LessHello,
The following error occurred when HelloWorld was created with NewApplication in ModusToolbox.
No space is used.
Could you identify the cause of the problem?
ModusToolbox Version: 3.1.0
Install Directory : C:/Users/170251/ModusToolbox
Project Location : C:/Users/170251/mtw/Hello_World_1
Best Regards,
Show LessI have a need to generate 3 or more target programs from almost the same code base. However:
- design.modus must be different
- some preprocessor DEFINES need to be different.
I'm still using MTB 2.4, but will migrate to 3.0 soon. Usually I would just create many targets in the makefile. But I read that MTB2.4 makefiles cannot support multiple targets.
What is the best practice for this? It seems like I need separate projects which is suboptimal, but OK. But is there an easy way to include adjacent directores of source files above the project directory without creating libraries?
Show Less
We would like to support WPA3 Enterprise and AES-192 modes by CYW4373 using murata Type 2BC.
Using bindings for Linux driver is as below for Infenion CYW4373.
https://github.com/STMicroelectronics/linux/blob/v6.1-stm32mp/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
Are all Enterprise security modes supported that are listed by wpa_supplicant here?
https://w1.fi/wpa_supplicant/
The templates that can be selected for Modus's new PSoC6 project are all PSoC62/63/64 series. How can I build a new PSOC61 project
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/ModusToolbox/modus-toolbox-PSOC61%E5%B7%A5%E7%A8%8B/td-p/653041
Show LessAre there any example projects implementing the CYBT-353027-02 for audio?
What stereo codec would be recommended?
Can the CYBT-353027-02 be used as a source to connect to generic headsets?
Thanks
Show Less
Hello,
I opened an old program to update my electronic card by reinstalling WICED Studio 6.6.1.
When attempting to program my card with JTAG , I received the following error message:
"Making snip.scan-BCM943362WCD4.bin
Downloading Bootloader ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading DCT ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading Application ...
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Resetting target"
Could someone please explain the steps to install or test the setup correctly?
Show Lessin wiced_hal_pspi.h
in spiffydriver.h
spiPinPullConfig is UINT8, it's always 0 whenever use which enum ?
Show LessI had a project using 2 SAR ADC's on the marvelous PSOC 5.
The PSOC Creator is a great platform for getting complex projects done very quickly. I usually have a project up and running before any other IDE out there has finished pointing me to the Google search areas where the IDE has made your life difficult. But I digress.
I was running the SARS in Differential Input Mode sharing a common reference, all on port 3.
The router routed SAR1 input to SAR2 and vice versa, even though the pin numbers were correct.
I put in an analog pin on port 3 to monitor the SAR Input, and suddenly it routed correctly. Took it away and got a bad route.
I was able to permanently cause a proper route by using a monitoring pin for the opAmp driven reference on an unused Port 3 pin. (I noticed it took more analog iterations to do the route, so I think the iterator said it was done too soon otherwise.
So, next time some thing like that happens, place an additional monitor on an unused pin on that port to see what happens!
Show Less