PSoC™ 4 Forum Discussions
Is it possible to set the input logic levels of the I2C pins to LVTTL?
Target module is CYBLE-012011-00 and I2C is set to master.
Thank you.
Show LessHi all,
let me announce that PSoC4 family is now supported in OpenOCD.
OpenOCD is a multiplatform on-chip debugger. It can be used as a gdb server with gdb-derived debuggers. OpenOCD can drive most of standard JTAG/SWD adapters, like J-Link... For more info see http://openocd.sourceforge.net/
PSoC4 support includes SWD debugging (almost standard Cortex-M0) and a driver for flash programming. This features were integrated very recently so PSoC4 support is available only in a git version for the moment. I'll let you know when a suitable Windows and Linux binary will be released.
OpenOCD can help in following scenarios:
-
PSoC4 debugging with Linux PC or an embedded Linux powered system
-
PSoC4 debugging over local or wireless network
-
PSoC4 debugging using a standard or special SWD adapter
To Cypress: I hope you do not consider this announcement as spoiling your business with MiniProgs and PioneerKits. I'm sure that an open-source alternative can boost wider spreading of your innovative chips in students communities.
If Cypress wishes to support our open source project please let me know.
Tomas
Show Lessi am using a demo board of CY8CKIT-043 with very low resources (32 macro-cell)
could you write a short code the do the folowing:
input= digital INPUT, random behaviouer of 0 or 1
output, digital= error1, error2
Period= every 50mS
clock=1MHz (or equvivalent)
( a 50mSec period has 50,000 pulses of 1MHz clk)
for each period
start with count=0
for each clk:
if INPUT=1, count=count+1
if INPUT=0, count=count (no change)
at period end:
if count is <30% , then error1="1" [30% of 50,000]
if count is >36% , then error2="1" [36% of 50,000]
else error1=error2="0"
repeat period endlessly
thank you!!!!
Itzhak Gavyus
I was working my way through AN-73503, USB HID Bootloader earlier today. I followed their instructions to delete the default Device Descriptor root. I then imported the Descriptor Root Bootloader.root.xml. I continued on in the tutorial, but when I went to compile I had some errors. I had been messing around with other stuff so I decided to delete the USBFS from the schematic and start again in a new project.
Now I am all of a sudden unable to call up a USBFS component. I look in the CyComponentLibrary and it appears to all be there. I have run an update, a repair and have even uninstalled PSoC Creator and reinstalled it. But, the same thing: no USBFS. I have renamed my Cypress folder, installed PSoC creator again and tried to load a USBFS component, but no dice.
I have noticed that the application seems to know which projects I have worked on recently when I load the newly installed software. Maybe this is a hint? I don't know.
I am unsure where to go from here. Any help would be much appreciated.
Thanks!
Show LessIt is hard to ignore that there is a consistent grouping of the PSoC 3 and PSoC 5 architectures. I do not recall ever seeing a document title with 3/4, 4/5 or 3/4/5 referenced together. I see that also in references to applicability to solutions. Are 3/5 more suited to analog? What does separate PSoC 4 ? I would like to understand it.
What about PSoC 6. What bucket does it fall in ? A new bucket ?
I will appreciate if someone can enlighten me
Tony
Show LessI'm starting a new project which I think the Analog Coprocessor Kit would be a good kit to use for the initial testing. I'm looking at replacing the detector (datasheet attached) with some standard photodiodes and a PSoC.
I have 2 photodiodes, http://www.excelitas.com/downloads/DTS_vtb1112b13b.pdf and https://media.digikey.com/pdf/Data%20Sheets/Excelitas%20PDFs/VTP9812FH.pdf
I plan on connecting the photodiode to a TIA and following that with an ADC. I haven't worked with one of these sensitive circuits since the dawn of ages so I was hoping to get some helpful kick starting tips to proceed.
Thanks,
George
Show LessHello; I try to follow or reproduce the video: How to Create a PSoC Android BLE App.
I include the CapSense CSD Module, the BLE Module, and the digital outputs. After DesignBuilding I get the following error:
"prj.M0120: Build error: 'CapSense_LinearSlider0__LS' undeclared (first use in this function).
I checked the CapSens_CSHL.h the function is existing and also the CapSens_CSHL.h is include via the project.h in the main.c file.
I assume it will be a short problem with definition; thanks in advance- Norman
Show LessHey Guys and Gals,
Whenever I send a firmware update the file is sent successfully but the firmware is identical to the previous iteration. In short the changes I've made to the firmware aren't shown even after the OTA firmware update. Is there anything else I have to do??
Thanks In Advance!
Show LessHello All,
I am experiencing a long attributes discovery times when using long connection interval set.
What I am trying to achieve is to minimize power consumption by extending the connection interval, but this is also causing the connection process to take a long time (4 s) which I believe is caused by all the characteristics being transmitted using low connection interval (I might be wrong)
Any ideas how to make the connection process quick but the connection intervals long?
I tried to start with short intervals and then increase them using CyBle_GapcConnectionParamUpdateRequest() but it does not seem to work. Is it the right way?
Regards,
Piotr
Show LessHi. I am currently working on a high-voltage motor driver based on the motor evaluation kit CY8CKIT-037. Specifically, the bus voltage is 310V while the power output should be around 200W. I used the Pioneer kit CY8CKIT-042 as the control board, using the same pin assignments on the Arduino headers. I have implemented the Sensored BLDC on the modified driver board and now I am working on the Sensorless FOC. What changes on the firmware should I consider? I have read the Sensorless FOC application note and it seems that motor and hardware parameters are the only variables I can modify to reflect the high-voltage configuration of my driver board. Thanks for any help and/or advice
Show Less