PSoC™ 6 Forum Discussions
Infineon has publicly stated
- PSoC 3 is produced on 130nm process.
- PSoC 6 is produced on 40nm process
Will future PSoCs use a smaller process?
What process do the other PSoC technologies use?
Greg
Show LessHello :),
I am using Modustoolbox 3.1 and a PSOC 6 CY8CPROTO-063-BLE with kitprog3. I tried to measure voltage with the simple available application "ADC Basic" using HAL but when I debug/run it, nothing happens. I am using a terminal emulator "Tera Term". I am aware that using HAL and Device configurator can't work on a same pin source thats why I did 0 change in device configurator thinking that the application which was available did all the set up needed.
Power Supply: Vref=3,3V
If you need more informations please let me know.
I am trying to run this application for days and I am hopeless.
Thank you in advance for your help.
Enys
Show LessHello Everyone, I am having a Psoc 6 CY8CKIT-062-WIFI-BT. I would like to have a DFU bootloader using UART or USB but there are unfortunately no examples online using PSoC Creator.
All I could find was using Modus Tool Box and none using Creator.
I am able to achieve my task using Modus toolbox but I am required to get it done using creator
I am referring the below documentation. Please let me know if there are any sample codes for DFU using Creator
Infineon-AN213924_PSoC_6_MCU_Device_Firmware_Update_Software_Development_Kit_Guide-ApplicationNotes-v09_00-EN.pdf
https://infineon.github.io/dfu/html/index.html#section_dfu_quick_start
Show LessI'm using PSoC 6 based controller. I'm using a autoreload timer, to connect to the wifi network. The timer is stopped only when it connects to the wifi network. Timer stop function is called from the timer_callback function. For some reason because of the cy_wcm_connect() function the timer is not able to stop. Instead the callback function is called and because the device is connected to wifi it again tries to stop the timer. I want to know how to stop the timer in right way. I tested the timer callback function with and without the cy_wcm_connect() function.
I would like to have some help over this.
Show LessDear all.
I tested emulated EEPROM and I want to decrease flash time.
I tested with ev-kit 'Cy8CKIT-062-WIFI-BT' and using application 'Emulated_EEPROM' link below
(https://github.com/Infineon/mtb-example-psoc6-emulated-eeprom/blob/master/README.md)
This is my setting
1. Core clock
2. Register setting
3. Code
4. Result
Write Time = 49ms
Erase Time = 26ms
Read Time = 2ms
5. Datasheet
I thought my register setting was the fastest, but is differs a lot from the data sheet.
(Infineon-CY8C62x6_CY8C62x7_PSoC_62_MCU_Arm_Cortex_-M4-DataSheet-v18_00-EN.pdf)
which parameter causes the time long?
please let me know any method to flashing time shorter.
thanks.
Show LessHi. I have zero knowledge of SW. I'm a hardware engineer. Could you step by step with pictures and code examples explain how to assign PWM signals to certain pins of the board when some events appear? I use MTB but have no idea how to do it...v Maybe let's do it together?
Show LessHello I'm trying to run ble using CY8CPROTO-063-BLE and configure as an hid service to send keystrokes to the host. I tried following examples published here https://github.com/Infineon/PSoC-6-MCU-BLE-Connectivity-Designs
but was not able to successfully implement. Wondering if someone can point me to some updated examples or resources.
Thanks in advance
Show LessError: kitprog3: failed to acquire the device
Info : clock speed 2000 kHz
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
Error: DAP 'psoc6.cpu' initialization failed (check connection, power, transport, DAP is enabled etc.)
Info : psoc6.dap: powering down debug domain...
Error: Error connecting DP: cannot read IDR
Error: Error connecting DP: cannot read IDR
After changing the port number, when I try to compile, I keep getting the following error codes. Could you please assist me in resolving these issues?
my board is CYW20829
When I was writing my BLE program based on RTOS, I created some other tasks and ran the program, which caused Bluetooth to fail to initialize, meaning it could not start. The program only printed the content before Bluetooth initialization.
/* Initialize bluetooth porting layer by setting HCI configuration */
cybt_platform_config_init( &cybsp_bt_platform_cfg).
/* Register call back and configuration with stack */
result = wiced_bt_stack_init(app_bt_management_callback,
&wiced_bt_cfg_settings).
/* Check if stack initialization was successful */
if( WICED_BT_SUCCESS == result)
{
printf( "Bluetooth Stack Initialization Successful \n ");
}
else
{
printf( "Bluetooth Stack Initialization failed!!! \n ");
CY_ASSERT(0).
}
The program printed Bluetooth Stack initialization successfully on the terminal, but it seems that the program is stuck in a certain task, causing The program printed Bluetooth Stack initialization successfully on the terminal, but it seems that the program is stuck in a certain task, causing I would like to ask what direction I should take to solve this problem when it arises. (Note: I modified it using the modustoolbox BLE routine).In other words, under what circumstances will Bluetooth fail to start
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-6/Regarding-the-issue-of-Bluetooth-not-starting-properly-when-programming-with/td-p/735250
Show LessHi: When I use MiniProg4 to burn in CY8C6247FD1-D02, PSOC Programmer prompts: Hex File parsing failure. Unknown record type.
May I ask what causes this? What do I need to do to fix it?
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-6/MiniProg4-%E7%83%A7%E5%BD%95CY8C6247FD1-D02/td-p/735074
Show Less