Datasheet

72 PSoC Designer IDE Guide, Document # 001-42655 Rev *B
System-Level Editor
lighted in green. The green highlighting indicates that those pins will accept the driver you assigned.
Drop the blue rectangle on any one of these pins.
When you finish assigning pins, click Next for the last step in the build process.
3.9.1 Pin Color Legend
When you select and drag a driver, all pins are outlined in one of three colors: green, orange, or
black.
 Green indicates the pin is a legal placement and unblocked.
 Orange indicates the pin is a legal placement but another driver placement blocks it.
 Black indicates the pin is not a legal placement.
Note A legal and blocked placement may be blocked by another driver’s selected internal resources.
If it continues to be difficult, start over and place the difficult drivers first.
3.9.2 Lock Pins
Locking the pins prevents PSoC Designer from changing the pin assignments on this design. This is
useful when your design has been finalized with all of the drivers that you will use in the final design
and your only changes are likely to be parameter changes.
3.9.3 Unassign All Pins
Returns all drivers to the unassigned state.
3.9.4 Auto Assign
This window provides a button to automatically assign any currently unassigned drivers to available
pins. Whenever there is a problem with a complex pin assignment, drag all drivers off of their pins
and select Auto Assign to see how pins are assigned without conflict.
3.10 Generating Output
During the build process, PSoC Designer performs the application generation, translating the graph-
ical and textual design information into PSoC hardware specific configuration and firmware, running
PSoC Designer transparently to perform the low-level code generation, and then compiling and link-
ing this information into a PSoC programming file (hex file).