Printable View
Sweet, thank you for the unique vehicle identifier code! Tested it by reading both cars, and it saved the unique IDs just fine. Will need to actually make some changes to see if it recognizes them too but glancing at the code it should do that without any issues.Quote:
Originally Posted by steveo
That said, this time I did manage to catch that "unable to reboot T-Side" error on the '94. I've attached a log to this post.
It doesn`t get response on the reboot request. Than the pcm reboots and response on second upload request that is locked. Flashhack assumes it lost comm and tries to unlock pcm. It manages to unlock pcm and enters mode5, than tries to upload reboot code which also crashes tside. Some death loop is triggered here out of nowhere.Quote:
Originally Posted by NomakeWan
Maybe we can increase the timeout before the pcm crashes on reboot upload, so there is enough time for the response to be send.
it would definitely be nice to get a response from that reboot command. we could make a program for rebooting the tside that actually sends the response first then continues to execute so it behaves as expected?Quote:
Originally Posted by kur4o
Thanks for the update Steveo - I'll skip ahead to the new version.Quote:
Originally Posted by steveo
I'll check out the fingerprinting - that could take care of the multiple vehicles with multiple shared PCMs scenarios I had in mind.
Should be covered by having a unique id for each PCM and keeping the latest installed bin configuration for use as the reference.
I'll test out b0.6.1 this weekend.
Jim
just so you know how it works, the 'unique vehicle id' fingerprinting uses a slightly cascaded sum of the calibration id and checksum, which are both values that never change when uploading new bins. make sure your ECMs don't have the same vin and cal id set for some reason.
its a very weak fingerprint that i wrote but i think the odds of a collision exceed the likelyhood that an asteroid will hit the earth every hour for the next year or something. i'm not great with math.
if for some reason my weak sum fails and you run into a collision, it still checksums both the ecm and your local bin before flashing them, so in the worst case it'll just flash the other half of the ECM when it doesn't need to and waste a minute of your time.
Thanks for the info Steveo - the b0.6.1 read/write functions worked with no issues on a 95 F-body, as expected.Quote:
Originally Posted by steveo
However, the vehicle fingerprint kept changing on each subsequent write to the same PCM. Since flashhack then couldn't find a matching fingerprinted bin, each time it defaulted to a full write. It did create and store a new reference bin for each write.
I wrote to the PCM four times alternating between two bins. The only difference between the bins is a spark tweak to test selective write. Here are the four fingerprints:
14MNAO5G24A25TWKA9F
14MML85G24A25TWKAXV
14MMNG5G24A25TWKAVN
14MNGN5G24A25TWKA3G
I verified the PCM vin and cal ids were unchanged using eehack, and read back the last two writes from the PCM using flashhack including the ram region and there were no differences in the cal / vin region.
Hopefully there's enough info above to help point you to the problem. Let me know if you need something more.
Jim
ah that was a typo. posted a new version should work better
Ooh, I'm gonna have to get me one of those OBDX devices. I don't yet have an OBDII $EE, but if I were to get really lucky I might someday. It'd be nice to be able to flash and tune those LT4s just like I do the LT1s.
Also looking forward to the new reboot routine, whenever that gets done. No big in the meantime, I can just load the kernel then unload it again to do the same thing. Cheers!
i had a thought about the reboot routine but i'm working on too much other stuff to play with it. i do want a proper response from it so we can maintain some protocol. its really nice to not have to make workarounds for a bunch of stuff.
the obdxpro seems really nice so far, i do have it talking just on its own, but there are bugs to iron out before i'll even bother hooking it to an ECM. the documentation is a bit incomplete. also there's the small matter that i know absolutely nothing about these ecms or their protocols but i'm sure i'll get there.
Thanks Steveo - I'll grab the new version.Quote:
Originally Posted by steveo
Jim
i've fixed the reset bug. the e-side was actually the issue. when first resetting it, seems to generate some SPI crap that hangs the tside for a moment, so just needed a small delay in between rebooting the eside and tside. also added a small delay to the reset code itself just to make sure the response has a chance to make it before we wipe the kernel out (probably unnecessary but whatever)
Steve, I have down loaded the new flashhack and tried to get my original bin loaded from the 94-Buick Roadmaster system I'm using. I've read it several times but when trying to save it the file it won't save as a .bin file. I've uploaded the saved files just to check the data into Tuner Pro but nothing was in the file. The "save as type" doesn't offer a bin type.
Want to save original before using an existing bin for the updates I need to make.
i don't understand what that means. do you mean the file is empty? have you pressed 'read calibration'? can you post the log of that?Quote:
I've uploaded the saved files just to check the data into Tuner Pro but nothing was in the file.
yeah it does and has for a few versions now. you might not be using the latest versionQuote:
The "save as type" doesn't offer a bin type.
Sweet! Can’t wait to test out 0.6.3 when it’s out.Quote:
Originally Posted by steveo
im pretty sure it's 100% but if people report problems i can increase the delay further. i want you to test the multiple vehicle thing too.