PSoC™ 4 Forum Discussions

I like to use this device running an USB - HID profile. According datasheet Pin 13.1 (D-)  13.0(D+) and P13.2 VBUS (5V from USB?). Datasheet of USB tells me that I also have to assign VBUS to P0.0 ..(for 4200L devices). For me this is all not clear how to wire. It would be very great if your datasheet hold a schematics of all possible scenario.. how to connect. Pease assist !!

I like to run it as self powered, Not Bus powered. Please tell me the exact setting in USB configuration, and how to wire... what to connect where and how, Thanks.

Hello, Cypress supporters.

About PSoC4: CY8C4024LQS S411, I want to set Pin(UART Rx setting) to detect GPIO edge occurrence and wake up from Deep Sleep. However, according to "AN90799: PSoC® 4 Interrupts", it says:

2.1 Interrupt Sources

(1)There are pin limitations; not all ports have dedicated interrupts. If the UART selected pins do not have dedicated port interrupt, it cannot wake up the device. See the "Interrupts" chapter in device Architecture Technical Reference Manual (TRM) to learn about ports that have dedicated interrupts.

It says "If the UART selected pins do not have dedicated port interrupt,"　Which Pins can't wake up?
I looked at the relevant part of TRM, but I can't find the description.

Thank you for your support.

I am using the USB HID example from cypress. On the Cy8CKIT-059 (psoc5) it is running fine. I have to use CY8C4247AZI-L485 in a custom board.The system is self powered. I connected D+  D- and VUSB to the pins of the USB connector. I can programm but USB enumeration is not completed. The flow hangs in the while loop

int main(void)
{
uint16_t OUT_COUNT;
uint8_t* response;
CyGlobalIntEnable; /* Enable global interrupts. */

/* Place your initialization/startup code here (e.g. MyInst_Start()) */

/* Start USBFS operation with 5-V operation. */

USBFS_1_Start(USBFS_1_device,USBFS_1_5V_OPERATION); // USBFS_1_3V_OPERATION

while(USBFS_1_bGetConfiguration() == 0x00)
{
/* Waiting for device to be configured */
}

I also tried the 3V operation. I checked the USB configuration  and tried all options avaliable

also using P0.0 with a voltage divider connected in parallel to VUSB. What do I miss? How can I get  the device running?

I have a running USB project with only a USB block in TopDesign. And I have a second complete project with pinning and pheriperals but USB does not work. I compared both USB settings and did not find any difference. Ist there a way to clone this projects that I will get the USB in second project working by overlaying both projects

uint8 ProgramData(uint32 address, uint8* data, uint32 length)
{

.........

}

I want to define this function in ram so that after hardwa reset it will  disappear. I tried to change the link file add a section in ram area and use "CY_SECTION".It builded successfully but it failed in programming.It showed that the hex file not correct.Could somebody tell me how to modfiy this code?🤔

Hello,

We know that the "CE210291 - PSoC® 4 CapSense® Low-Power One Button" project transitions between Deep Sleep and Active mode to achieve CapSense with low power consumption. When the Deep Sleep current is measured using CY8CKIT-041-40XX with the power supply voltage set to + 3.3V, it is several μA.

On the other hand, when the Deep Sleep current is measured with the power supply voltage set to + 5 V and the VREF set to 2.021 V, approximately 350 μA is consumed.

Do we need to put VREF to sleep before executing CySysPmDeepSleep ()?

If the power supply voltage is + 5V and the Vref is 2.473V, the Deep Sleep current will be several μA.

We would like to adjust the gain of raw count value with Vref.

Best regards.

Yocchi

I've got some code I've been writing that I now want to convert over to be able to upgrade Over The Air.

The code has the BLE component set up as a Client and Server profile.  The Client profile is configured with a Current Time Service, to enable syncing of the time in my code whenever it is accessed via a central device.  In the Server profile, I've got various custom services along with all the normal ones (Device Information, Generic Attribute, Generic Access, etc).

The Server profile is also set up to stuff some data into the Scan Response Packet, to make it easier to get data across to the Client without requiring a connection.  Connection is reserved for firmware updates (if I can get this to work!)

The code, as a non-OTA arrangement, compiles and works fine.  Until I attempt to convert it over to an OTA Fixed Stack Bootloadable version.  I've done this before, just not with the CTS functionality included, and its always worked.  I've followed all the steps outlined in the OTA Guide (AN97060), but I'm still not getting the Bootloadable code to compile.  Its throwing up a bunch of errors associated with the CTS functionality, even though I've made sure I've included the appropriate header files, etc.

The particular things its getting errors on are:

• CyBle_GetClientState()
• CYBLE_CLIENT_STATE_DISCOVERED
• cyBle_ctsc

I can see that these are all defined in the Bootloader source code (in BLE_eventHandler.h & BLE_cts.c and BLE_cts.h), but for whatever reason, my Bootloadable code isn't seeing them.

Any ideas what I'm doing wrong??

Cheers,

Mike

Hello,

I am using the PSOC CYBLE-022001-00.  I have a timer interrupt that is programmed to interrupt every 250msec.  The interrupt service routine toggles a port pin that drives an led.  The program works fine in debug mode but in regular run mode the timer interrupt does not happen.  Any help would be greatly appreciated.