PSoC™ 6 Forum Discussions

Hello,
I have questions about PSoC61.

1. In the PSoC6 overview (Infineon Homepage), PSoC61 is classified as a single core.
    But does PSoC61 actually contain M0+ as well as M4?

    The datasheet states as follows : "In PSoC 61 the Cortex M0+ is reserved for system functions, and is not available for applications."

2. I created a PSoC61 BSP, there is a cy_m0p_image[] array in the psoc6_01_cm0p_sleep.c file.
     What is it for? Does it make the M0+ core go to sleep and jump to M4?
     When I compile the project, are both M0+ and M4 created as one hex file?

3. If I use the IAR compiler should I export the progect and include psoc6_01_cm0p_sleep.c?

Thanks and Regards,
YS

Dear support team,

    I'm using CY8CKIT-062S2-43012 demo and MTB 2.4 to debug UART comunication. now the uart TX interrupt funcation is ok. but uart RX interrupt can't  go into the interrupt service,so can't recive data.Although uart polling mode can revice the data, which also certify the hardware is ok. i have attched my uart code as below, could you give me some advice?thanks!

I have two projects, the first is called Simple Port and the second Simple Port 2. Simple Port 2 was created by saving the first project under a new name. Everything has worked olkay in both projects until about a week ago, when I noticed today that PSoC Creator is showing me copies of some of the first project's files which have been created in My Templates.

I have simply no idea how or why this happened. Is it supposed to happen? Is there a way to respore my project under a new name with the up to date copies?

Dear Receiver, 

Can I use "PSoC Creator 4.4" to test cap sense functions in "CY8CKIT-062S2-43012" kit ?!

(Because using PSoC creator 4.4 is more convenient than using Modustoolbox at this moment.) 

Thank you.

Sorry if this is the wrong location to post this, I wasn't entirely sure where to...

I am very new to drivers (in this case, USB) so I may be wrong or misguided with this info, but I will try my best.

I have a C# Visual Studio desktop app (a GUI) that bootloads code onto my PSoC device through USB using calls from CyUSB.dll. I have heard that CyUSB.DLL is a legacy implementation, and hasn't been maintained, so to use the Microsoft HID libraries and drivers instead.

Here are two closely related community posts:
Solved: Re: Should we use Cyusb.dll with VC# for a PSoC5 H... - Infineon Developer Community

Solved: Alternative to CyUSB.DLL - Infineon Developer Community

I suppose my question here can be split up:

1) Is there any more information on why CyUSB.DLL is obsolete and/or what exactly isn't maintained? Does this mean that new supporting libraries (like Microsoft?) have been released for newer hardware, and the CyUSB library is no longer being updated alongside those?  Any kind of explanation about this would be appreciated and may help my general understanding.

2) In terms of alternatives, would it better for me to use Windows HIDAPI or WinUSB?

3) What would be the general way to go about replacing CyUSB.dll in my desktop code, or where would be a good place to start? Just replacing CyUSB library call in my desktop app with corresponding functions from Windows HIDAPI/WinUSB?

4) Does the new library need to interface with cybtldr APIs?

Overall, I am just a bit out of the loop on exactly why CyUSB.dll is obsolete, and am looking for advice on where to start on getting it replaced for future use cases, or to be able to bootload over from newer machines.

Any answers to any of my questions would be hugely appreciated, as well as any correction if I am wrong about something here. Trying to expand my knowledge here. Thank you!

Hi! I work with demo project of QSPI Flash RAM Access (for Cy8CKIT-062-BT-WIFI) and i see that this project set up for CY15x104QSN Flash IC (exactly file serial_fram_api.h). But now i have to use the same project with S25FL128S IC. Could you help me to find a driver of tihs chip (smth like serial_fram_api.h)? Or suggest another case how could i work with it?
Thank you!

USB CDC echo example builds and runs fine right after creating the app in Modus Toolbox 2.4. Problems arise when I use the library manager to update the CY8CPROTO-062-4343W BSP from 1.3.0 to latest 3.x release.

With no other changes, the build now fails with errors:

