This is possible if you define control files for the component. I'm taking an example of SW_Tx_UART in this case.
Let's keep the UART Tx pin to P1 for the 4000S kit (CY8CKIT-145) and P4 for 4100S Plus kit (CY8CKIT-149). Once the component is imported and all modifications are done, right-click on the component and choose "Add component Item"
Scroll down and choose Control File. Uncheck the Target generic device option and choose the family and the device that is needed. Then, click Create new.
In the control file, you can specify the pin that needs to be connected to the hardware block. For example, in my case, the Tx pin needs to be connected to P1 and hence, my control file would be
-- === SW_Tx_UART ===
attribute port_location of \`$INSTANCE_NAME`:tx(0)\ : label is "PORT(1,3)";
This can be repeated to include the required devices. I've attached the project for your reference. You can read more about control files under Help -> PSoC creator help topics -> Control files.
Hope this helps.
Design01.cyprj.Archive01.zip 560.6 K
Thank you for your suggestion. I am fully aware of the Control File. However (as posted on another discussion thread) it is tied to the Family, Series and/or Device not to the implementation of the Kit or Eval board.
The components I listed in the first posting, seem to not need the Control file to auto-assign or auto-default to specific pins or port assignments.
I believe even these components the pins need to be assigned manually, by specifying them in the DWR. Just dragging and dropping the component does not automatically configure the pins. Can you please explain an example of what you are trying to achieve?
In case of USB, since the D+ and D- are fixed, these pins can be mapped only to those pins.
In any case, since most of the kits have different chips anyway, a ctl file maybe worth a try. But yes, the ctl files do not have a direct kit dependency.