PSoC™ 6 Forum Discussions
Hello,
I designed a board around the CY8C6144LQI-S4F92 MCU. I found the QFN package difficult to solder by hand so I'm looking for a QFP replacement for the next revision. Specifically, I need the following specs:
- 1 USB-FS interface
- 3x I2C lines
- 24x GPIO
- 2x ADC chan
- 5x DAC chan
- 3.3V operation
I found that the CY8C614AAZI-S2F44 is a QFP part with these specs currently in stock on Arrow. I looked at it on the device configurator in ModusToolbox and it seems to have all the specs I need. Would this be a valid replacement for the current part I'm using or are there some gotcha's I'm not seeing?
Thanks,
Sam Shersher
Show LessHello,
I tried to get segger systemview running to trace the freertos tasks.
The way freertos is used in Modustoolbox is so fundamently different that I was not able to get it running.
Can you support a project using freertos and has everthing implemented so that segger systemview works?
Thank you and best regards
Phil
Show LessHello,
I would like to drive TFT 480x272/RGB/16bpp using PSoC 6. The MCU provides "Graphic LCD Controller" component to do that, but it needs an external RAM buffer. There are larger RAM PSoC6(512kB 1024kB) on the market. Theoretically it should be possible to place a frame buffer into internal RAM and operating display(refreshing, hsync, vsysnc, DE, clock) using DMA+UDB logic without external RAM.
Does anyone have experience with such a solution?
Than you,
Jan
Show LessCan someone please provide a simple SCB UART sample for Modus Toolbox which interrupts on a character received? Thanks in advance.
Hi,
Can we expect any RTOS official component on Creator anytime (maybe until Creator 5)?
Maybe a wrapper around FreeRTOS source code, the FreeRTOS examples include one example running on a PSoC5 device, but it might be useful to have a PSoC6 example as well.
Show LessHi I have just started working on psoc6 CY8CKIT-062S2-43012 in Modus tool Box and trying to connect Greengrass v2 edge device through MQTT.
I am unable to connect my psoc6 board to my edge device where I have installed Greengrass v2. I have used MQTT Client code from the examples of psoc6 CY8CKIT-062S2-43012 in modus Tool box, it is working fine when I am using endpoint of AWS IoT core. but when I am using the end point of my Greengrass v2 edge device then I am unable to connect.
when I am using AWS Greengrass v2 SDK from AWS python code directly from terminal, then it is also working proper.
please provide some support or examples if available for modus tool box.
Thank you in Advance
Show LessHi,
I have the CY8CEVAL-062S2 with LAIRD M.2 module and running MTB 2.4. If I use the "Wi-Fi_Onboarding_Using_Bluetooth_LE" example with the PSoC6 BSP = CY8CEVAL-062S2-LAI-4373M2, I'm unable to pair with an Android 10 Pixel3XL phone, or an Android 11 Pixel2 phone. However, I'm able to pair with an Android 12 Samsung A52 phone (it prompts for a passkey).
On the other hand, the same code example built for PSoC6 BSP = CY8CKIT-062S2-43012 and running on the older PSoC 62S2 Pioneer Kit, is able to pair with all 3 phones (passkey method).
Could you help? Please find the attached logs. Thanks!
Show Less通过阅读 Infineon-AN218241_PSoC_6_MCU_Hardware_Design_Considerations-ApplicationNotes-v01_00-EN
可知 VDDIO0 是负责给PORT11 供电,如果想单独PORT11供电1.8V ,请问应该怎么接线呢 ?
By reading Infineon AN218241_ PSoC_ 6_ MCU_ Hardware_ Design_ Considerations-ApplicationNotes-v01_ 00-EN
It can be seen that VDDIO0 is responsible for powering PORT11. If you want to power 1.8V separately for PORT11, how should you connect it?
Show Less
Two Questions:
1) Where is a BSP for cy8c6144lqi-s4f12 ?
This official BSP will be needed for the final design.
2) Is BSP cy8c6144lqi-s4f12 identical to BSP cy8c6244lqi-s4d92 from a PCB interface perspective?
If these two parts are drop in replacements of each other and every pin supports the same function, either BSP can be used to layout the PCB.
While desiging for cy8c6144lqi-s4f12, I realized there is currently no BSP. The closest part is cy8c6244lqi-s4d92 within CY8CKIT-062S4.
Greg
Show Less
hello.
Please inquire about SAR DMA interrupt.
I tested it using the test_adc1() function in adc_core.c .
* condition
- target : CY8C6136
- SAR : 4 channel
- DMA : channel 0
* case-1
#define TEST 1 // Normal operation such as interrupt generation
* case-2
#define TEST 0
-> DMA works well
-> Interrupt related service routine address/register normal -> Do not go to interrupt routine
It has to be used like case-2 for compatibility with existing projects, and has been progressing without any problems in other MCUs.
All peripheral configurations are as in case-2, and other interrupts are judged in the same situation.
I want to attach an iar project that contains only the relevant content, but it cannot be attached due to a capacity problem, so only some files are attached.
In this regard, please review which part should be checked.
thank you
/*******************************************************************************
* Function Name:
********************************************************************************
* Summary:
*
* Parameters:
*
* Return:
*******************************************************************************/
void test_adc1(void)
{
#if TEST == 1
in_adc1_init();
while(1)
{
Cy_SAR_StartConvert(SAR, CY_SAR_START_CONVERT_SINGLE_SHOT);
Cy_SysLib_Delay(1000);
}
#else
adc_core_init();
while(1)
{
adc_conversion_start(ADC_CH_1);
Cy_SysLib_Delay(1000);
}
#endif
}
Show Less