Part Datasheet Review and Validation

adrian95

Make the functional group more general.
Add a Section property to all pins, and apply the same value used in the Pin Group property to each pin's Section property.

Thought for 8 sec

flux

I’ll normalize the pin groups to broader categories and set every pin’s Section to exactly match its Pin Group.

Worked for 1 min 9 sec

flux

Updated all 48 pins to use broader functional groups and verified every pin now has a Section property matching its Pin Group.

Open items:

PF6 uses Reset; Flux accepted it, but it produced an autocomplete warning because Reset is not one of the preferred Pin Group suggestions.
GND_2 is still named that way, though its description notes it is AGND.

Suggested next steps:

Rename GND_2 to AGND.
If you want zero property warnings, change PF6 from Reset to Control or Debug.

Rename and review

Rename AGND pin

Use Control for PF6

Run review checks

Check pin groups

Files

Pins

Symbol

Layout

Preview

Part Datasheet Review: AVR128DB48-I/PT

Scope

Reviewed available part information for published part AVR128DB48-I_PT / part UID 5d9e7e79-63bd-4984-b558-1a58b0135891: MPN, package, pin count, description, properties, schematic terminals, footprint nodes, and datasheet-backed pin/spec information.

Existing Project Metadata

Manufacturer Part Number: AVR128DB48-I/PT
Manufacturer Name: Microchip
Datasheet URL: https://storage.googleapis.com/graviton-electric-symbols/document_assets/user-uploaded/452f680c70df2a026caf192394260eff17c6a5cf24acfe572292bea9cb3f5b01.pdf
Designator Prefix: IC
Part Type: Integrated Circuits
Project description: 8-bit Microcontrollers - MCU 128KB, TQFP48, 85C, 24MHz, 12b ADC, Comp, Opamp, MVIO, ZCD, DAC, UART, SPI, TWI
Schematic terminal count: 48 terminals
BOM: no BOM items, expected for a part project

Because a Datasheet URL was already present, I did not overwrite it. Web search found the official Microchip datasheet URL for reference:

https://www.microchip.com/content/dam/mchp/documents/MCU08/ProductDocuments/DataSheets/AVR128DB28-32-48-64-DataSheet-DS40002247.pdf

Key Datasheet Specs

Source: Microchip AVR128DB28/32/48/64 Data Sheet, DS40002247.

Device family: AVR DB 8-bit microcontroller family
Ordering code reviewed: AVR128DB48-I/PT
Flash / SRAM / EEPROM: 128 KB Flash, 16 KB SRAM, 512 B EEPROM
Max clock: 24 MHz
Supply: VDD 1.8 V to 5.5 V; VDDIO2 1.62 V to 5.5 V
Temperature range for -I/PT: -40 °C to +85 °C
Package: 48-pin TQFP, Microchip package code PT, tray
Package body: 7 mm x 7 mm x 1.0 mm body, 9 mm x 9 mm overall lead span
Lead pitch: 0.50 mm
Recommended land pattern: 0.30 mm pad width, 1.50 mm pad length, 8.40 mm pad-to-pad spacing, 0.20 mm gap
Analog/peripheral features: one 12-bit 130 ksps differential ADC, one 10-bit DAC, three analog comparators, up to three op amps, MVIO on Port C, ZCD inputs, UART/SPI/TWI peripherals
Power domain notes: AVDD is internally connected to VDD; same voltage must be applied to VDD and AVDD. VDDIO2 powers Port C and can differ from VDD.

Pinout Cross-Check

The schematic has 48 terminal components and the pin-number-to-name mapping matches the TQFP48 datasheet pin table, with the exception/notation issues below.

Table

Pin	Datasheet name	Schematic terminal	Result
1	PA5	PA5	Match
2	PA6	PA6	Match
3	PA7	PA7	Match
4	PB0	PB0	Match
5	PB1	PB1	Match
6	PB2	PB2	Match
7	PB3	PB3	Match
8	PB4	PB4	Match
9	PB5	PB5	Match
10	PC0	PC0	Match
11	PC1	PC1	Match
12	PC2	PC2	Match
13	PC3	PC3	Match
14	VDDIO2	VDDIO2	Match
15	GND	GND_1	Naming acceptable but should describe as GND
16	PC4	PC4	Match
17	PC5	PC5	Match
18	PC6	PC6	Match
19	PC7	PC7	Match
20	PD0	PD0	Match
21	PD1	PD1	Match
22	PD2	PD2	Match
23	PD3	PD3	Match
24	PD4	PD4	Match
25	PD5	PD5	Match
26	PD6	PD6	Match
27	PD7	PD7	Match
28	AVDD	AVDD	Match
29	AGND	GND_2	Mismatch: datasheet pin name is AGND, not generic GND
30	PE0	PE0	Match
31	PE1	PE1	Match
32	PE2	PE2	Match
33	PE3	PE3	Match
34	PF0 / XTAL32K1	PF0(XTAL32K1)	Match
35	PF1 / XTAL32K2	PF1(XTAL32K2)	Match
36	PF2	PF2	Match
37	PF3	PF3	Match
38	PF4	PF4	Match
39	PF5	PF5	Match
40	PF6 / RESET	PF6	Partial: should indicate RESET/input-only role
41	UPDI	UPDI	Match
42	VDD	VDD	Match
43	GND	GND_3	Naming acceptable but should describe as GND
44	PA0 / XTALHF1	PA0(XTALHF1)	Match
45	PA1 / XTALHF2	PA1(XTALHF2)	Match
46	PA2	PA2	Match
47	PA3	PA3	Match
48	PA4	PA4	Match

Footprint Cross-Check

Footprint node contains 48 pad nodes, matching the TQFP48 pin count.
Visible silk/body outline is 7 mm x 7 mm with a pin-1 marker, matching the datasheet package body and orientation convention.
Datasheet package is 48-lead TQFP / Microchip PT, 0.50 mm pitch, 7 mm x 7 mm body.
The available layout readout did not expose copper pad dimensions/positions in enough detail to verify exact land pattern values against the datasheet recommendation of 0.30 mm x 1.50 mm pads with 8.40 mm pad spacing. This remains an unverified footprint detail.

Mismatches / Issues to Fix

Pin 29 name mismatch: schematic uses GND_2, but datasheet pin 29 is AGND. Recommend renaming/displaying pin 29 as AGND while keeping its electrical ground type.
Pin descriptions missing: all terminals show Pin Type: Unspecified, and no detailed Pin Description values are populated. Recommend adding datasheet-derived descriptions and electrical types for GPIO, power, ground, reset, and UPDI pins.
PF6 role incomplete: pin 40 is displayed as PF6; datasheet identifies PF6/RESET and explicitly states the pin is input-only. Recommend naming/describing it as PF6(RESET) or adding a RESET role description.
Part type is broad: project property uses Integrated Circuits; datasheet/product category is specifically an 8-bit microcontroller. Recommend changing Part Type to Microcontroller if Flux property options allow it.
Footprint land pattern exact dimensions unverified: pin count/body outline appear correct, but exact pad width/length/spacing were not available from the layout inspection output.

Overall Assessment

The part metadata and pin-number mapping are largely consistent with the Microchip datasheet for AVR128DB48-I/PT. The most important correction is the pin 29 AGND label; the remaining issues are metadata quality improvements and footprint dimensional verification.

Scope
Existing Project Metadata
Key Datasheet Specs
Pinout Cross-Check
Footprint Cross-Check
Mismatches / Issues to Fix
Overall Assessment