Huh? Since it requires new hardware then it can’t be done with an over-the-air update.
I presume if were designed with over-the-air updates in mind, it wouldn’t have been coded in hardware in the first place. (Right, is that what’s happening? I’m not a computer expert, but I assume the wonky code is located somewhere non-writable, as opposed to some flashable firmware or something. Anybody help me out on this detail?)
Guess I’ll keep my 2016 CX-5 outta there.
@Dr.Strangelove was saying that it could more sensibly have been designed for over-the-air updates, but people don’t want that. And this is the alternative.
Exactly. At some level, I get the distaste for OTA updates–what if they make things worse? Doesn’t this just allow them to write buggier code in the first place? Etc. Those arguments aren’t completely wrong, but the fact is that modern software stacks are too complicated these days to get perfect at the outset. Having to replace a hardware module–or even having a service appointment at all–is a dumb way to fix the inevitable bugs.
I’ve seen some cases where end users could load a USB stick with a new firmware to load into their device. That’s not too bad an alternative, and certainly better than the apparent situation here.
Here’s where I pull my sexagenarian card and ask exactly who decided we wanted radio that needs firmware updates.
I have an LG OLED TV that runs WebOS, which is their Linux-based operating system. Yesterday it updated the software and after I was required to accept the user agreement. Something of a novelty to have to do so to watch TV.
Your radio has been running software since the 80s.
RDS (Radio Data System) is the standard for sending you digital information like song titles and station names alongside analog FM broadcasts. It’s been around since 1984.
The bug here is about HD radio, which gives extra metainformation (like pictures) due to the improved bandwidth, but the same kind of bug could have been around for decades.
As a Mazda owner, I don’t mind. I listen to MPR’s news station about half the time and switch to The Current (also MPR) the other half.
I’m not any sort of expert, but I find it hard to believe that a radio like this has software.
Yes, some analog radios still exist (though it wouldn’t shock me if even the one you’ve linked to has some microcontroller in there somewhere, if only in the power supply). We’re talking car radios here, and I’m presuming ones that aren’t specifically designed to be some kind of throwback. If it has a digital display, a CD player, more than a handful of buttons, etc. (let alone anything like a USB port or MP3 support)–then it’s running software. Though it may be called firmware to reflect that it’s not easily changed after production.
The OTA updates are a fairly recent development, doubt that Mazda was doing that in 2016. Your “radio” is no longer just a radio, its an infotainment center that interfaces with many other modules such as HVAC controls, clocks, CD, satillite radio, warning sounds, audio amplifiers, the instrument cluster, cameras and DVD systems. The fact that it requires a hardware swap tells me it must be a chip malfunction, likely the tuner chip.
The SW files that handle all of the different configurations that a head unit is subject to is huge and requires years of developement and support. It also involves that it meets the requirements of several global regions, its not a minor undertaking which is why there is only a handful of suppliers that provide them to the automotive OEMs.
When I worked at Bose they tried to develope their own head unit and actually sold one generation to Ferarri and they quickly decided not to pursue that business. Too much support required for too little profit I suppose.
Good thing then that our 2010 Fit is the no-nav base model.
Unlikely. As noted above, the bug comes from receiving an image file without an extension. From Mazda:
Between 1/24-1/31, a radio station in the Seattle area sent image files with no extension (e.g., missing .jpeg or .gif), which caused an issue on some 2014-2017 Mazda vehicles with older software. Mazda North American Operations (MNAO) has distributed service alerts advising dealers of the issue
That’s not a tuner chip issue; that’s the software/firmware deciding what to do with an image type and borking itself when finding something it can’t handle.
OTA updates have been difficult for most automakers due to them outsourcing almost everything, and those suppliers often doing their own outsourcing. No one controls the full software stack; hence no one can perform updates. They screwed up by building systems that were completely dependent on software but without the ability to do easy updates.
I didn’t dig into the root cause because its too much like work, which I just left. 
But yeah, a misformatted file name could cause issues. So much can go wrong its a wonder cars even get out of the driveway.
So apparently some Mazda dealers are saying it requires a hardware swap, but I find it hard to believe that it really requires a hardware swap. I suspect the service managers saying that don’t really understand the problem and are just defaulting to “just replace it” because they don’t know what else to do. There has got to be a way to do some sort of “hard reset” on the thing and restore it back to its factory defaults, and perhaps do a fresh reinstall of the firmware. Basically the equivalent of wiping your hard drive and reinstalling Windows.
Dealers make more money doing HW swaps. If their techs cant get the SW fix to work they just swap parts because people want their car back and dealerships dont have time to deep dive into repairs.
They may not be using much new hardware. The dealer can swap the module with a known good one so the customer can leave quickly; then unbrick and reflash the module on their own time; then use that module for the next customer’s swap.
One would have thought in all these decades they could have made it ironclad.
… then one considers Windows, and realizes these guys are doing pretty darn well all things considered.
Heh, my oldfartastic fist shake was not solely at the car equipment but also at the guys on the broadcasting side who keep throwing out the latest and greatest that I’m not really sure anyone asked for.
Though I’m pretty sure my old 2009’s head unit would be impervious to the KUOW glitch, who knows what else could have gone wrong. (Though the CD changer was less than outstanding and once out of warranty I said, whatever, and just permanently plugged an iPod Nano [remember those?] into the AUX input.)
Perhaps, but it seems extremely weird that you can’t just reset the module yourself, like you can pretty much any other device that can possibly freeze or crash. Why wouldn’t there be that little button you can shove a pin into to reset it.
Sure, that wouldn’t fix the bug, but if the issue is fixed on the station’s side, the radio would still work.
Also, who came up with a standard that required filenames at all? The standard is to identify image types with their headers, and has been for decades now. And the filename would never be displayed to the user. Why isn’t it just a blob?