Obviously there are many boards available in the market, but I don't want to use them. because i also want to learn to design boards. And the benefit of all this will be that my thinking ability will increase, many real problems will come in front of me, which I will try to solve.

If you want learn something new for you, never start with complex designs or you never finish this thing. Always use in new designs mostly parts you are familiar with and add only few new things to it. This will make designing and troubleshooting much easier.

 

Yes. NEVER disagree with the client about this!

If you do have some reason to disagree, they shouldn't be a client. But absolutely it is the consultant's work to create a solution to the problem that it is the client's work to clearly articulate. Though they very well may need help to sort out the difference between specifications and design goals.

 

@Pushkar1 I actually do have a little more advice for you. Given your goals, I suggest you reverse engineer something like an RPi as your first step in learning. It will teach you how a successful design is put together.

 

If you want learn something new for you, never start with complex designs or you never finish this thing.

I can design a simple project and I don't have problems with it. But it is a bit difficult to understand how big projects can be designed.

 

I suggest you reverse engineer something like an RPi as your first step in learning. It will teach you how a successful design is put together.

I have a Raspberry Pi 3 Model B Plus so what can I do reverse-engineering it.

 

Big projects are a set of small projects with a plan of how to connect them together.

 

I have a Raspberry Pi 3 Model B Plus so what can I do reverse-engineering it.

Look at the PCB layout (find documentation on it, too.) Look at the chipsets in use, get the datasheets and trace the circuits.

Look at the various functional subsystems like the power supply and the I/O.

Figure out what they've done and try to work out why. Possibly build your own versions of various subsystems.

 

Look at the PCB layout (find documentation on it, too.) Look at the chipsets in use, get the datasheets and trace the circuits
Figure out what they've done and try to work out why. Possibly build your own versions of various subsystems.

That's a good suggestions. I will definitely work on it