Results 1 to 15 of 63

Thread: $EEHack Read Failure Every Time?

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    757

    Exclamation $EEHack Read Failure Every Time?

    Hello,

    So I've been testing out EEHack with a cable from ALDLcable on my '94 with the 16-pin connector. The program itself seems to work just fine--I can clearly see correct data, and the actuators all do exactly what they're supposed to (except for toggling the SES light on and off, but I have a feeling that's related to it coming on whenever I plug anything into the 8192 data line). However, whenever I try to read the stock ROM from my car, the read fails at the end with a checksum error. I've tried tens of times with the same result every time but one. The one time I had something different happen was when it failed partway through and warned me I needed to pull the PCM fuse. Once I figured which fuse that was everything was fine with the car. I did try CATS's WinFlash tool and that did successfully pull the ROM. I threw it into TunerPro with EEX and it loaded up fine. After switching the XDF to EEXTRA I discovered that someone had, at some point in this car's past, flashed the PCM with a Hypertech Power Programmer III. I don't know if that's related, but I figure I'll put as much info in here as possible with hopes that it'll lead to a fix. I noticed I'm not the only one with this issue, but the other threads across the internet don't have any solutions either.

    What I've tried:
    Checking battery voltage. Initially yes, it was low--11.7V on my DMM. I left the car on the charger all day and came home to it at 12.8V. Tried again three times but still got the same result. Notably the successful read with WinFlash was done before checking battery voltage.
    Checking cable settings. Initially the COM port was set to 16ms latency. I changed it to 1ms. That improved speeds marginally but didn't change the outcome at all.
    Changing USB ports. No change.
    Changing COM port. Did this because CATS's tool won't let you select any port number over 8. No change.
    Changed setting in $EEHack to allow saving invalid BINs. Didn't do anything at all. Similarly found that $EEhack doesn't remember my setting for COM port (it always goes back to 4), and ignores my setting for not warning me before closing without saving a log...basically the program doesn't seem to like paying attention to the settings menu at all.
    Changed program to "Run as Administrator." No changes.
    Uninstalled program from default directory, wiped registry key, reinstalled program to my own user directory to rule out access permissions issues. No changes.
    Tried out kur4o's latest beta fork. Same result, and similarly ignored everything in the settings menu too.

    What I've noticed:
    WinFlash has no problem connecting and reading the ROM to a BIN, but it seems to struggle to display vehicle information when the car is first turned on without first commanding a read. When it finally does work, all the information populates except for Calibration ID, which does not. $EEHack's main page displays all values including Calibration ID as soon as the connection is established, every time. I've done two reads with WinFlash, and using VBinDiff there are differences between the two, but they seem to be in specific locations. Loading the two BINs into TunerPro and using its difference tool, it reports that all of these differences are in MEMORY areas, which I assume are RAM, which is why they're different and thus not relevant. Hopefully this is a correct assumption.

    What I have not tried:
    Switching compatibility modes. I do not think this is necessary with a Qt program on Windows 7, even though it was absolutely necessary in order to get WinFlash to even install.
    Flashing the completely stock ROM. On the off chance there is something wrong in my setup or with one of the programs, I do not want to brick the car. I would rather ask for expert assistance first and be asked by said experts to do so after careful analysis of the problem at hand than go with the nuclear option right off the bat.

    The laptop I'm using is Windows 7 32-bit. I installed $EEhack natively, not using any compatibility modes, and don't have any compatibility modes set. I will attach to this post a screenshot of the outcome of a read with $EEHack, a verbose log output of starting $EEHack and only attempting a read (start car -> wait 10 seconds -> open $EEHack -> Connect -> wait 10 seconds -> Flash Read -> Exit), and the two dumps from WinFlash. Hopefully we can figure this out.

    Thank you!
    Attached Images Attached Images
    Attached Files Attached Files

  2. #2
    Fuel Injected! spfautsch's Avatar
    Join Date
    Apr 2015
    Location
    Montgomery City, MO
    Age
    52
    Posts
    883
    FYI, the aldlcables piece is a know problem w/ eehack. I think steveo managed to borrow one to try and troubleshoot but he's a busy guy.

    >link<

    My suggestion is to make your own with an ftdifriend or similar.

  3. #3
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    757
    Somehow I had missed that thread when I was searching through all the stuff on Google. I'm not sure how it slipped past me, so I apologize. I'll try cracking open the cable to see what chipset it is.

    Hilariously enough I was so impatient waiting for the cable to arrive that I DID build my own out of a 5V FTDI Friend, but the instructions I followed required a 1N914 diode and a 4.7k resistor on the TX and RX lines to prevent a potential current surge in the event of crosstalk. This cable worked (barely, not well) with Scan9495 and not even once with EEHack. I suppose I can try removing the protection circuitry and wiring it directly to the car instead and see if that works.

    Thank you for the reply! I look forward to updates.

  4. #4
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,007
    no diodes and resistors necessary

    eehack was mostly developed and tested with the rx and tx wires literally twisted together and hanging in mid air, from a cheap ftdi ebay board

  5. #5
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    757
    Well that settles that!! As soon as I get home from work I'll swap out the protection circuit wiring for bare wires and run another test!

  6. #6

Similar Threads

  1. First Time Posting Long time as a fly on the wall
    By Mrgto68 in forum Introductions
    Replies: 0
    Last Post: 12-18-2018, 12:00 AM
  2. Long time listener, first time caller.
    By Shameless in forum Introductions
    Replies: 1
    Last Post: 06-26-2018, 06:26 AM
  3. EEHack continuous checksum failure ???
    By kris72079 in forum GM EFI Systems
    Replies: 17
    Last Post: 09-01-2017, 10:17 PM
  4. Would Checksum failure cause these issues?
    By trippyjoey in forum GM EFI Systems
    Replies: 8
    Last Post: 10-01-2014, 09:22 PM
  5. ERROR: PROM I/O returned failure?
    By brian617 in forum TunerPro Tuning Talk
    Replies: 4
    Last Post: 10-14-2013, 01:51 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •