>>电子设计资源
.. >>数字版本
.. .. >>本周的顶级故事
.. .. .. >> 2021电子设计预测
你会学到什么：
- 汽车和医疗市场将是嵌入式软件行业的主要驱动因素。
- 5G，物联网和边缘计算的升高将进一步推动集成和部署。
- 发展工具和流程的演变。
2021 will be a breakout year for RISC-V.
我们在大型客户中看到了R＆D集团涉及RISC-V看他们是否希望基于它的平台，我们已经看到较小的客户开始使用它。一些大公司确实致力于至少一些业务部门使用它。
While part of the RISC-V trace specification was ratified this past February, there will still be a few tweaks made in 2021. Ultimately, you’ll see a good deal of high-quality debug information like live instruction trace, interrupt visibility, power usage, and other metrics that can be fed through the debug port.
在其他事情中，这将真正赋予嵌入式开发人员更快地生产应用程序，因为它们能够更轻松地识别代码中的错误和瓶颈。我认为痕迹真的会起飞，我预测它会尽可能地帮助将RISC-V转变为主要的球员。
The automotive and medical markets will continue to grow and drive unprecedented innovation among embedded software developers.
I think we will continue to see automotive grow like gangbusters as autonomous driving pushes the envelope further and further. Leases on cars are way up, mostly because people want the latest and greatest tech and therefore don’t want to buy a car to keep right now. That’s fueling quite a bit of growth in the industry, not to mention the electrification of vehicles.
使这些现实和它们之间的沟通所需的大量系统将使嵌入式开发人员更加认识到在复杂的系统中运行。这将更加注重测试和代码质量。
此外，我认为，由于大流行，医疗会看到相当多的增长。很多人还在问，为什么要暂时才能获得疫苗？为什么我们的测试不快和更便宜？下一轮疾病会发生什么？
How will this impact embedded developers? They will be making smaller, more portable devices to diagnose infections instead of having to send things off to a large-scale lab. In my mind, the moon-shot would be to have devices that could take a virus profile, which would then get uploaded into a database. Such a database would be used in a handheld device that can give you positive or negative results against that profile in seconds. It would take a lot of creativity, but I think embedded developers are already at the forefront of making that a reality. However, it’s going to be more so in 2021.
我们可能需要在阶段中采取这一点，使检测更小，更便宜。因此，我们可以每个测试网站拥有一个实验室单元，只能检测Covid-19，可能是其他一些条件。理想情况下，通过使探测器可重编程可以通过重新编程来检测下一个大流行。很容易说，难以做到，但嵌入式开发人员是令人难以置信的创造力，他们将弄清楚如何做到这一点！
连续集成/连续部署将由IOT，5G，AI和云/边缘计算的快速增长驱动。
The biggest impact of this growth, which will continue in 2021, is the trend of continuous integration/continuous deployment. Teams are pushing out software updates faster than ever. This requires a rigorous set of tools to inspect code quality for potential pitfalls and automated testing to verify that the software conforms to the software specifications.
The tricky part is capturing all of the requirements in these types of tests to make sure that what gets pushed out doesn’t break things or make a system unreliable. That’s why continuous integration inspects source code to make sure it conforms to safe and reliable coding practices. Then it subjects the code to a rigorous battery of tests designed by the QA engineers to make sure that it’s doing the right things. The push to deliver things faster is really tricky in embedded software; if you get something wrong, it can render the system inoperable.
因此，从2021年嵌入式软件开发的IOT，5G，AI和云/边缘计算的快速增长的最大影响最大：在2021年的嵌入式软件开发中：继续关注提高质量，但仍仍然更快地提供。有趣的是，大多数人不会意识到它将拥有的关键影响是如此微妙。
开发工具将有助于公司应对时间挑战，但只有他们背后的技术专业知识。
毫无疑问，大多数公司面临的最大挑战是时间：上市时间，收回投资的时间，基于我之前所说的，有助于提高代码质量的开发工具将是节省时间的关键 - 甚至是关键比往年更多的是在前几年。
但是，同样重要的是支持您可以依赖于帮助您的时候，当您在一个时间紧缩时：为什么这个中断没有触发？为什么我在这个用例中是难倒的，更重要的是，在代码中发生在哪里？这是编译工具中的一个错误，如果是的话，我如何绕过它？
有一个旧的公理时间是金钱，当你必须阅读reams和web页面的读取来找到小块来帮助你得到修复或解决方法时，它会花费很多钱和时间。同样，如果您的代码不够快地运行满足您的需求，那么您可以举起手工优化它，这可能会花费大型时间。有时人们诉诸编写汇编程序代码，通常不是很便携，加上代码变得凌乱，并使源的静态分析较差。
当您使用质量开发工具时，它会在工具上讨论这些问题，而不是您。此外，当您遇到问题时，您可以提供技术专家您可以呼救。因此，你在前面花了一点钱，但你在结束分析中节省了很多时间和金钱。
代码质量的基本发展实践将继续evolve。
正如我们所提到的，发展实践不断改进，因为更多它们正在变得自动化。在Ye Olden的日子里，唯一对任何明显程度进行自动测试的人是功能安全领域中应用的开发人员。现在我们看到即使为消费者设备推出自动化测试。显而易见的是，对更形式化和自动化测试的代码进行更多的代码来缩小代码。
It used to be that code inspections were rare. As long as your code didn’t have bugs, you could be as sloppy as you wanted, putting spaghetti code here, there, and everywhere. With automated continuous integration, you can’t get away with that anymore. You’re forced to write your code using best practices, and if you don’t, everyone can see it in the output of the continuous integration system.
随着人们发现新的和更好的方式添加到自动化测试，它将强迫人们使用当地的代码分析副本，而他们在桌面检查其代码之前，并在它进入正式构建之前。他们想知道他们的代码是否会在其他人看到连续集成输出之前通过集合。
Studies like the ACM paper, which we cited in a由IAR Systems的白皮书，已经表明，在开发人员面前越早将这种反馈越多，他们越严重地对待它。如果您将其作为夜间构建过程的一部分留下，该过程在第二天接受反馈的情况下，由于“幸存者效应”，此类问题会不那么认真对待。但随着检查变得更加严格，人们将要更快地检查自己的代码。
提高整个开发过程的经验和质量：充分和准确地记录代码将比以往更重要。
我无法开始告诉您我看到多少次代码，其中包括少数注释。通常开发人员宣称他们的代码是“自我记录”。我已经听说过这个术语很有点，但我认为这就像嵌入式开发社区的独角兽一样 - 我一直听到它，但我从未真正看过它。
Developers need to do a thorough job documenting their code not only for anyone who will review or maintain their code, but also for themselves. Six weeks from now, when someone finds a bug in that section of code, you’re going to spend lots of time trying to remember what you were thinking when you wrote that section. If you had just taken a few extra minutes to clarify your thought process in the comments, you wouldn’t be in that pickle.
I’ve also heard developers claim that by making their code abstruse with a paucity of comments to document it, they’re increasing their own job security. I think that’s just silly; you’re making it harder for yourself and everyone else. Job security comes in being able to do your job so well that a company has no reason to want to replace you. And when you mentor other people in how your code works, you increase your value to your colleagues.
我从来没有是我们在我以前的雇主之一所谓的“400磅脑综合征”的粉丝，其中一个人拥有一些关于某些事情的知识和嫉妒地守卫。分享您的知识;这是你对公司的真实价值。它使您的发展体验更好，同时帮助您周围的其他人。
