Pin Function Grouping
Thought for 37 sec
Yes — and I should group them so each pin appears only once, under its most appropriate shared function, not repeated across multiple groups. That matches the pin-grouping guidance for IC-style parts: use common functional groups like Power, Ground, GPIO, Communication, Clock, Control, etc., and derive groups from shared naming/function rather than duplicating pins across categories.
For example, the structure would look like:
Table
| Group | Pins |
|---|---|
| Power | 3V3, VDD, VBAT, etc. |
| Ground | GND_1, GND_2, EPAD, etc. |
| GPIO | IO0, IO1, IO2, etc. |
| Communication | TX, RX, USB_D+, USB_D-, SPI_xxx, I2C_xxx |
| Clock | XTAL_IN, XTAL_OUT, 32K_XP, 32K_XN |
| Control | EN, RESET, BOOT, CHIP_PU |
| No Connect | NC pins only |
The important rule is: don’t add the same pin twice. If a pin has multiple alternate functions, it should still be placed in the one primary functional group you want to represent in the symbol. The sync guidance is explicit that every pin should be assigned once, and that pin grouping should be based on the shared logical prefix/function.
However, I can’t safely list the exact grouped pins yet from the datasheet because the searchable results available to me right now did not surface the actual pin table, and the rules explicitly say to never guess pin numbers/names and to use the datasheet as the single source of truth.
If you want, send me the pin table page or upload the datasheet PDF directly, and I’ll turn it into a clean, de-duplicated grouping immediately in this format:
Table
| Group | Pins |
|---|---|
| Power | ... |
| Ground | ... |
| GPIO | ... |
| Communication | ... |
| Clock | ... |
| Control | ... |
| No Connect | ... |
If you paste the pin table, I’ll do the grouping with no duplicate pins.
Group by function
Make groups concise
Add pin table
Welcome 👋
Flux accelerates your PCB design with AI.
Create your account to start using this component and bring your ideas to life.