zte s165 dcc write error in 1.62, 1.61

[partha ghosh]

AFter activating 30 crdedits every cdma phone write flash error, before v1.57 working good

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.40 (RIFFBOX1), JTAG Manager Version: 1.62
Selected Resurrector: [ZTE S1602 V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x122CE0E1 - CORRECT!
Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]
Settings Code: 0x24010000000000000000000000800000

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: 0x0020/0x88C0 (8MB)

Writting FLASH1 memory from 0x000000000000 to 0x0000007FFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000000030000

here is only 1 example, but i have all cdma write flash problem

pleasesolve my problem thanks

[anuyash]

yes i also have problem in 3 boxes

[Legija]

First You have to set RTCK to 1MHz, to make sure it's not connection quality problem.
0x30000 of data was written already in first log, so this is probably connection issue.

[ramchandra]

zte s165 dcc write error in 1.62, 1.61

i am unable to write dump in zte s165 in dcc read/write.
i never got any error in 1.56 and 1.37 firmware.
after update to riff box 1.62 and firmware 1.40 it give error in dcc read/write.

please fix this error? and tell me solution?

[Legija]

Please post logs.

[partha ghosh]

how to solve this prb sir.

[Legija]

how to solve this prb sir.

Can You read ?

First You have to set RTCK to 1MHz, to make sure it's not connection quality problem.
0x30000 of data was written already in first log, so this is probably connection issue.

[anuyash]

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: 0x017E/0x0063 (16MB)

Writting FLASH1 memory from 0x000000000000 to 0x000000FFFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000000150000


error on flashing s183

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: 0x017E/0x0063 (16MB)

Erasing FLASH1 memory from 0x000000000000 to 0x000000FFFFFF..

earsing is working in s183 but flash not working

[Legija]

@anuyash

Please post complete logs from operations You've performed.

[ramchandra]

here is log for zte s165

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.40 (RIFFBOX1), JTAG Manager Version: 1.62
Selected Resurrector: [ZTE S165 V1.0.4609.43971]
Restarting target (nRST Low then High)...OK

Connecting to the dead body...OK
Detected dead body ID: 0x122C80E1 - IGNORED!
Set I/O Voltage reads as 1.80V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 1 MHz]
Settings Code: 0x26010009000000000000000000800000

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: 0x0001/0x007E (8MB)

Writting FLASH1 memory from 0x000000000000 to 0x0000007FFFFF
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000000010000

i am facing same problem in s183 8mb flashing.

[ramchandra]

both are working good in old ver 1.56 and firmware 1.37

today i have 4 handset. 1 zte s165 and 1 s183 8mb.

[ramchandra]

i think its problem in riff box firmware. because i have installed old ver in my another pc.
same issue on that pc with 1.56.

its fault in riff box firmware.

please fix it

[Legija]

If I remember well, not all chips was supported with S183 DLL.

We know that this can be problem in new firmware, and this is why is very important for us to see complete logs of every tested unit.
Logs can be extracted from "JTAGManager.txt" file in RIFF directory.

Please find these logs and post them here.

We may also need one user with decent internet connection for tests over Remote Helper system.

[ramchandra]

If I remember well, not all chips was supported with S183 DLL.

We know that this can be problem in new firmware, and this is why is very important for us to see complete logs of every tested unit.
Logs can be extracted from "JTAGManager.txt" file in RIFF directory.

Please find these logs and post them here.

We may also need one user with decent internet connection for tests over Remote Helper system.

i am available here. you can contact me at any time at yahoo
raj.tataindicom@yahoo.com
i am available at yahoo msgr.

i have 2 phone in my hand. one zte s165 and s183 8mb

[anuyash]

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.40 (RIFFBOX1), JTAG Manager Version: 1.62
Selected Resurrector: [Micromax C111 (QSC1100) V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x122C80E1 - IGNORED!
Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 800 kHz]
Settings Code: 0x24010008000000000000000000800000

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: 0x0001/0x007E (8MB)

Resuming write FLASH1 memory from 0x000000000000 to 0x0000007FFFFF on 0x000000010000
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Timeout while waiting for DCC Loader response. Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x000000010000