PSoC™ 4 Forum Discussions
I have a design where I'm reusing SWC and SWDIO. No, I'm not out of pins, but I want to be able to access these pins externally to the device. It has a DB-9 with a couple of pins that are used as inputs. So I configured it to use the SWD pins as GPIO. According to the documentation, I can't debug that way, but I can re-program the device, because the programmer asserts reset and gains control of the pins. The device is Cy8C4247LTI-M475 and the programmer is KitProg2 from a CY8Kit043.
But when I go to program, the KitProg2 never asserts XRES and fails to acquire the target. It is putting appropriate waveform on the SWC and SWDIO pins, but the target isn't responding (presumably due to the lack of reset). What am I missing here? At present, I have no control over the target CPU to even change the SWD setting.
Thanks,
Wilton
P.S.: I tried this both with PSOC Creator 4.4 and with PSOC Programmer 3.29.1, both with the same result.
P.S.2: XRES is indeed being asserted, but it is very weak. With no load at all, it only falls to about 1 V. With a 10k pull up (which I put on the target board to prevent accidental resets from noise, there is no hint of a reset pulse. This doesn't seem normal to me. Interestingly, the first time I programmed the target, it worked fine, but I have been unable to connect to it since.
P.S.3: The KitProg reset output is also very weak at pull up. A 1 k resistor to ground basically killed it. But using a 10 k resistor to ground and a CMOS buffer, I was able to reproduce a reasonable reset signal, but still no luck re-programming the IC. I've order more KitProg2s in case this one is damaged. I don't think the reset output should be so weak. The other signals (clock and data) look fine, but it still isn't communicating with the IC.
Show LessHi, community,
I am looking for a way to easily change only the hardware settings in a project where the processing done in main.c is exactly the same.
For example, I am thinking of a way to switch and build only a config file that has been prepared in advance for multiple parameters, such as manual tuning of capsense.
As a test, I added new_design.cycapsense to the default design.cycapsense, but the build failed with a "cyforcebuild.mk" error.
Please tell me how can I build with multiple config files in one project?
I'm using Modus tool box 3.1 and capsense configurator.
Here is the error I get after adding the second config file.
make: *** [../mtb_shared/core-make/release-v3.2.2/make/core/search.mk:45: C:/xxxx/MSC_CAPSENSE_CSD_Button_Tuning/build/APP_CY8CKIT-041S-MAX/Debug/cyforcebuild.mk] Error 1
Best Regards,
Chihiro Tatebayashi / NEXTY
Hi Community, I'm working on CY8C4245AXI-483 controller for my Touch Switch Application. I'm using Interrupt for Touch Detection and wants to do it without Interrupt since I need to Implement a new Feature in which I need to Touch and Hold my Capacitive Touch Sensor and while the variable increment is going on I'll be Pressing some desired button on my remote which will do specific task. So If I'm already in the loop for Touch Detection, Can I use the IR Interrupt in between?
Show Less
I have been trying to run a WS2812 RGB+IC LED with a small PSoC 4 device which has no UDB's. I can not seem to get my timing fast enough. Seems like with a 24MHz part I should have no problem bit banging an IO pin to run this WS2812 LED. Could some one who has used this type of part, possibly look over my code and setup to see where I am going wrong. My code is simple just drives a single LED(pixel).
When I run WS2812_sendPixel(0, 0, 0) routine my zero sequence runs 880nS which is to slow. Looking for 400nS or less.
Also when I run WS2812_sendPixel(255, 255, 255) my code seems to run right but data sent out is not symmetric, the last 3 bits are not like the first 4 bits.
I have attached my project. The PSoC4 device I am running is CY8C4025LQI-S402T
Show LessI have a need to determine the chip id of PSoC™ 4, but I can't found it after searching the datasheet. Can anyone know.
At the same time, i want to confirm wheter the I2C address of this PSoC.
Thx!
Show LessI am trying to follow Infineon SSD1306 OLED instructions in ModusToolBox API Documentation. When I follow its directions for running the demo program it does not build. Could I please get some help on how this is to be done properly. I am very new to ModusToolBox which I must say is very hard learning curve compared to Creator. Any way I would sure appreciate some help with this to get a display running for my application with ModusToolBox.
u8g2 application instructions
Step2 Question: Its says add this this library to the application. Is this the SSD1306 OLED Controller library in Library Manager?
Step3 Question: It says add u8g2 library to the application from github. Were is it to be add into the application?
I tried to load it under libs directory but when i do it it produces well over 70+ errors.
I believe i have attached my application in a zipped file below. I am running this test on a CY8CKIT-145-04XX
Show LessThe following is an online download error. Previously a gitee connection was changed to github by changing the environment variables. The web can open GitHub.
Offline mode:
If the system displays a message indicating that the file under lcs cannot be found, the decompressed content is stored under lcs. And change the name of mtb-super-manifest-fv2.xml to: super-manifest-fv2.xml to continue.
When creating from MPN, an error is also reported:
Hope to help solve! Thank you!
Show LessDear develpers,
No signal from I2C.
4.7kΩ pull-up on I2C with drive mode set to "open drain ,drive low"
However, with this setting, no signal is emitted from I2C.
But when set to "Strong Drive" setting, I2C works.
What is the reason why it does not work with "open drain, drive low"?
Device:CYBLE-014008-00
I2C SDA: P3[4] ,pull-up 4.7k ,3.3V
I2C SCL: P3[5] ,pull-up 4.7k ,3.3V
VDD: 3.3V