Skip to content

Conversation

@rishabhroyy
Copy link
Member

@rishabhroyy rishabhroyy commented Nov 20, 2025

Changes

Misc

  • Hide Digikey labels in stm32-test project schematic
  • Created CAN_TRANSCEIVER Design Block

Changed decoupling capacitor layout

  • Removed duplicate 10uF capacitors, reference schematic only has 1
  • Changed the layout/wiring of the capacitors
  • Added a 600 Ω @ 100Mhz Ferrite Bead from Digikey between VDD(s) and VDDA (the reference schematic from STM had it)
  • I'm 99% sure I did it right but I'd really appreciate it if you could double check it

Questions

  • I couldn't find a button that's exactly the same as ours, but I did find a similar one with J-leads that is 6mm by 6mm. Should I change it out?
  • "The unused clock source should be disabled and the unused I/Os should not be left floating. The unused I/O pins should be configured as analog input by software; they should also be connected to a fixed logic level 0 or 1 by an external or internal pull-up or pull-down or configured as output mode using software."
    • Should I do something about this? Like ground every unused pin?
  • "Might be worth including a solder bridge pad for a 0-ohm resister that ties it to ground in case we ever want to change that, but honestly I can't see us needing to."
    • It has a resistor to ground, so I'm guessing you mean solder pads for a resistor to +3V3, and I decided to not add it, because after reading the STM pdf I see why you said we'd probably never use it, so it'd probably be unnecessary, but if you actually want me to add it lmk.

@rishabhroyy rishabhroyy requested a review from bvngee November 20, 2025 09:39
@rishabhroyy rishabhroyy self-assigned this Nov 20, 2025
@rishabhroyy rishabhroyy changed the title STM32G4 MCU Design Blocks STM32G4 and F4 MCU Design Blocks Dec 1, 2025
Copy link
Member

@fezboy fezboy left a 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

Copy link
Member

@fezboy fezboy left a 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

image
  • This should probably be a straight horizontal line, for simplicity and so that it doesn't block PB1.
image

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part number doesn't match here
image

Copy link
Collaborator

@bvngee bvngee left a 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants