2004 to 2020 Mazda 3 Forum and Mazdaspeed 3 Forums banner

1 - 20 of 67 Posts

·
Registered
Joined
·
1 Posts
Discussion Starter #1
Hello,

today i wanted to install the v70. I pressed the Start-Stopp Button one time and successfully installed the failsafe package. After that i wanted to install the reinstall package but an error came up "Failed to validate package certificate". So i pressed the Start-Stopp Button another time so the ignition goes on and turned off the car. After that i tried to another time so pressed the Start-Stopp Button and the MZD comes up. Everything fine. I wanted to check the USB stick on computer if there is anything wrong. After that i tried another time. So i pressed the Start-Stopp Button one time and the Screen remains black.

Radio is still working and chaning the Volume works.

I've tried to reset the whole system over the settings menu. Nothing happens.
Also the soft reset (BACK + MUTE + NAV) changes nothing.

I've searched the forum for an solution and found out that there is way over SSH.
But without an tutorial.

Is there a way to safe my system or should the dealer do this thing?

Thanks for helping
 

·
Registered
Joined
·
326 Posts
Hello,

today i wanted to install the v70. I pressed the Start-Stopp Button one time and successfully installed the failsafe package. After that i wanted to install the reinstall package but an error came up "Failed to validate package certificate". So i pressed the Start-Stopp Button another time so the ignition goes on and turned off the car. After that i tried to another time so pressed the Start-Stopp Button and the MZD comes up. Everything fine. I wanted to check the USB stick on computer if there is anything wrong. After that i tried another time. So i pressed the Start-Stopp Button one time and the Screen remains black.

Radio is still working and chaning the Volume works.

I've tried to reset the whole system over the settings menu. Nothing happens.
Also the soft reset (BACK + MUTE + NAV) changes nothing.

I've searched the forum for an solution and found out that there is way over SSH.
But without an tutorial.

Is there a way to safe my system or should the dealer do this thing?

Thanks for helping
Sory to hear about that! But with your decrible, i think your CMU totally bricked... and it's very hard to recover...
 

·
Registered
Joined
·
569 Posts
Hello,

today i wanted to install the v70. I pressed the Start-Stopp Button one time and successfully installed the failsafe package. After that i wanted to install the reinstall package but an error came up "Failed to validate package certificate". So i pressed the Start-Stopp Button another time so the ignition goes on and turned off the car. After that i tried to another time so pressed the Start-Stopp Button and the MZD comes up. Everything fine. I wanted to check the USB stick on computer if there is anything wrong. After that i tried another time. So i pressed the Start-Stopp Button one time and the Screen remains black.

Radio is still working and chaning the Volume works.

I've tried to reset the whole system over the settings menu. Nothing happens.
Also the soft reset (BACK + MUTE + NAV) changes nothing.

I've searched the forum for an solution and found out that there is way over SSH.
But without an tutorial.

Is there a way to safe my system or should the dealer do this thing?

Thanks for helping

In this case you should post your question on a different thread instead of starting a new one since the most knowledgeable may not see to respond...specifically "Mazda Connect All firmware Version (Only for downloads)". It's usually on the first page of all the threads since it gets so many hits. That is where all of these questions get answered. Hopefully ASH8 will see your post and give you the verdict....warning, he is sort of a Soup Nazi kind of guy, but don't take it personally.
 

·
Treveloper
Joined
·
534 Posts
Hello,

today i wanted to install the v70. I pressed the Start-Stopp Button one time and successfully installed the failsafe package. After that i wanted to install the reinstall package but an error came up "Failed to validate package certificate". So i pressed the Start-Stopp Button another time so the ignition goes on and turned off the car. After that i tried to another time so pressed the Start-Stopp Button and the MZD comes up. Everything fine. I wanted to check the USB stick on computer if there is anything wrong. After that i tried another time. So i pressed the Start-Stopp Button one time and the Screen remains black.
Radio is still working and chaning the Volume works.
I've tried to reset the whole system over the settings menu. Nothing happens.
Also the soft reset (BACK + MUTE + NAV) changes nothing.
I've searched the forum for an solution and found out that there is way over SSH.
But without an tutorial.
Is there a way to safe my system or should the dealer do this thing?
Thanks for helping
Sory to hear about that! But with your decrible, i think your CMU totally bricked... and it's very hard to recover...
So you did brick your CMU you cannot turn the vehicle off during the update for any circumstances or you end up with a nice brick. The only way to recover will be with a serial connection and you will have to corrupt the fail safe so that it starts the update process over again from the beginning but you need a pretty much expert knowledge of what you are doing to pull that off because this guy only tells you why it happened but not too many details about how to fix it: JCI: "fail-safe" code that isn't
You might as well take it to the dealer because they already know that can happen.
 

·
Registered
Joined
·
468 Posts
You'll be fine. Just turn it on and off during a process that specifically says not to do that. Maybe this time apply a flame to it or a hammer. I believe these items are also not recommended to be applied during the update process.
 

·
Registered
Joined
·
21 Posts
CMU bricked repair

Hi,

Actually, your CMU is bricked. I did the exact same thing as you where my car was turned off just after installing the failsafe package. Luckily there is a way to recover, which is not so easy to do, bit it's quiet doable if you are not afraid to unmount the CMU, open it and plug some wires.

Full explanation:
Thanks to this website: http://www.2x4logic.com it saves me a lot of time to dig on how the system works. The CMU update process is indeed very badly designed, as it has plenty of failure points where it ends with a bricked device that will not boot anymore. The easiest way to do that is by shutting the CMU off after the failsafe package installation. Basically what happens is that a small flash chip that contains the boot program has a flag on it that decides on which system it has to boot. It can either be the normal Mazda system, or the «failsafe» software. When you install the failsafe update package without the 2nd reinstall package, the flash chip boot select mode is set to boot on the ibc1 partition, which does not match the current Mazda system. This ibc1 partition is updated by the reinstall package. So it’s bricked because it cannot boot anymore.
The easiest fix here is to change the boot select value on the flash chip to boot on ibc2 (the failsafe). This is normally done by the update process, after the reinstallation package is checked for integrity. Here we are going to do it by forcing the boot. It will start the «failsafe» installation software, that will tell us that installation fails and that we can retry by putting a USB key into the car with a correct reinstallation package. Then the installation will continue and finish.

Tutorial:
Here is a step by step tutorial on how to achieve this. Be aware that It can be hard to do this if you do not understand what you are doing. But in case your CMU is bricked (black screen after a failed upgrade or so) you have nothing to loose, right? Bringing the car to a dealer will not help, they will just charge you for a full CMU replacement, and that costs a lot…

The flash chip is placed on the back of the CMU’s PCB. It’s a NOR SPI Flash. The idea is to directly connect to this chip and use a raspberry pi (that has an SPI bus) to reprogram the memory.

Required hardware:
  • A raspberry pi
  • A Programmer Test Clip SOIC16 or 6x IC Test clips (I used test clips)
  • A breadboard to do the connections

On the raspberry pi, you need to install Raspbian (Lite version is ok). From a fresh install of Rasbian, setup the pi to have SPI enabled by running:
Code:
sudo raspi-config
(enable SPI in Interfacing Options*)
sudo reboot
Install some required tools:
Code:
sudo apt-get update
sudo apt-get install build-essential libusb-1.0-0-dev libusb-dev git wget curl libpci-dev
Get a newer version of flashrom:
Code:
git clone https://github.com/flashrom/flashrom
cd flashrom
make
sync
Shut the power off of the raspberry.

Now the raspberry pi is ready. Unmount the CMU from your car (look on youtube for video on how to do it, it’s easy), unscrew the PCB from the CMU and plug the wires from the raspberry to the flash chip like here (see attached pic) and http://www.2x4logic.com/mcbot-annotated.jpg

Turn the raspberry pi on. And check if the flash is detected:
Code:
cd flashrom
./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=8000
This will tell if a chip is detected or not. If not your wiring is not ok. When something is detected, flashrom may tell you that multiple different chips are detected. That’s because some chips from a same manufacturer can have the same protocol. You need to read the right device model from what is written on the chip. I had a MX25L6445E. I know that some other CMU may have a different chip model. It should also work if flashrom can detect it.

