Hello everyone, I remember Cheng.
The boss talks about a big project.
After returning, convene a meeting with the person in charge of R&D to evaluate hardware requirements, evaluate software requirements, and so on.
After confirming that the project can be done, convert the customer's needs into executable technical points (this is usually done by the project leader or department leader), subdivide and refine, and form a function list document. The form of each company's document may be different of.
The project team is established, and the R&D personnel receive project-related documents, product definition, function list, project background, etc.
After the hardware engineers are familiar with these materials, they start to draw the hardware block diagram of the project. After the hardware architecture is drawn, the company will conduct an internal review.
After the hardware architecture is determined, the engineer starts to draw the hardware schematic diagram.
Then the following is the text, which can answer the questions asked by the landlord, remember to read down .
It can be seen that the host is a novice, not familiar with the basic process, and the hardware knowledge is so complicated, so it is normal to have questions.
The hardware newcomers who have just joined the job are not capable of doing projects, because the risk of hardware is very high.
The anxiety of many newcomers lies in: there are too many hardware knowledge points, I don’t understand all kinds of resistor components, characteristics, and selection, I haven’t learned the drawing software, and I don’t know how to draw PCBs. When can I start the project.
Anxiety is due to the wrong learning method. It is impossible for us to learn all the knowledge points and prepare them well before doing projects. This is also impossible, and Rome was not built in a day.
1. In the company, work from top to bottom, with the goal of doing a good job in the project/product
Use a top-down method to decompose the project, from the hardware architecture, to each functional module, and then to the electronic components under each functional module, and then get familiar with electronic components and learn to select models.
For example, if there is DC-DC in the circuit, then we will learn how to choose the input and output capacitors? How is inductance calculated? How to configure the output voltage? What should be paid attention to in DC-DC PCB routing? Make sure that the DC-DC circuit is designed correctly in the project.
Distinguish priorities, focus on key points, and save deeper knowledge points for projects that are not in a hurry or in spare time to learn.
2. In our spare time, we study from bottom to top, with the goal of perfecting the knowledge system and laying a solid foundation
The second point is the process from laying the foundation to building the fortress. The more complete the knowledge system, the stronger the foundation, the more stable the fortress, and the lower the probability of error.
After talking about the two methods, let's add a little more about how to reduce the error rate of drawing schematic diagrams .
Drawing a schematic diagram is actually a process of building blocks. In order to prevent mistakes, a lot of human work and processes must be inserted in the process to reduce the error rate.
1. For the same functional circuit, the company's internal mature circuit scheme is preferred, and the risk is small. The new scheme means great risk and troublesome debugging .
2. Add more compatible circuit solutions
Compatible circuits, in layman's terms, are A compatible with B, you can use either the A circuit scheme or the B circuit scheme, reserve the PCB patch position, and then change the BOM later. What are the benefits?
- Realize different functions , such as constant power supply and control power supply, etc., to achieve low power consumption.
- Compatible with different chips , avoiding shortages, price increases, and long delivery times of certain chips. Through compatible chip design, this problem can be reduced to a certain extent.
- It is convenient to debug parameters . For some uncertain circuit schemes, you can make compatible circuits. After the board is back, you can test it and finally decide which scheme to choose.
3. Test and verify the new circuit in advance
For some new circuits, in addition to adding compatible circuits, if possible, the circuit can be built in advance for testing, and the circuit scheme and parameters can be determined. On the one hand, to avoid wrong design, on the other hand, after the parameters are determined, manual replacement of materials can be avoided after trial production.
4. Please check the schematic diagram and PCB from the original factory
Now the technical support of the platform is very good. After drawing the schematic diagram, it is best to ask the original factory to check, mainly for chips, and it is best to send to the original factory the complete circuit related to the chip, including power supply, antenna path, etc.
PCB is generally PDN simulation. If the company does not have the PDN simulation conditions, it should send the PCB file to the original CPU factory. It is best to choose the version that is about to be archived for simulation, so as to reduce the delay in back and forth simulation.
5. Comply with the company's design specifications
In some large companies, there will be their own design specifications. Some novice engineers like to follow their own pace, not strictly follow the specifications or design requirements, and take it for granted if the company has a second person to check, otherwise it may not be Necessary revisions will delay the progress of the project.
Hardware design requires a lot of experience. When you have no ability or experience, show your own seriousness, don't be afraid of trouble, follow the rules , and you can avoid many unnecessary problems.
If you have technical problems, you can click on the business card below to contact me.