Pitfalls for hardware engineers learning embedded Linux

Nubility

Pitfalls for hardware engineers learning embedded Linux [Copy link]

 

There are many hardware companies that have similar ideas to mine, and I want to expand into software. I have made mistakes in this area and suffered heavy losses, so I want to share my mistakes so that more people can avoid them.

1. Buy a good development board. Recommended boards include Zhengdian Atom, Wildfire, and Weidongshan. I strongly do not recommend the boards from Beijing "Xun" Wei. The information is rubbish, the after-sales service is rubbish, and the atmosphere in the learning and exchange group is extremely poor.

2. Don't get stuck in a rut, don't delve into details from the beginning. Linux and uboot have a lot of knowledge points. For example, Makefile, shell script, Kconfig, .config, what is defconfig, uboot/Linux boot process, device tree, mount, why are there only files under Linux, what is platform bus/driver/device, kernel module, what is character/block/network device, what is I2C subsystem, GPIO subsystem. When facing these things, you must stop at the surface, and never try to fully understand them in the beginner stage. Follow the tutorial first, and then delve into the details according to specific needs after you can use it. If you delve into various knowledge points from the beginning, you will find that you are facing an abyss, which is not only ineffective, but also very disappointing.

3. Do more projects. Not only do you need to accumulate experience in hardware, but you also need to accumulate more and more detailed knowledge when working on embedded Linux, especially BSP and driver work. Don't think about changing careers when you just get started. It's best to expand into software discovery while you're still working. It's more valuable to gain experience in the company's real projects than doing your own projects.

hellokitty_bean

Brother Nu, I’m here just to give you a thumbs up!

I especially appreciate the second one, which avoids getting bogged down in details. . . .

hellokitty_bean

But... But... What about the other way around???

Brother Nu, you can also write about how to avoid pitfalls when switching from software to hardware.

Nubility

hellokitty_bean posted on 2024-7-8 19:54 But... But... What about the other way around? ? ? Brother Nu, you can also write about how to switch from software to hardware and avoid pitfalls

Because I don't have such experience, I can't write it

hellokitty_bean

Then write about your experience as a hardware engineer.

Simplex is not as good as duplex. . . .

walker2048

It's pretty good. I met many novices who thought they could quickly grasp the essence of Linux and were unwilling to follow the tutorials and do basic cases down to earth.

Nubility

walker2048 posted on 2024-7-8 22:49 It's pretty good. I met many novices who think they can quickly grasp the essence of Linux and are unwilling to follow the tutorials to do basic cases.

Yes, one is afraid of floating, thinking that you can solve everything. The other is afraid of getting stuck in a dead end, wanting to understand everything thoroughly.

秦天qintian0303

Makefile, shell script, Kconfig, .config, defconfig, still in the Linux environment configuration stage

Nubility

Qintianqintian0303 posted on 2024-7-9 07:00 Makefile, shell script, Kconfig, .config, defconfig, still in the Linux environment configuration stage

It's easy to get hung up on these things.

beyond_笑谈

The author wrote a very practical article. He learned Linux from scratch for the project requirements. At first, he was confused because Linux and MCU are completely different things (he had written MCU programs before). In the end, he went straight to the project requirements and made up for what he lacked without being too greedy for details.

dukedz

Usually use Linux as the main system, then learning Linux embedded system will be much easier

请假扣工资

How good is your grasp of C language? Have you developed microcontrollers before?

okhxyyo

Great! Indeed, sometimes beginners can easily miss the point and focus too much on details.

damiaa

The atoms are fine. But I still have to dig into some horns later.

Nubility

Posted on 2024-7-9 10:34 How good is your grasp of C language? Have you developed a single-chip microcomputer before?

No, just played it.

se7ens

It feels like a big step.

To convert hardware to software, you can start by learning the C language of microcontrollers

It feels too fast to switch to Linux all at once.

Nubility

se7ens posted on 2024-7-10 10:42 I feel like it’s a bit of a big step to switch from hardware to software. You can start with the C language for microcontrollers and then move on to Linux. It feels too fast and I can’t handle it...

This depends on personal circumstances, you can also transition

laker2008

Haha, I was envious of the salary of embedded engineers in the company back then. I also tried to switch several times, but it seems that I am not good at programming, so I didn’t succeed completely. Later, I lost interest.

Nubility

laker2008 posted on 2024-7-10 11:39 Haha, I was also envious of the salary of embedded engineers in the company back then, and I also tried to transform several times, but it seems that I am not good at programming, ...

It is easy for software developers to obtain patents. In the past, I saw that they could apply for several patents every month and get an extra 3,000-5,000 patent subsidies.

UUC

You really can't skimp on the details of a difficult book. If your self-confidence is dampened, you won't be able to proceed.