Brothers who work on microcontrollers don't seem to be used to version management, cp folders are everywhere

freebsder

Brothers who work on microcontrollers don't seem to be used to version management, cp folders are everywhere [Copy link]

 

For the same project, the folders are all over the place, and I don't know which folder corresponds to which version. There is no log either.

I have seen engineers in the MCU industry do this a lot. The version control concept in other software environments is much better.

I have said many times that MCU engineers complete a function and upload it to git in time, but they just cannot execute it.

I don't know if anyone has a good solution.

sint27

I work on MCU software, and I don't have any version management software. I think there are several main reasons.

1. There is very little multi-person collaboration in single-chip microcomputers. Basically, one person completes a project.

2. Product function iterations are rare, and the basically finalized ones can be sold for a long time. If the functions are iterated, the hardware will also change in many cases, and it will directly become another model.

3. Many products do not have OTA upgrade methods. During the development process, we will test as much as possible and try to eliminate bugs in the company. Therefore, the same product rarely modifies the software multiple times due to bugs.

PS: 1. The above more and less are relative to the IT industry;

2. Maybe our company is too small and has too few employees, so we don’t have version management.

flyaqiao

This is not absolute. I put all my code under version management, so at least if I find something broken one day, I can restore it. Or if I need to modify the code in the company, I can just check it out and modify it directly, without copying it back and forth, and finally I don’t know which one is the latest.

lcofjp

This problem has nothing to do with collaborative development by several people. There are two main points:

1. Not realizing the benefits of version control

2. Learning version management also requires a lot of effort, and it is not easy to use it well.

dcexpert

sint27 posted on 2024-1-30 15:23 I am engaged in MCU software, and I don’t have version management software. I think there are several main reasons. 1. There is very little multi-person collaboration in MCU, and basically...

Some large companies are not much better. There are not too many people on a project, and there is not too much collaborative development work. Only projects that are complex enough can reflect the advantages of version management.

bobde163

I am also engaged in single-chip microcomputer development. From the beginning of learning software, I have been thinking about one day being able to ghost backup code with one click like in the winxp era. It would be great if the change differences could be automatically recorded. Later, I started using SVN and then Git and couldn't live without it. It is really easy to use, but it is still a little different from my ideal smarter way of recording each change with a timestamp. But now I can't go back to the days of writing update logs.

aozima

Firmware release only uses CI, and it cannot be released without submission.

freebsder

aozima posted on 2024-1-30 18:07 Firmware release only uses CI, it cannot be released without submission.

Could you please tell me what tools are used and how are they managed?

freebsder

bobde163 posted on 2024-1-30 17:33 I am also engaged in MCU development. From the beginning of learning software, I have always wanted to be able to back up the code with one click like in the winxp era. If I can automatically...

Some colleagues have said it countless times, and I guess they really haven't realized the benefits of version management. What's even more uncomfortable now is that both folders and versions are in use. Damn, sometimes it's even more messy. It seems that we must take drastic measures, not just talk about it.

freebsder

dcexpert posted on 2024-1-30 16:50 Some large companies are not much better. There won’t be too many people on a project, and there won’t be too much collaborative development work. Only projects that are complex enough will show...

We mainly have a small number of customized and special ones, and we temporarily use a folder to deal with them. In the end, we can't trace them back to the time, so we have to argue about it.

freebsder

lcofjp posted on 2024-1-30 16:31 This problem has nothing to do with collaborative development by several people. It mainly has two points: 1. Not realizing the benefits of version management 2. Learning version management also requires a lot of effort...

Some of us use git, which can merge scattered files. If there is a problem and they find that they are missing after searching for a long time, it doesn't matter. At worst, they can start over. They merge most of them, but if 1 or 2 are missing, I would doubt whether it was intentional.

freebsder

flyaqiao posted on 2024-1-30 15:26 This is not absolute. I put all my code in version management, at least if I find that it is broken one day, I have to restore it. Or if I need to modify the code in the company, I can just check it out...

Some people may not realize the advantages, and folders are faster.

freebsder

sint27 posted on 2024-1-30 15:23 I am engaged in MCU software, and I don’t have version management software. I think there are several main reasons. 1. There is very little multi-person collaboration in MCU, and basically...

We are currently using git, which has some learning costs. The problem is that the more traditional svn is a bit confusing for me, an engineer working on microcontrollers.

ljj3166

Version management? Non-existent.

Do a batch process, add the name and date, compress it with zip, and then copy it to the specified location.

lugl4313820

I'm the same, I'm not used to it, and I'll still need version management in the future.

吾妻思萌

How do you deal with this old picture that has been useful for thousands of years?

qzc飘曳

The modular design of the microcontroller is still relatively lacking, and the correlation between various files is relatively high

wangerxian

If you use Git for microcontroller code, I think it must be promoted. This will make it very convenient to find problems and record versions. I think you can enforce it and require it to be updated once a day.

Basically, I will release a version when I change a function. If there is a problem with this function, it will be easier for me to find it.

wangerxian

freebsder posted on 2024-1-30 19:48 We are using git now, which has some learning cost. The problem is that it is a more traditional svn, and I, an engineer who works on single-chip microcomputers, am also a little confused.

Are you using a graphical operating software or a command line?

fjdeepblue

For MCU programs, GIT is also a good choice. One is for version control, and it is also convenient to synchronize multiple computers. I use TortoiseGit, and it feels pretty good.