Programming Error (0x25) is it HW?

[delower10]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.81V, TCK Frequency is 8 MHz

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0001 (VYL00M, 0x03AB400000 Bytes)

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x0000000000 is handled as Cut Excess.
ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x040000)

[dailor]

Almost same here:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.32, JTAG Manager Version: 1.43
Selected Resurrector: [Samsung i9100 V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, TCK Frequency is 100 kHz

Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0001 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x000000080000 Bytes = 0.50 MB)

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)

Regarding this analogue issue commented by Legija, maybe it is HW problem with NAND.

[BABAK NURI]

Hi
..................................

Error code 0x25

Returned by the DCC Loader when it fails to program part of flash memory. This is not an abnormal situation for NAND memories – bad blocks and pages are sometimes appear due to specific NAND memory’s technology. User shall select how to handle block program error in the JTAG Manager – for this user must be familiar with bad blocks handling techniques in general.

[dailor]

OK, but error 0x25 refers to Error Code 0x24. I already tried both Cut Excess and Overlap with Ignore set to react on Error during Flash Write, results in same respond by JTAG Manager (even different TCK Frequencies).

[legija]

Originally Posted by dailor

OK, but error 0x25 refers to Error Code 0x24. I already tried both Cut Excess and Overlap with Ignore set to react on Error during Flash Write, results in same respond by JTAG Manager (even different TCK Frequencies).

You don't understand what is bad block then.

DCC Loader reports that there is bad block at specific address. Bad blocks are unrepairable, but can be skipped and device can function normally up to some percent of bad blocks.

With eMMC memory chips, things are different. eMMC contains it's own controller, and problem You have comes as response from controller it self. This error in irrepairable, and You need to replace eMMC chip with working one.

[dailor]

Originally Posted by legija

You don't understand what is bad block then.

DCC Loader reports that there is bad block at specific address. Bad blocks are unrepairable, but can be skipped and device can function normally up to some percent of bad blocks.

With eMMC memory chips, things are different. eMMC contains it's own controller, and problem You have comes as response from controller it self. This error in irrepairable, and You need to replace eMMC chip with working one.

Thanks for good explanation, that is what I really want to know, i.e. this error refers to pure HW issue and need chip replacement.

Best Regards