Snagged a spare ecm at the pick and pull today!
$30.
I got the connectors with it, so I have a bunch of extra pins and the possibility to hook it up on the bench.
There are never any LT1 cars out there, so I got pretty lucky.
Anyway, whenever you feel fairly good about it I can test flashing, as if I brick it it's not a total loss.
1994 LT1/4L60E Formula
that's really nice of ya!
here's the latest beta version if you want to try it, im pretty sure it's safe now.
http://fbodytech.com/download/223/
to be extra helpful, please enable debugging and leave the debug window open when flashing. if something goes wrong, please copy/paste the entire log into a notepad document or something
anyone else that wants to try it is welcome..
Flash successful!
I did notice at the end of the debug log there is this:
I don't know if that is expected or not, but it flashed properly anyway.Code:REPLY MATCH OK: =F45706AA05 WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F45609AD Write buffer too slow !
I did the whole bin, both sides. have not tested flashing a single side.
1994 LT1/4L60E Formula
awesome! i really appreciate you taking a chance on it.Originally Posted by fbody_Brian
[/quote]I did notice at the end of the debug log there is this:
I don't know if that is expected or not, but it flashed properly anyway.Code:REPLY MATCH OK: =F45706AA05 WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F46204000000000000000000000000A6 Write buffer too slow ! WRITE=F45609AD Write buffer too slow !
I did the whole bin, both sides. have not tested flashing a single side.
that's sort of expected. those are messages intended for normal 'disconnection' that cancel any mode4 effects (and make damn sure they're cancelled), and resume normal comms. in this case, they don't work, which is no big deal.
thanks again for testing! it's great news. my test ECM is bricked right now (until my chinese sockets n chips arrive), and i only have one car, so i'm unable to do any testing myself.
I was hoping I wouldn't be out there in the driveway in the dark swapping out my ecm. lol
It's my only car and I have to work in the morning.
I really like the progress meters and that it shows each side and you have an idea what's happening. It's definitely already better than what else is available. How confident are you about just flashing one side, using the previous bin?
I'm usually making just small changes, so it would be a welcome change.
1994 LT1/4L60E Formula
thanks, that's exactly what i was going for... i'm not hiding anything about the operation, and it's open source, so the entire flashing routine is publicly exposed.I really like the progress meters and that it shows each side and you have an idea what's happening.
along those lines, i've found the 'erase' procedure to be a bit 'scary looking' since it just kinda freezes while erasing, im going to improve that so you see some activity and know that it's still trying to erase. (the program actually does get status updates during that time)
it should work fine, in fact since it only erases one side, it should carry half the risk (and take half as much time).How confident are you about just flashing one side, using the previous bin?
that's why i made the compare feature, if you use it properly makes such operations safe if you don't quite know what you've changed and what side that code is on. i have a fairly good understanding of how the flash procedure works now, and what it does, and i can't forsee any problems.
of course the compare feature itself is only lightly tested at this point, as is flashing, so again, use at your own risk.
i can't wait till i get sockets, im going to test the hell out of it in every possible condition.
Changed a small bit in my bin file, loaded write bin and prev bin, it showed just e-side checked. I clicked upload bin file to ecm. It then proceeded to erase and write t-side, followed by the e-side. And it may be just in my head, but I swear that the fans didn't cut on at the beginning. I was sure that it was going to be ecm swap time. It finished successfully though.
1994 LT1/4L60E Formula
i just realized the beta i posted has force enable of both sides, so im not suprised that happened..
here's the latest
http://fbodytech.com/download/223/
well, just writing e-side failed...
1994 LT1/4L60E Formula
damn what happened? did you get a log?
it sat there saying erasing forever, I thought it was going to fail. Then it said writing e-side, then it popped up a message saying that the write failed and that my ecm was probably toast. lol
Code:WRITE=F45608AE WRITE=F45608AE WRITE=F45608AE WRITE=F45608AE READ =F456 READ =08AE WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025608446A21FD1C0075FE66660000008080808000000000000000872000000000D0000000000093 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025607436A20FD1C0076FE66660100008080808000000000000000872000000000EE000000000076 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025606446A20FD1C0075FE66660000008080808000000000000000872000000000EC00000000007A WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025606436E21FD1C0075FE66660000008080808000000000000000872000000000EC000000000076 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025605436E20FC1C0076FE66650100008080808000000000000000872000000000D500000000008F WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025605446A21FD1C0075FE66650000008080808000000000000000872000000000E3000000000084 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025605446A21FD1C0075FE66650000008080808000000000000000872000000000D4000000000093 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025604446B21FC1C0075FE67650000008080808000000000000000872000000000D4000000000093 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025604466E20FD1C0075FE66650100008080808000000000000000872000000000D0000000000092 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025606436A21FD1C0078FE67660000008080808000000000000000872000000000CF000000000093 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025607446B21FD1C0077FE66660000008080808000000000000000872000000000CF000000000092 WRITE=F4570100B4 READ =F492 READ =0100000000000000003C2F00000040004000FFFF00FF025606446B20FD1C0077FE67650000008080808000000000000000872000000000CC000000000097 WRITE=F4570D01A7 READ =F459 READ =0D0150EF66 WRITE=F4590D02AF10E5 READ =F458 READ =0D02AAFB Successful unlock routine! WRITE=F45605B1 READ =F457 READ =05AA06 WRITE=E4570D01B7 READ =E459 READ =0D0150EF76 WRITE=E4590D02AF10F5 READ =E458 READ =0D02AA0B Successful unlock routine! WRITE=E45605C1 READ =E457 READ =05AA16 Sending MEMORY CONTROL LOOP to t-side: WRITE=F4FF06014686AA3618308606C601FEFFBCAD0032392E178B558D2918A6008D2418085A26F6962E408D1A1F2E40FCB6180384BFB7180337C60B5A26FD331D2D0818383239BD01931F2E80F9A72F9B2E972E3937C655F7103A53F7103AC650F71806C6A0F7180633393CCE10021D000838393CCE10021C0008383936200336860A374D270BC64BBD01935A26FA4A26F533323937FC100EFD1016337F10222007B61023848027058680B71023396A READ =F457 READ =06AA05 WRITE=F4FF0600AF86AA3618308606C601FEFFBCAD0032392E810626D98D3A972C7A00318D33972D7A003118DE2C8D2918A70018087A003126F48D1D5D26B718DE2C18AD0020AF8D103C30CC05AAED00C602BD012C387E009D183C18CE05757F002F7A002F260418092707BD01931F2E0E0538387E009D1F2E20E7A62F16DB2ED72E18383936183C3C1838CE10008608A72D37C60B5A26FD33B618038A40B71803B618028A40B718024F972E86F48D4B READ =F457 READ =06AA05 WRITE=F4FF06001886AA3618308606C601FEFFBCAD003239E07E01D3000000000000000000000000000000000000000000000000000000000000008E004A0FB618018A80B71801B61800847FB71800B6180384BFB71803B610098A01B71009B6100884FDB71008B610038A08B71003BD01A93C3013320107CC0601ED002008143201CC06AAED00C602BD012C38CE10008604A72DEC2E4F972E1C2D028D5281F426EB8D4C805625E597318D44810527AD READ =F457 READ =06AA05 WRITE=F480060000204920470000000000000000000000002000FFFF7E012C7E01937E01A97E01B27E01BB7E01BE7E018C READ =F457 READ =06AA05 Sending MEMORY CONTROL LOOP to e-side: WRITE=E4FF06013E86AA3618308606C601FEFFBCAD0032392E178B558D2918A6008D2418085A26F6962E408D1A1F2E40FCB6180384FBB7180337C60B5A26FD331D2D0818383239BD018B1F2E80F9A72F9B2E972E3937C655F7103A53F7103AC650F71806C6A0F7180633393CCE10021D000838393CCE10021C0008383936200336860A374D270BC64BBD018B5A26FA4A26F533323937FC100EFD1016337F10222007B61023848027058680B710233956 READ =E457 READ =06AA15 WRITE=E4FF0600A786AA3618308606C601FEFFBCAD0032392E810626D98D3A972C7A00318D33972D7A003118DE2C8D2918A70018087A003126F48D1D5D26B718DE2C18AD0020AF8D103C30CC05AAED00C602BD0124387E0095183C18CE05757F002F7A002F260418092707BD018B1F2E0E0538387E00951F2E20E7A62F16DB2ED72E18383936183C3C1838CE10008608A72D37C60B5A26FD33B618038A04B71803B618028A04B718024F972E86E48D0B READ =E457 READ =06AA15 WRITE=E4FF06001086AA3618308606C601FEFFBCAD0032397E01B37E01B67E01D87E01CB0000000000000000000000000000000000000FB6180284FCB71802864997018E004A0FB618018A7FB71801B6180384FBB71803B610098A01B71009B6100884FDB71008B610038A08B71003BD01A13C3013320107CC0601ED002008143201CC06AAED00C602BD012438CE10008604A72DEC2E4F972E1C2D028D5281E426EB8D4C805625E597318D44810527DD READ =E457 READ =06AA15 WRITE=E478060000203C20470000000000000000000000002000FFFF7E01247E018B7E01A17E01AAC7 READ =E457 READ =06AA15 WRITE=E47F0602009D1D86AAB755558655B7AAAA8690B755559D1A3C3C30FC2000ED02CC06AAED00C6049D14383839F6 READ =E459 READ =06AA000013 WRITE=E4D80602493C30CC06AAED00C6029D143839CC06AA2003CC06073C30ED00C6029D14389D1A3936373C3C30CC0655ED00C6029D1438383332399D294FB702C8DE1208094F369D2632270F7C02C8F602C8C10525058DD07F02C89D1DC640E700C600E7009D17C6C0E7009D1AE60027074C811923E520099C1026C8CC00002003CC06063900003E READ =E457 READ =06AA15 WRITE=E4AE060200BD027D1A83000027037E025E4FB702C7DE109D1DC620E700E7009D230908C6A0E7009D179D1A369D2632270F7C02C8F602C8C10525058D327F02C8C6FFE100270F4C26CE7C02C7F602C7C10C23C4200B9D1D9C1226C71E READ =E457 READ =0606B9 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WAITED_TOO_LONG in serial_read_packet: Bytes =0 WRITE=F46204000000000000000000000000A6 WRITE=F46204000000000000000000000000A6 WRITE=F45609AD
1994 LT1/4L60E Formula
Do you have part numbers for the chips and sockets?
1994 LT1/4L60E Formula
You will need sockets only of the following type PLLC32 smt(surfice mount)
Flash chips will be reuseable. In the rare case of chip failure PN is an28f512 -120
Also you will need some programmer and raw rom image of the chips.
I ordered some sockets. I have the equipment to do the chip removal and solder the socket on. I'll need to get a chip programmer. I have one for pic micro-controllers, but don't think that will work.
Where or how do I get a basic raw rom image, something just to get it talking?
1994 LT1/4L60E Formula
so what happened is the second part of the erase program was uploaded. usually it would respond with a message 0x55 for each stage of the erase procedure, and 0xAA when complete. i've never seen a message 0x06 response, but the checksum is correct, so it's a legit message.. i'll have to do some disassembly and try to figure out what makes that occur.
this might be the program bitching about starting the erase procedure, but that means your ECM should still be in a useable state? so it's more likely it started trying to erase and something went horribly wrong
Posting Permissions
Reply With Quote
Bookmarks