Yes — for Apollo510B, the best Flux-ready approach is to split the symbol by function, with every pin assigned to exactly one sub-symbol, keeping each block readable and putting all supply/ground pins into a dedicated Power block

That structure follows the recommended IC grouping rules for Flux part projects: dedicated Power, banked GPIO groups, and separate functional blocks for communication, analog, clock, control, and debug

Put all supply and return pins here, including exposed pad / thermal pad if listed. Power and ground should not be scattered across other blocks

Typical names to place here:

If the datasheet uses banked naming such as GPIO0, GPIO1, or P0.x, group by the shared prefix. Flux guidance is to derive Pin Group from the common name prefix and use separate sub-symbols for large GPIO banks

Use:

Combine peripheral I/O that is not plain GPIO:

This matches Flux’s recommended Communication section for serial and bus interfaces

Use for:

Use for:

Use for singleton system-management pins:

Singleton control pins should usually use their own Pin Group, such as RESET or BOOT, even if they live inside the Control sub-symbol

Use for:

If the datasheet explicitly marks any pins as NC, DNC, or reserved no-connects, place them in a dedicated NC sub-symbol or fold them into the least cluttered block if there are only one or two. Flux guidance allows a dedicated no-connect classification and says these must still be represented exactly if listed in the package pin table

For each pin on Apollo510B, I’d use these Flux properties:

Those orientation and section rules are directly aligned with the Flux part sync guidance

For Apollo510B, I would start with this exact sub-symbol set:

If the datasheet shows more than two GPIO banks, extend to GPIOC and GPIOD. If communication pins are numerous, split further into Serial and USB_Audio, but only if needed to keep each block readable. Flux recommends roughly 5-15 pins per sub-symbol where possible

I’ve given you the Flux-ready grouping scheme, but not the final per-pin assignment yet. To do the exact Apollo510B mapping correctly, every pin must be extracted from the attached datasheet by category and assigned from the actual pin table; Flux’s guidance is explicit that pin numbers and assignments must never be guessed

If you want, next I can turn this into a pin-by-pin Apollo510B table with:

using the attached datasheet as the source of truth.

I can do the pin extraction and grouping work, but I can’t apply it in this current project because it’s a published part project owned by florencia755424 and I don’t have edit access here.

Your options:

If you want, I can next produce the pin-by-pin Apollo510B sub-symbol assignment table so it’s ready to apply in your editable copy.