Is a Mac suitable for embedded development? I often get asked this question, and my answer is: Not suitable! As for why, if you observe your colleagues (classmates or friends) who are engaged in embedded software and hardware development, you will notice a phenomenon: Very few people use macOS for embedded development.
Reason 1: Many software tools do not support macOS
Have you ever wondered: Does Keil support macOS? I believe many people have this question, including myself in the early days. As I broadened my knowledge, I discovered that many software tools in the embedded field do not actually support macOS. Here are a few common software tools in our field that do not support macOS.1. Keil This refers to the entire series of Keil products, including Keil C51, MDK, C251, C166. (Keil system requirements) Official address:
https://www2.keil.com/system-requirements/
The official requirement for the latest version of the software is to run on at least Windows 8 or higher. Of course, Windows 7 can also be installed and run, but some features may have compatibility issues. (The latest version of the software does not support XP, but it seems that Keil MDK V5.18 or 20 can still run).
2. IAR 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:
3. Source Insight 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/
4. Altium Designer Another hardware tool 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.5. More 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, feel free to leave comments at the end to add).
Reason 2: Ecosystem, Compatibility, and Openness
There is no denying that macOS is very well made, but it cannot leverage its advantages in the embedded field. In fact, not only in the embedded field, but there are many areas that are not suitable for macOS, such as: mechanical manufacturing, electrical automation, gaming, etc. (You rarely see someone buying a Mac to play games, right?)Ecosystem, Compatibility, and Openness Because Windows was popularized earlier, many embedded development tools and resources are heavily reliant on the Windows system, leading to a better ecosystem for embedded development on Windows. You will find that many small tools for embedded development are basically only available in Windows versions, and individual developers can write some Windows version small tools. (For example: serial port, network debugging tools, CAN, I2C analyzers, etc.).
Furthermore, resources (materials) in the Windows environment are richer, and related issues can be quickly resolved with answers or solutions. The reason why Windows is more suitable for embedded development than macOS is due to the ecosystem, compatibility, and openness of the Windows system.
Reason 3: Macs are Expensive
The reasons mentioned above may not be the main reasons. The main reason may still be that Macs are expensive
Macs are expensive, and the user base is relatively small, which naturally leads to an incomplete embedded development ecosystem, and the supporting tools are lacking, making DIY or small tools developed on macOS even fewer. After all this, some may argue: macOS can run virtual machines, or Macs can also run Windows?
Indeed, macOS can also be used for embedded development, but it cannot leverage 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 on money and do not mind the hassle, feel free to buy a Mac for embedded development and then share your pitfall experiences with everyone.Source: strongerHuangFriendly Reminder:
Due to recent changes in the WeChat public platform push rules, many readers have reported not seeing updated articles in a timely manner. According to the latest rules, it is recommended to click on “Recommended Reading, Share, Collect” more often to become a regular reader.
Recommended Reading:
-
Loosening chip restrictions, the US modifies its plan for China under pressure~
-
Germany ignores US bans, US lawmakers: Germany endangers European security!
-
To maintain world leadership! The US Semiconductor Association states: We need to do three things!
-
Paralysis + blindness will be a thing of the past? Musk reveals the latest results of brain-machine chips, 6-month human trials!
-
Bonuses exceed annual salary, TSMC’s new engineers never work overtime, buy a Porsche after one year?
Please click 【View】 to give the author a thumbs up
