your aldl comms might be sketchy, but is it throwing any DTC errors?
your aldl comms might be sketchy, but is it throwing any DTC errors?
oh also make sure the ecm has been booted up for a little bit (30 secs i think?). before flashing
Letting the pcm "boot up" made all the difference. One thing I am noticing, one of my chips keeps hanging at the same address. Is this likely a failing chip? I am also seeing data breaks while data logging, this proceeded the first crash.
so its crashing at adress 2D80 on 2 different chips. I am going to try another bin but is there a way to burn the bin directly to a chip or is the bin we use to revive a chip just pulled from a living chip?
yeah it’s pulled from a living chip
ill build a converter soon
i have a new 8051 ecm coming thanks to a really awesome eehack user
ill backtrace those stupid address lines and eehack will be able to spit out a bin in the either format in like 0.5 ms
That would make this soo much easier. I had this stupid thing crash 5x today trying to update a spark table.
so cant get it to take a tune now. Looks like I'll be driving to corvette for a while
Last edited by space387; 01-25-2020 at 06:41 AM.
I have seen similar behaviour with bad cable. The flash goes smoothly till some point, when the cables freaks out. Also a PC or laptop crap power supply can totally destroy usb communication. And the last reason is not enough current or low voltage supply. Are you trying to flash on a bench with some shoddy power supply?
it really sounds like the chip to socket to board connection might be imperfect
are both eehack and tunercat/winflash producing the same error
haven't tried tunercat yet but I will absolutely check tomorrow to be sure I have good contacts within the socket.
Any luck with the bin splitter steveo?
nah haven't worked on it yet sorry
i'll probably be more motivated when my test bench is running again
Steveo I was watching a video on youtube about building a 16bit ecu and saw them using an arduino to record the address and data sent to in and out of the ecu. Because we have access to the memory chip is this the info you need for the bin splitter?
The arduino I have only has enough ports to give you address only but knowing the order they write should allow us to match to the locations used. I'll see what I can do this weekend to replicate what I saw.
Bookmarks