When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Just got finished applying the labels from your work to the N3M5EK ecu. Going to start updating the romraider definitions file so i can compare it. Here it is on my github
Hey Equinox, as I see that you are really fit in this matter I have a problem and was hoping that you could help me please. I have a friend who buys rotaries and fix them drives them sells them remaps them. He uses versatune to tune his cars as he has a pro sub or whatever. The thing is he bought now a rx8 but he can't tune it. As I understand it should have a tune already with mazdaedit I guess? And that changed the seed key algorithm on the bootloader section of the rom. Now my question do you know where exactly this happens on the bootloader so I can modify it reading and writing the ECU through JTAG? Or maybe do you know if I can flash a ROM from your repo directly without losing immo data? Thanks in advance!
You should be able just to flash a stock ROM on via JTAG/SHBoot, and from there you'll be able to reprogram the module via CAN/OBD for Versatuner.
None of this will delete immobilizer data as it's all stored in the EEPROM.
Yes that was also my understanding but I said better be safe than sorry. As I am not accustomed on working on denso ECUs. Is the bin file read out through obd and JTAG the same? Same size and full read? That would be crazy as most ECUs I have worked in the past European mostly are at best half read or you cannot read them through OBD and have to get a virtual file from the tool. Thanks man for your work and help!
I just got a OBDX Pro VX cable this morning and could not for the life of me get the RX8 Man software to recognize it. I was able to get device manager to recognize it though. I didn't get to try too much, but I did install both the Openport 2.0 drivers and the OBDX drivers. I also included the log file for the software if that helps anyone. I will likely look into this a little more after I get back from work today, but it may also be a little while.
Originally Posted by tharp
I've used a GoDiag J2534 cable which is around 30 bucks I think. It works just like the tactrix. The only difference is that you need to rename the godiag drivers to the tactrix dll that the software looks for.
Tharp also responded to me earlier, and I have not had the chance to look into this. I am not 100% sure what will work here, but it's worth a shot. Let me know if you have any other ideas too.
Yes that was also my understanding but I said better be safe than sorry. As I am not accustomed on working on denso ECUs. Is the bin file read out through obd and JTAG the same? Same size and full read? That would be crazy as most ECUs I have worked in the past European mostly are at best half read or you cannot read them through OBD and have to get a virtual file from the tool. Thanks man for your work and help!
I just got a OBDX Pro VX cable this morning and could not for the life of me get the RX8 Man software to recognize it. I was able to get device manager to recognize it though. I didn't get to try too much, but I did install both the Openport 2.0 drivers and the OBDX drivers. I also included the log file for the software if that helps anyone. I will likely look into this a little more after I get back from work today, but it may also be a little while.
Tharp also responded to me earlier, and I have not had the chance to look into this. I am not 100% sure what will work here, but it's worth a shot. Let me know if you have any other ideas too.
From my limited experience with J2534 drivers and such, it definitely seems like the RX8Man software can't find the driver?? Honestly not entirely too sure.. I'll forward this to RX8Man and see if there is any quick insight.
I had some issues with this, I had to copy my registry files for the driver and move them to another location, since that is where the Rx8Man program expects to see them. i forgot which location they were originally in, but make sure they are in both:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\P assThruSupport.04.04\GODIAG - J2534
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSuppo rt.04.04\GODIAG - J2534
Where the firmware path and function library is the file location of the drivers (any J2534 drivers should work)
Alright, I have confirmation that the OBDX Pro VX cable does work to at least read the ECU with a cable. The issue was I had issues with the RX8 Man install. Once I redownloaded it, it worked immediately. To get it working as expected, I ended up installing multiple things. In order to get it to work, the installs needed are the USB driver and VX J2534 API alongside the other RX8 Man installation software. Default install locations for all of the software should work to get it running. I haven't tried reflashing yet, but it seemed to be able to data log a little and was able to read the ecu memory no problem. I'm pretty impressed with the cable, especially for $80. I will update this post when I get confirmation of reflashing, Bluetooth, and data logging. For now, I can at least confirm that I know that this cable is recognized by RX8 Man and will rip the rom.
Update: Logging data has been tested with a cord and works!
Last edited by Conner Hart; May 19, 2026 at 05:42 PM.
Still working through adding new definitions to RomRaider for my ecu. i'd say about 80% of the tables are the same (different memory locations, same axes and values). The main differences so far have been in the fueling tables. The open loop and closed loop is quite different from the 04 ecu, as well as some of the limiter strategy. Also added and renamed some more function and variables names. I'll post here again when I get a majority of the important tables figured out in romradier.
Hey Equinox,
I appear to be having trouble writing ROMs to my two spare ECUs via RX8Man. I seem to be able to read them, but the upload fails at different stages (depending on ECU) and bricks the ECU. Noting that i'm trying to use the immo disbale function as i'm experimenting with additonal ECUs I have whilst keeping my regular ECU untouched to fall back on.
I can unbrick via Renesas, but it's a painful process.
I've attached my Def file which i've developed for my AU ROMs, not sure if this is causing issues.....
Any help would be greatly appreciated.
I don't believe the parameters file would matter for anything aside from datalogging with RX8Man.
You could also have an intermittent connection at the OBD port, have seen this many times where the pins get a bad connection due to so many cycles of plugging and unplugging devices in. I've had to push back the contact tabs on many OBD port pins to solve that. Not guaranteed, but it's free and easy to ensure a solid connection. Random dropouts tend to be things like this.
Any update on this? I finally have some funds to buy a cable and have been eying this cause its fairly affordable, especially cause tactrix hasn't been quick on making their new design.
I have an update!!
I finally got their adapter in, they sent over an OBDXPro VX
After having to make an account (big fat BOO) and installing both the drivers and the VX J2534 API, it seems to work with RX8Man for datalogging and ECU ROM dumping and reflashing. I was able to pull a ROM on my bench ECU, and reprogram it with totally new software, as well as slightly modified software.
I was looking at a forum thread (here), and it seems like there are some issues with in-car flashing with mazda edit. Just because I don't yet have hardware to un-brick my ecu and won't try flashing until I do, have you tried the in-car reflash yet with this cable? If not, no worries, I can get to it eventually.
