Corvette CCM Reverse Engineering Anyone?

[steveo]

At this rate, all the work on getting the CCM to play nice with aftermarket computers will be for naught.

i don't know about that.

i think the work you're doing is on the same scale as the work i'm doing

it serves no real purpose in the grand scheme of things, and you will succeed and excel and your product will be the best there is, at the cutting edge of its game, because there is no competition with this old junk anymore, everyone gave up, got bored, and moved on

the two or three people that decide they want to shoehorn a totally inappropriate engine into their oddball mid 90s american fiberglass computerized 'muscle' car will really appreciate it

it's a hobby, though, and one that would terrify ordinary people if you tried to explain it to them.

that's really why i do what i do

the terror

[steveo]

i have released the new version to play with.

the DBG_C button in the advanced section writes the eeprom only if anyone wants to try that too.

[NomakeWan]

i have released the new version to play with.

the DBG_C button in the advanced section writes the eeprom only if anyone wants to try that too.

Went ahead and tried it out. Read out my PCM first just for giggles, that worked perfectly. Did DBG_C but it appears that routine doesn't actually have an exit coded in yet. It loads the program, does the writes, but then just sits there hammering the bus with F108 messages rather than rebooting the T-Side and E-Side and disconnecting. Log attached.

i don't know about that.

i think the work you're doing is on the same scale as the work i'm doing

it serves no real purpose in the grand scheme of things, and you will succeed and excel and your product will be the best there is, at the cutting edge of its game, because there is no competition with this old junk anymore, everyone gave up, got bored, and moved on

the two or three people that decide they want to shoehorn a totally inappropriate engine into their oddball mid 90s american fiberglass computerized 'muscle' car will really appreciate it

it's a hobby, though, and one that would terrify ordinary people if you tried to explain it to them.

that's really why i do what i do

the terror

Heh! I do it just because it's interesting, and because ever since I was a kid I couldn't stop tinkering with everything I owned. Plus I really hate when people tell me what something can or cannot do, especially when it's some company telling me I can't do it. To hell with that, it's my device/car/etc, I'll do what I want! Upside is I have a bunch of old equipment that continues kicking around. Downside is I'm surrounded by obsolete tech and can't stop myself from wasting time tinkering with all of it.

EDIT: Also, I noticed while editing that BIN I just read that it appears the function to clear Automatic Transmission tables on a manual isn't quite complete. It did set almost everything to FF, but it missed the last few cells of 38AE Shift Time (sec) Vs. %TPS Vs. Shift, Performance, High Alt.

[steveo]

Went ahead and tried it out. Read out my PCM first just for giggles, that worked perfectly. Did DBG_C but it appears that routine doesn't actually have an exit coded in yet. It loads the program, does the writes, but then just sits there hammering the bus with F108 messages rather than rebooting the T-Side and E-Side and disconnecting. Log attached.

yeah you can press unload kernel if you wanted afterwards

if the bin you've loaded is unchanged (except for the eeprom) just press flash write and it should take care of things

one unresolved issue is we currently use the vin for the 'vehicle fingerprint' feature, but we're now automatically programming the vin from the loaded bin, so it would be pretty easy for a user trying different bins out to constantly and unknowingly change their fingerprint (which would just result in unnecessary reflashing)

the onboard eeprom programming routine itself runs regardless of any bin compare, since it's nearly instant if no changes have occurred anyway.

[steveo]

EDIT: Also, I noticed while editing that BIN I just read that it appears the function to clear Automatic Transmission tables on a manual isn't quite complete. It did set almost everything to FF, but it missed the last few cells of 38AE Shift Time (sec) Vs. %TPS Vs. Shift, Performance, High Alt.

actually i think you might have just uncovered an issue. might not want to use that new version to do a complete flash. i'll report back.

[steveo]

it turns out for some reason nobody has noticed that EE flashhack was clearing a totally incorrect region on the t-side (actually it's been clearing bytes in the ram area instead, due to a typo, which it doesn't write, so nothing was happening). the only reason you have FF bytes in that area are likely because you had been working with a bin that you had read back after those areas had been FF'd by eehack before.
i'll fix that

the region it's supposed to set to FF is offset 0x28A0 length 4150 bytes (this is from EEHack, but might be a bit conservative, which is why you had a few stray bytes at the end there)

[steveo]

i will start a new thread about this to stop polluting this one with non-CCM related stuff.
edit: also pulled the new version till i fix a few more things