There are differences in how the middleware is provided. For example, CapSense functionality is provided in
PSoC
™
Creator as a Component. For ModusToolbox software, there is a Configurator and a middleware library.
See the respective documentation for the two IDEs for details of what’s the same, and what’s different.
Whether you use PSoC
™
Creator or a third-party IDE, firmware developers who wish to work at the register level
should also use the driver source code from the PDL. The PDL includes all the device-specific header files and
startup code you need for your project. It also serves as a reference for each driver. Because the PDL is provided
as source code, you can see how it accesses the hardware at the register level.
Some devices do not support particular peripherals. The PDL is a superset of all the drivers for any supported
device. This superset design means:
•
All API elements needed to initialize, configure, and use a peripheral are available
•
The PDL is useful across various PSoC
™
6 MCU devices, regardless of available peripherals
•
The PDL includes error checking to ensure that the targeted peripheral is present on the selected device
This enables the code to maintain compatibility across some members of the PSoC
™
6 device family as long as
the peripherals are available. A device header file specifies the peripherals that are available for a device. If you
write code that attempts to use an unsupported peripheral, you will get an error at compile time. Before writing
code to use a peripheral, consult the datasheet for the particular device to confirm support for the peripheral.
PSoC
™
Creator provides Components that are based on the PDL. This retains the essence of PSoC
™
Creator in
utilizing Infineon or community-developed and pre-validated Components. However, the PDL is a source code
library that you can use with any development environment.
The PDL includes the following key software resources:
•
Header and source files for each peripheral driver
•
Header and source files for middleware libraries
•
Device-specific header, startup, and configuration files
•
Template projects for supported third-party IDEs
•
Full documentation, available in
<PDL install directory>\doc\
There are two key documents:
The PDL v3.x User Guide covers the fundamentals of working with the PDL, such as the following:
•
Creating a custom project using the PDL (including third-party IDEs)
•
Configuring a peripheral
•
Managing pins in firmware
•
Using the PDL as a learning tool for register-based programming
•
Using the PDL API Reference documentation
The PDL 3.x API Reference Manual.html. This reference has complete information on every driver in the PDL,
including overview, configuration considerations, and details on every function, macro, data structure, and
enumerated type.
2.3
Support for other IDEs
You can also develop firmware for PSoC
™
6 MCU using your favorite IDE such as
.
It is recommended that you generate resource configuration using a configuration tool. For PSoC
™
Creator,
configuration is integral to the IDE.
PSoC
™
Creator is used to set up and configure PSoC
™
6 MCU system resources and peripherals. You then export
the project to your IDE, and continue developing firmware in your IDE. If there is a change in the device
configuration, you edit the TopDesign schematic in PSoC
™
Creator and regenerate the code for the target IDE.
You can work effectively in most if not all IDEs. If your IDE is not supported in the Target IDEs panel, you can
still use PSoC
™
Creator. After you generate code, add the necessary files directly to your IDE’s project.
Getting started with PSoC
™
6 MCU on PSoC
™
Creator
2 Development ecosystem
Application Note
8
002-21774 Rev. *G
2022-07-21
