Browse the Community
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.
Discussion forum regarding WICED™ Studio related topics.
Discussion forum regarding PSoC Creator & Designer Software topics.
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).
I'm using ModusToolbox with PSoC6.
I know it is possible to launch the debugger from ModusToolbox IDE, but I need to use it from command line.
Any one know which settings should I use?
What I did so far:
I have 3 terminals:
The only thing that I did was: `make debug`
I connect with OpenOCD using:
```telnet 127.1 4444
init; reset init
I connect using gdb by doing:
(gdb) break main
(gdb) target extended-remote :3333
Remote debugging using :3333
0x0000012a in ?? ()
And it gets stuck in 0x0000012a
I never reaches `main`
Any idea? Thanks!
I am not sure if I locate this question correctly in this forum, but it is as follows:
- for unit testing of our application SW we need to be able to easily compile (and link) the ANSI C code of one particular "SW-component under test" into an elf file, which would run certain SWC_main() function in an endless while loop on our TC387:
- without configuring any (or as less as possible) peripherals of the TC387 uC
- Our project-specific compiler shall be used for compiling
Maybe there exists such a tool, maybe provided by Infineon, which could make it possible to do it?
So at the end we would need an elf file with some very basic (but better Infineon approved) start-up code for TC387 which would after start-up proceede to an endless while loop, which would run our SWC_main function.
I would be grateful for all suggestions.
P.S. writing our own makefile and linker we would also like to avoid, but use some proven sollution, which shall for sure exist.Show Less
When trying to create a new project I get this error. I think there is something wrong because shouldn't connect this to github.com/infineon... ?
Thanks in advance.
I'm using Cypress Wiced studio IDE (V 220.127.116.11) for CYBT 343026-01 Bluetooth module. For my requirement, In the Wicked studio IDE, I'm using only spp.c file under 20706-A2_Bluetooth project. In this spp.c file, I'm using 'wiced_hal_puart_set_baudrate()' function for changing the Baudrate. By using this function, I'm able to change my Baudrate to 115200 and 57600 only. But if I change to 38400 or 19200 or 9600 values then the CYBT 343026-01 Bluetooth is not communicating through Uart. Please tell me the reason why it is communicating only for 115200 or 57600. I want it to work for lower Baud rate values also. so please tell me the solution for my problemShow Less
We are working on a bluetooth project using a LAIRD EWB. The STM32F412v mcu does not contain a LPTIMER. In working with the CYHAL interface, it appears that a LPTIMER is mandatory. What is the alternative to LPTIMER when using CYHAL?
Cypress Android release for the broad market.
This release has been qualified on Hikey 960 and NXP i.MX8MQuad Evaluation Kit (EVK) platform.
Customers wishing to leverage the Android Open Source Platform now have an out of the box Android solution for Cypress's connectivity parts.
The release package includes:
* Hikey 960
* NXP i.MX8MQuad Evaluation Kit
* 55572 Sanity and VTS
* Initial postShow Less
I would like to port application which was developed on CY8CKIT-062-WIFI-BT using CY8C6247BZI-D54 to CY8C6137BZI-F34.
I tried to create custom BSP, follow all available documentation for Modus Toolbox.
But still in device configuration is previous part number.
Can anybody help how to easy swap devices in Modus Toolb?
I'm trying to make a very low power firmware for a cyw43907 board based on the dev kit design. I have some issues finding example and implementing the low power techniques.
The few example I found were only for wiced. And the templates in modustoolbox unfortunately do no use powersave.
Are there examples or doc somewhere for cyw43907 and powersave?
I tried to replace all the UAC1 descriptors with UAC2 descriptors, but Windows says "This device cannot start. (Code 10)" and tdd.exe says *** ERROR: Descriptor has errors! ***
Endpoint Descriptor: ------------------------------ 0x09 bLength 0x05 bDescriptorType *** ERROR: Invalid descriptor length 0x09 Hex dump: 0x09 0x05 0x86 0x03 0x02 0x00 0x1E 0x00 0x00
It looks like this was length 9 in UAC1 (Table 4-17: Standard AC Interrupt Endpoint Descriptor) but is now supposed to be length 7 (Table 4-25: Standard AC Interrupt Endpoint Descriptor). The bRefresh and bSynchAddress fields have been removed. But USBFS component does not have "Endpoint Descriptor 2.0", it just has "Endpoint Descriptor" with bRefresh and bSynchAddress fields that cannot be turned off?
It has similar errors for other interfaces and endpoints:
AS Interface Descriptor: ------------------------------ 0x07 bLength 0x24 bDescriptorType 0x01 bDescriptorSubtype *** ERROR: Invalid descriptor size 0x07 Hex dump: 0x07 0x24 0x01 0x01 0x01 0x01 0x00 Endpoint Descriptor: ------------------------------ 0x09 bLength 0x05 bDescriptorType *** ERROR: Invalid descriptor length 0x09 Hex dump: 0x09 0x05 0x01 0x05 0x86 0x01 0x01 0x00 0x88 AS Isochronous Data Endpoint Descriptor: ------------------------------ 0x07 bLength 0x25 bDescriptorType 0x01 bDescriptorSubtype *** ERROR: Invalid descriptor size 0x07 Hex dump: 0x07 0x25 0x01 0x01 0x00 0x00 0x00 Endpoint Descriptor: ------------------------------ 0x09 bLength 0x05 bDescriptorType *** ERROR: Invalid descriptor length 0x09 Hex dump: 0x09 0x05 0x88 0x11 0x03 0x00 0x04 0x03 0x00