PSoC™ Creator & Designer Forum Discussions

My next audio experiment is Percussion generator (include beta component)

PSoC5LP Bootloadable project for Pioneer Kit and P3[0] pin output

Kamil

 In new PSoC Creator 3.0 bit data types are highlighting as error. Project compile correct.

PSOC 4 component catalog includes the Wavedac. That should be deleted from

the PSOC 4 component catalog as it requires DMA. and a VDAC, which of course the

4 does not have.

Regards, Dana.

It would be a nice feature if either in device catalog or by detection,

when adapting another users project, the device can be readily

identified when changing device in supplied project to DVK board

the new user is going to run it on. Or a highlight/additional column, in device

catalog, signifying that device was used on DVKxx.

Right now its a magnifying glass to look at P/N or the users manual

has to be opened. Tedious.

Regards, Dana.

 I just started working on making my first PSoC component, and I am a little bit confused about something. I did a schematic of the part, but I'm not sure how to access the hardware that I put in my schematic.

For example, I included five digital output pins in my schematic. How do I access those pins in my API files? When using components in a project you generate the application, and then you can use that components autogenerated API to access the hardware, but when I try to generate an application for the schematic in my component the API files for the pins don't seem to be made?

I've read through the component author guide, but I can't find this information.

I'm sure the answer is super simple, but I just can't think of how to do it!

I am using PSoC Creator 2.2 at the moment.

Thank you!

Hello

I'm wondering if it's possible in psoc creator 3 to easilly view the occupied resources (fixed function blocks and UDB blocks).

for fixed functions I found that it's possible to see which components are used in "Analog" tab in DWR.

thx

Here is a DDS approach another poster turned me on to, very fascinating.

Think State Variable, second order, 2 integrators + sign change = oscillator. Or think

second order IIR with positive feedback.

Runs just from C code, 80 uS ( 12.5 Khz ), 40 samples/sine.

With optimization, conversion to fixed point, binary size elements, ASM vs C, or HW solution,

should yield much higher freq.

Add a timer to control code placed in ISR, eg.  sample period, or just use a delay function to control sample rate.

Regards, Dana.