Part 1 – Electronics at a glance
The purpose of this series of articles is to describe in clear terms what is involved in the development of systems that include custom electronics. Tasks include the specification, design, and electronic development of hardware and software that provide a set of functions and facilities for an electronic product. Together, these tasks are often described as embedded or integrated engineering. Each of the documents includes a set of definitions that are expected to be useful to the reader and a setting for reading the articles. We therefore include below the definitions of four terms that are related to integrated engineering.
Embedded System:
A system consisting of one or more components, designed to provide autonomous functions. These systems can be integrated into a product. A car braking system is an example.
Embedded Software:
The intangible components of a computer integrated into an electronic system or product.
Microprocessor:
A small computer built into an electronic device that can be programmed with embedded software to perform certain stand-alone functions.
Microcontroller:
It is a type of specialized microprocessor that includes the ability to process signals as well as data. The signals are processed by silicon blocks in the microcontroller. Blocks that convert analog signals to digital data (AD converters), are one example. Synergy will be referenced throughout the article series. Synergy is the name of a family of microcontrollers from Renesas. Each member of the family is destined for particular areas of the market. For example, the S1 is designed for use in markets where low power consumption is essential, whereas the S7 can be used for video processing. Synergy's offering also includes specific embedded software.
When starting the design of an electronic system, the purpose and scope of the application should be studied in order to find out which components and in particular which microcontroller should be selected. Figure 1 illustrates the main parts of an electronic product, broken down into sub-components and key components. Component selection is an important part of the designer's job, but it's also important not to make the process too complicated. As a starting point, the functionality of the product should be considered. Of the various technologies, the most appropriate options can be evaluated and from here the appropriate components can be selected. If, for example, the product is video streaming, technologies are required to support fast processing. But if the product is used for data collection instead, robust and secure communications may be more important.
Also, when data needs to be collected, say, from a health monitor, the ability to capture data from a sensor will be needed. Each product in detail, therefore, will be different and consequently will be the subject of a specific design; but, in simple terms, each design will have to consider communication functions, processing and detection functions. Final selection of components is not likely to occur late in development as issues such as cost and longevity also come into play. The moment of the selection of components will depend on the design and development strategy chosen, paying special attention to the intangible components of embedded software, which will more often require development together with the tangible product. However, the Synergy range has been designed to cater for a wide range of application areas.
Important software development support is included, making it easier to integrate into the company's design and development strategy. Selecting the most appropriate strategy is not a simple task and will depend on the level of ambiguity and uncertainty involved. Simple questions such as how much research and testing will be required to de-risk the project in order to proceed correctly along the established path. There are an abundance of methods and processes to support product development strategies, but they can generally be broken down into distinct stages, where one set of tasks must be completed before the next can begin. Agile approaches are typically chosen, with time as the basis. However, all strategies have the common goal; to finish on time and within budget. Perhaps the most important question when starting a project is what is meant by finish? Is it when a model is shown to work, or do you mean when a set of acceptance tests have been passed? Too often we have reviewed plans where there is no firm definition of finishing, or in tests and criteria where a clear finish line has been thought of. The situation is further exacerbated when you rely on unstated assumptions to achieve success.
One way to avoid common pitfalls is to consider the life cycle of the product or system being developed. Working backwards from market implementation to release and then to development can stop simple mistakes like neglecting software development maintenance functions or skipping design-to-manufacturing. Taking extreme care during the design process to ensure that the product can be well cared for and maintained throughout its life cycle will pay off.
This is particularly important in fast-moving markets where customized products or product families are required. Reusable components and technology platforms to support such markets can be designed from day one and it is particularly in this arena where Synergy can play an integral role. The target market and the life cycle go hand in hand, but it must be remembered that a product can have multiple life cycles, depending on the markets it is intended for. Additionally, different markets may have different compliance and end-of-life handling requirements.
The sheer number of different standards that need to be met can seem daunting, but if good processes are in place and the necessary information is put in place, particularly if records of tests performed and decisions made are compiled in a technical file, most requirements can be met. can easily meet. All electronic products must undergo Electromagnetic Compatibility (EMC) testing before they can be placed on the market. Mains powered devices will also be subject to the requirements of the Low Voltage Directive (LVD) and those containing any wireless communication, the Radio Equipment Directive (RED).
The requirements for these standards, along with market-specific standards such as those for medical and automotive products, should be included in the overall product requirement. Electronic product development is multifaceted, and each facet requires significant skill to complete. The key is to ensure that all the work is done diligently and visibly so that the design can be easily tested.
