Sorry for the confusion brought to you. The APIs you listed - ADC_Start() / UART_Start() are the upper level API generated for a concrete component. PDL APIs(name begun with "Cy_" ) are called inside.
Actually, the users can only call PDL APIs to fulfill the requested function. We have some code examples demonstrating that a same function constructed by either pure PDL APIs or component APIs.
1 of 1 people found this helpful
Thank you for your response.
PSOC6 is a great product but I have some comments.
1.The data sheets with component APIs explain their function significantly better than the PDL documentation.
2.The PDL documentation is very vague and difficult to decipher.
3.What good are the component names if the APIs don't use them anymore (PDL 3.1). Isn't that what the GUI is for? To set the component parameters and set the code accordingly. For instance in previous versions the GPIO PIN names were relevant, but now you need to reference the actual pin numbers. Seems like a giant step backwards.
The PSOC products are really cool. One of the reasons I chose them was for the simplicity of the development platform and the power of PSOC of course. I understand you need to help out users with more complex needs please don't thrown out one for the other.
As far as I can tell, Cypress has decided to make the PSoC 6 harder to use with PSoC Creator than previous members of the PSoC family in order to push people over to ModusToolbox.
There indeed are some differences between the use of PSoC 6 and previous PSoC generations in PSoC Creator, as you said.
PDL is introduced here just for the universality to develop P6 on different platforms, not just PSoC Creator. It's easier to be transplanted. If you are accustomed to use the P4, you can still use the set of APIs generated with the component name on P6. They are still there