Presented by
-
US FAE Team Manager, IAR
Sign in to access this content and additional site features.
The complexity of embedded applications has grown exponentially over the past decade. There are many reasons for this, but one of the biggest driving forces is the relentless pursuit of more functionality for an embedded system and desire to keep up with the competition. Other reasons for the increased complexity are emerging industry standards, which are often driven by legislation (especially in the area of embedded security), and end-of-life (EoL) or hard-to-access parts that require a device upgrade, for example from NXP 32-bit to NXP 64-bit cores and even multi-core devices. That added complexity means more time developing more software, requiring more resources from the NXP device you choose, and you need to make sure that all of the software works well with every other part of the system for your automotive, industrial, medical or even machinery application. If you add that development teams are spread all over the world, how do you keep up?
The best development tools have in their core the traditional embedded development with compiler and debugger tools but are also able to integrate analysis tools for code quality and compliance with standards as well as tools that have been pre-certified by third party certification and accreditation entities. All these needs to be available.
Also for modern and scalable build server topologies for CI/CD pipelines. Finally, all the core investment needs to be protected for security legislation compliance, hopefully with just a few tick boxes.
In this session, we’re going to cover modern best practices and development tools for your NXP MCU-based embedded applications.
Ask our NXP Community community and get expert advice.
Subscribe to our newsletter to stay updated with our latest developments and if you need further assistance, we are here to help.
Subscribe Contact Support