make: *** [secondstage_build] Error 2
make[1]: *** [/Users/user/mtw/USB_CDC_echo_1/build/CY8CPROTO-062-4343W/Debug/libs/psoc6hal/COMPONENT_PSOC6HAL/source/cyhal_adc.o] Error 1
make[1]: *** [/Users/user/mtw/USB_CDC_echo_1/build/CY8CPROTO-062-4343W/Debug/libs/psoc6hal/COMPONENT_PSOC6HAL/source/cyhal_clock.o] Error 1
make[1]: *** Waiting for unfinished jobs....
conflicting types for 'CYHAL_CLOCK_IMO'
conflicting types for 'CYHAL_CLOCK_EXT'
conflicting types for 'CYHAL_CLOCK_ILO'
conflicting types for 'CYHAL_CLOCK_ECO'
conflicting types for 'CYHAL_CLOCK_WCO'
conflicting types for 'CYHAL_CLOCK_LF'
conflicting types for 'CYHAL_CLOCK_PUMP'
conflicting types for 'CYHAL_CLOCK_BAK'
conflicting types for 'CYHAL_CLOCK_FAST'
conflicting types for 'CYHAL_CLOCK_PERI'
conflicting types for 'CYHAL_CLOCK_TIMER'
conflicting types for 'CYHAL_CLOCK_SLOW'
conflicting types for 'CYHAL_CLOCK_ALT_SYS_TICK'
conflicting types for 'CYHAL_CLOCK_PATHMUX'
conflicting types for 'CYHAL_CLOCK_FLL'
conflicting types for 'CYHAL_CLOCK_PLL'
conflicting types for 'CYHAL_CLOCK_HF'
'cyhal_clock_t' has no member named 'div_type'
'cyhal_clock_t' has no member named 'div_num'
redefinition of '_cyhal_clock_allocate'
'cyhal_clock_t' has no member named 'div_num'
incompatible type for argument 2 of '_cyhal_utils_try_alloc'
too few arguments to function '_cyhal_utils_try_alloc'
'cyhal_resource_pin_mapping_t' has no member named 'inst'
'cyhal_clock_t' has no member named 'div_num'
'cyhal_clock_t' has no member named 'div_type'
'cyhal_clock_t' has no member named 'div_num'
'cyhal_clock_t' has no member named 'div_type'
'cyhal_clock_t' has no member named 'div_num'
'cyhal_clock_t' has no member named 'div_type'
'cyhal_clock_t' has no member named 'div_num'
'cyhal_clock_t' has no member named 'div_type'
'cyhal_resource_pin_mapping_t' has no member named 'inst'
incompatible type for argument 1 of '_cyhal_utils_reserve_and_connect'
incompatible type for argument 1 of '_cyhal_utils_reserve_and_connect'

I also get these warnings: 

passing argument 3 of '_cyhal_utils_try_alloc' makes pointer from integer without a cast [-Wint-conversion]
implicit declaration of function 'cyhal_hwmgr_free_clock'; did you mean 'cyhal_hwmgr_free'? [-Wimplicit-function-declaration]
implicit declaration of function '_cyhal_utils_is_new_clock_format'; did you mean '_cyhal_utils_get_clock_count'? [-Wimplicit-function-declaration]
passing argument 2 of '_cyhal_utils_reserve_and_connect' makes integer from pointer without a cast [-Wint-conversion]
passing argument 2 of '_cyhal_utils_reserve_and_connect' makes integer from pointer without a cast [-Wint-conversion]

My problem is that I had configured many peripherals based on the CDC Echo app. Now, even when I downgrade to 1.3.0 again, the errors do not go away and I cannot manage to build the project. 

How can I repair the project? Is there a way to better understand what needs to be changed in the example to be compatible with BSP version 3.0.0? Is there a changelog or do I need to manually run diffs on Github? 

Thanks! 

Hi,

I used to work with PSoC 5LP and now I'm going to use PSoC6.

I have few questions-

1. Is PSoC6 has less uarts/i2c/a2d then PSoC5LP?

2. What  is the benefit of usuing the VBUCK?

3. Do I need an external crystal oscillator? If I'm using USB I need extanell oscillator?

4. I saw that every port has it's own power supply pin. Can I give 1.8V to some ports and 3.3V to other?

5. Can I operate only part of the port? For example- give 3.3V to VDDD and all the othere are off.

BR

Shmuel

Hi,

i developed a PSoC 6 based prototype pcb with BLE antenna and a pi matching network similar to the CY5677 BLE USB Dongle.

The antenna is a bit longer as described in AN91445 (Antenna Design and RF Layout Guidelines) and should be tuned by adjusting the length. I want to use the Pi network to tune the chip side. Unlike the system used in AN91445, I now have no real reference point.

The possibility I see would be to connect the VNA to the contact of C20 (see pic) and ground plane. Then I could tune the antenna. But for tuning the chip side I would then have to cut the antenna (and destroy my PCB).

How is this done in practice, for example for the BLE dongle?

Thanks!