[Alma12]

Update: my CMU is working again! It seems my .bin file was corrupted or wrong. First time when I started the upgrade I had failsafe and reinstallation files with wrong checksums and maybe this wrong failsafe stored in Flash Memory. Later when I had the correct FW, the update failed again. Also the Testclip caused a lot of headache due to the wrong contacts. I measured 4-5 times the wires with multimeter to get the good contact, everything looked perfect but reprogramming the Flash Memory failed (I have 2 sets of Testclips and adapters). Finally I soldered the wires directly to the chip, corrected .bin file uploaded (Trafmaster sent me a perfect rescue .bin, thank you!) to Flash Memory and success!

 

[Alma12]

Is there any chance i could get ahold of the rescue .bin? I'm in a 2%-3% boot loop on fail safe trying to get from 59.00.504 4A N to 70.00.100A

I sent you a PM.

 

[Alma12]

Hello KKC,

First of all, checksums must be correct. As Tristan wrote earlier, these are the right values (I think you need North American FW) :
cmu150_NA_70.00.100A_failsafe
MD5: 9324D1907C2C722738B0A389DE73E91D
SHA-1: DB04E842A797AC20449853ED63CBE38821A76162

cmu150_NA_70.00.100A_reinstall
MD5: DA7667967E62E324C4EF457DE4A262BF
SHA-1: 8C0C6608B229A1079D8F467816687B900D996EA7

If your FW has different values it might cause headache again. If it is right, go ahead.

I asked Chat GPT about the 2 Eprom programmers. The EZP2019 USB is good for your purpose, but the PIN layout is different. Please check the following pages how to connect your programmer to MZD CMU’s SPI NOR Flash memory.

EZP2019 USB manual
CH341A Mini Programmer Schematic and Drivers

About the voltage: I don’t know if the 5V damages the chip. I modified my CH341A programmer, just to be sure. You need to search tutorials how to do it with EZP2019 USB Programmer.

Did you search CH341A on ebay? Maybe you can find local seller who can ship it faster than any Overseas, Chinese stores.

 

[Alma12]

Yes, I checked those as well, not the same as your value provided in #205 post - but strangely, same as with your linked files. It seems I have only FWs which have wrong checksums. Where to find the correct ones?

Edited:
I already have the correct files, the checksums are OK. I inserted the pendrive and unfortunately the forced update process did not begin. Maybe the .bin file wrong?

 

[Alma12]

70.00.100 and 70.00.100A are the same
Have you checked the hashes/checksums of your downloaded files? This way you could be sure if the files are OK.
Otherwise you could try these files: Mazda Connect Firmware - Google Drive

I tried to use your files, unfortunately none of them helped (70.00.100A, 59_00_545А). Rebooting continues.

In the meantime I learnt how to check the hashes/checksums. I compared the values in your files with the "reference" values you wrote in the #205 post and both the MD5 and sha-1 values are different.
I'm clueless how to continue. Maybe reprograming the EEPROM, somebody uploaded a corrected 513B.bin file, I try to use it.

 

[Alma12]

70.00.100 and 70.00.100A are the same
Have you checked the hashes/checksums of your downloaded files? This way you could be sure if the files are OK.
Otherwise you could try these files: Mazda Connect Firmware - Google Drive

WOW! Very quick response .
Unfortunately I don't know how to check the hashes/checksums . I downloaded your files and try to use them. I'll come back a couple of days later to summarize the process.
Thank you very much.

 

[Alma12]

Hi guys, I need some help, direction to get my CMU alive. I hope someone can help me.
I tried the SW upgrade from 56.00.512A to EU N 70.00.100A. Unfortunately I did not remove the MZD AIO tweaks and also during the upgrade process the power went down --> black screen. I followed the instructions to modify Fs to 0s:

• I bought a CH341A programmer with the required wires, clips
• the programmer module modified to feed EEPROM with 3.3V.
• downloaded the 1.18 programming SW and
• successfully changed the Fs to 0s. READ -> ERASE -> PROGRAM -> VERIFY steps went smoothly, no errors
• I assembled the CMU unit, attached FAT32 formatted 16GB SanDisk pendrive (and later I tried with another pendrive as well)
• the CMU is waiting for the FW to retry the upgrade automatically. However the forced update process did not begin, the system is waiting for 70.00.100, but I have 70.00.100A on the pendrive. I don't know how it happened, because I have 70.00.100A failsafe and FW only, I never had 70.00.100. And then reboot, waiting for the FW, reboot, waiting for the FW, and so on.

My question is: can someone help me to correct my .bin file? Or do you have any suggestions?
When I bought the Android Auto/CP upgrade kit, the seller provided the FW links, maybe those files are not correct. How can I find a working 70.00.100A and 70.00.367A files?

Thank you for your help in advance.