Tag Archives: automotive engineering

Are you designing for the latest automotive embedded system?


Eventually, self-driving cars will arrive. But until then, here’s a look at what will drive that progression.


The next arrow of development is set for automotive

We all have seen it. We all have read about it in your front-center technology news outlets. The next forefront for technology will take place in the vehicle. The growing market fitted with the feature deviation trend does not appeal to the vision of customizing more traditional un-connected, oiled and commonly leveraged chassis vehicles of today. Instead, ubiquity in smartphones have curved a design trend, now mature while making way for the connected car platform. The awaiting junction is here for more integration of the automotive software stack.  Opportunities for the connected car market are huge, but multiple challenges still exist. Life-cycles in the development of automotive and the mobile industry are a serious barrier for the future of connected cars. Simply, vehicles take much longer to develop than smartphones other portable gadgetry. More integration from vendors and suppliers are involved with the expertise to seamlessly fit the intended blueprint of the design. In fact, new features such as the operating system are becoming more prevalent, while the demand for sophisticated and centrally operated embedded systems are taking the height of the evolution. This means more dependence on integration of data from various channels, actuators, and sensors — the faculty to operate all the new uses cases such as automatic emergency response systems are functionality requiring more SoC embedded system requirements.

A step toward the connected car - ecall and how it works

What is happening now?

People. Process. Governance. Adoption. Let’s look at the similarities stemmed from change. We are going to witness new safety laws and revised regulations coming through the industry. These new laws will dictate the demand for connectivity. Indeed, drawing importance this 2015 year with the requirement set by 2018, European Parliament voted in favor of eCall regulation. Cars in Europe must be equipped with eCall, a system that automatically contacts emergency services directing them to the vehicle location in the event of an emergency. The automotive and mobile industries have different regional and market objectives. Together, all the participants in both market segments will need to find ways to collaborate in order to satisfy consumer connectivity needs. Case in point, Chrysler has partnered with Nextel to successfully connect cars like their Dodge Viper, while General Motors uses AT&T as its mobile development partner.

General Motors selected AT&T as its mobile partner

What is resonating from the sales floor and customer perspective?

The demand is increasing for more sophistication and integration of software in the cabin of cars. This is happening from the manufacturer to the supplier network then to the integration partners — all are becoming more engaged to achieve the single outcome, pacing toward the movement to the connected car. Stretched as far as the actual retail outlets, auto dealers are shifting their practice to be more tech savvy, too. The advent of the smart  vehicle has already dramatically changed the dealership model, while more transformation awaits the consumer.

On the sales floor as well as the on-boarding experience, sales reps must plan to spend an hour or more teaching customers how to use their car’s advanced technology. But still, these are only a few mentioned scenarios where things have changed in relation to cars and how they are sold and even to the point of how they are distributed, owned, and serviced. One thing for certain, though, is that the design and user trend are intersecting to help shape the demand and experience a driver wants in the connected car. This is further bolstered by the fast paced evolution of smartphones and the marketing experiences now brought forth by the rapid adoption and prolific expansion of the mobile industry tethered by their very seamless and highly evolved experiences drawn from their preferred apps.

Today, customer experiences are becoming more tailored while users, albeit on the screen or engaged with their mobile devices are getting highly acquainted with the expectation of “picking up from where I left off” regardless of what channel, medium, device, or platform.  Seamless experiences are breaking through the market.  We witness Uber, where users initialize their click on their smartphone then follows by telemetry promoted from Uber drivers and back to the users smart phone.  In fact, this happens vis versa, Uber driver’s have information on their console showing customer location and order of priority.  Real life interactions are being further enhanced by real-time data, connecting one device to draw forth another platform to continue the journey.  Transportation is one of the areas where we can see real-time solutions changing our day-to-day engagement.  Some of these are being brought forth by Atmel’s IoT cloud partners such as PubNub where they leverage their stack in devices to offer dispatch, vehicle state, and geo fencing for many vehicle platforms.  Companies like Lixar, LoadSmart, GetTaxi, Sidecar, Uber, Lyft are using real-time technologies as integral workings to their integrated vehicle platforms.

The design trajectory for connected cars continues to follow this arrow forward

