Pin swapping can simplify routing, but a shorter connection is useful only when the new assignment preserves the product’s function. Review the permission to swap separately from the tool operation that performs it. Then make every dependent design record agree with the final assignment.
Altium’s pin, pair, and part swapping documentation describes configurable swap information and reassignment of connected nets. The software can apply an allowed transformation, but the design team must establish that the configured permission reflects the device and circuit requirements.
Qualify the proposed swap group
Compare the device’s actual pin functions and restrictions. Pins that share a broad label such as GPIO may differ in startup behavior, peripheral assignment, voltage domain, or other constraints. Treat the datasheet and system configuration as the authority for the specific device.
For multi-unit devices, check the complete unit, including power connections and any asymmetric behavior relevant to the design. Do not infer interchangeability from identical-looking schematic graphics. Preserve the reasoning behind permitted swaps in the library or project documentation.
Review the resulting assignment
| Domain | Question |
|---|---|
| Schematic | Do the final numbered pins carry the intended nets? |
| PCB | Does actual copper follow the accepted assignment? |
| Firmware or programmable logic | Does the configured physical pin mapping agree? |
| Test documentation | Do probes and diagnostic names identify the correct signals? |
Record before-and-after pin mappings for the swapped group. A visual comparison of routing alone can miss a changed association at the package. Include neighboring pins that must remain unchanged as a useful control when reviewing the result. For a differential pair, also verify the intended polarity and any receiver configuration that permits or forbids a polarity change.
Close the synchronization loop
- Confirm the swap is permitted for this design.
- Apply the routing transformation in a controlled revision.
- Back-annotate using the supported tool workflow.
- Review the resulting schematic and netlist changes.
- Update dependent configuration and regenerate outputs.
Investigate any unexpected change outside the intended group. Do not accept a large synchronization operation solely because the desired swap appears among its entries. Check whether the tool is also proposing unrelated component, net, or rule changes.
Finish with validation of the synchronized design and an explicit assignment record. If software mapping has not yet been updated, keep that remaining dependency visible instead of treating the hardware edit as complete. The release should contain one coherent physical pin assignment that can be followed from the circuit diagram through assembly and product test.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist