Hi Infineon community,

I'm currently developing a project in ModusToolbox using the CY8CPROTO-063-BLE, along with the Bluetooth_LE_Hello_Sensor. My aim is to create five distinct characteristics, but I've encountered an issue where only a maximum of four characteristics are visible in the AIROC Bluetooth Connect App. The same limitation occurs with other Bluetooth applications as well. Could there be a specific reason why the fifth characteristic is not being displayed?

Regards,

Luis Flores

Hi Infineon Community, 

I'm experiencing a connection issue with the CY8PROTO-063-BLE when using the AIROC Bluetooth Connect App. On one smartphone, I can successfully connect, view services and characteristics, and use them without any problems. However, with another, newer phone, despite the device being visible, I'm unable to establish a connection. It attempts to connect but fails to do so. The same issue occurs when trying to connect with an iPad. What could be causing this problem that prevents the connection from being established? Both iPhones are running the latest iOS version.

Regards,

Luis Flores

Hello,

I work with ModusToolbox via VSCode. I have successfully tested my programme on the CYPROTO-063-BLE kit. To do this, I had to adapt the flash memory there. Now I would like to run the same programme code on the CY8C6245, but I have the problem that the linker files are structured a little differently. For example, the following programme section is missing in the linker file of CM4:

/* Size and start address of the Cortex-M0+ application image */
FLASH_CM0P_SIZE = 0x20000;
FLASH_CM0P_START = ORIGIN(flash);
/* Size and start address of the Cortex-M4 application image */
FLASH_CM4_SIZE = LENGTH(flash) - FLASH_CM0P_SIZE;
FLASH_CM4_START = FLASH_CM0P_START + FLASH_CM0P_SIZE;

Furthermore, I have already tried to change the origin of the flash memory, but then the multicore debugging no longer works.
In the appendix you can find some pictures of the working programme code for the CYBLE.
My question would be what exactly I have to change for the CY8C6245.

Hi all,

I had a question while studying the UART function of MTB.

I understand that the UART API is divided into two categories: High-level and Low-level.

In MTB, I could choose which API to use.

However, even if I chose the High-level API mode and only use the Low-level API to write firmware, UART works normally.

Similarly, although I chose Low-level API mode and only use the High-level API to write firmware, it still works.

So, what is the meaning of choosing the MTB API mode as High-level or Low-level?

Thank you for your support,

Regards,

I see the latest version of PDL (3.17) for PSOC creator has USB driver and Middleware are from version 1.0. But from PDL API reference I see the current version  for USB Driver and Middle ware is version 2.20

Where do I get the latest version (2.20)of  PSOC Creator compliant  USB Driver and middle ware?

I use CY8C6347BZI_BLD53. I use SPI_DMA to transfer data. When I set the SPI speed to less than 15MHz, the transmission is normal. When the SPI speed is greater than 15MHZ, the DMA is transmitted to the middle, and suddenly every 16 clock cycles will stop. The signal chart is as attached. What is the reason for this, and how can I solve it.

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-6/PSOC6-spi-dma%E9%AB%98%E9%80%9F%E4%BC%A0%E8%BE%93%E6%97%B6-%E4%B8%AD%E9%97%B4%E6%9C%89%E5%A4%A7%E6%A6%824%E4%B8%AA%E6%97%B6%E9%92%9F%E5%91%A8%E6%9C%9F%E7%9A%84%E5%81%9C%E9%A1%BF-%E8%BF%99%E6%98%AF%E4%BB%80%E4%B9%88%E5%8E%9F%E5%9B%A0/td-p/648841

Hi,

We are using a CYB06445LQI-S3D42 device.

Starting with a default clock configuration worked well.

When we have tried to configure the system clocks according to our board design (we have an ECO), the BSP fails to initialize the clocks.

These are the parameters of the configurations. To note that exactly the same parameters work well on another project with exactly the same ECO but on PSOC63 (CY8C6347BZI).

The BSP fails in the clock initialization 

Could you help me understand why and what to do?

Thanks

Hi all, good day. I want to know how to use SEGGER AppWizard GUI Builder Software with CY8CKIT-062-WIFI-BT  in ModusToolbox? I built the GUI and Exported but I don't know how to implement it in the Modus Toolbox IDE I know there is an example for it but I don't know how they actually made it. They didn't explain how to add the exported files and implement in modustoolbox properly. please provide us with kind support. Also If there are any tutorials that any of you can recommend please do as there aren't that many PSoC modusToolbox tutorials on youtube that I know of. thank you best regards.

I have a custom board that has the CY8C6136BZI-F14 and a TI CC3135 WiFi chip. I have created a custom BSP for the board. Per the information in the BSP assistant documentation I based this custom BSP on the CY8CPROTO-062-4343W.

I am new to using these MCUs so I also purchased a CY8CPROTO-062-4343W so that I could use the examples to learn how to use the ModusToolbox, build applications, program the MCU and debug. To get an understanding of how the WiFi works I used the WiFi TCP Client example and was able to program the eval board and run this application. I then examined the library configuration to determine which libraries were included for this application.

I took that information back to my application for the custom board with the intent of configuring WiFi for the board. The TI part on the custom board is connected via the SPI bus and so I had selected that option when setting up the custom BSP. However, when I pulled up the library manager for the custom board application I found that the options for the WiFi-related libraries do not exist under Core, Middleware and Utilities and the WiFi menu is not present. I have searched through the documentation and the community to try to find information on enabling WiFi support in a custom BSP but have come up empty.

I have tried working this through starting with copying the wifi-core-freertos-lwip-mbedtls.mtb file into the deps directory for the custom board application and, while I can see WiFi-related components being built, that did not change the library manager menu configuration. It's clear that there are a lot of details around this including dependencies in the existing code (such as the wifi_nvram_image.h file) that make it seem like modifications are necessary, not just for the custom BSP, but also for the mtb_shared area.

Can anyone provide either a path to a step-by-step document for enabling WiFi in a custom BSP or provide some insight into how this is supposed to be done? Also, why would the library manager menu content not be consistent from one application to another?

Thanks for your help.