Cars are becoming more of a software platform where value chain add-ons tied to an ecosystem are enabled within the software tethered by the cloud where data will continue to enhance the experience. The design trajectory for connected cars follow this software integration arrow.  Today, the demand emphasizes mobility along with required connectivity to customer services and advanced functions like power management for electric vehicles, where firmware/software updates further produce refined outcomes in the driver experience (range of car, battery management, other driver assisted functionalities).

Carmakers and mobile operators are debating the best way to connect the car to the web. Built-in options could provide stronger connections, but some consumers prefer tethering their existing smartphone to the car via Bluetooth or USB cable so they can have full access to their personal contacts and playlists. Connected car services will eventually make its way to the broader car market where embedded connections and embedded systems supporting these connections will begin to leverage various needs to integrate traditional desperate signals into a more centrally managed console.

Proliferation of the stack

The arrow of design for connected cars will demand more development, bolstering the concept that software and embedded systems factored with newly-introduced actuators and sensors will become more prevalent. We’re talking about “software on wheels,” “SoC on wheels,” and “secured mobility.”

Design wise, the cost-effective trend will still remain with performance embedded systems. Many new cars may have extremely broad range of sensor and actuator‑based IoT designs which can be implemented on a single compact certified wireless module.

The arrow for connected cars will demand more development bolstering the concept that software and embedded systems factored with newly introduced actuators & sensors will become more prevalent; “software on wheels”, “SoC on wheels” and “secured mobility”.

Similarly, having fastest startup times by performing the task with a high-performance MCU vs MPU, is economic for a designer. It can not only reduce significant bill of materials cost, development resources, sculpted form factor, custom wireless design capabilities, but also minimize the board footprint. Aside from that, ARM has various IoT device development options, offering partner ecosystems with modules that have open standards. This ensures ease of IoT or connected car connectivity by having type approval certification through restrictive access to the communications stacks.

Drivers will be prompted with new end user applications — demand more deterministic code and processing with chips that support the secure memory capacity to build and house the software stack in these connected car applications.

Feature upon feature, layer upon layer of software combined with characteristics drawn from the events committed by drivers, tires, wheels, steering, location, telemetry, etc. Adapted speed and braking technologies are emerging now into various connected car makes, taking the traditional ABS concept to even higher levels combined with intelligence, along with controlled steering and better GPS systems, which will soon enable interim or cruise hands-free driving and parking.

Connected Car Evolution

Longer term, the technological advances behind the connected car will eventually lead to self-driving vehicles, but that very disruptive concept is still far out.

Where lies innovation and change is disruption

Like every eventual market disruption, there will be the in-between development of this connected car evolution. Innovative apps are everywhere, especially the paradigm where consumers have adopted to the seamless transitional experiences offered by apps and smartphones. Our need for ubiquitous connectivity and mobility, no matter where we are physically, is changing our vehicles into mobile platforms that want us users to seamlessly be connected to the world. This said demand for connectivity increases with the cost and devices involved will become more available. Cars as well as other mobility platforms are increasingly becoming connected packages with intelligent embedded systems. Cars are offering more than just entertainment — beyond providing richer multimedia features and in-car Internet access.  Further integration of secure and trusted vital data and connectivity points (hardware security/processing, crypto memory, and crypto authentication) can enable innovative navigation, safety and predictive maintenance capabilities.

Carmakers are worried about recent hacks,  especially with issues of security and reliability, making it unlikely that they will be open to every kind of app.  They’ll want to maintain some manufactured control framework and secure intrusion thwarting with developers, while also limiting the number of apps available in the car managing what goes or conflicts with the experience and safety measures.  Importantly, we are taking notice even now. Disruption comes fast, and Apple and others have been mentioned to enter this connected car market. This is the new frontier for technological equity scaling and technology brand appeal. Much like what we seen in the earlier models of Blackberry to smartphones, those late in the developmental evolution of their platforms may be forced adrift or implode by the market.

No one is arguing it will happen. Eventually, self-driving cars will arrive.  But for now, it remains a futuristic concept.

What can we do now in the invention, design and development process?

