PSoC™ 5, 3 & 1 Forum Discussions

Is there a way to code the PSoC to have another reset button? I'd like to have an external switch that can reset the program just like SW1 can. Something like this.

[D6R40 F1 LFS C&K Components | 401-1975-ND DigiKey Electronics]  

Hello 
For my current project i need 36x phase PWM  output Up to ~100khz  each , with phase shift , and dead time  control .
Whether implementation of this project is possible using Psock5 , with use of any existing components. ?

Hello,

Recently, I post similar topic but I think I am facing with another problem. I want to take data from accelerometer sensor(mcu9255). I look at the EP56273 example. In this example, when button is switched SPI transmission occurs. I did it in MCU9255. However, in my project, I want to do it continuous cycle with DMA.  But I am facing with some problems. When I did it continuously, my spi rx interrupt work only one time. 
Do you have any experience like that ? 

I just think that it can be do with DMA but I don't know what's the point ! 

Thank you
Burak

Hi everyone

I need some help with the following code.

This code is based on RC5 protocol for Irda communication.
I just take from it the bit time, half bit time and the 36 khz modulation frequency.
The idea is implement a 64 bit infrared link. The two first high byte send to the receiver start with 0xFFFF at MSB and MSB-1.
The emitter is implemented with a regular infrared emitter diode and the receiver with
TSOP38436.
To synchronize I wait for the first high to low transition at Demod_input which is the first clock transition of Manchester encoding.
After a Delay of 0.445 ms I can say that the reading at Demod_Input is "1".
After successive sampling of Demod_Input at intervals of 1.778 ms I would say that I am recovering each bit of payload received.

I can get the code running and I suspect about left shift 64 bits data.

The the scopes' screenshot show the TSOP38436 yellow trace and the inverted output as blue trace.

Thank you in advance for any help.

Hi, I have very little experience using PSoc 5 (have to use it for a Uni project). I'd like to use the optical sensor on a  mouse to get relative X Y positional data. The mouse  is a Dell (P/N 4k93w). From checking the pin outputs I think it has an ADNS9500 optical sensor, and it also has a Cypress CY763823-SXC encore II peripherial controller. My question is what is the best way to get the data?

Do you use an SPI Master to connect to the ADNS9500 directly and have the ADNS9500 as a slave, or do you connect to the controller , again as master? I'm not that familiar with SPI, would it be better to find a mouse that supports PS/2 (again equally unfamiliar with Ps/2  but just looking for the easiest way to get the data).

Any and all help appreciated. Thanks.

I've been looking into trying to use the PSOC 5LP in an application requiring a customized serial protocol and wonder what the best way to go about it might be.   The basic idea is that I have several sensors that use SPI to communicate.  The PSOC would need to be able to grab data from these sensors, pack it into a "frame",  prepend a synchronization word, add a few other housekeeping words, and then push it out as a set of serial bits at a rate of roughly 5Mb/s.   Does this sound feasible using say the CY8C5888LTI-LP097?   If so, what would be the most likely path to success?  I've been playing with the shift register block, but have been struggling to get it working correctly. 

It seems there are two hurdles to overcome with this:  1) Grabbing the data from each of the separate SPI ports and packing the data into (maybe a ping pong or circular?) buffer.    2) Generating a structure with low enough latency to push out 5Mb/s consistently from one frame to the next.

As a follow up question, I was curious about how many separate SPI ports could be instantiated before the PSOC started complaining .... turns out the number for this device is apparently 8.  If anyone has any insight into talking to more than 3 or 4 SPI slave devices at once, I'd be interested to learn about it.