Welcome in the forum, nameless ;-)
The component you are referring to is a pure software solution, it does not use any clock but the execution clock for the CPU. So there is no way to change the clock frequency.
When you tell us a bit more what you would like to perform (except from understanding how it works) we could probably help you.
Let us know which Cypress Kit exactly you use.
I'm using a CYBL10462-56LQXI to just mainly send some CapSense data to the PC ( I know there is the tuner for that, but it's just to play around and for me to see what happens at what time). Everything works fine.
It's really just about understanding, what I'm supposed to be calculating for the error, because I will eventually have to write a short report about what I am doing for my school.
On a side note: should I even be using the Software UART? It seemed very easy and does just what I need, plus the datasheet isn't 200 pages long. But since it uses "software delays, implemented with CyDelay function" does it slow down the execution a considerable amount? I find it hard to judge how big a difference these delays will make.
The software UART will disable interrupts during transmission of a byte to maintain timing. At 9600 Baud this will take more than 1ms.
Yes, I admit that the datasheet for SCB UART has got more than 200 pages, but it is describing several different interfaces, so the UART is quite less than 200 pages.
First of, thank you for your answers so far.
So using 115200 bps that's around 0.1ms?
But for the Non-Software UART I would only block the CPU while writing the data into the buffer register,so I should use that one, especially since I'm polling the CapSense - Sensors all the time and want to evaluate what's happening when?
And one last question, just to be clear: is the UART the right way to go for very minimal, one way communication or should I also look into the other interfaces.
The 200 is just a bit intimidating if you're swimming in documents you just don't completely understand. I'm actually quite glad everything is so well documented.
is the UART the right way to go for very minimal, one way communication
The UART is one of the simplest interfaces.