The broader output of manufactured cars will need to continue in leveraging new designs that take in more integration of traditional siloed integration vendors so that the emergence of more unified and centrally managed embedded controls can make its way. Hence, the importance now exists in the DNA of a holistically designed platform fitted with portfolio of processors and security to take on new service models and applications.

This year, we have compiled an interesting mixture of technical articles to support the development and engineering of car access systems, CAN and LIN networks, Ethernet in the car, capacitive interfaces and capacitive proximity measurement.

In parallel to the support of helping map toward the progress and evolution of the connected car, a new era of design exists. One in which the  platform demands embedded controls to evenly match their design characteristics and application use cases. We want to also highlight the highest performing ARM Cortex-M7 based MCU in the market, combining exceptional memory and connectivity options for leading design flexibility. The Atmel | SMART ARM Cortex-M7 family is ideal for automotive, IoT and industrial connectivity markets. These SAM V/E/S family of microcontrollers are the industry’s highest performing Cortex-M microcontrollers enhancing performance, while keeping cost and power consumption in check.

So are you designing for the latest automotive, IoT, or industrial product? Here’s a few things to keep in mind:

  • Optimized for real-time deterministic code execution and low latency peripheral data access
  • Six-stage dual-issue pipeline delivering 1500 CoreMarks at 300MHz
  • Automotive-qualified ARM Cortex-M7 MCUs with Audio Video Bridging (AVB) over Ethernet and Media LB peripheral support (only device in the market today)
  • M7 provides 32-bit floating point DSP capability as well as faster execution times with greater clock speed, floating point and twice the DSP power of the M4

We are taking the connected car design to the next performance level — having high-speed connectivity, high-density on-chip memory, and a solid ecosystem of design engineering tools. Recently, Atmel’s Timothy Grai added a unveiling point to the DSP story in Cortex-M7 processor fabric. True DSPs don’t do control and logical functions well; they generally lack the breadth of peripherals available on MCUs. “The attraction of the M7 is that it does both — DSP functions and control functions — hence it can be classified as a digital signal controller (DSC).” Grai quoted the example of Atmel’s SAM V70 and SAM V71 microcontrollers are used to connect end-nodes like infotainment audio amplifiers to the emerging Ethernet AVB network. In an audio amplifier, you receive a specific audio format that has to be converted, filtered, and modulated to match the requirement for each specific speaker in the car. Ethernet and DSP capabilities are required at the same time.

“The the audio amplifier in infotainment applications is a good example of DSC; a mix of MCU capabilities and peripherals plus DSP capability for audio processing. Most of the time, the main processor does not integrate Ethernet AVB, as the infotainment connectivity is based on Ethernet standard,” Grai said. “Large SoCs, which usually don’t have Ethernet interface, have slow start-up time and high power requirements. Atmel’s SAM V7x MCUs allow fast network start-up and facilitate power moding.”

Atmel has innovative memory technology in its DNA — critical to help fuel connected car and IoT product designers. It allows them to run the multiple communication stacks for applications using the same MCU without adding external memory. Avoiding external memories reduces the PCB footprint, lowers the BOM cost and eliminates the complexity of high-speed PCB design when pushing the performance to a maximum.

Importantly, the Atmel | SMART ARM Cortex-M7 family achieves a 1500 CoreMark Score, delivering superior connectivity options and unique memory architecture that can accommodate the said evolve of the eventual “SoC on wheels” design path for the connected car.

How to get started

  1. Download this white paper detailing how to run more complex algorithms at higher speeds.
  2. Check out the Atmel Automotive Compilation.
  3. Attend hands-on training onboard the Atmel Tech on Tour trailer. Following these sessions, you will walk away with the Atmel | SMART SAM V71 Xplained Ultra Evaluation Kit.
  4. Design the newest wave of embedded systems using SAM E70, SAM S70, or SAM V70 (ideal for automotive, IoT, smart gateways, industrial automation and drone applications, while the auto-grade SAM V70 and SAM V71 are ideal for telematics, audio amplifiers and advanced media connectivity).

IMG_3659

[Images: European Commission, GSMA]

Single chip MCU + DSP architecture for automotive = SAM V71


