Adding Resistance Values ​​to CC Resistors

In this additional step I added the resistor values ​​for the two resistors going to GND from the USBC connector.

The entire project has been completed. It was supposed to be a blast, but it turned out to be very difficult and demanding.

Final PCB Fix

I managed to fix most of the errors.

The remaining issues, such as violations of hole clearance and similar minor problems, honestly don’t interest me—just like vias. I’m not creating a microcontroller for an F-35, but for a drone, so these details don’t matter to me.

Overall, I didn’t follow the tutorial step by step; I started creating this project before the tutorial was released.

I was advised not to include a donation section if I don’t need money.

I consider the project finished.

Improvements v2

Key Changes

• Impedance Matching: Adjusted the distance of critical cables, such as DP and DN, to achieve similar impedance and minimize interference.
• Via Reduction: Removed vias wherever possible. While complete elimination wasn't feasible, the number has been significantly reduced.
• Visual Improvements: Enhanced the overall appearance for better readability and aesthetics.

These changes aim to improve performance while maintaining a clean and professional PCB layout.

I think that's all it will take to fix anything, and it will work for me. I don't need a huge demand.

Fixed PCB

I repaired the PCB and reduced the number of layers from 4 to 2.

It was hell, but I managed to get everything done.

Additional Notes

• I had to re-route a significant portion of the board to fit everything onto two layers.
  
• Some traces required complete redesign due to space constraints.
  
• Despite the challenges, the final layout is cleaner and easier to manufacture.
  
• The experience gave me a much better understanding of layer optimization and signal routing.

Overall, it was a tough but valuable learning process.

Troubleshooting and Fixes

During troubleshooting, I found a few issues, mainly related to incorrect routing, although I also discovered one mistake in the schematic. Fortunately, I managed to fix it.

This is unfortunately the last post, as there’s nothing more to do here—just an update for reviewers - I was also instructed not to include a parts basket image if I don’t need a grant.

I ignored these aesthetic flaws. I only care about performance.

PCB Routing and Component Placement

In this almost final stage, I routed and placed all footprints on the PCB to ensure everything works.

It was quite challenging because I usually rely on autoroute, but in this case, since I didn’t want to risk mistakes, I did everything manually—and I have to say, I’m really proud of myself.

Now there’s just one step left: checking for errors and ordering the PCB.

this is how it looks like :o

Schematic Creation

I created the full schematic. As I prefer not to waste time, I built a complete design, including understanding components such as the gyroscope and accelerometer, the pins on the microcontroller (e.g., ATmega), and how the new project structure will function.

Being a student in Automation Technology, PCB design and electronics are no problem for me (we even worked with complex numbers in the 2nd year, btw).

The schematic took me just a few hours to complete, but since I have limited time, I need to lock in the progress.

I focused on practical work and efficiency: the schematic is fully functional and ready for the next steps.

(For people who think it's fast and are beginners, it really doesn't work that way. I spent countless hours practicing other boards that were easier. Do the same and you'll master it.)

Understanding How the Flight Controller Works

At this stage, I focused on understanding the minimal set of components a flight controller needs to work:

As I prefer getting straight to the point, I didn’t focus much on unnecessary components and immediately started researching and creating the PCB and schematic.

I also apologize to the people who will be checking my work, but there is not much to say here... J*B!