-
Notifications
You must be signed in to change notification settings - Fork 3
STM32G4 and F4 MCU Design Blocks #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Hide purple MFG labels in STM32-test
barebones templates for design blocks
6c247fa to
2865394
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functional:
- What aspect does the wildcard at the end of each MCU part number affect? should we specify it?
Ordering:
- Bead, Crystal, Debug Header, and reset button need specific part numbers in the Value field
- Add a Digikey Link field to each part. (Digi URL)
Aesthetic
- Boot pulldowns should be wired directly
Aesthetic nits
- Nets that jump across the page should be labeled with flags (it's ~ fine ~ here but I want to keep my notes consistent.
- VSS pins can (should) share ground labels
- Wires shouldn't come out of pins at an angle, have a bit of wire coming out before you turn (VCC pins, crystal) The main thing with this for me is the green dot overlapping with text
...la_slug_design_blocks_library.kicad_blocks/STM32G441KBTx.kicad_block/STM32G441KBTx.kicad_sch
Show resolved
Hide resolved
...la_slug_design_blocks_library.kicad_blocks/STM32G473RCTx.kicad_block/STM32G473RCTx.kicad_sch
Show resolved
Hide resolved
fezboy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aesthetic:
- Crystal Frequency should be indicated on schematic, a text note next to it would be good (Sorry I should've specified this on my previous notes)
- Global labels should indicate direction, for example,
UART_TXshould be an output at the microcontroller and an input at the debug header.
Aesthetic Nits
- It would be a good idea to set pin functions for the pins you're using, especially as it can serve as a hint to users of the design block to do the same. (https://docs.kicad.org/9.0/en/eeschema/eeschema.html#alternate_pin_functions)
- You have room to give these caps more space, I think it could make the text easier to read
- This should probably be a straight horizontal line, for simplicity and so that it doesn't block PB1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bvngee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One tiny thing, could you rename UART_TX/RX to VCP_UART_TX/RX, to differentiate in case someone uses another UART?

Changes
Misc
Changed decoupling capacitor layout
Questions