Page 7 of 7 FirstFirst ... 234567
Results 91 to 103 of 103

Thread: Next EEHack update

  1. #91
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    757
    If there’s anything else I can do to help let me know.
    1990 Corvette (Manual)
    1994 Corvette (Automatic)
    1995 Corvette (Manual)

  2. #92
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    today was a REALLY good day for testing. kur4o has had some really big wins on the 68k end of things and i've done a lot of debugging on my region mapping/ordering algorithms, so we now have a functional recovery rom which is switchable and the logic necessary.

    in other words you can now remove power from the ECM during almost any point in the flash procedure and then plug it back in later, and it'll reflash like nothing ever happened.

    if you've missed how it works, since only some of it has been posted here, the way this rom works is basically some extra jumps in the original code to run all the processor init and communication loops necessary to do basic reprogramming (modes 5 and 6), and those extra jumps use a check byte. if the check byte is unset, it runs the basic communication code only. if the check byte is set, it runs as usual.

    so we program the communication code first with a few small patches, then the rest of the bin, and finally the check byte. that way until the last byte is written, it's still 'recoverable'.

    it's really a nice peice of work, it's about 2kb of code per eeprom, and as long as the recovery rom boots, flashhack will manage to upload the kernel again, and you can flash the thing again like nothing happened.

    So the failure window for ECM power dropping is now between the final ERASE program upload and the first 1859 bytes (ESIDE) and 2230 bytes (TSIDE), this takes around 7 seconds.

    outside of that 7 seconds you can do anything you want and it's brick proof.

    there should also be NEARLY ZERO failure window if ECM power is maintained, this is only for total ECM power failure during flash.

    the skip algorithm is now more efficient and even with the recovery rom in place, we can skip 48kB of writing even with an automatic transmission bin, so that decreases the rate of failure even more.

  3. #93
    Fuel Injected!
    Join Date
    Sep 2012
    Location
    Huntsville, AL
    Posts
    237
    Just curious, how much of that 7 seconds is the erase action, and how much of it is programming?

    And forgive me if this is a stupid question, but are both sides independent, so if there's only updates to the E side, does only that side get erased and reflashed?

  4. #94
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    Just curious, how much of that 7 seconds is the erase action, and how much of it is programming?
    most of it is erase time. erasing can take a variable amount of time as you have to erase and check repeatedly but on a healthy chip it seems to take 'bout 5 seconds. the new log has timestamps if you're curious to check how long your erase cycle takes.

    the important improvement in this new tool is that even if the erase totally flunks, as long as you keep the ecm ignition power on, you can go have a beer, plug in your battery charger for a while, close the flash program and play some video games, and when you come back and press flash again, it should work fine.

    And forgive me if this is a stupid question, but are both sides independent, so if there's only updates to the E side, does only that side get erased and reflashed?
    yeah they're independent.

    eehack had a built in bin compare feature in its flash routine to know which sides to skip but it wasn't really perfect - it trusted the user not to make edits to the original bin on disk, and if you were flashing multiple ECMs, it wasn't exactly smart enough to realize that.

    right now in the new program you need to go check the 'write e-side' or 'write t-side' box in the parameters as the feature isn't implemented yet.

    i'm going to do it a bit differently now, having the program store the last successfully written eside and tside. before writing it'll run a checksum on the ecm and the bin to make sure nothing has been changed in the meantime.

  5. #95
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    i think i'll start a new thread for this tool just because the title of this one isn't too hot.

    the main thing the next eehack update is getting is new connection routine (once we figure out why this one sucks with y-bodies..again..) and we'll hide the flash tool and recommend flashhack instead.

  6. #96
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    new eehack release finally retires the built-in flash tool, because flashhack is just too good.

    i also ported over the connection code from flashhack, so you no longer have to select a vehicle type, and it should connect to any vehicle with a normal 8192 baud aldl bus. this might make it easier to write datastream definitions for other aldl based cars...

  7. #97
    Fuel Injected!
    Join Date
    Mar 2013
    Posts
    1,470
    What will be really cool is to integrate both program. In eehack click on flash and flashhack starts when you are finished it closes and control is back to eehack.
    It is time to add some patching system in flashhack, or guys will be locked out of patches.

    Since when eehack is open and disconnected the comm port is bogged and can`t be used with flashhack. The only way to free the port is to close eehack

  8. #98
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    that wont happen, eehacks codebase is too rough to do it.

    the eehack logging patches are already in the latest version of EEX if anyone wants them

    edit: i will add a patching facility to flashhack in the future of course

  9. #99
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    Quote Originally Posted by steveo View Post
    Since when eehack is open and disconnected the comm port is bogged and can`t be used with flashhack. The only way to free the port is to close eehack
    does it really do that? i never even noticed. that'll be easy to fix (way easier than trying to make two completely different programs work together)

  10. #100
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    757
    Quote Originally Posted by steveo View Post
    new eehack release finally retires the built-in flash tool, because flashhack is just too good.

    i also ported over the connection code from flashhack, so you no longer have to select a vehicle type, and it should connect to any vehicle with a normal 8192 baud aldl bus. this might make it easier to write datastream definitions for other aldl based cars...
    Tested the new version. Errors still creep up on the '94, but it stays connected and seems to be logging just fine as before. No issues noted. Doesn't disconnect the ABS anymore, just the ASR, similar to Flashhack. Unlike Flashhack, however, it doesn't cause the digital dash to reset on connection or keep-alive.
    1990 Corvette (Manual)
    1994 Corvette (Automatic)
    1995 Corvette (Manual)

  11. #101
    LT1 specialist steveo's Avatar
    Join Date
    Aug 2013
    Posts
    4,008
    Quote Originally Posted by NomakeWan View Post
    Unlike Flashhack, however, it doesn't cause the digital dash to reset on connection or keep-alive.
    they now have the same exact code to connect, keepalive, and disconnect, so i find that difficult to understand.

  12. #102
    Fuel Injected!
    Join Date
    Jul 2019
    Location
    Orange, CA
    Posts
    757
    So I was messing with speedlogger today logging my commute, and noticed there's a bug in EEHack 4.9.3 if you enable Speedlogger and Transmission data streams. It causes the Dash tab to freak out and flicker like crazy and not actually display sane data. Turning transmission data back off puts it back to normal.

    I have a feeling this may be unavoidable/by design, but if so, it might be good to make it impossible to do. Or maybe it's a bug. No clue, so I figured I'd report it.
    1990 Corvette (Manual)
    1994 Corvette (Automatic)
    1995 Corvette (Manual)

  13. #103

Similar Threads

  1. EEHack 5.0 2020 update
    By steveo in forum GM EFI Systems
    Replies: 9
    Last Post: 09-30-2022, 06:37 AM
  2. EEHack 2019 update
    By steveo in forum GM EFI Systems
    Replies: 154
    Last Post: 02-20-2020, 05:31 PM
  3. $4D update
    By steveo in forum GM EFI Systems
    Replies: 4
    Last Post: 07-19-2014, 09:33 PM
  4. Tables won't update
    By POZE in forum TunerPro Tuning Talk
    Replies: 2
    Last Post: 02-17-2013, 09:48 AM
  5. TunerPro V5 update!
    By EagleMark in forum TunerPro Tuning Talk
    Replies: 27
    Last Post: 07-16-2012, 02:42 AM

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
  •