ceron1977 (12th September, 2018)
... it seems that this hsfi 2.1 ecu bricked must have been suffered a bad writing. The flash memory could not support the hsfi 2.4 dump file. But i don't have a tool to boot this thing (for the moment) i.o. to reflash it to the initial state. I would not bother with it, because i have lots of 2.1s, but for the sake of research, i will try other tools in the future, hoping to rebring it to life.
ceron1977 (12th September, 2018)
Review: had the same problem, as i said (volo69 is me, also).
1st bricked hsfi2.1- copied the eeprom of the hsfi2.4, then the flash with kess(with error on the end of writting). After eeprom copy, all went ok, car didn't start, obviously. After copying the flash, ecu got bricked no interface can recognize the ecu(wake up error). No flasher (nor mpps18, kess, galletto, avdi abrites, carprog, mdi sps) could read this. The mil light flashed intermittently 0.5hz.
2nd bricked hsfi2.1- copied the flash first with mpps18, got a wake up error at the end.
Somebody tried with io terminal. Could read the ecu as being an undefined hsfi model. Could not reflash it with io terminal to the original state(as an hsfi2.1!) So, here are the facts! To me, it seems like this is a real issue, and the hybrid ecus ar sh*tty!
ceron1977 (12th September, 2018)
Corrupted message. Sorry
Last edited by volorucinski; 18th August, 2018 at 11:04 PM.
ceron1977 (12th September, 2018)
ceron1977 (12th September, 2018)
Does anyone know what type of eeprom has hsfi 2-1 ? I think it could be read /write using an external programmer ,maybe with help of lowering supply voltage or shorting xtal on the board ...
ceron1977 (12th September, 2018)
I have the tool but i don't have the time to identify the jelly sh*t cmd points on the ceramical pcb. It will be easy if i could recognize a similar flash/eeprom/cpu pins on the pcb... there are no smd components to identify as a known capsule. that is the tricky part.
Last edited by volorucinski; 12th September, 2018 at 07:49 PM.
ceron1977 (12th September, 2018)
It has to be an i2c ic somewhere, on the pcb... the z18xe has it. But who the f can put the bdm sticks on those tiny little dots, there, without breakimg the golden wires? I will try when witer comes to rebring those bricked ecus to life. If you have a st memory flasher, you can try playing. After you identify the boot pin or the i2c connectimg points!
I've found on forum that hsfi 2.2 can be written in hsfi 2.1 ? Somebody tried this? Will this work?. I know that hsfi 2.2 has can..but those wires can be connected on hsfi 2.1
Thanks!
Sent from my V9H using Tapatalk
Had a look once at both 2.1 and 2.2 ,they are 90 and so % same but not 100 % .Few parts missing ,few extra ..
I saw that. Bit stii need flash. No one seems to have flash for this ecu.
Sent from my V9H using Tapatalk
Let's see... Sda scl... Do this tell you something? Blocked ecus can be brought to live by writting the eeprom with a spi interface... I've got a hsfi 2.1 resetted with Carprog... Never reset with carprog! Just get the carpass and reset it with Opcom... I have learned my lesson... Resetted with CP, ecu sits for a loooong while in its world... In security wait time like, but no, it is in a f@#$*#-::$!!king state of wilderness and never comming back with nothing... Except connecting on pcb thru spi and writting the eeprom again... Old sh*t, i know, but my country is full of this sh*tty type of ecus.
Last edited by volorucinski; 16th April, 2019 at 11:38 PM.
Alladdin205
I've got a 2.2 flash and eeprom dumps... If you are still looking for... CP can r/w this files
I had reset one hfsi 2.1 with carprog...
First I get the pin and after I reset it....
I can remember when read the pin after resetting, I had ffff....
Ecu works fine at car....
Maybe I was lucky....
Yes,i know it's a piece of s**t.i didn't try, to flash 2.4 in 2.6 because there are some hw differences.
Bookmarks