Almost all copmponents have API calls to registers to configure
the component. But in general one stays with the graphic
configuration due to ease, interrelationship of parameters, etc.
...and additionally the configuration for pins are done (semi) graphical, too. This eases the switching to a different configuration, there is (mostly) no need for changing pin configurations programmatically.
...and: Welcome in the fascinating world of PSoCs!
These might help -
http://www.cypress.com/?docID=48512 AN74170 PSoC® 1 Analog Structure and Configuration With PSoC Designer™
http://www.cypress.com/?rID=2901 AN2104 - PSoC® 1 - Dynamic Reconfiguration With PSoC® Designer™
And this is doc/video area for ap notes, training videos, forums...... -
One other thought, when you do register programming there is
a TRM (Technical Reference Manual) and another manual for
Registers. Because PSOC has much more programmability than
"normal" processors there is a burden to pay particular attention
to notes and foot notes associated with registers. Often the users,
myself included, do not read the fine print. The notes cover intera-
ctions with the HW and other registers and can give you unexpected
results if you do not read them.
The more control you get the greater burden to manage it well.
I find the graphic configuration tools is easy to use. However, some times you need to understand the internal register to make changes on the fly while running the code.
Thanks for the advice I will stick with the Graphical interface. And thanks for the links. I am sure I will be back with more questions once I get the CY3210 Kit.