Hi All, 

I'm using in PSOC5 - CY8C5868AXI-LP035.

I've tried to figured out how to software the pin XRES but without successful.

There any options how can to software the XRES so i can do reset to PSOC without external intervention?

Thanks for any help.

Hi all,

If i write to TCPWM_WriteCompare() or TCPWM_WritePeriod() everything works fine.

But if I write to TCPWM_WriteCompareBuf() or TCPWM_WritePeriodBuf() nothing happens.

I have read TRM and Data Sheet  but it is not clear to me how the switch input is used?

Attached picture how I connected switch input.

Regards

Luis

Hi, What is the absolute max junction temperature and max recommended operating junction temperature of S29GL512S10TFI02 (industrial) and S29GL512S10TFV02 (industrial plus)?  Both are TSOP-56 package.  The datasheet gives max Ta  (ambient operating temperature) but does not give max rated junction temperature Tj.  Thanks,

I have been using iwd for wifi connections on  my RPis (Zero/3/4). These all use the brcmfmac/cyfmac 43430/45455 chip. They work reasonably well in station mode with iwd. The current RPi kernel uses an old driver, though I have built and installed the latest driver from 20200925 and also the firmware in the same package. The main advantage of iwd over wpa_supplicant is that the devices connect almost immediately. Very fast.

I cannot get AP mode to work at all with iwd. hostapd works fine. Can we get assistance getting the fmac driver/firmware updated so that it will work with IWD in ap mode?

from the IWD group, this is one difference noted:

The issue is that iwd uses NL80211_CMD_REGISTER_FRAME to be notified of incoming management frames,
and this is what kicks off the 4-Way Handshake in ap.c. But brcmfmac does not support this (except in P2P mode?).

Appreciate any comments and help with this.

Keith

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

For a project that needs "intelligent bitbanging" the PSoC for seems to be perfect. I'm evaluating following chain:

Pin => combinatorial logic 1 => status register => CPU processing => control register => combinatorial logic 2 => Pin

I connected the two pins externally and put an inverter as a minimal combinatorial logic 1 into the schematic. The registers/pins are set to transparent for minimal latency (I'll add synchronisation as appropriate later, that's just an experiment). Combinatorial logic 2 does not yet exist, it's a direct connection for now.

The code contains an unrolled loop like that (compiled from C):

ldrb r1, [r2]
uxtb r1, r1
strb r1, [r3]
ldrb r1, [r2]
uxtb r1, r1
strb r1, [r3]

or handwritten assembly:

ldrb r0, [r5]
strb r0, [r6]
ldrb r0, [r5]
strb r0, [r6]

This roundtrip takes approximately 11 cycles (230 ns) at 48 MHz, maybe 10 cycles plus propagation delay.

Is this correct? Where are the cycles needed?

Hello, 

We have designed a capacitive sensing trackpad using the CYBLE-214015-01 module. We followed the Cypress recommendations when creating our 7 by 7 trackpad. Now for a project, we are using the PSOC Creator Sense Tuner in order to acquire the x and y positions of a finger touch on our trackpad. From the Widget View on the Sense Tuner I am able to see the 7 rows and 7 columns working perfectly and going over the finger threshold. The problem we are having is that when we log the x and y positions and then extract it and analyze it we seem to be missing data points. Is there any recommendations as to how to fix this? Below I show what our raw data looks like. In reality the data points should be spread across the entire area as I went back and forth the entire trackpad surface for an entire minute. We do not understand why there is some areas that are completely blank. For the parameters, we are using a 8 bit resolution and a 3x3 centroid.  I have attached the code that I am using in order to use the tuner.

Hi all

For infineon+CYPRESS people.

Are there any plan for releasing PSOC 4200L prototyping kits.

I vote for it😊

Regards

Luis

Hello, 

It seems that the function "CapSense Gesture" is not supported for controller CY8C4025LQI-S411, is that correct? And if so, is there an alternative controller? Where can I find an overview.

Many thanks

I am using a CY8C4244 and have been using PSOC4 for several years now, and have run into a situation that does not make sense.

Setting up a non-dedicated interrupt is not apparently an option, and this is very bad for my design as I cannot have as many dedicated interrupts as is required,

What gives here, why is this not functioning like all other PSOC4s I have used to date?  Please respond ASAP, this is a big issue.