Flashhack - New LT1 flash tool

[steveo]

so here's the struggle... look at the difference in aldl request timing!
the bbody bin spits out messages at a much higher rate.
between windows drivers and serial interfaces, this confirms the precise approach of sending a request between packets is impossible. i am going to come up with something way better. i want to try to abuse the length and checksum to basically 'hang' the bus and then unhang it at the same time that we send the request....

FBODY:

159ms to 175ms (16ms) :: F056F4C6
::: GAP34ms
209ms to 231ms (22ms) :: 905A02080008FF05
::: GAP31ms
262ms to 285ms (23ms) :: 0A58FF00009F
::: GAP27ms
312ms to 330ms (18ms) :: 905A02080008FF05
::: GAP31ms

BBODY:

::: GAP0ms
0ms to 17ms (17ms) :: 92551919
::: GAP9ms
26ms to 42ms (16ms) :: A6550505
::: GAP9ms
51ms to 68ms (17ms) :: F056F4C6
::: GAP9ms
77ms to 103ms (26ms) :: 405F020400870000007F00480D
::: GAP0ms
103ms to 132ms (29ms) :: 4563000000000000080000000000A0A010
::: GAP5ms
137ms to 154ms (17ms) :: 12559999
::: GAP21ms
175ms to 194ms (19ms) :: 10559B9B
::: GAP9ms
203ms to 218ms (15ms) :: 92551919
::: GAP9ms

[steveo]

okey dokey! i did load a b-body bin and found it did fail a lot of the time, even on a bench harness, you were not kidding around.

try this beta which seems to solve the problem 100% of the time with a more of a machine gun rather than a pistol. fortunately there are very few civilian bystanders in an aldl bus so nobody should be hurt.

http://fbodytech.com/flashhack/

[sherlock9c1]

What's amazing is that I've flashed literally dozens of B-body tunes through this exact same interface and NEVER had a brick with eehack.

Summary:

1. Read with no errors.
2. Wrote with no errors.
3. Pulled USB during T side write, was able to recover after some clunkiness with the USB and flashhack.
4. Pulled USB during E side write, same as above. Specifically wrote only the E side afterwards, had no issues.
5. Tried out the PCM with EEhack, seems to run fine on the bench.

Well done! Emailed you a log.

[steveo]

nice. i feel bad i even tried a precise approach when we just needed to smash the bus appropriately.

yes pulling the usb cable might require a program restart.... it's a pain to check if the bus is actually still there with every single byte and most programs that deal with usb devices will throw a total fit if you unplug it mid-byte. as long as it recovers if ECM ignition power wasn't cycled in that condition i'm happy.

edit: i guess if it's possible could you huck that the ECM in a car and make sure it actually runs with kur4o's crazy recovery patch in place?

[sherlock9c1]

Maybe midday tomorrow. The car currently has nothing more than manifolds, no cooling system, accessories or transmission. I cobbled it together enough to start it and verify oil pressure, ignition and fuel. Now time for the rest of the car to go back together. BTW you know how you can tell if an LT1 ignition and injectors are good? When it starts up with a BOOM exactly 1/2 second after you crank it. Every time. Scared the crap outta my kids, LOL. "Son, what was the oil pressure?" "I dunno dad I was duck and covering." "I TOLD you it'd be loud! What's the oil pressure!?" This was WITH everyone having ear protection on!

[NomakeWan]

Woah! Sorry for not getting back to you sooner, I was a little busy in the "real world" doing boring stuff. But yeah, I went ahead and gave the new beta a test. Still didn't work, but I've got some new logs for you to check out.

The first log I forgot to tick the 'timestamp' button, apologies there. The fourth log is from my manual '95, just to see if it did anything different. It still failed to read, so doesn't look like it.

As always if there's anything else at all I can do to help just lemme know--I will likely have more 94-95 Corvettes in the future, so I'd love to join your F-body flash party. :)

Oh yeah, and the adapter I'm using is the one from ALDLcable. http://aldlcable.com/products/aldlobd2u.asp

Just for reference.

Oh, and just as a refresher, my '95 is the one that works almost perfectly with EEHack. I can read/write/log with it perfectly. Every once in a while the logger will hiccup for unknown reasons and to be honest I'd be willing to blame the USB port on my laptop for that. The '94 is the one where EEHack threw constant errors and would fail to read. Never tried to write because of it.

[kur4o]

I checked the logs and it looks like the bus freeze at mode 08 bombardment and than resumes normal communication.

Can you try to give a 4-5 attempts burst than wait for silence, than again 5 attempts,than wait for silence. I think when the mode 8 went through at least 5 second silence can be observed.
What is the normal silence on end of message , can we use that to identify the end of messages, For example read byte to byte delay and when a pause longer than the expected 8192 baud is received the end of message can be flagged and the buffer dumped.