PSoC™ 4 Forum Discussions

I frequently check data through SW Download and I2C communication with MiniProg4, but it can be inconvenient because the two ports are separated. So, I am using these two ports connected, and there is no problem. In the case of MiniProg4, can it be used by connecting SWD and I2C? Is it not a problem because SWD and I2C never operate at the same time?

Hi, I am using the Psoc 4100 s max  microcontroller in which CY8C4149AZI-S598 mcu used. Can you please help in finding out which pins we can configure for SPI communication in this microcontroller. I am unable to find out these and also dont have pinout diagram for that.

Hi, Community,

I am trying to do an I2C communication project with CY8CKIT-041S-MAX.

I have almost finished writing the code, but when I build, I get an error about Cy_SCB_I2C_Enable (cy_scb_i2c.h).
I found a similar phenomenon in PSoC6 post.
To solve this problem, I tried to add the necessary files in the library manager, but that did not solve the problem.

If you know the best way to deal with this error, please let me know.

The error message is as below:
C:/xxx/build/APP_CY8CKIT-041S-MAX/Debug/main.o: in function `Cy_SCB_I2C_Enable':
make: *** [../mtb_shared/core-make/release-v3.2.2/make/core/main.mk:374: secondstage_build] Error 2
make[1]: *** [../mtb_shared/core-make/release-v3.2.2/make/core/build.mk:422: C:/xxx/build/APP_CY8CKIT-041S-MAX/Debug/mtb-example-psoc4-empty-app.elf] Error 1
undefined reference to `sI2C_InterruptHandler'

Best Regards,

I am using Psoc Creator with cy8ckit-42 with a lengthy assembly file added to the simple blinky project. While the code has been building and running successfully and as it has gotten larger, adding an additional instance of a macro running correctly in other parts of the code causes the M0120 build error:

Build error: invalid offset, value too big (0x00000404)

The macro only accesses registers but has the instruction  "ldr r1,=0x00010000" The disassembly shows the constant is accessed with a pc offset in another instance so I guess it must be this offset that is too large. Is the only way to deal with this is to declare the constant in memory? Thanks very much.

Hi @Rohan_M ,

I removed all #ifndef TARGET_APP_CY8CKIT_040T conditions from blinky main file,

Its switching from blinky file to bootloader file with command input [w 0c 01 3b 00 00 c4 ff 17 p] via Bridge Control Panel(BCP).

Not switching from bootloader to blinky file, if we give command input [w 0c 01 ea 17 p] via Bridge Control Panel(BCP).

I attached the Project file, kindly check and give your feedback.

Thank you,

Step 1: Pin_A is enabled, and Pin_B is disabled.

Step 2: Enable Pin_B.

Step 3: Pin_A is automatically disabled. This is because Pin_B has been enabled.

Is there a feature that operates like Step 3?

It seems that entering a function in the Disable Property of the Built-in Tab for the component should work,

but I am not sure which function to use or how to write it. Could you please tell me how to do it?

“Pin_B_Disabled = not Pin_A_is_Disabled”

Hello,

I'm not sure from which revision, but the PSoC4000S power-down slew rate is listed in the datasheet.(1V/ms min, 67V/ms max.)
The current design does not meet this requirement (slow power fall), so I am considering adding a reset IC to the XRES to solve this problem.

For example, if the reset IC assert XRES at 1.7V or lower, is there any problem even if the slew rate at power-down does not meet the datasheet specs?
If the problem can be solved by adding a reset IC, what should the trip voltage be set to?

Regards,
Shimamura