PSoC™ 6 Forum Discussions
I'm using the CY8C6144AZI-S4F92 to develop something. I'd like to program it from modustoolbox with the use of JTAG.
To set this MCU in programming mode many checks have to be done, with the use of pseudocode.
If i purchase the CY8CKIT-002 and connect it to the MCU via JTAG, will the CY8CKIT-002 perform all the checks?
In other words, will it check the silicon ID, erase the application flash and will it perform all the other checks, so i can just plug everything in, and then upload my code using modustoolbox?
Show LessHi everybody,
I'm working on project with a PSoC 6, using MTB 3.1, Eclipse as IDE and when initiating "Building Application" the "Auto-discovery in progress..." takes forever and makes a fast working impossible. How can I make this faster, like the fast incremental builds one is used form other build systems?
BR
Bernhard
Show Less
I have an application on a PSOC63 with FreeRTOS running BLE in dual-core mode. It offload data quickly through bursts of large notifications (512 ATT MTU size, 495 byte payload). The project follows the examples of "CE223508_PSoC6_BLE_MultiSlave_RTOS" for setting up a BLE Task capable of handling multiple slaves (BLE connections), and the offload/notification parameters of "CE222046_Throughput_Measurement" for maximum throughput.
All notifications are sent from this method, where the connection status, busy status and notification enable status are checked before calling the API:
uint8_t i;
/* Send notification top all the connected device */
for(i = 0; i < CY_BLE_CONN_COUNT; i++)
{
/* Confirm that the BLE stack is ready */
if (Cy_BLE_GATT_GetBusyStatus(appConnHandle[i].attId) == CY_BLE_STACK_STATE_FREE)
{
/* Check if the client/slave is both connected and subscribed to this notification */
if((Cy_BLE_GetConnectionState(appConnHandle[i]) == CY_BLE_CONN_STATE_CONNECTED )&&
Cy_BLE_GATTS_IsNotificationEnabled(&appConnHandle[i], handleValuePair.attrHandle))
{
/* Send BLE notification */
cy_stc_ble_gatts_handle_value_ntf_t param =
{
/* Fill all fields of the Write request structure ... */
.connHandle = appConnHandle[i],
.handleValPair = handleValuePair,
};
bleApiResult = Cy_BLE_GATTS_Notification(¶m);
/* Check if the operation has been successful */
if(bleApiResult == CY_BLE_SUCCESS)
{
DebugPrintf("Info : BLE - Sent notification. \r\n");
}
else
{
DebugPrintf("Failure! : BLE - Sending notification. Error Code: %d \r\n", bleApiResult);
}
}
}
else
{
/* Stack is busy, the current notification data will be dropped */
Task_DebugPrintf("Error : BLE - Stack busy to send notification", 0u);
}
}
When the "Maximum number of BLE connections" is set to 1 in the BLE component, the application runs with no issue. However, if the "Maximum number of BLE connections" is set to 2, I begin to receive "CY_BLE_ERROR_MEMORY_ALLOCATION_FAILED" error responses from the Cy_BLE_GATTS_Notification (or Cy_BLE_GATTS_SendNotification) methods when sending notifications rapidly, which eventually results in a CM4 Fault. A second BLE device does not need to connect to cause this issue, just allowing a second seems to cause it. At no time during the calling sending of notification do I see the STACK_BUSY event. I call Cy_BLE_ProcessEvents() before and after the send notification.
I've tried debugging this from every angle, changing the size of the BLE message payloads, changing the allotted RAM of CM0 and CM4, but cannot get the issue resolved.
Show LessDear Infineon,
Regarding the VDDIO question, the VDDIO0 supplies eFuse power and needs a 2.5V power supply.
If the eFuse is not supported, the supply voltage can be between 1.7V~3.6V, right?
Show Less
Hi,
i'm in trouble with a device that does not load the new application because it fails this function (Cy_DFU_ValidateMetadata(..)).
Trying with another device all work perfectly.
I compared the entire flash of the two devices and it's the same.
Why it fails? it returns CY_DFU_ERROR_VERIFY
Help please
Show LessDevice: CY8C6136BZI-F34
IDE: PSoC Creator
Design Goal: Switch applications from the bootloader [app0] to the bootloadble application [app1].
Design Approach: Followed the DFU application note and configured the linker to work with this PSOC.
Issue: When app0 switches to app1, the PLL function Cy_SysClk_PllManualConfigure is failing because the PLL is already running. This code is in an auto-generated file called "cyfitter_cfg.c". All clocks from app0 run at the same frequency as the clocks in app1.
What do I need to do to make it so app1 will run?
Show Less
Dear Infineon,
The picture shows that the MCU requires two Crystals (WCO/ECO). WCO supports watchdog and RTC functions. We would like to know what features ECO supports?
If we don't use this feature, we don't need ECO Crystal, right?
Show Less
Hello.
I am trying to create a 16-bit control register in PSoC creator by linking two 8-bit registers. I intend to use the created registers for the purpose of storing the output results of SAR via DMA. After researching, I recognized that I could create the register by registering each register in UDB, and I set it up myself, but the output only shows the result of one of the registers. The program I am creating is shown below, so please let me know why it does not succeed.
Equipment used
PSoC 6 (CY8C62x7), PSoC creator 4.4
Show Less
Dear forum:
I develop a product with psoc6 (CY8C6137BZI - F14).
I set the power to LDO 1.1v, but when I set pSoc to deep sleep,
I checked the VBUCK1 port, the power is 0.9v,
can you tell me the reason?
or what is the possible that the VBUCK1 is 0.9V?
My soft setting:
I use the modus IDE.
I checked the generated code:
Device: CY8C6136BZI-F34
IDE: PSoC Creator
Design Goal: Read the current status of a GPIO output pin that is controlled from a PWM block.
Design Approach: Connected a PWM block PWM_n output to a GPIO output pin.
Issue: When I try to use the function Cy_GPIO_ReadOut using the correct port and pin number of my GPIO pin, it always returns "1", even when the GPIO is currently being driven low. I do not use any software commands to change the GPIO pin state, the GPIO is driven from a PWM block on the schematic. I need to know the current output level of the pin to provide feedback on its level.
This works fine for any GPIO output pins I control thru the software.
I cannot find any functions that return the current state of the PWM block pwm or pwm_n signal.
Show Less