DIY Process for Hardware Circuit Boards: “First This, Then That, Finally…”

“The Process of Single Board DIY”

1. Concept Stage

When starting with hardware DIY, it is advisable to find some interesting mature cases to imitate. During the replication process, strive to understand the circuit principles involved and establish a block diagram for the project from both hardware and software perspectives. Once the basic functionality is achieved, consider switching to your own design or adding some new ideas. If you attempt to design a project from scratch as a beginner, you may encounter significant challenges.

If the project you want to undertake is relatively complex, you can initially use ready-made modules to complete the hardware setup while simultaneously programming the software, and later replace each module with your own design.

2. Schematic Design

Process: Package Preparation > Schematic Drawing > Schematic Compilation > Netlist Import

In circuit board design, there is no need to get hung up on which software to use; these are just tools. The same schematic designed by different people will result in different PCBs.

Initially, you may not be able to design schematics, and that’s okay; just copy them. While copying, clarify the circuit composition and signal flow of each part, and as you accumulate experience, you will be able to design schematics on your own. Additionally, many functional chips provide design guidelines in their manuals.

A complete single board hardware circuit can typically be divided into three parts: power supply, minimum system, and peripheral functional circuits. Having this division in mind will help with the layout and routing of the PCB later on.

3. PCB Design

Process: Rule Setting > Layout > Routing > Rule Check > Export Production Files

At first, it may seem like there are many things to pay attention to, especially since you are not yet familiar with the software and need to consider some established rules. This feeling is normal; as you handle more projects, these will gradually become habitual.

PCB layout and routing can be done according to the direction of the signals, modularizing the layout according to the three parts mentioned earlier, and then adjusting positions within the board frame.

The design of a PCB is essentially a process of finding the optimal balance; it is difficult to achieve a perfect score, as the design process often involves various compromises among different criteria.

4. Board Debugging

Process: Power Debugging > Minimum System Debugging > Peripheral Functional Circuit Debugging

There are many manufacturers that can produce boards; you can package and upload your PCB files or Gerber files, and after a few days of patience, the bare board will be in your hands.

Debugging is the most thrilling part for designers, akin to waiting for exam results.

Soldering can start with manual soldering while simultaneously ordering the corresponding components. If some components have tightly packed pins or special packages, consider using the stencil-solder paste-reflow soldering method; it is not advisable to start with surface mount components right away, as it can be difficult to troubleshoot if issues arise.

Some friends solder all components onto the board at once and then confidently power it on, resulting in sparks and smoke, leading to a chaotic situation and a frustrating end to their brief career. This approach is incorrect; it is recommended to first solder the power supply section, check if the power supply is functioning correctly, and only then proceed to solder and debug the other sections.

Some individuals find that their board exhibits confusing phenomena and intermittent issues during soldering and debugging, leading to repeated attempts and existential doubts. In such cases, a prayerful mindset often helps; generally, the problem can be resolved by checking for cold solder joints or poor connections.

On the software side, first try programming the firmware, and once that is successful, proceed to validate the business logic program and gradually improve it. During this process, it is essential to master some basic debugging techniques, such as using printf and breakpoints. The ability to locate and troubleshoot issues during debugging is invaluable, and you can also compare with the previous setup using ready-made components to identify the source of the problem.

— To Conclude —

Take your time; there is no need to rush. Completing a project thoroughly will yield some rewards, especially in the early stages. Instead of merely discussing the project after completion, it is better to spend more time summarizing and reflecting on it, asking more “why” questions, and thoroughly investigating the project’s details. Having a bit of obsession and passion for technology is quite beneficial.

Follow the Station | Continuous Sharing

Public Account & CSDN

< Renze Station, Welcome >