I ordered a few chips CY8C4024AXI-S402 from DigiKey (https://www.digikey.com/en/products/detail/infineon-technologies/CY8C4024AXI-S402/11486333). Two chips were soldered and powered as it is recommended in Page#6 in the hardware design guide. I use PSoC creator 4.4, release date 10/01/2020, MiniProg4 programmer with PSoC programmer version 3.29.1.4659. All software and components were updated. The problem is PSoC creator cannot accuse this device. PSoC programmer status is Connected and Powered. I develop a simple project for this chip, builded it, but if I tried to program hex file by PSoC programmer, I got the message "Program terminated. Detected silicon ID "D5 80 21 A9" is not in database. The second chip has silicon ID "C3 80 21 A9". These silicon IDs showed up the same way when I tried multiple times. I found that the original silicon ID must be "19 17 11 A9" for this chip. I tried resolve this issue as it is recommended in in this post https://community.infineon.com/t5/PSoC-4/Silicon-ID-not-in-database/td-p/100222, but my case is different. I worked with PSoC 4200 family before, there were no problems like this with PSoC 4000. As I found out the problem can be in these chips that actually have different silicon IDs. I can actually edit the hex file to change the SiliconeID metadata and recalculate the checksum, but I think that's not good variant. 

What is the input to output delay time for the PSoC4 series?
I am sure it will vary depending on the circuit configuration, etc., but since you are asking me roughly, I would appreciate it if you could give me a figure.
Please use the model number CY8C4124PVQ-442.

Hi, Community 

I am currently working on a project about proximity sensing with a PSoC4000S evaluation board and Capsense components v7.0.
In my project, I want to get the value when the proximity sensor detects the capacitance of a finger and control something.
However, proximity sensing does not seem to have a function to get rawdata like other capsense widgets.
For example, for a linear slider, I consider the following API to return the center of gravity position of the finger.
CapSense_GetCentroidPos ( widget ID);

Do you know of any function similar to this for proximity sensing?

Can anyone give me some advice?

Best Regards,

Chihiro Tatebayashi / NEXTY

Hi all,

I will have to customize the protocol (specifically the packets) of the communication between bootloader and PC host, basically ignoring the commands used in Infineon out-of-the-box update process.

Reading through the various appnotes, it seems to me that the only way to achieve this is through:

void Bootloader_InitCallback(Bootloader_callback_type userCallback);

that initializes the callback variable used when the bootloader receives an unknown packet.

As I have no hardware yet to test this, Am I right? 

If yes,  is there a way to throw away all the code that supports the Infineon standard commands? From what I see, it seems precompiled in binary form in cybootloader.c (Generated):

__attribute__ ((__section__(".cybootloader"), used))
const uint8 cy_bootloader[] = {
0x00u, 0x10u, 0x00u, 0x20u, 0x11u, 0x00u, 0x00u, 0x00u, ...

Thanks for any hint,

BR

F

I am trying to use the proximity sensor function (Proximity0) in PSoC Creator.

The proximity function can read the value with CapSense_IsProximitySensorActive() in CapSense_Structure.c, but the proximity determination remains OFF. Please refer to the image below for the arguments (even though you put your hand close to the electrode sheet). ）

I think a scanning process will be required before proximity determination can be made, but in Capsense_Sensing.c

 CapSense_Scan calling (). Please let me know if there are any other APIs you need to call.

 

 

 

 

Dear Sirs and Madams,

We have a question about ExtClk clock settings in Bootloader project.

We are using CY8C4024AZI-S403 device with a UART Bootloader configuration in PSoC Creator 4.4 IDE.

In order to improve the clock accuracy of UART communication, The system clock is running with ExtClk.

When receiving a firmware update command from UART, the Bootloader is started by calling the Bootloadable_Load() API.

We have confirmed that the firmware update can be completed successfully if the Bootloader clock resource is IMO.

 < Bootloader project clock settings : IMO >

 However, firmware updates will not work properly if the Bootloader clock resource is set to ExtClk.

< Bootloader project clock settings : ExtClk >

*Note 1: Both projects correctly assign Bootloader.hex to Dependency of Bootloadble.           

Is it not possible to set the Bootloader clock resource to ExtClk in the UART Bootloader of PSoC4000S?

Since clock accuracy between target of PSoC4000S and the host is important for UART communication, We are considering using ExtClk instead of IMO.

Regards,

Dear Sirs and Madams,

We are considering to implement the PSoC4S MAX proximity sensor on a metal frame that is connected to the FG.

The image diagram is below:

When We verified the operation, the sensitivity of the proximity sensor of PSoC4S MAX is very poor because the metal frame becomes a strong ground.

Will the following two work as a countermeasure?

Please tell us the best way to use a proximity sensor in such a strong grounded metal frame.

(1) Use an insulating sheet

(2) Isolate PSoC4S MAX and proximity sensor ground

Regards,

I have a CY5676A PRoC BLE 256KB module that I'm trying to program with PSoC Creator, but I can't find it in the device selector. What additional add-on software do I need to install in order to use it with PSoC Creator?

Thanks!