PSoC™ 6 Forum Discussions
Hi,
i'm trying to build a psoc6 based project on psoc creator and i'm in trouble. the error is :
Build error: L6050U The code size of this image (134708 bytes) exceeds the maximum allowed for this version of the linker.
Could you help please?
thanks
Show LessHello,
I'm relatively new to PSoC and PSoC creator.
I'm trying to access the Cryptography hardware acceleration. I've done so successfully using the Client-Server PDL provided. However, when trying to use "Direct Crypto Core Access" (e.g. Cy_Crypto_CoreTrng()), I can't seem to find the requisite .h or .c or .a files. When I try to include cy_crypto_core.h as the documentation indicates, it's not found. My build fails with "undefined reference to Cy_Crypto_CoreTrng().
I tried unsuccessfully to find the straight-forward answer to the simple question: are the Cy_Crypto_Core_xx() functions supported in PSoC Creator ? Below is my environment.
Any help would be greatly appreciated.
Environment:
PSoC Creator 4.4 (4.4.0.80)
Culture: English (United States)
OS Version: Microsoft Windows NT 10.0.19044.0
CLR Version: 4.0.30319.42000
Installed CyInstaller Products:
Peripheral Driver Library 3.1.3
Peripheral Driver Library 3.1.5
PSoC Programmer 3.29.1
PSoC Creator 4.4
Hi. I am trying to create a project using CY8CKIT-062-BLE PSoC 6 BLE Pioneer Board and connect FreeRTOS to it as described in the manual. But I am facing the problem of not understanding what kernel is selected in this project. I see in the bsp makefile that kernel BSP_COMPONENTS:=CM0P_BLESS is selected but when I add configuration file to my project with the right kernel, the project gives errors in another file from mtb_shared folder. Can you explain the logic of working with this kind of error?
And I keep getting this error Unresolved inclusion: "cy_utils.h". How can this be fixed?
Show LessHi All
I have designed a circuit using a CYBLE 416045-02 module but when I tested my fabricated board, it did not respond to Bluetooth, I tried to test it with the "find me" example, and no response
My board can communicate through a USB-SERIAL chip to Tera term and also I can program using miniprog programmer (SWD) pins.
I have attached part of the circuit if anyone can help on this issue thank you in advance
power is provided by 3.3 V, The power to the chip goes through a jumper hence different naming
@dourc_264766 @horiamodran @modranhoria @doruc_1309621
Show LessHi!
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 all,
My English is a little poor. I'm sorry if there is a spelling mistake. Please forgive me.
I have a question:
I am using CY8CK-062S4 from PSoC™ 62 MCU. I tried using DMA to transfer two simultaneous ADCs for a total of 512 pieces of data. Normally, these 512 pieces of data should be one continuous signal, but I actually found that it was two signals. The first 256 pieces of data represent one segment of the signal, and the last 256 pieces of data represent another segment of the signal. It looks like this picture.
The manual indicates that 1D transmits a maximum of 256 data. Whether there is a delay at the 256th data position?
This is part of the code,
I felt very confused and desperately wanted someone to help me.
Show LessHi 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
Show LessI 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
Show Less
Hi all,
I'm sorry if this is covered in another post; please point me there if so. I'm relatively new to PSoC and PSoC Creator (my employer requires that I use PSoC Creator versus MTK or other)
I have, what I think, is a simple question:
I'm adding a couple of features to an existing application. I've been getting warnings/errors from PSoC Creator during build that I'm exceeding the flash memory available. I can find a lot of posts and have found the file where I can change the allocation; that is not my question. Two questions:
1) I can see during download how many "blocks" are being sent. Am I correct that a "block" is 1K ? I have seen __cy_memory_0_row_size = 0x200; with makes me doubt my assumption. Can someone confirm conclusively that the little ticker in the lower left is indicating 1K blocks during download ?
I see numbers like 537 total blocks sent. My m0p code is larger and my m4 code is currently a few lines. So, I might think that "most of 537" might be getting close to 512K ?
2) Is there a file that contains the flash image size (as one simple number) after building so I can know how close I'm coming the limit ? I have looked in the .map files ... hard to discern which number might be giving me the answer.
I'm using CY8C6247BZI-D54, which has 1M flash. I'm dividing it evenly between the m0p and m4.
Show LessHi,
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 */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~