our cars have long been software defined. not just a high level software that they put now. but for a long time there has been chip that is responsible for a LOT of stuff, brakes, steering, abs, traction control etc.
It should be said, though, that brakes and steering are still possible via plain mechanics in hopefully all cars. There's usually electronics to amplify it, meaning your car brakes harder and steers more easily without you putting in full force, but if that fails, it should degrade gracefully.
Had that happen in my old car a few years ago, that the whole engine and everything just turned off while I was rolling downhill. It was a bit of a panic moment, when suddenly the brake pedal and steering wheel took a lot more force to move, but the instinct reaction to just put in that force worked.
Its pretty exciting too. With EVs it makes even more sense and hopefully means we can see more competition in the market since it means more modular vehicles (imagine if every steering column could work for every drive train for example).
As someone who's working with Elektrobit and software produced by them, both are hot, steaming garbage. I'm not envying anyone who swallows this bait. Mildly put, Elektrobit underdelivers both on time and quality of their commitments. I hope at least they're cheap but I don't have visibility in that area.
Many things are based on Linux that does not mean anything for the customer, because those end up being heavly modified version being able to run just on this specific chip and only support vendor provided software on top.
My TV runs Android, so Linux kernel, but can I reinstall it and run some Debian with Kodi bypassing all the spyware Android crap? Heck no.
One of the more interesting paradigm shifts underway in the automotive industry is the move to software-defined vehicles.
Instead, you'll find a small number of domain controllers—what the automotive industry is choosing to call "high performance compute" platforms—each responsible for a different set of activities.
You should expect to see this approach more often as automakers develop new platforms, and there are already examples from Audi, BMW, McLaren, and Porsche on the road or arriving shortly.
"The beauty of our concept is that you don't even need to safety-qualify Linux itself," said Moritz Neukirchner, a senior director at Elektrobit overseeing SDVs.
"So in the end, since we take Linux out of the certification path and make it usable in a safety-related context, we don't have any problems in keeping up to speed with the developer community," he explained.
And this is the kind of challenge that you're being put up to if you want to participate in that speed of innovation of an open source community as rich as that of Linux and now want to combine this with safety-related applications," Neukirchner said.
The original article contains 688 words, the summary contains 183 words. Saved 73%. I'm a bot and I'm open source!
As much as I love Linux and the idea of open operating systems in general, I just flat out don't want an OS in my car of all things!
Everyone says it's convenient for in-car entertainment but literally everyone I know with an "infotainment" system in their car just bluetooth their phone to it anyway. I can do that with the cheap headunit I bought from eBay for my 2003 Mitsubishi. And it's just a single button press instead of having to use a touch menu...
In a car with numerous driver aids, a 15 inch touchscreen, 40 cameras and a laser guided cruise missile, yes I agree, you want an OS.
I personally want a car where the "smartest" aspect is the fuel delivery system. Power steering, brakes, etc can all be done mechanically. I'm not a fan of advanced assists as I've seen far, FAR too many people become reliant on them and turn into lazy, dangerous drivers. I strongly believe that all base models should still be sold with zero assists, mainly to encourage people to actually act like they're licensed to operate a piece of heavy equipment in a public space.
While I agree with the sentiment, I have accepted that the simple way to make "things" work now is to leverage the cheap computing that is ubiquitous. That headunit is likely now built on a SoC or some embedded OS and is easier and cheaper because of it.
Functionally we need regulations and safeguards in place that maintain the accountability for making the choice to use and build an OS as a life safety device that also serves Bluetooth audio. If the cost of supporting it, or failing to properly develop it, then perhaps the choice to make it dumb will become more adopted. Other economic forces are more likely to play out, but it's a possibility that we can reinforce by what we buy and signal.
The safety-critical features tend to be on systems separate from the infotainment ones, in part because it's a lot easier to safety-certify something simpler and more dedicated to automotive tasks. You won't die if your AC and Taylor Swift stop working.
Not buying it. The colossal attack surface of a giant monolithic kernel should not be controlling an automobile. No offense to Linux or anyone who works on it, it's great, you just can't rely on it with your life. It was never designed to be.
then remove that "colossal attack surface" by compiling a custom kernel and utilities that only includes the features the product needs. create a system tuned to the exact product to make it extremely reliable. almost everything electronic you see in commercial use is Linux because of this very fact.
Many medical devices run Linux.
Toyota, Tesla, Audi, Mercedes, and Hyundai vehicles use Linux.
you certainly can rely on it for your life and nearly every electronic device you use will use some derivative of it.
Can you please name at least one product that directly uses and relies on Linux for a safety-critical system? Those vehicles only use Linux for the ICE and not the ECU. And those medical devices are not directly controlling patient-facing instruments via Linux as far as I know.
I come from a MCU background and feel the same way. Linux kernel is for consumer level stuff. For serious machinery, I choose a real-time OS like FreeaRTOS. Less code, and more low level code makes it easier to review, maintain, and have less chance to break.
Ive been seeing Linux take a more controler of controllers kind of role. Handling updates, networking, complex logic, logging, metric, etc.
It'll be interesting to see where it goes. On one hand ASICs, FPGAs, and microcontroller are getting easier than ever to program, its still not as easier as having a full Linux OS to build on.