PSoC™ Creator & Designer Forum Discussions

 Is there any decent document or examples around that shows how to use the UART FIFO?

I note many discussions on UARTs and there seems to be plenty of confusion.

At present, I set up the UART for single byte RX interrupt and have a circular buffer being fed by the interrupt and the mainline code dequing and parsing the received data, looking for valid packets.

It seems to me the FIFO should be able to replace my circular buffer.

There seem to be little documentation regarding inetrrupt driven UART, Use of the FIFO and what sort of error checking should be done.

Thanks

Hello everyone,

i am using the CapSense controller of PSoC.

The touching element i built can be seen in the attached file....I coated a transparent conductive layer on the substrate and then separate the layer into eight stripe elements. In the end i made a nonconductive overlayer on top of conductiving eight elements.

I programmed the PSoC, assigned the pins, then connected the pins with 8 elements using alligator clamps. When i touch certain element, the corresponding LED light should be on and the LCD also shows the touching position. But it does not work as i wanted, the Capsense controller seems not able to detect the capacitance change from the finger.

I  measured the resistance of each strip element (130-200 Ohm), is it because of the high resistive load that the capacitance change cant be sensed?

But when i remove the alligator clamps from the touching element and i touch certain clamp, the desired effects were shown.

Anyone has idea why cant the finger touch be sensored on the touching elements?

Regards

Sammi

Is there any documentation on creating custom services in psoc-ble??    

I am trying to create an interface similar to the TI SensorTag and when I create the custom service with custom characteristics in the profile then generate the application, I don't see any generated code for the custom service.  

Am I missing something???

Bill

 Hello. I'm using a board which has a Bootloader app generated using PSoC Creator 3.0 using UART. Now, using PSoC Creator 3.1 the Bootloader Host cannot program my aplications (neither new apps nor old ones). I've gotten diffent error messages from:

"Unable to read data from the target device"

to Checksum errors.

I never had problems before and now I'm even having errors with the Standalone Bootloader Host. I thought It would work fine since it is a Santdalone version, but it is not.

¿Does anyone is having similar issues?

 Hello, 

in an older version of Creator 3.1 (I'm not sure which), the  BLE Battery Level  example project (for PSoC 4 BLE)  used a watchdog timer for periodic wakeup from deeplseep. In it's BLE.c autogen code it had a function 
CyBle_WdtRegisterIsrCallback

which was used to setup the watchdog ISR.

In the comment for this function  was this note:

"Summary:

 This function registers the callback function for the WDT interrupt event.

 <b>Note</b> This API will not be available in the final release of PSoC

 Creator 3.1. Refer to the component datasheet errata section about WDT.

"

I use this example project for a project of my own, using this watchdog timer and api.

Now, the updated version of 3.1 seems to have gotten rid of this api, and my code is broken.

Can someone please point out the documentation or api's to be used in the new version of Creator 3.1 (for PSoC 4 BLE chips)  to use the watchdog timer and wdt interupts?

Thank you very muchly.

Neal

Hi,

does anybody know if it's possible to write software for the PSoC devices without using the graphical part of PSoC Creator?

Reason why I ask is that I should get our electronical trainees to the first touch with microcontrollers, and I'm thinking about to use the PSoC devices for education.

However, since the PSoC approach of graphical programming/configuration and ready-made APIs is a bit uncommon compared with other microcontrollers, I want to first teach the 'generic way', meaning that the trainees should write the drivers for timers, UART, etc first completely by themselve before allowing them to use the APIs provided by PSoC Creator or using the schematic part of Creator.

That means, there wouldn't be any schematic used in the first projects. So, each and every thing must be written manually, beginning at configuring and controlling ports, modifying the internal oscillator, timers, etc.

But, I'm not sure if this can be done, especially when thinking about the connection of e.g. timer output to a given pin, etc.

Regards,

Ralf

 After the 400th time I wrote the same project to test something simple with the ADC and put the result on the LCD, I decided to make a component to simplify things.  This component does everything you would need to do to sample the ADC and display the result on the LCD, a standard practice when learning and debugging.

I added some common features:
1.) automatic sampling, just all Easy_ADCToLCD_Start() and you are done.  (blocking forever, great when you just want to do something really simple) 
2.) built in averaging (filtering) of the samples to smooth out any noise.  the size of the average is adjustable
3.) a "transfer function" that allows you to convert the voltage into another unit, say current or ohms.  you can specify any C equation to convert the voltage from the ADC into anything else, includes units.
4.) uses 32 or 16 bit get result API so it can be used with the DelSig or the SAR
5.) Just put in the name of the ADC and the LCD and the component takes care of the rest for you.

its a simple component, but I really like how it simplifies my life.  The concept could be extened to anything really, like sending the data out to a UART ...