Automotive apps are running in production by million units per year, and cost is a crucial factor when deciding on an integrated solution.


It’s all about Cost of Ownership (CoO) and system level integration. If you target automotive related application, like audio or video processing or control of systems (Motor control, inverter, etc.), you need to integrate strong performance capable MCU with a DSP. In fact, if you expect your system to support Audio Video Bridging (AVB) MAC on top of the targeted application and to get the automotive qualification, the ARM Cortex-M7 processor-based Atmel SAMV70/71 should be your selection: offering the fastest clock speed of his kind (300 MHz), integrating a DSP Floating Point Unit (FPU), supporting AVB and qualified for automotive.

Let’s have a closer look at the SAM V71 internal architecture, shall we?

A closer look at Atmel | SMART ARM based Cortex M7 - SAMV71 internal architecture.

A closer look at Atmel | SMART ARM based Cortex M7 – SAMV71 internal architecture.

When developing a system around a microcontroller unit, you expect this single chip to support as many peripherals as needed in your application to minimize the global cost of ownership. That’s why you can see the long list of system peripherals (top left of the block diagram). Meanwhile, the Atmel | SMART SAM V71 is dedicated to support automotive infotainment application, e.g. Dual CAN and Ethernet MAC (bottom right). If we delve deeper into these functions, we can list these supported features:

  • 10/100 Mbps, IEEE1588 support
  • MII (144-pin), RMII (64-, 100, 144-pin)
  • 12 KB SRAM plus DMA
  • AVB support with Qav & Qas HW support for Audio traffic support
  • 802.3az Energy efficiency support
  • Dual CAN-FD
  • Up to 64 SRAM-based mailboxes
  • Wake up from sleep or wake up modes on RX/TX

The automotive-qualified SAM V70 and V71 series also offers high-speed USB with integrated PHY and Media LB, which when combined with the Cortex-M7 DSP extensions, make the family ideal for infotainment connectivity and audio applications. Let’s take a look at this DSP benchmark:

DSP bench-Atmel-SAM-Cortex-M7

ARM CM7 Performance normalized relative to SHARC (Higher numbers are better).

If you are not limited by budget consideration and can afford integrating one standard DSP along with a MCU, you will probably select the SHARC 21489 DSP (from Analog Devices) offering the best-in-class benchmark results for FIR, Biquad and real FFT. However, such performance has a cost, not only monetarily but also in terms of power consumption and board footprint — we can call that “Cost of Ownership.” Automotive apps are running in production by million units per year, and cost is absolutely crucial in this market segment, especially when quickly deciding to go with an integrated solution.

To support audio or video infotainment application, you expect the DSP integrated in the Cortex-M7 to be “good enough” and you can see from this benchmark results that it’s the case for Biquad for example, as ARM CM7 is equal or better than any other DSP (TI C28, Blackfin 50x or 70x) except the SHARC 21489… but much cheaper! Good enough means that the SAMV70 will support automotive audio (Biquad in this case) and keep enough DSP power for Ethernet MAC (10/100 Mbps, IEEE1588) support.

Ethernet AVB via Atmel Cortex M7

Ethernet AVB Architectures (SAM V71)

In the picture above, you can see the logical SAM V71 architectures for Ethernet AVB support and how to use the DSP capabilities for Telematics Control Unit (TCU) or audio amplifier.

Integrating a DSP means that you need to develop the related DSP code. Because the DSP is tightly integrated into the ARM CM7 core, you may use the MCU development tools (and not specific DSP tools) for developing your code. Since February, the ATSAMV71-XULT (full-featured Xplained board, SAM V71 Xplained Ultra Evaluation Kit with software package drivers supporting basic drivers, software services, libraries for Atmel SAMV71, V70, E70, S70 Cortex-M7 based microcontrollers) is available from Atmel. As this board has been built around the feature-rich SAM V71, you can develop your automotive application on the same exact MCU architecture as the part going into production.

SAMV71 Ultra Xplained - Atmel ARM Cortex M7

Versatility and Integrated DSP built into the ARM CM7 core allows for MCU development tools to be used instead of having to revert to specific DSP tools. You can develop your automotive application on exactly the same MCU architecture than the part going into production.

