New RP2354A circuit check!
Hi everyone! I'm designing my PCB around the RP2354A and would really appreciate a general schematic review before I start laying out the board. Right now this is just the core/skeleton of the design, so I know many of the GPIOs are not connected yet. I'll be adding the sensors, connectors, and the rest of the circuitry after I know the foundation is correct. I'm mainly looking for someone to verify that the power circuitry, decoupling capacitors, internal switching regulator components, 12 MHz crystal/oscillator circuit, USB Type-C connector, USB D+/D- routing/components, and boot/programming circuitry all look correct. Will this board be programmable over USB as shown, or is there anything missing or wired incorrectly? I'm also wondering if there are any RP2354A hardware design recommendations I've overlooked, or if there are any small changes you'd recommend before I move on to the rest of the schematic. #Schematic#
PCB DESIGN CHECK.
Hey guys, I'm spinning a new flight computer board and wanted a quick sanity check on the layout before moving forward. I'm trying to keep the design super simple for now: the USB-C connector will power the whole board, and I want to be able to program the chip directly through the Arduino IDE. There are no outputs or extra components hooked up yet, so I just want to make sure my power and data lines look right to you guys before I start adding anything else—let me know if you see any red flags in the setup! #Schematic#
First flight computer Design! Would love a quick schematic review!
#Schematic#
First big PCB Design! Would love a quick schematic review
Hey everyone, I’ve been working on a small custom ESP32-S3 board (ESP32-S3-MINI-1-N8) and I’d really appreciate a second set of eyes on it before I send it out for fabrication. It’s a compact, battery-powered design using a single-cell 3.7V LiPo. Charging is handled with a TP4057, and I’m regulating down to 3.3V with an LDO (recently switched to a TLV75533P for better dropout and stability). The board also supports USB-C for power + programming, and I’m planning to use the ESP32-S3’s native USB (no external USB-UART bridge). A couple things I’m specifically wondering about: Will the USB setup reliably support flashing and serial (given no dedicated auto-reset circuit)? Power stability — does this setup look solid for WiFi current spikes, or am I cutting it close? Battery/charging side — does the charge rate and general implementation look safe/reasonable? RF/antenna layout — I’ve tried to follow keepout rules, but would love feedback here General layout/grounding — anything that stands out as a potential issue? I’ve attached both the schematic and PCB layout. This is only my second or third serious board, so I’m trying to catch any mistakes before ordering. Any feedback, even small stuff, would be super helpful. Thanks! #Schematic#
First big PCB Design! Would love a quick schematic review
The overall project goal is a one-time, self-latching controller called “VORTEX Powered by AVS.” I want the board to power up in a guaranteed safe OFF state with the output completely disconnected (no current can flow even if there is noise, floating pins, or a momentary power glitch). After power is stable, a single short trigger pulse (button or signal on J1 lasting ~0.25 seconds) must instantly latch the system ON forever with no way to turn it off except by removing power. The latched ON state must drive both a red status LED and turn on the low-side MOSFET switch so the external circuit on the output connector (labeled OUT) fires and stays powered continuously until the battery is disconnected. I specifically want the TLV809EA29 voltage supervisor to hold the flip-flop’s CLR# low for its full delay at power-up so the Q output stays low (OUT = 0 V). Then, when the 2N3904 pulls PRE# low, the flip-flop must set Q high and latch it permanently even after the transistor turns off. The latched high Q must light the red LED and drive the IRLML6244 gate high so the MOSFET pulls the OUTPUT “–” pin to ground while the “+” pin is tied directly to VCC, completing the circuit. I also want the green power LED to show the board is alive from the moment VCC is applied, and I want clean decoupling, proper trace widths on the output path, and a 2-pin header that supplies switched ground on pin 2 with VCC on pin 1. Does the submitted schematic and PCB layout achieve exactly this behavior? Please confirm that every part matches what I described or if anything is missing or wrong. #Schematic#
Need help to check my schmatic.
Hello! I was wondering if someone could look over my PCB design before I hit purchase, just to check for any beginner mistakes. The goal of this project is to have a .5V signal sent to the timer pins, which will then trigger the output pins to ignite an e-match. The circuit is powered by a 3.7V LiPo battery. I want to ensure the trace widths can handle the current and that my switching components are compatible and are wired correctly. #Schematic#
Need help with my 555 timer circuit!
Hello everyone. I’m working on a 555-based bistable multivibrator using a single-button latching configuration. While the circuit functions correctly once powered, I’m encountering an inconsistent initial state—the LED may start either HIGH or LOW upon power-up. I’ve experimented with various RC combinations to create a Power-On Reset (POR) for the Trigger and Threshold pins, but haven't achieved a reliable result. Does anyone have a proven schematic or tip for ensuring a consistent 'off' state at startup? #Schematic#
First PCB Design! 2N3904 Transistor Multivibrator — Would love a quick schematic review
Hey all! I'm officially diving into PCB design and just completed my first project. Would anyone be willing to take a look at my schematic and layout? I’m mostly looking to see if it’s functional and if there are any beginner mistakes I should fix. Thanks for your help! #Schematic#