2004 to 2020 Mazda 3 Forum and Mazdaspeed 3 Forums banner
241 - 260 of 319 Posts
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.
 
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?
 
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!
 
Hey folks,

Does anyone have current links to NA firmware?

I was able to use a culmination of this and other posts to recover my CMU which was rebooting every 8s, and it's a joy to finally have music in my car again and not have to rush my backing out before the screen resets.

I used the link from this post earlier in this thread by @Tristan-cx5 (sorry, can't link in my first post), which put me on 70.00.100 EU N. and Fail Safe version 55.00.750. However, I'm in NA and want to make sure I start with a known-good NA firmware image before I proceed with further upgrades for AA and AIO tweaks to enable AA touchscreen and other features.

To get me there, I need a couple of images whose links seem to get taken down a lot:
  • 70.00.100A NA N - I understand this version is a common one to flash and is like the one I was able to flash, but I believe that I need the NA version as a starting point.
  • The newest firmware version, maybe 74.X? I have a Gen 3 Mazda 3, and from what I can tell, there are some 74.X versions floating around, but I'm having trouble finding the changelog.
  • I'd also appreciate any links/references to major version changelog for these firmware releases. It's not clear to me why 74 was released and what it fixes, and the discussions seem a bit nebulous. Any key summaries around min/max versions for AA, AIO, Gen3, etc. would be much appreciated.
 
@ASH8 : Sorry, I copied the links from another forum and thought as they are known in the wild it would have been OK. Anyway, I learned that it is not OK and I understand and accept your reaction and will stick to it.

@penguinairlines :

Changelog of firmware- up to latest 74.00.324: https://static.nhtsa.gov/odi/tsbs/2022/MC-10226834-0001.pdf

AIO Tweaks - here are some short info:
a) If below 59.00.502 - just install the ID7/Autorun Tweak from AIO
b) If between 59.00.502 and 70.00.100 (including these two), you have to use ID7 serial connection: www.mazdatweaks.com/serial . For a) and b) the ID7/Autorun tweak will remain if you update up to/including 70.00.100.
c) For 70.00.335 and 70.00.352 you have to use ID7v2 serial access: www.mazdatweaks.com/id7
d) For other/higher firmware nothing is published how to enable it to install AIO tweaks.

As this is the wrong thread for AIO Tweaks, please keep this thread at its original topic and do not ask follow up questions here - search for other more fitting threads. Thanks.
 
Hello all,

Thanks for your information. I think this forum give the solutions that I need and your experience save me from making mistakes. Good job everyone.

I ordered EZP2019 USB Programmer from Amazon instead of CH341A because I don't want to wait till next year to receive it.

My question is this Programmer allow me to update this chipset that we are discussing? Also, this usb programmer does not allow me to change the voltage. Will it damage the chipset while I am reading from /writing to it? Thanks.

My MCU's info:
2019 Mazda CX5
Failsafe 70.00.100 NA firmware (factory settings)

I didn't read the instructions carefully when I am doing the update. I installed the Reinstall Package 70.00.100 NA and caused this problem. The installation was just 2%. What is your recommendation to me if I successfully modified the chipset? The latest version or the last install version (Restacking package 70.00.100 NA)? Thanks.

KK


EZP2019 USB Programmer High Speed EEPROM Programmer BIOS Chip Programmer for 24 25 93 EEPROM Flash Bios(with sockets + Test Folder + Conversion Socket)
 
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.
 
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.
Hello Alma12,

The EZP2019+ doesn't detect my chip. Then, I buy CH341A and it also cannot detect my chip. Now, I think it may be the test clip's problem. I just order a new one and hope it can fix the problem.

However, I didn't modify my CH341A (cut it and put a jumper to make sure it is 3.3V).

I hope it will not damage my chip. It is because I tried to erase and program the chip with the modified bin file from"Ride and Live". The software shows that it was successfully wrote into the chip, but it is not when I read and verify the data.
 
Don't modify CH341A, I've used it unmodified hundred of times never had a problem, in fact I modified my second ch341, I accidentally shifted test clip and I smoked programmer 3.3V regulator. SIP ROM can handle 5V data lines.
The first step for a successful programming is AUTO DETECT SIP-ROM, don't worry if programmer ID as 6405 instead of 6445, it's because 6445 is not in version 1.18 chip database but they are identical in size. PRESS CTRL + D in KBD.
IF IT DOESN'T ID CHIP CORRECTLY, RE-ATTACH TEST CLIP AND TRY AGAIN. DON'T CONTINUE UNTIL YOU HAVE A SUCCESSFUL ID.
When you're attaching test clip touch with your finger CH341 regulator, near USB connector, if you feel it's getting hot pull clip and reattach, that means clip is shorting out.
First thing you do it's a READ when software ends, scroll down data, if you see all FF's chip is empty or it didn't read at all, not all FF, good, SAVE data. Proceed to flash it, OPEN FILE, ERASE, PROGRAM and VERIFY.
Image
 
Hello all, I am new on this forum, and I need some help with Mazda 3 CMU. I have bricked my cmu when shutting power after installing failsafe file. I have succesfully unbrick CMU using information from this forum and some others, but now I am stuck with that black screen asking me to insert USB and update system. I have tried to use 70_00_100A EU version which I have on the USB, but it says it is not correct file. I have attached my succesfully modified rom, please could you tell me what version I should use to update cmu. Or can I upload to cmu this rom: rom-513B and then cmu would start in normal mode? Thank you for any help. Dusan
 

Attachments

I have the same situation. I modified my CMU with his .bin file since I cannot reinstall my firmware with my modified .bin file. I am using "cmu150_NA_70.00.100A_failsafe.up". The CMU cannot read the fail_safe file (cmu150_NA_70.00.100A_failsafe.up)
 
@samaygrover : Please post the solution, which you got via private message, so that everyone can benefit from it.
Hi @Tristan-cx5 need your help.
Radio stuck at install not successful screen.
Miss out to install failsafe before install reinstall file.
From 59.00.504 -> 70.00.100
what bin file to write?

Image
 

Attachments

I would put 70.00.100 to the usb stick and check the hash/checksum before inserting it to the car's usb hub.
If this does not work, you could try a bin file posted here in the thread and try to install the according firmware file(s). You could use the EU version and install EU firmware version. Afterwards you can install any other region version - e.g. ADR.
 
241 - 260 of 319 Posts