Interested? More information on this eval/dev board can found here.


This post has been republished with permission from SemiWiki.com, where Eric Esteve is a principle blogger as well as one of the four founding members of SemiWiki.com. This blog first appeared on SemiWiki on April 29, 2015.

Atmel’s new car MCU tips imminent SoC journey


The fact that these MCUs are targeting highly-sophisticated connected car applications like infotainment and ADAS means that the journey toward bigger and more powerful chips is now inevitable.


The automotive industry has reached a new era marked by giant initiatives like infotainment, connected car and semi-autonomous vehicles. And, no one seems more excited than the MCU guys who have been a part and parcel of in-car electronics for the past two decades. However, the humble microcontroller is going through a profound makeover in itself in order to come to terms with the demands of the connected car environment.

Take Atmel Corporation, one of the top MCU suppliers, who has launched its SAM DA1 family of microcontrollers at Embedded World 2015 in Nuremberg, Germany. The automotive-grade ARM Cortex-M0+-based MCUs come with capacitive touch hardware support for human-machine interface (HMI) and local interconnect network (LIN) applications. The SAM DA1 series integrates peripheral touch controller (PTC) for capacitive touch and eliminates the need for external components while minimizing CPU overhead. The feature is aimed at capacitive touch button, slider, wheel and proximity sensing applications.

Moreover, SAM DA1 microcontrollers offer up to 64KB of Flash, 8KB of SRAM and 2KB read-while-write Flash. The other key features of SAM DA1 series include 45 DMIPS and up to six serial communication interface (SERCOM), USB and I2S ports. SERCOM is configurable to operate as I2C, SPI or USART, which gives developers flexibility to mix serial interfaces and have greater freedom in PCB layout.

Atmel | SMART SAM DA1 ARM based Cortex-M0+  microcontrollers

Atmel | SMART SAM DA1 ARM based Cortex-M0+ microcontrollers

The automotive-grade MCUs — operating at a maximum frequency of 48MHz and reaching a 2.14 Coremark/MHz — are qualified to the AEC Q-100 Grade 2 (-40 to +105degreeC). According to Matthias Kaestner, VP of Automotive at Atmel, the company is targeting the SAM DA1 chips for in-vehicle networking, infotainment connectivity and body electronics.

Atmel-Automotive-Touc-Surface-Demo-PTC demo board

Automotive touch surface demo at Embedded World 2015

The fact that the SAM DA1 devices are based on powerful ARM cores clearly shows a trend toward more performance and the ability to run more tasks on the same MCU. The Cortex-M0+ processor design comes with a two-stage pipeline that improves the performance while maintaining maximum frequency. Moreover, it supports a new I/O interface that allows single cycle accesses and enables faster I/O port operations.

That’s no surprise because the number of electronic control units (ECUs) is on the rise amid growing momentum for connected car features like advanced driver assistance systems (ADAS). However, a higher number of ECUs will make the communication among them more intense; so automotive OEMs want to reduce the number of ECUs while they want more value from the MCU.

Moreover, car vendors want to bring down the number of ECUs to avoid complexity within the larger car network. The outcome of this urge is the integration of more performance and functionality onto the MCU. Each ECU has at least one microcontroller.

Atmel and the Evolution of MCU

Atmel’s SAM DA1 device is another testament that the boundaries between MCU and SoC platforms are blurring. The fact that these MCUs are targeting highly sophisticated connected car applications like infotainment and ADAS means that the journey toward bigger and more powerful chips is now inevitable.

Atmel is an MCU company, and this product line has played a crucial role in its transformation that started in the late 2000s. At the same time, however, the San Jose, California–based chipmaker seems fully aware of the critical importance of the system-level solutions. Atmel calls the SAM DA1 family of chips MCUs; however, its support for more peripherals, larger memories and intelligent CPU features show just how much the MCU has changed over the course of a decade.

 Memory Protection Unit in Cortex-M0+

Memory Protection Unit in Cortex-M0+

Atmel has a major presence in the automotive market with its MCUs and touch controllers being part of the top-ten car vendors. It’s interesting to note that, beyond its MCU roots, Atmel has a lot of history in automotive electronics as well. Atmel was one of the first chipmakers to enter the automotive market.

