PSoC™ 5, 3 & 1 Forum Discussions

When using the SPI slave tx software buffer in the API, how do I get an interrupt when a transfer is complete?

I.e. not when the software buffer has been transferred into the FIFO, but when the last byte of the transfer placed in the soft buffer has started to come out of the TX pin.

WP 20180509 17 00 51 Pro - YouTube

Hi to all,

after reading forum and examples and after a couple of problems regarding USB drivers, now I am able to use USBUART (CDC) interface with PSoC5LP!

It remains only a problem: manage the connection/disconnection of the USB cable.

I read KBA210620:

http://origin-www.cypress.com/knowledge-base-article/troubleshooting-psoc-3-psoc-4-l-series-and-psoc-5lp-usb-designs-kba210620

This document suggest to monitor the VBUS line to detect the disconnection event.

But, in my current design, I cannot monitor the VBUS line (SELF POWERED - NO VBUS).

I did a bit of experiments but I was not lucky.

There is someone that knows a solution to detect USB disconnection (USBUART - CDC) without monitoring the VBUS line?

Thank you in advance to all 😉

PS: UBUART component datasheet v.3.20 does not define USBUART_GetConfiguration() API

I am making an project where I would implement a start button.

My plan was to initialize everything and the enter a while loop waiting until the button was press with code like this:

bool START=false;

main()

{

Init all

while(!START)

{ }

Program

}

And then having a interrupt changing START=true; 

The problem is I can see the interrupt routine is called, but the program doesn't leave the while loop.
I have tried to turn on a LED in the interrupt routine and the read the output pin afterward but that doesn't work either.

I have isolated the problem to this archive, where i have placed an LED in port 1[7] to GND and uses Port 15[5] as button by pulling it low.

pressing the button should turn on the LED.

Any working solution for a button will be appriciated, but a fix or reason to the problem would be nice too

Hello!

I have an application that is taking timing info from a UART and updating the frequency and duty cycle using a PWM block.  I want to be able to MUX a signal to output pins.  Ideally, I'd like to scale it so that I can vary the number of channels I'm MUXing it to (either in software or hardware) so I could have a desired number of outputs (ie 3, 7, 13, etc rather than just 2, 4, 8, or 16) but this is less important.

I was wondering what the best approach would be?  I thought about using the interrupt on the PWM to create a signal that toggles everytime the PWM toggles (using the interrupt on terminal counter, I think it was) and use that as a clock for a counter (though the counters are only 4 bit, so if I wanted to use a desired number of outputs, such as 7, I assume I'd have to have some sort of software comparison to the MUX signals to reset the counter if the count is over 7 or something to that effect?

The other possibility, I guess, is to create my own UDB block that's custom for my application but I'm not sure if I'd be able to vary the number of outputs at that point.

Anyway, if anyone has any suggestions as to the best way to approach this application (or a way, or feedback on my previous thought process), I'd appreciate it.  Thanks!