Then try to read the memory and do a backup:
Code:
./flashrom -r backup-cmu.bin -c "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" -V -p linux_spi:dev=/dev/spidev0.0,spispeed=8000
Carefully read what flashrom is doing to check of any failure. I had to use the option -c "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" to select the right chip model in flashrom as it was written when using the -p option (list all detected devices)

Once you have the backup, we modify the boot-select byte inside the file
Code:
cp backup-cmu.bin cmu-mod.bin
printf '\x00' | dd of=cmu-mod.bin bs=1 seek=65536 count=1 conv=notrunc
Now it’s time to write the modified file to the flash:
Code:
./flashrom -w cmu-mod.bin -c "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" -V -p linux_spi:dev=/dev/spidev0.0,spispeed=8000
Read back the flash to verify it worked
Code:
./flashrom -r cmu.bin -c "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F" -V -p linux_spi:dev=/dev/spidev0.0,spispeed=8000
Check if the file matches by verifying the checksum
Code:
sha1sum cmu.bin cmu-mod.bin
The checksum should match, if they do, the procedure is done. It’s time to unplug everything and put the CMU back in the car. The CMU should boot into the failsafe recovery system and ask you for a USB key with the reinstall package.

Good luck, and happy hacking! ;)
 

Attachments

·
Registered
Joined
·
1 Posts
A massive thanks to you raoulh! I bricked my CMU the same way but your instructions got me back on track. Firmware is updating now.

Thanks again for taking the time to provide these directions!
 

·
Registered
Joined
·
21 Posts
A massive thanks to you raoulh! I bricked my CMU the same way but your instructions got me back on track. Firmware is updating now.

Thanks again for taking the time to provide these directions!
You're welcome! Glad to hear that it worked for you ;)
 

·
Registered
Joined
·
3 Posts
Hello in the image with the CMU back/breadboard/raspberry PI what is the thing that is attached to the bottom of the breadboard? Is that necessary for this to work?
 

·
Registered
Joined
·
3 Posts
Hello I'm trying to reset the CMU NOR FLash with a RPi. I have a SOIC 16 test clip. I had a question. When i'm doing the breadboard plugins. Does the breadboard need a power supply? Or does the RPI being powered on supply the voltage through the breadboard to flash the chip? Sorry i'm not entirely sure about this and i keep getting an error of

"NO EEPROM/flash device found"

I'm not sure how else to do the wiring. I've tried it multiple ways... Thanks.
 

·
Registered
Joined
·
312 Posts
Hello I'm trying to reset the CMU NOR FLash with a RPi. I have a SOIC 16 test clip. I had a question. When i'm doing the breadboard plugins. Does the breadboard need a power supply? Or does the RPI being powered on supply the voltage through the breadboard to flash the chip? Sorry i'm not entirely sure about this and i keep getting an error of

"NO EEPROM/flash device found"

I'm not sure how else to do the wiring. I've tried it multiple ways... Thanks.
I have not checked the NOR chip pinout but 3.3v and ground are supplied from the red/black wires. On the photo the bottom item is a power supply but it is not connected to anything on the breadboard pins used by the RPI or CMU wiring. Here are two RPI pinout drawings.
 

Attachments

·
Registered
Joined
·
4 Posts
Part numbers and wiring diagram would be handy please Viên Tịnh
Programmer Testing Clip SOP 16 ebay
ebay.com/p/Programmer-Testing-Clip-SOP-16-SOP-SOIC-16-Dip16-Pin-IC-Test-Clamp-With-Cable/2131170762

USB BIOS EEPROM SPI FLASH Programmer CH341A 24 25 series
ebay.com/itm/USB-BIOS-EEPROM-SPI-FLASH-Programmer-CH341A-24-25-series-/301443899698

program and driver: karadev.net/basto/CH341A-programmer-software-1.29/CH341A-1.29-programmer-software.zip

conntecting :
 

·
Registered
Joined
·
3 Posts
Hi,

I'm in trouble. Much like everybody else here I managed to bust my CMU during a firmware upgrade. I would really appreciate the help in bring it back to life.

Do you have more detailed instructions on how to restore the software once I have the hardware all sorted out ?

Thanks,

Vio
 
1 - 20 of 67 Posts
Top