Follow+Star Public Account, don’t miss out on exciting content
Author | strongerHuang
WeChat Public Account | strongerHuang
Is macOS Suitable for Embedded Development?
From time to time, some friends ask me similar questions, and my answer is: Not Suitable!
As for why, if you observe carefully the colleagues (classmates or friends) around you who are engaged in embedded software and hardware development, you will notice a phenomenon: Very few use macOS for embedded development.
Reason 1: Many Software Do Not Support macOS
Have you ever had such a doubt:Does Keil support macOS?
I believe many people have this doubt, including myself in the early days. As my knowledge broadened, I discovered that many software in the embedded field actually do not support macOS.
Here are a few common software in our field that do not support macOS.
This refers to the entire series of Keil products, includingKeil C51, MDK, C251, C166.
(Keil system requirements) Official address:
https://www2.keil.com/system-requirements/
The official requirement is that the latest version of the software must run on at least Win8 and above. Of course, Win7 can also be installed and run, but some functions may have compatibility issues(the latest version of the software does not support XP, but it seems that KeilMDKV5.18 or 20 can still run).
IAR is similar to the entire series of Keil products, including many IAR products, such as: IAR EWARM, EWSTM8, EWMSP430, EWAVR, EW8051··· etc.
For example, EWARM V9.30.1 (latest version) system requirements:
Source Insight is also a commonly used editor tool for embedded software engineers, but it is a software that only supports Windows and does not support macOS.
(Source Insight system requirements) Official address:
https://www.sourceinsight.com/
Another hardware software is Altium Designer, which is also a software that only supports Windows and does not support macOS.
(AD system requirements) Official address:
https://www.altium.com/cn/documentation/altium-designer/system-requirements
The latest version of AD software has relatively high system requirements, not only does it only support Windows, but it also requires 64-bit and has graphics card requirements, which should be used for 3D rendering.
There are many classic and commonly used software tools, such as: STC-ISP download programming software, STM32 ST-LINK Utility, etc.(There are many more, please feel free to add in the comments at the end)
Reason 2: Ecology, Compatibility, and Openness
I do not deny that macOS is very well done, but macOS cannot exert its advantages in the embedded field.
In fact, it is not only in the embedded field, but also many other fields are not suitable for macOS, such as: mechanical manufacturing, electrical automation, gaming, etc.(You rarely see someone buying a Mac to play games, right?)
Ecology, Compatibility, and Openness
Because Windows was popularized earlier, many embedded development tools and resources are relatively dependent on the Windows system, leading to a better embedded development ecosystem on Windows.
You will find that many small tools for embedded development basically only have Windows versions, and individual developers can write some Windows version small tools. (For example: serial port, network debugging tools, CAN, I2C analyzers, etc.).
Again, the resources (materials) in the Windows environment are richer, and related issues can quickly find answers or solutions.
The reason Windows is more suitable for embedded development compared to macOS is due to the ecosystem, compatibility, and openness of the Windows system.
Reason 3: Mac Computers Are Expensive
The reasons mentioned above may not be the main reasons.The main reason may still be that Mac computers are expensive
Mac computers are expensive, and the number of users is relatively small, which naturally leads to an imperfect embedded development ecosystem, and the supporting tools are lacking, resulting in fewer DIY or small tools developed on macOS.
After saying so much, someone might argue: macOS can run virtual machines, or Mac computers can also run Windows?
Indeed, macOS can also be used for embedded development, but it cannot exert its advantages and may lead to unnecessary “troubles”.
I often say that what suits you best is the best; some people say Keil is difficult to use, while others say Keil is very easy to use. Who do you think is more reasonable?
Finally, if you are not short of money and don’t mind the trouble, feel free to buy a Mac computer for embedded development, and then come share your pitfall experience with everyone.
———— END ————
● Column “Embedded Tools”
● Column “Embedded Development”
● Column “Keil Tutorial”
● Selected Tutorials from Embedded Column
Follow the public account reply “Join Group” to join the technical exchange group according to the rules, reply “1024” to see more content.
Click “Read Original” to see more shares.
