Bricked MSS54HP, turns on for a few seconds

[sapote]

Engine was able to run for a sec, so I think the DME firmware programming is ok. Can't imagine engine can fire up with corrupted codes/data DME.

[sapote]

I flashed an MSS54HP with the CSL software

Is it your original DME or a spare S54HP? To narrow down if it's hardware or firmware issue, I would install the stock DME back to test.

[D-O]

Engine was able to run for a sec, so I think the DME firmware programming is ok. Can't imagine engine can fire up with corrupted codes/data DME.

Fires on one cylinder and dies sounds like what I experienced when having EWS delete issues.

Unresponsive to software/programming tools and a maxed out temp gauge sounds like it is stuck in program mode. At least that is what I experienced.

He has not responded, so maybe he sorted it out.

[Nexite]

Hey sorry guys! This is a second DME, my stock dme works completely fine and I just did a 800 mile roadtrip on it no problem.

[Nexite]

Finally have some time to work on this again, I tried re-programming via winkfp, the DME is able to identify itself and report the old VIN of the car it was taken off of (I BDM the stock image back on) but then when WINKFP goes to actually start updating it it gives the following error. Comfort mode -> Update ZUSB -> MSS54 -> No vin entered -> Done -> Program ZUSB update. I know its been a while but any insight anyone could give would be great! Been running the stock Alpha N tune and its getting to me a bit lol.

One note, the ECU seems to be more functional than it was before, it now properly reports the temperature and RPM of the engine to the gauge cluster but doesn't show the check engine light when turning the ignition to the second position (which I believe it does do on my normal ECU).

[karter16]

Finally have some time to work on this again, I tried re-programming via winkfp, the DME is able to identify itself and report the old VIN of the car it was taken off of (I BDM the stock image back on) but then when WINKFP goes to actually start updating it it gives the following error. Comfort mode -> Update ZUSB -> MSS54 -> No vin entered -> Done -> Program ZUSB update. I know its been a while but any insight anyone could give would be great! Been running the stock Alpha N tune and its getting to me a bit lol.

One note, the ECU seems to be more functional than it was before, it now properly reports the temperature and RPM of the engine to the gauge cluster but doesn't show the check engine light when turning the ignition to the second position (which I believe it does do on my normal ECU).

Not a winKFP expert but I'm pretty sure that bootsectorupdate should not be active.


Sent from my iPhone using Tapatalk

[terra]

Not a winKFP expert but I'm pretty sure that bootsectorupdate should not be active.


Sent from my iPhone using Tapatalk

I don't think it makes a difference for ECUs that don't have 0ba files anyway

Honestly I wonder if his ECU is having the same issue one of mine on the bench was having. The slave CPU just drops out intermittently. A second ECU works fine

[Nexite]

I don't think it makes a difference for ECUs that don't have 0ba files anyway

Honestly I wonder if his ECU is having the same issue one of mine on the bench was having. The slave CPU just drops out intermittently. A second ECU works fine

Is there any way to test this or good resources for the pinouts of the CPUs? I've got access to a good scope and multimeter.

[terra]

Is there any way to test this or good resources for the pinouts of the CPUs? I've got access to a good scope and multimeter.

Dunno if there's a good way to test. I think the pinout matches this, but not 100% sure https://www.nxp.com/docs/en/user-guide/MC68336376UM.pdf

[Samsonite79]

I haven't messed around DME in a long time but if my memory serves me right, maybe you need to put it in boot mode.

https://nam3forum.com/forums/forum/special-interests/coding-tuning/113973-mss54hp-boot-mode-grounding-pins-32-on-the-eeprom