Page 1 of 2

Bricked Holden VF HUD recovery

Posted: Fri Apr 01, 2022 7:42 pm
by hjtrbo
Hey all,

Bricked my* Holden VF HUD unit doing an SPS update over CAN.

There is a flash memory chip on the board with part number S25FL032P. I do have another** HUD sitting here but it is a different Holden part number. The chips on that board have the same numbers.

Code: Select all

Part			| Year	| Eng	|Model		| OS			| Cal ID 1		|Cal ID 2		
----------------------------------------------------------------------------------------------------------------
92280511 * 	| 2016	| LSA	| VF CALAIS	| 92289162	| 92284266	| 92294931 
92273303 **	| 2014	| L77		| VF CALAIS V	| 92289164	| 92274239	| 92294929 
https://www.infineon.com/dgdl/Infineon- ... -datasheet
VF2 R8 2.jpg
Before I swap in the replacement I would like to see if it is possible to recover the original. Has anyone got any suggestions on what I need or someone to send it to (or a home call near Warragul VIC)? I am a novice and have only ever programmed 1 eeprom a long time ago.

Cheers, HJ

xref https://forums.justcommodores.com.au/th ... es.294081/

Re: Bricked Holden VF HUD recovery

Posted: Fri Apr 01, 2022 9:29 pm
by Tazzi
How do you know it’s bricked? What exactly did you do?

This would determine whether it’s recoverable over obd or not.

Re: Bricked Holden VF HUD recovery

Posted: Fri Apr 01, 2022 10:07 pm
by hjtrbo
I was using SPS2 and VX Diag Nano to update all the modules on my car (VF2 R8). I wasn't following good flashing practice is what I think happened. I'm thinking something along the lines of the battery voltage dipped momentarily during the flash (no battery maintainer or fully charged auxiliary battery was connected) or I had a bit of spike on the comm line from my laptop as it was connected to the AC charger (not isolated from earth).

Steps;
I tried repeatedly to reprogram straight away. NG
Disconnected battery overnight and reconnected the next day and tried to reprogram. NG
Used GDS2 to perform module diagnostics. Was not able to find module. NG
DTC's stored in radio and IC for loss of comms to HUD. NG

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 8:51 am
by Tazzi
Based on that, I’d say your entire operating system is wiped, and only a partial write back has been achieved before communication dropped out and sps exited the running bootloader.

In that circumstance, module would be bricked as it’s missing it’s OS. There is no repair for that over OBD unfortunately.

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 9:41 am
by hjtrbo
Cool. Can anything be done at board level while it's all apart? I do have another board sitting here but it is from a different part number HUD 2016 R8 (Mine) vs. 2014 Calais V (Spare). I was thinking of swapping the main boards and see what happens when I plug it in.

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 11:15 am
by hjtrbo
Great, installed replacement. Working fine except it had the Holden logo instead of HSV so went to update via SPS and like last time it fucked this one. Same deal. Had everything hooked up properly this time.

I have 2 bricked boards if anyone wants them.

The bins are attached. 2016 VF2 HSV R8 Clubsport LSA

Part Number 92280511
OS 92289162
Cal ID 1 92284266
Cal ID 2 92294931

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 1:06 pm
by Tazzi
A standard non HSV HUD cannot be programmed with a HSV system as they are not compatible from my previous work with them.

Once I'm back from holiday, I will check if any of my previous work includes recovery on HUDs.

Another issue you could be facing is the VX nanos are not something I would trust being 100% j2534 compliant, which could be causing the failure.

Are you able to attach the SPSlog which is saved in the same location the bins are saved? That will indicate where why its failed.

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 1:14 pm
by hjtrbo
Thanks Tazzi for your interest and replies.

Something went amiss with java???

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 2:31 pm
by Tazzi
Looking through that, appears theres heaps of communication dropouts occurring while programming. This could be due to other modules interrupting, or the vx nano was unable to successful transmit reliably.
I believe its actually a combination of both of those things, since the size of the update blocks being sent are huge so theres high chance of issues occurring. The module responds back with a failed writing at the end meaning its completely failed the Operating System write.

Personally, I find my own vx nano can fail processing large can blocks (over 4000 bytes) when using my own software so I make sure it does smaller blocks. Obviously you don't have this choice when using GMs SPS2 :thumbdown:

I can take a look at it, feel free to send me a PM.

Re: Bricked Holden VF HUD recovery

Posted: Sat Apr 02, 2022 6:13 pm
by hjtrbo
Thanks Tazzi, PM sent.

Quick one for you before this thread goes quiet for a while, I was running x64 Java latest version v8.321 I have had it pointed out to me the GM wants Java x86 v8.45. Could that of contributed? I seen the timeouts in the log but it was ticking over slowly. Then just shat itself. I would like to understand the autopsy a little better.