PSoC™ 6 Forum Discussions

Hi!

I found the Snippet code of async recording from the microphone CY8CKIT-062-WiFi-BT with CY8CKIT-028-TFT display here:
https://infineon.github.io/mtb-hal-cat1/html/group__group__hal__pdmpcm.html (Snippet 2: PDM/PCM Asynchronous Receive). My application record a 1-second audio frame and processes it by NN in parallel. I measured the power consumption of PSoC6 and aligned the measured results with the time, required for the calculation in my application (screenshot below) and found, that for almost 0.8 seconds wait for end of the new recording. 

 
The microphone is configurated to record data and write it by using DMA only. So, if I do not use the CM4 while async recordings, is it possible to set the CM4 in sleep mode and wake up it by the event of the ending of the recording (CYHAL_PDM_PCM_ASYNC_COMPLETE)?

I attached the main.c file and remove some processing parts. The idea is to set CM4 to sleep after processing at line 186 and wake it up by end of the recording event (CYHAL_PDM_PCM_ASYNC_COMPLETE).

If CM4 cannot be awakened by the CYHAL_PDM_PCM_ASYNC_COMPLETE event, maybe somebody can recommend other techniques for reducing power consumption while recording data?

Thanks,
Andrii

Hi Team,

We are using  CYB0644ABZI-S2D44 MCU in our project.

We have following questions related to certificate storage

1. can we store our root certificate in place of the keys which are currently generating through cysecuretools application?

2. can you share the mechanism to authenticate these certificate

3. Do you have any support documents for the authentication process?

Thanks,

Sameem

I am editing this post to provide a quick answer for the next person:

In PSoC Creator, the process for instantiating and using a USBFS block is not the same for PSoC 5 and PSoC 6, which leads to some confusion.

Problem:

Placing a USBFS block and generating the design without running the USB configurator results in USBUART_cfg.c and USBUART_cfg.h each containing the following:

#error File ..\cycfg_usbdev\cycfg_usbdev.c does not exist! Launch USB Configurator

Solution:

• For a PSoC 5 design, the block in the palette is "USBFS V3.2".  Double-clicking on a V3.2 instance opens the USB Configurator.
• For a PSoC 6 design, the block in the palette is "USBFS V1.0".  Unlike the USBFS V3.2 block, double-clicking on a V1.0 instance opens a simple configuration dialog. Instead, right-click on the USBFS instance and from the context menu click "Launch USB Configurator". 

My design is for a PSoC 6. What threw me off was the term "Launch USB Configurator", which lead me to the stand-alone USB Configurator application found in the Windows start-menu Cypress folder. This is not what you want. 

The good news is that while the USB Configurator looks daunting, the default values are sufficient to make a working design. 

Best,
Peter 

Hi,

I am trying to create a project based on the https://github.com/Infineon/mtb-example-psoc6-security/tree/release-v1.0.0  project. So far I used the CY8CPROTO-062-4343W evalboard and everything was fine. I was able to build a bootloader and application, upload it to the hardware, etc.

The problem arose when I wanted to do the same on a custom BSP. As per  https://www.infineon.com/dgdl/Infineon-ModusToolbox_2.4_User_Guide-UserManual-v01_00-EN.pdf?fileId=8ac78c8c7e7124d1017ed97e72563632 section 4.3 Creating your own BSP, I created a target using 'make bsp TARGET_GEN = myBSP DEVICE_GEN = CY8C6247FDI-D32' and went through all the steps.

In bootloader  https://github.com/Infineon/mtb-example-psoc6-security/blob/release-v1.0.0/bootloader_cm0p/source/main.c#L45 I changed references to "cybsp.h" and changed init_cycfg_all () to cybsp_init (), no problem with that.

There is a problem with the MCUBoot library. The build logs (at the bottom of the post) show that for some reason the file mtb_shared\mcuboot\v1.7.2-cypress\boot\cypress\libs\cy-mbedtls-acceleration\mbedtls_MXCRYPTO\crypto_common.h with the declaration of the type cy_en_crypto_ecc_curve_id_t is not included. The same is true for a few other files.

If I only change TARGET=CY8CPROTO-062-4343W then everything compiles and the bootloader works on the board.

Additional information is the fact that all files related to the bootloader folder itself along with main.c have been compiled, and the problem appears later while MCUBoot is compiling.

What might be missing from my setup?

Best regards,
PZbb