Moreover, Atmel bought the IC division of Temic Telefunken Microelectronic GmbH for approximately $110 million back in 1998. Telefunken was an automotive electronics pioneer with an early success in electronic ignition chips that made way into Volkswagen cars back in 1980.

The release of SAM DA1 series marks a remarkable opportunity as well as a crafty challenge for Atmel in the twilight worlds of MCU and automotive electronics. Tom Hackenberg, a senior analyst at IHS, calls the phenomenon ‘SoC on wheels.’

Hackenberg says that the automotive industry consumed approximately a third of all MCUs shipped in 2013. However, now there is an SoC on the road, the brain behind the connected car, and it commands a deeper understanding of the AEC-Q100 standard for automotive quality and ISO 26262 certification for car’s functional safety.

Atmel’s AvantCar touchscreen demo at the CES 2015

Atmel’s AvantCar touchscreen demo at the CES 2015

The integration of touch controller into SAM DA1 chips can be an important value proposition for the car OEMs who are burning midnight oil to develop cool infotainment platforms for their newer models. Next, while AEC Q100 Grade 2 qualification is a prominent part of the SAM DA1, Atmel might have to consider augmenting the ISO 26262 certification for functional safety, a vital requirement in ADAS and other connected car features.


Majeed Ahmad is author of books Smartphone: Mobile Revolution at the Crossroads of Communications, Computing and Consumer Electronics and The Next Web of 50 Billion Devices: Mobile Internet’s Past, Present and Future.

 

5 IoT challenges for connected car dev

Growth in adoption of connected cars has exploded as of late, and is showing no signs of slowing down, especially the vehicle-to-infrastructure and vehicle-to-retail segments. As adoption grows exponentially, the challenges in how we develop these apps emerge as well.

One of the biggest challenges to consider will be connectivity, and how we connect and network the millions of connected cars on the road. How can we ensure that data gets from Point A to Point B reliably? How can we ensure that data transfer is secure? And how do we deal with power, battery, and bandwidth constraints?

connected car

1. Signaling

At the core of a connected car solution is bidirectional data streaming between connected cars, servers, and client applications. Connected car revolves around keeping low-powered, low-cost sockets open to send and receive data. This data can include navigation, traffic, tracking, vehicle health and state (Presence); pretty much anything you want to do with connected car.

Signaling is easy in the lab, but challenging in the wild. There are an infinite amount of speed bumps (pun intended) for connected cars, from tunnels to bad network connectivity, so reliable connectivity is paramount. Data needs to be cached, replicated, and most importantly sent in realtime between connected cars, servers, and clients.

2. Security

Then there’s security, and we all know the importance of that when it comes to connected car (and the Internet of Things in general). Data encryption (AES and SSL), authentication, and data channel access control are the major IoT data security components.

NHTSA-Connected-Cars

In looking at data channel access control, having fine-grain publish and subscribe permissions down to individual channel or user is a powerful tool for IoT security. It enables developers to create, restrict, and close open channels between client apps, connected car, and servers. With connected car, IoT developers can build point-to-point applications, where data streams bidirectionally between devices. Having the ability to grant and revoke access to user connection is just another security layer on top of AES and SSL encryption.

3. Power and Battery Consumption

How will we balance the maintaining of open sockets and ensuring high performance while minimizing power and battery consumption? As with other mobile applications, for the connected car, power and battery consumption considerations are essential.

M2M publish/subscribe messaging protocols like MQTT are built for just this, to ensure delivery in bandwidth, high latency, and unreliable environments. MQTT specializes in messaging for always-on, low-powered devices, a perfect fit for connected car developers.

4. Presence

Connected devices are expensive, so we need a way to keep tabs on our connected cars, whether it be for fleet and freight management, taxi dispatch, or geolocation. ‘Presence’ functionality is a way to monitor individual or groups of IoT devices in realtime, and has found adoption across the connected car space. Developers can build custom vehicle states, and monitor those in realtime as they go online/offline, change state, etc.

connected car

