[diagso]

I don't have parallel programming checked. It is not related to this option.
I've reloaded Emmc a few times and unfortunately it doesn't help

I would go for v850 clear, factory reboot and then flash via esys. Or straight to p/d flash with programmer.

[laso]

I'm unlikely to be able to clean the V850 with a cable. I would need a dump to id4 changed to id6. Could someone assist? GPS version

[donjuan020]

I'm unlikely to be able to clean the V850 with a cable. I would need a dump to id4 changed to id6. Could someone assist? GPS version

Is there communication with NBT? If you can contact Esys with NBT, I can help. If Esys is not communicating, first try a sandisk or micron emmc backup from the same hardware. If the problem persists, the problem is caused by GL. You will need a programmer who studies GL. If you write the healthy GL backup, communication will come.

[diagso]

Now I'm stranded and no clue why after programing ?

Part1
I used 4.43.21 data to program the unit via esys and it finalized the flash, but before coding it lost all communication (log attached). I had p/d-flash for it along with emmc backup - I've wrote it, but still nothing. Fan spinning fast but "no signal" on screen no communication via esys. So I started switching PCB and once I've exchanged one that has ports on the back it worked like a charm.

Part2
Now with replaced PCB unit boots in programing mode so let me flash it once again and boy was I suprise as exact same thing happen. For clarity I'm also adding the svt's, tal along with FA used for flash

Any idea how to fix those PCB's ?

[Siki78]

Try to add 654 dab and start flash again

[diagso]

Try to add 654 dab and start flash again

No communication with unit, hence not able to flash anything

[LeonidLunin]

First, check if oabr connected.

[diagso]

First, check if oabr connected.

It's on bench and I can guarantee that obar is connected. Not to mention I wrote that I flashed unit, if it was via uds I would mention it