Compiling ext file swap_move.c
In file included from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/ecp.h:267,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/pk.h:41,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/oid.h:34,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/src/image_ec256.c:40:
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/ecp_alt.h:175:1: error: unknown type name 'cy_en_crypto_ecc_curve_id_t'
175 | cy_en_crypto_ecc_curve_id_t cy_get_dp_idx(mbedtls_ecp_group_id gid);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
make[1]: *** [libs/core-make/make/core/build.mk:387: /user/project/bootloader_cm0p/build/myBSP/Custom/ext/mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/src/image_ec256.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/ecp.h:267,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:36,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/sha256_alt.h:38,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/sha256.h:69,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/include/bootutil/crypto/sha256.h:29,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/src/image_validate.c:36:
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/ecp_alt.h:175:1: error: unknown type name 'cy_en_crypto_ecc_curve_id_t'
175 | cy_en_crypto_ecc_curve_id_t cy_get_dp_idx(mbedtls_ecp_group_id gid);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/sha256_alt.h:38,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/sha256.h:69,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/include/bootutil/crypto/sha256.h:29,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/src/image_validate.c:36:
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:112:43: error: unknown type name 'cy_stc_crypto_sha_state_t'
112 | int cy_hw_sha_start (cy_hw_crypto_t *obj, cy_stc_crypto_sha_state_t *hashState,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:113:22: error: unknown type name 'cy_en_crypto_sha_mode_t'
113 | cy_en_crypto_sha_mode_t shaMode, void *shaBuffers);
| ^~~~~~~~~~~~~~~~~~~~~~~
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:115:43: error: unknown type name 'cy_stc_crypto_sha_state_t'
115 | int cy_hw_sha_update(cy_hw_crypto_t *obj, cy_stc_crypto_sha_state_t *hashState,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:118:43: error: unknown type name 'cy_stc_crypto_sha_state_t'
118 | int cy_hw_sha_finish(cy_hw_crypto_t *obj, cy_stc_crypto_sha_state_t *hashState,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:122:22: error: unknown type name 'cy_stc_crypto_sha_state_t'
122 | cy_stc_crypto_sha_state_t *hashStateDst, void *shaBuffersDst);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/crypto_common.h:124:44: error: unknown type name 'cy_stc_crypto_sha_state_t'
124 | int cy_hw_sha_process(cy_hw_crypto_t *obj, cy_stc_crypto_sha_state_t *hashState,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../../mtb_shared/mcuboot/v1.7.2-cypress/ext/mbedtls/crypto/include/mbedtls/sha256.h:69,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/include/bootutil/crypto/sha256.h:29,
from ../../mtb_shared/mcuboot/v1.7.2-cypress/boot/bootutil/src/image_validate.c:36:
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/sha256_alt.h:44:5: error: unknown type name 'cy_stc_crypto_sha_state_t'
44 | cy_stc_crypto_sha_state_t hashState; /* Structure used by CY Crypto Driver */
| ^~~~~~~~~~~~~~~~~~~~~~~~~
../../mtb_shared/mcuboot/v1.7.2-cypress/boot/cypress/libs/cy-mbedtls-acceleration/mbedtls_MXCRYPTO/sha256_alt.h:48:5: error: unknown type name 'cy_stc_crypto_v2_sha256_buffers_t'
48 | cy_stc_crypto_v2_sha256_buffers_t shaBuffers; /* Structure used by CY Crypto Driver */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi,

I have a tight time requirement from POR to CM4 image in CY8CPROTO-064B0S.

Then, I want to know if I can disable secure boot in CY8CPROTO-064B0S such like by adjusting policy files.

Is it possible?

Thanks,

Hello, World!

I have a PSoC 6 project with one working SPI block and need to create a second. At least I think I do (one chip uses CPHA=1, CPOL=0 and the other uses CPHA=0, CPOL=0). When I add the second SPI block, I get the following:

Elaborating Design...
HDL Generation...
Synthesis...
Tech Mapping...
Info: plm.M0038: The pin named CY_CPUSS_SWJ_SWCLK_TCLK(0) at location P6[7] prevents usage of special purposes: SCB[6].uart_cts. (App=cydsfit)
Info: plm.M0038: The pin named CY_CPUSS_SWJ_SWCLK_TCLK(0) at location P6[7] prevents usage of special purposes: SCB[6].spi_select[0]. (App=cydsfit)
Info: plm.M0038: The pin named CY_CPUSS_SWJ_SWCLK_TCLK(0) at location P6[7] prevents usage of special purposes: SCB[8].spi_select[0]. (App=cydsfit)
Info: plm.M0038: The pin named CY_CPUSS_SWJ_SWDIO_TMS(0) at location P6[6] prevents usage of special purposes: SCB[6].uart_rts. (App=cydsfit)
Info: plm.M0038: The pin named CY_CPUSS_SWJ_SWDIO_TMS(0) at location P6[6] prevents usage of special purposes: SCB[6].spi_clk. (App=cydsfit)
Info: plm.M0038: The pin named CY_CPUSS_SWJ_SWDIO_TMS(0) at location P6[6] prevents usage of special purposes: SCB[8].spi_clk. (App=cydsfit)
Analog Placement...
Error: fit.M0059: FFB and IO placement failed: Failed to find a valid placement for \SPI_2:SCB\. (App=cydsfit)
Dependency Generation...
Cleanup...
Error: fit.M0050: The fitter aborted due to errors, please address all errors and rebuild. (App=cydsfit)
--------------- Rebuild Failed: 11/30/2022 00:22:46 ---------------

I think the problem is rooted in the info messages, but I am still a noob and don't really understand what's going on. 

I am using a Pioneer board and have 1 x I2C, 2 x SPI, and some analogs. I tried to choose pins that I can get at from the Pioneer's headers.

I2C_1:scl     P6[0] pin K8
I2C_1:sda     P6[1] pin J8
SPI_1:miso_m  P12[1] pin B4
SPI_1:sclk_m  P12[2] pin C4
SPI_1:s0_m    P12[3] pin A3
SPI_2:miso_m  P5[1] pin K6
SPI_2:mosi_m  P5[0] pin L6
SPI_2:sclk_m  P5[2] pin J6
SPI_2:s0_m    P5[3] pin K7
UART:rx       P11[0] F5
UART:tx       P11[1] E5
AIN0          P10[0]  B8
...
AIN5          P10[5] B7

I am using P6[0] and P6[1] but not P6[7] or P6[6].   Can I not use anything on P6?

In a nutshell, I'm trying to use as many of the Arduino header pins as I can but am willing to connect to any pin that makes the project work. 

Any thoughts?

Thanks in advance!

Peter

Hi there!

I'm using the CYBLE-416045 module  & PSoC Creator to implement the "CE218553 - PSoC 6 MCU: PWM
Triggering a DMA Channel" project example. Specifically I'm trying to use the CM0 processor instead of the default CM4.

On the CM4, which the example project defaults to, everything works fine. (see attached screenshot)

But once I move the code from the CM4 to the CM0, then the Timer output stays Low and the Compare never triggers. However Overflow does trigger, indicating that the Timer is still running. Presumably the Compare value is not being changed by DMA for some reason, which is why the timer compare isn't happening. (see attached screenshot)

Is the CM0 processor capable of handling DMA?

Is there something special that needs to happen for DMA to run on the CM0 processor?

Let me know if there's any additional information that I can provide to help troubleshoot this problem.

#include "project.h"

#define ARRAY_SIZE               (256u)
#define BREATHING_CHANGE         (512u)

uint32 compareVal[ARRAY_SIZE];

void arrayInit(void);

int main(void)
{
    cy_stc_dma_channel_config_t channelConfig;
    __enable_irq(); /* Enable global interrupts. */
    Cy_SysEnableCM4(CY_CORTEX_M4_APPL_ADDR); 

    arrayInit();  /*initialize the compareVal array */
    
    /* Initialize, enable and trigger the  PWM */
    Cy_TCPWM_PWM_Init(       PWM_HW, PWM_TCPWM__CNT_IDX, &PWM_config);
    Cy_TCPWM_Enable_Multiple(PWM_HW, PWM_CNT_MASK);
    Cy_TCPWM_TriggerStart(   PWM_HW, PWM_CNT_MASK);
    
    /* Configure DMA Descriptor to change the PWM compare value per breathingLed array */
    DMA_Descriptor_1_config.srcAddress = &compareVal;
    DMA_Descriptor_1_config.dstAddress = (void *) &(PWM_HW->CNT[PWM_TCPWM__CNT_IDX].CC);
    Cy_DMA_Descriptor_Init(&DMA_Descriptor_1, &DMA_Descriptor_1_config);
    
    /* Configure DMA Channel with the descriptor configured above */
    channelConfig.descriptor        = &DMA_Descriptor_1;
    channelConfig.preemptable       = DMA_PREEMPTABLE;
    channelConfig.priority          = DMA_PRIORITY;
    channelConfig.enable            = 0u;

    Cy_DMA_Channel_Init(  DMA_DW__BLOCK_HW, DMA_DW_CHANNEL, &channelConfig);
    Cy_DMA_Channel_Enable(DMA_DW__BLOCK_HW, DMA_DW__CHANNEL_NUMBER);
   
    /* Enable DMA hardware block */
    Cy_DMA_Enable(DMA_DW__BLOCK_HW);

    Cy_SysEnableCM4(CY_CORTEX_M4_APPL_ADDR); 

    for(;;)
    {
    }
}


void arrayInit(void)
{
    uint32_t i=0u;
    /* Creating the array with increasing and decreasing compare value to generate the breathing */
    compareVal[i] = 0;
    
    for(i=0u; i < ARRAY_SIZE>>1; i++)
    {
        /* Increase compare values */
        compareVal[i] = compareVal[i-1u] + BREATHING_CHANGE;
    }
    for(i=(ARRAY_SIZE>>1); i < ARRAY_SIZE; i++)
    {
        /* Decrease compare value */
        compareVal[i] = compareVal[i-1] - BREATHING_CHANGE;
    }
}