Take fleet management for example. When delivery trucks are out on route, their capacity status is reflected in realtime with a presence system. For taxi and dispatch, the dispatch system knows when a taxi is available or when its currently full. And with geolocation, location data is updated by the millisecond, which can also be applied to taxi dispatch and freight management.

5. Bandwidth Consumption

Just like power and battery, bandwidth consumption is the fifth connected car challenge we face today. For bidirectional communication, we need open socket connections, but we can’t have them using massive loads of bandwidth. Leveraging M2M messaging protocols like the aforementioned MQTT lets us do just that.

Building the connected car on a data messaging system with low overhead, we can keep socket connections open with limited bandwidth consumption. Rather than hitting the servers once multiple times per second, keeping an open socket allows data to stream bidirectionally without requiring requests to the server.

Solution Kit for Connected Cars

The PubNub Connected Car Solution Kit makes it easy to reliably send and receive data streams from your connected car, facilitating dispatch, fleet management applications and personalized auto management apps. PubNub provides the realtime data stream infrastructure that can bring connected car projects from prototype to production without scalability issues.

Hot August Nights Fever? Atmel Automotive Infographic

People love their cars. It’s one of those near universal facts. Whether they live in big cities or small rural hamlets, drive a mini or a hummer, there is just something about the sexy vroom vroom of an engine that excites people on a primal level.

Perhaps it’s the destructive force in us that is drawn to what is basically a controlled explosion on wheels. Perhaps it’s something to do with an automobile’s sleek and contoured chassis – or the human need for speed.

Or maybe, it’s because there is a certain zen to be found in tinkering with an engine. Of souping up and optimizing an already lean, mean machine, and making it purr. Somewhere in all of us is an engineer who simply wants to solve puzzles – and what greater puzzle to solve than the many moving parts to be found under the hood?

We at Atmel are especially passionate about the automotive space, having been one of the first semiconductor companies to enter the market, embracing both the productive and the creative passion from the get-go.

Atmel_August Auto_Final

Telefunken (the pre- predecessor of Atmel Automotive) was founded as early as 1903, while the Heilbronn fab in Germany, acquired by Atmel in the 1980’s, was founded way back in 1960.

Atmel’s first success in automotive was (rather fittingly) the electronic ignition IC which, in 1979/1980, was installed in every Volkswagen car.

Another early milestone along Atmel’s automotive roadmap was, ironically, braking. A start-to-stop scenario, so to speak.

The market for connected vehicles is expected to grow to a whopping $53 billion by 2018, with consumers demanding more and more connectivity each year.

A study by Deloitte in 2011 determined that 46% of people between the ages of 18-24 cited connectivity as being “extremely important” to them when it came to cars, with 37% wanting to stay as connected as possible while in their vehicles. A resounding 65% identified remote vehicle control as an important feature in their next automotive purchase; while 77% favored remote diagnostics minimizing dealer visits. And let’s face it, who can blame them?

A 2013 study by Cisco went even further, positing that Vehicle-to-vehicle (V2V) communications could enable cars to detect each other’s presence and location, helping avoid accidents, lower road costs and decrease carbon emissions. The report also found that intelligent cars would lead to 7.5% less time wasted in traffic congestion and 4% lower costs for vehicle fuel.

With over 1 billion passenger cars careening through the world’s streets already, increased digitization can’t come fast enough!

Today, Atmel supplies all 10 of the top 10 tier 1 automotive electronic suppliers in the world, not only with microcontrollers (MCUs), but with touch sensor technology too. Indeed, Atmel’s latest touch innovation, the bendable, flexible, printed wonder that is Xsense, has now been fully qualified and is ready to ramp, meaning sexy curved glass dashboards are closer than you’d imagine… Not bad for a feature originally developed as a piece of wood attached to the front of a horse drawn carriage to prevent mud from splattering the driver!

Atmel is also renowned for being a leading car access supplier, meaning we make the chips that enable cool remote keyless entry (RKE) systems with immobilizers, to reduce the risk of anyone stealing your steel beauty away from you. In fact, Atmel has already delivered over 250 Million ICs for this specific application, so that’s a whole lot of key fobs! Speaking of key fobs, here’s a fun fact; holding a remote car key to your head doubles its range because the human skull acts as an amplifier.

