PSoC™ 6 Forum Discussions

1. The board support package CY8CEVAL-062S2 PSoC™ 62S2 lacks the network stack LWIP which is main requirement.
2. It also has the MbedTLS Acceleration support but limited header files in it, but other similar BSP has the MbedTLS support which has more header file and how to be leveraged in our BSP(i.e CY8CEVAL-062S2 PSoC™ 62S2).
3. While porting the module application respective to WICED, we have ported all corresponding header files to MTB shared folder, but it does'nt works or compile. Similarly once we have paste all the soure files to the path (D:\MODUSTOOLBOX\ModusToolbox\tools_2.4\gcc\arm-none-eabi\include)
it compiles.
4. Once module configured from Library manager( eg. FreeRTOS) for selected BSP, how to incorporate those application in main file?
5. Does LWIP support IPV6 is available in selected BSP CY8CEVAL-062S2 PSoC™ 62S2. If so how to identify and implement.
6. There is an need of AUX flash for EEPROM emulation which is used for NVVAR Storage.
7. How to incorporate Bootloader in specific project? and How to verify it with the Target board?

Fig - 1 Selected BSP - CY8CEVAL-062S2 PSoC™ 62S2.

Fig - 2 Similar BSP which has MbedTLS and LWIP support - 
CY8CKIT-062-WIFI-BT

Hello!

While working on a project with PSOC 6 (CY8C-0620WIFI-BT Kit), the IC CY8C6274BZI-D54 got too hot and project stopped working when given power through the USB cable of PC. Also, the software PSoC creator could not further detect  this device CY8C6274BZI-D54 for uploading code again. Incase if the microcontroller CY8C6274BZI-D54 has got damaged, is it possible to replace the microcontroller CY8C6274BZI-D54 alone or will the board PSoC 6(CY8C-0620WIFI-BT Kit) will not work any further? Incase of replacement of CY8C6274BZI-D54 IC , how to contact Cypress?

Thanks in advance.

Dears

I would like to see complete build log of project in Modus Toolbox 2.4

During compilation process - in log window is updated text information. But after finished build / completion there is only a part of text in the window even if I scroll to up (or select all text in window). It looks like it was sometimes overwritten during the process .. It's available somewhere in the LOG file, I found some LOG in the TEMP folder, but the victim was only a few lines...

Is there saved complete build log ?

Regards

Radim

Hello,

I'm workin on a custom board that use implements a single USB CDC and noticed a problem. When PSOC6 boots with power up, or by hardware reset and the USB cable is connected to the PC windows immediately recognizes it and assigns a consistent serial port #. (USB Serial Device (COM#), COM13 in my case.  However, if I momentarily disconnect the cable from the PC and connect it again, windows doesn't recognize it anymore wht the message "Device failed to enumerate".

To avoid hanging the firmware I'm monitoring the 5V VBUS line from the external device with a resistor divider to ensure that the connection is present before initializing the USB device.  I want to do this before entering the endless loop.

Why is this happening if the CDC profile is already initialized and waiting for the USB mesasages?

Do I need do a reinitialization of the USB in the reconnection scenario?

Hi,

Is it possible to code daisy chain SPI in PSOC 6(CY8C6247BZI-D54)?

If possible, can anyone tell the settings for that or code example?

Thank You,

Anjali

I have implemented DFU for a PSOC6 (CY8C6247BZI-D54) with the update provided over UART by a Sitara running Debian. The update works just fine, but my PSOC design has a USB serial interface to the Sitara. The Sitara recognizes the USB device but immediately disconnects.

[66991.563301] usb 1-1: new full-speed USB device number 10 using musb-hdrc
[66991.712709] usb 1-1: New USB device found, idVendor=04b4, idProduct=f21d, bcdDevice= 0.00
[66991.712730] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[66991.712738] usb 1-1: Product: CDC Serial Port
[66991.712745] usb 1-1: Manufacturer: MSI
[66991.712753] usb 1-1: SerialNumber: 12101010
[66991.720231] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[66991.770830] usb 1-1: USB disconnect, device number 10

When running the application as a non-DFU application, the USB works just fine. I have tried numerous things to fix, like increasing the flash size of app1. I am stumped. Any suggestions are welcome and appreciated.

Thanks,

Todd

Dear Expert.

Hello. I have a question as below.

I'm trying to use the emwin Driver provided in PSOC6. (pre included Driver at MTB IDE)

1. Is there a extra cost to implement the graphic function using the driver? Or is it available for free?

Please help.

Hi,

We are trying to port the existing firmware in PSOC Creator to ModusToolbox to make it available for the new chips.

However, the biggest challenge we are facing right now is the Analog Multiplexer that's not available in ModusToolbox as it is in PSOC Creator.

I'm wondering if there is any example on how to use the AMUX in ModusToolbox?

Any help will be much appreciated.

Thanks in advance.

GP

I am using CY8CPROTO-063-BLE PSoC 6 BLE Prototyping Kit, and I want to send heart rate sensor data to the CySmart mobile app over BLE. I am new to CyPSoC devices and having some trouble making the connection.

Are there any code examples I can follow to do this with some explanation of the code?

I found several example codes on the internet on how to send data into the PSoC6 via BLE. But so far, no luck finding a good code to take data from PSoC6 via BLE.

Any help or advice is highly appreciated. 

1. Created new modus application as follows : BSP > PSoC™ 62S2 > CY8CEVAL-062S2 > [NEXT]
: Select Application > Peripherals > MCUboot - Based Basic Bootloader > [CREATE]

2. Two project folders are created namely : MCUboot-Based_Basic_Bootloader.blinky_cm4 and MCUboot-Based_Basic_Bootloader.bootloader_cm0p

3. While building MCUboot-Based_Basic_Bootloader.blinky_cm4 we face 2 errors as mentioned below.

make[1]: *** [../../mtb_shared/core-make/release-v1.9.1/make/core/build.mk:557: CY_BUILD_app_postbuild] Error 126
make: *** [../../mtb_shared/core-make/release-v1.9.1/make/core/main.mk:434: secondstage_build] Error 2
"C:/Infineon/Tools/ModusToolbox/tools_2.4/modus-shell/bin/make CY_MAKE_IDE=eclipse CY_MAKE_IDE_VERSION=2.4 CY_IDE_TOOLS_DIR=C:/Infineon/Tools/ModusToolbox/tools_2.4 -j4 all" terminated with exit code 2. Build might be incomplete.

11:46:12 Build Failed. 2 errors, 11 warnings. (took 7m:493ms)

providing the way to resolve this error and compile without these errors would be helpful.