The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

ECU Editing

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

JohnnyT

15+ Year Contributor
104
0
May 15, 2007
Sioux City, Iowa
I recently purchased a Stage III chip for my Laser and I was wondering if the same chip would work for my friends 93 Eclipse GSX or my other friends 94 Eclipse GST. So what I really want to know is will my chip work in all 1g cars? And what about 2g's?
 
I'll add to the list: I pulled the EB21 out of a '94 MT California (produced 10/93)

Steve, it looks like the link is broken. I'm piecing together an XDF file, but it's taking more time than I would like. It feels like I'm starting about where some of these other people were...
Do you guys know of a list of what the hex equivalents are for the different commands?

I need all the information to verify. On the top cover you'll see the part number MDXXXXXX and E2TXXXXX

I fixed the link. It's late.

I'm not sure what your asking for by different commands. Are you asking about the op codes for the CPU instructions? That's in the files section on the DSM-ECU site.

http://autos.groups.yahoo.com/group/dsm-ecu/files/1g/e931_disasm/MH6111 OPCODES.txt
 
I'll add to the list: I pulled the EB21 out of a '94 MT California (produced 10/93)

Steve, it looks like the link is broken. I'm piecing together an XDF file, but it's taking more time than I would like. It feels like I'm starting about where some of these other people were...
Do you guys know of a list of what the hex equivalents are for the different commands?

Thank you Steve... I looked at the db of eprom numbers on dsm-ecu last night and it wasn't there.

Architechnik - Knowing the opcodes and the exact disassembly would be nice, but it's kinda over kill. The dsm binaries are based on a motorola chip (cmiir) but there are special proprietary opcodes that are not standard on that microprocessor. So it is a specialized chip. I think the easy way out is to just use a hex editor and find the memory locations on a stock eprom bin (like the one I sent you). You know what could be even better than that, is if that eprom CAME in your car (ie, you didn't buy it and install it later), it would be the best match for your car (not that it's a huge deal to use an e931 bin), to start hex editing.... but you'd have to get it off the board first and copy it. If you look at that link that Steve posted showing me where the eprom numbers were... I believe that is his site and he offers eprom services.
 
The CPU is part of the Motorola 6800 family. Mitsubishi licensed the architecture and made several derivative chips. The MH6111 is a 8 bit microcontroller that looks a lot like a Motorola M68HC11 with a few changes.

The operation code file lists the known instructions for the MH6111, you need it if your going to write any of your own code.

For people just starting out one things that trips them up is the idea of addressing modes.
Offsets in the EPROM are another.

Steve
 
Sorry about that, Steve. The top part numbers are MD304484 and E2T60879.
The processor is that MH6111 - I don't know if they made any changes through the years.
I think it's odd that there is a matching number on the outside (side sticker) to the EPROM chip - 121 Does this have any significance to what's going on with the board?

Bling, this is the original out of my car. It looks like there is part of the plug that's kind of rough/melted, though... maybe got burned by something!? Strange, but it's been in working order.

As far as tracking the opcodes, I'm thinking of writing a simple search function that could search the code for whatever process someone would be looking for... a sort of decompiling sequence. Also, to create that security feature we were talking about before by reading the tps value over certain intervals to activate/deactivate fuel cut.
 
^^Ahhh... very good. That's a little more than I'm capable of knowing how to do at this point, but that sounds like that's the proper way to do it.

Does anyone know if there's a difference between a PocketLogger brand cable and a home made one? My pocketlogger software still works, but I cannot get PDyno or MMcd to work. Neither of the latter two loggers are picking up any of the parameters what so ever. I am going to make my own logger cable and see if that doesn't help.
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top