Moving from cool keyfobs to total hotness, it’s also worth noting that Atmel sells some of the highest temperature resistant parts in the market, some of which can handle heat of up to 200°C.

Last, but certainly not least, Atmel boasts the world’s largest portfolio of Local Interconnect Network (LIN) devices, for communication between components in vehicles. The firm’s devices have OEM approvals from all major car manufacturers worldwide, which is certainly something to be proud of.

So next time you find yourself on that long and winding road, kicking into high gear and hugging those curves, spare a thought for the components, because when it comes to cars, the devil really is in the details.

Defining the LF Driver’s Main Parameters in Automotive PEPS Systems

By Dr. Jedidi Kamouaa

Passive entry passive start (PEPS) systems, already well established in the high-end car market, are the latest trend in mid-price vehicles. Strategy Analytics anticipates annual demand for PEPS systems to reach almost 19 million units by 2016. This trend is fueled by cost savings from a reduction in the number of coils per vehicle, the greatest contributor to system cost.

PEPS system design presents a number of challenges:

  • Generation of high drive current and, thus, the low-frequency (LF) magnetic field required to detect the key fob inside the vehicle or in the near vicinity
  • Drive-current regulation to allow reliable receive signal strength indicator (RSSI) measurement
  • Protection under thermal stress conditions and electrical diagnostics
  • Reduction in electromagnetic radiation
  • PEPS system speed

 A key part of PEPS systems is the LF driver. The Atmel ATA5279C multichannel LF antenna driver IC includes technical features to meet PEPS system requirements. It operates alongside the Atmel ATA5791 single-chip key fob controller, integrating the RF transmitter.

When developing an LF antenna driver system, you’ll need to consider:

  • Capability to generate sufficient magnetic field to detect the key fob inside the vehicle or in the vicinity of the vehicle
  • Use of a regulation loop of the drive current for reliable field strength and thus RSSI measurement
  • Protection under thermal stress conditions and electrical diagnostics
  • Electromagnetic radiation
  • The interface with the host microcontroller
  • Thermal factors

With the need for cost savings, car makers also expect the LF driver to perform the immobilizer backup function, which requires the merging of the immobilizer and LF driver functions, multiplexing one of the antennas and thus eliminating one coil (a major cost contributor). This merger allows the immobilizer base station coil in the steering lock cylinder to be removed, and the resulting change in car architecture will enable significant cost savings that should further increase PEPS system adoption.

For diagrams and detailed information about how to define the LF driver, see the article “How to Define the LF Driver’s Key Parameters in Automotive PEPS Systems.”

Creating an RF RSSI Sniffer Tool for Car Access Systems

By Chris Wunderlich and George Rueter

By reconfiguring the Atmel ATA5830N UHF transceiver chip through a simple method using its Flash program capability, you can create a received signal strength indicator (RSSI) monitoring tool that you can use both in a lab setting as well as in a vehicle.

The ATA5830N chip integrates a high-performance UHF transceiver with a low-power Atmel AVR 8-bit microcontroller. The device also has 6KB of Flash memory—this Flash memory space is what you can use to develop an application for an RSSI monitor that generates USART-formatted messages with RSSI data.  

To create the RSSI monitoring tool, we developed the software using the ATAK51002-V1 evaluation kit, a +5V power supply and the RF signal input. The kit includes a reference design that consumes about 9mA when running our application—low enough to support battery operation. Once we powered up the reference design, we awakened the ATA5830N device by momentarily connecting any of the “npwron” pins to ground or the “pwron” pin to +5V. Once the part was awake and active, we didn’t need to provide additional input and the RSSI data was available at PC3 pin 17.

Using the EEPROM configuration file, we programmed desired radio parameters into the part. You can select these values using an Excel spreadsheet tool that automatically generates the EEPROM file. Once we programmed the values into the EEPROM, the application of power automatically initiated the self-configuration and execution of the Flash application program.

You can use the resulting application for several common RF engineering tasks, including RF environment analysis, performance tuning of the receiver section, RF component selection and antenna performance evaluation. For diagrams and the full details about creating the RSSI tool, read our full article, “RF RSSI Sniffer Tool for Car Access Systems.”