Shulou(Shulou.com)06/02 Report--

This article mainly introduces how to choose the appropriate embedded design software, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, let the editor take you to know about it.

I. device / kernel support

When choosing embedded design software, you first need to consider the degree of support of the software you choose for the device you choose. To identify your needs, you need to make a list of the devices that appear in your product. Then, one by one, check whether the embedded design software you choose supports your device.

This is likely to happen, and the new software can no longer support old devices. When you don't need to develop new applications, but only need to maintain existing software, the software you already have may be enough.

Next, you have to consider the equipment you will use in the future. You certainly hope that the embedded design software you buy can also support newer embedded devices. You don't want to buy software every time a new device appears, which is not only expensive, but also takes time and effort to master the new software.

Second, ease of use

Ease of use is also a very important function. Difficult tools not only make developers nervous, but also prolong development time.

In order to ensure that the embedded design software you value is easy to use, you can download the software for trial. General development software provides a trial period of 15-30 days, which is very important for you who do not want to spend money unjustly.

To do this, you can first set up an experimental project. It doesn't need to be too complicated-- after all, you only have 30 days-- but the project has to be complex enough for developers to verify the performance and compilation quality of the software.

When you test, be sure not to use the reference projects given by the software provider, which are usually specifically optimized for the software and feel much better. You should write your own code or get code from a non-software provider.

III. Support for common functions

After the ease-of-use testing of the software is completed, it is also necessary to check the software's support for different functions, some of which are very important and some of which are not available. For example, whether to support real-time operating system (RTOS), whether to support communication hardware and software, such as: USB, TCP/IP, Bluetooth and so on. If your design requires this feature, but the software you are testing does not, then you may need a lot of time and money to design your own solution.

Another important feature for you is whether the software supports functional safety standards, such as ISO 26262, which provide guidance for the qualification of software tools. If this is important to you, the software you need should provide a solution to the standard you are dealing with.

IV. Debugging

No one can design software at once (with the exception of "hello world", of course), especially now that the software is already very complex. This means that developers need to spend a lot of time on debugging, so the speed and performance of the debugger are also important to save developers' time, which in turn may affect the time to market. Here are some features you may need to focus on:

Multiple information windows that allow you to monitor variables, memory and stacks.

It allows you to set complex breakpoints according to the number of instructions, cycles and timers to interrupt the execution of instructions.

Saving and restoring memory allows you to easily return to the previous state of the system.

V. Technical support

* consider the type of technical support that the supplier can provide. There are often significant differences in the types of technical support between suppliers. Some only provide online forum support, while others provide e-mail support, but even if you can find a solution, it may have taken a lot of time.

So I suggest you choose a supplier that can provide good technical support, which you can do some testing during the probation period. Send them a request for support and see how it turns out. Software with good technical support usually doesn't cost much more than other software, and you'll see how important it is when you really need technical support.

Thank you for reading this article carefully. I hope the article "how to choose the right embedded Design Software" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.