GSM Shop GSM Shop
GSM-Forum  

Welcome to the GSM-Forum forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.

Registration is fast, simple and absolutely free so please - Click to REGISTER!

If you have any problems with the registration process or your account login, please contact contact us .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > GSMServer Products > Medusa

Reply
 
LinkBack Thread Tools Display Modes
Old 10-25-2018, 00:08   #1 (permalink)
Junior Member
 
Join Date: Sep 2018
Location: FRANCE
Posts: 11
Member: 2865074
Status: Offline
Thanks Meter: 0
Medusa Pro JTAG Memory Dump question [Answered]


Hello, I just received my medusa pro box.
I am using Medusa Pro Software Solution 1.6.9.
I connected to JTAG on SAMSUNG I9505 and I want to fall on his memory.
The software reads the memory and a moment the connection is cut. This has happened to me at the RiffBox2 or the xxx Box, and with these boxes, when we resume the dump, the operation continues where it stopped.
With the box medusa, I have to start all over again from the beginning. Is there a function to allow to continue the dump when it stops? or do you have a tip?
Thanks in advance.

Last edited by Medusa Box; 10-25-2018 at 04:19.
  Reply With Quote
Old 10-25-2018, 04:18   #2 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 9,360
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks Meter: 3,398
Hello.

At first, please post here full Software log, we will check and advise You how to do the next.
  Reply With Quote
Old 10-25-2018, 10:03   #3 (permalink)
Junior Member
 
Join Date: Sep 2018
Location: FRANCE
Posts: 11
Member: 2865074
Status: Offline
Thanks Meter: 0
Hello, here are a few logs. I made several attempts. The dump begins during few minutes but stops. When I restart the operation, I have to start from the beginning



Model Settings:
Interface : JTAG
Core : Qualcomm APQ8064T
Voltage : 2000
Reset : RESET, Halt After 100 ms
Tap : Auto
Speed : Auto

Connecting...

Vref level is 1.76V.
Scan successfull, number of TAPs = 2.
TAP 0: Id code = 4BA00477, IR length = 4.
TAP 0: CPU name "Unknown", interface type = 0.
TAP 1: Id code = 2071B0E1, IR length = 11.
TAP 1: CPU name "Qualcomm APQ8064T", interface type = 9.
Enabling ARM Core...

Initializing interface...

JTAG speed : Auto (RTCK)
Protocol ver : 3.0
Buffer size : 0x10040 bytes
Storage type : eMMC
Storage ID : 0015:0001
Storage size : 15028 MB
Device : Samsung eMMC AFEABB
Page size : 512 B
Block size : 512 B
Block count : 30777344
Size : 14.68 GB (15028.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.6.9; FW: 1.24.
P00: GPT (00000000, 00002000) 4 MB
P01: apnhlos (00002000, 000063C8) 12.47 MB
P02: mdm (000083C8, 00019C38) 51.53 MB
P03: sbl1 (00022000, 00000100) 128 KB
P04: sbl2 (00022100, 00000200) 256 KB
P05: sbl3 (00022300, 00000400) 512 KB
P06: aboot (00022700, 00001000) 2048 KB
P07: rpm (00023700, 00000400) 512 KB
P08: tz (00023B00, 00000400) 512 KB
P09: pad (00023F00, 00008400) 16.5 MB
P10: efs (0002C300, 00006D00) 13.62 MB
P11: modemst1 (00033000, 00001800) 3072 KB
P12: modemst2 (00034800, 00001800) 3072 KB
P13: m9kefs1 (00036000, 00000618) 780 KB
P14: m9kefs2 (00036618, 00000618) 780 KB
P15: m9kefs3 (00036C30, 00000618) 780 KB
P16: system (00037248, 00564000) 2760 MB
P17: persist (0059B248, 00004000) 8 MB
P18: cache (0059F248, 0040B000) 2070 MB
P19: param (009AA248, 00003000) 6 MB
P20: boot (009AD248, 00005000) 10 MB
P21: recovery (009B2248, 00005000) 10 MB
P22: fota (009B7248, 00005000) 10 MB
P23: backup (009BC248, 00003000) 6 MB
P24: fsg (009BF248, 00001800) 3072 KB
P25: ssd (009C0A48, 00000010) 8 KB
P26: persdata (009C0A58, 00004800) 9 MB
P27: hidden (009C5258, 000FA000) 500 MB
P28: carrier (00ABF258, 0000A000) 20 MB
P29: userdata (00AC9258, 0128E000) 9.277 GB
Partition table has been found on device.
Save to D:/Medusa Dump folder...
Reading partition system... Read error at 0x0C719000...

ERROR[007]: Command fail.
At sector 407752
JTAG device has been disconnected.
Disconnected.

Model Settings:
Interface : JTAG
Core : Qualcomm APQ8064T
Voltage : 2000
Reset : RESET, Halt After 100 ms
Tap : Auto
Speed : Auto

Connecting...

Vref level is 1.76V.
Scan successfull, number of TAPs = 2.
TAP 0: Id code = 4BA00477, IR length = 4.
TAP 0: CPU name "Unknown", interface type = 0.
TAP 1: Id code = 2071B0E1, IR length = 11.
TAP 1: CPU name "Qualcomm APQ8064T", interface type = 9.
Enabling ARM Core...

Initializing interface...

JTAG speed : Auto (RTCK)
Protocol ver : 3.0
Buffer size : 0x10040 bytes
Storage type : eMMC
Storage ID : 0015:0001
Storage size : 15028 MB
Device : Samsung eMMC AFEABB
Page size : 512 B
Block size : 512 B
Block count : 30777344
Size : 14.68 GB (15028.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.6.9; FW: 1.24.
P00: GPT (00000000, 00400000) 4 MB
P01: apnhlos (00400000, 00C79000) 12.47 MB
P02: mdm (01079000, 03387000) 51.53 MB
P03: sbl1 (04400000, 00020000) 128 KB
P04: sbl2 (04420000, 00040000) 256 KB
P05: sbl3 (04460000, 00080000) 512 KB
P06: aboot (044E0000, 00200000) 2048 KB
P07: rpm (046E0000, 00080000) 512 KB
P08: tz (04760000, 00080000) 512 KB
P09: pad (047E0000, 01080000) 16.5 MB
P10: efs (05860000, 00DA0000) 13.62 MB
P11: modemst1 (06600000, 00300000) 3072 KB
P12: modemst2 (06900000, 00300000) 3072 KB
P13: m9kefs1 (06C00000, 000C3000) 780 KB
P14: m9kefs2 (06CC3000, 000C3000) 780 KB
P15: m9kefs3 (06D86000, 000C3000) 780 KB
P16: system (06E49000, AC800000) 2760 MB
P17: persist (B3649000, 00800000) 8 MB
P18: cache (B3E49000, 81600000) 2070 MB
P19: param (135449000, 00600000) 6 MB
P20: boot (135A49000, 00A00000) 10 MB
P21: recovery (136449000, 00A00000) 10 MB
P22: fota (136E49000, 00A00000) 10 MB
P23: backup (137849000, 00600000) 6 MB
P24: fsg (137E49000, 00300000) 3072 KB
P25: ssd (138149000, 00002000) 8 KB
P26: persdata (13814B000, 00900000) 9 MB
P27: hidden (138A4B000, 1F400000) 500 MB
P28: carrier (157E4B000, 01400000) 20 MB
P29: userdata (15924B000, 251C00000) 9.277 GB
JTAG device has been disconnected.
Disconnected.
  Reply With Quote
Old 10-25-2018, 10:58   #4 (permalink)
Junior Member
 
Join Date: Sep 2018
Location: FRANCE
Posts: 11
Member: 2865074
Status: Offline
Thanks Meter: 0
this is today :

Model Settings:
Interface : JTAG
Core : Qualcomm APQ8064T
Voltage : 2000
Reset : RESET, Halt After 100 ms
Tap : Auto
Speed : Auto

Connecting...

Vref level is 1.76V.
Scan successfull, number of TAPs = 2.
TAP 0: Id code = 4BA00477, IR length = 4.
TAP 0: CPU name "Unknown", interface type = 0.
TAP 1: Id code = 2071B0E1, IR length = 11.
TAP 1: CPU name "Qualcomm APQ8064T", interface type = 9.
Enabling ARM Core...

Initializing interface...

JTAG speed : Auto (RTCK)
Protocol ver : 3.0
Buffer size : 0x10040 bytes
Storage type : eMMC
Storage ID : 0015:0001
Storage size : 15028 MB
Device : Samsung eMMC AFEABB
Page size : 512 B
Block size : 512 B
Block count : 30777344
Size : 14.68 GB (15028.00 MB)
Connect successful.
---------------------------------------------------------------
SW: 1.6.9; FW: 1.24.
P00: GPT (00000000, 00002000) 4 MB
P01: apnhlos (00002000, 000063C8) 12.47 MB
P02: mdm (000083C8, 00019C38) 51.53 MB
P03: sbl1 (00022000, 00000100) 128 KB
P04: sbl2 (00022100, 00000200) 256 KB
P05: sbl3 (00022300, 00000400) 512 KB
P06: aboot (00022700, 00001000) 2048 KB
P07: rpm (00023700, 00000400) 512 KB
P08: tz (00023B00, 00000400) 512 KB
P09: pad (00023F00, 00008400) 16.5 MB
P10: efs (0002C300, 00006D00) 13.62 MB
P11: modemst1 (00033000, 00001800) 3072 KB
P12: modemst2 (00034800, 00001800) 3072 KB
P13: m9kefs1 (00036000, 00000618) 780 KB
P14: m9kefs2 (00036618, 00000618) 780 KB
P15: m9kefs3 (00036C30, 00000618) 780 KB
P16: system (00037248, 00564000) 2760 MB
P17: persist (0059B248, 00004000) 8 MB
P18: cache (0059F248, 0040B000) 2070 MB
P19: param (009AA248, 00003000) 6 MB
P20: boot (009AD248, 00005000) 10 MB
P21: recovery (009B2248, 00005000) 10 MB
P22: fota (009B7248, 00005000) 10 MB
P23: backup (009BC248, 00003000) 6 MB
P24: fsg (009BF248, 00001800) 3072 KB
P25: ssd (009C0A48, 00000010) 8 KB
P26: persdata (009C0A58, 00004800) 9 MB
P27: hidden (009C5258, 000FA000) 500 MB
P28: carrier (00ABF258, 0000A000) 20 MB
P29: userdata (00AC9258, 0128E000) 9.277 GB
Save to D:/Medusa Dump file...
Reading partition system... Read error at 0x29089000...

ERROR[007]: Command fail.
At sector 1344584
JTAG device has been disconnected.
Disconnected.
  Reply With Quote
Old 10-25-2018, 12:41   #5 (permalink)
Product Supporter
 
Medusa Box's Avatar
 
Join Date: Mar 2011
Location: Octopus-team
Posts: 9,360
Member: 1538383
Status: Offline
Sonork: 100.1587278
Thanks Meter: 3,398
At first try use fully charged battery or/and stable external power supply for powering the device. Also try to connect the device with lower JTAG speed value. Then try to read out Full flash again.

If the Read operation was interrupted and device was disconnected, try to connect the device again, select "Custom" option, set start read address manually (set the same or higher address where the reading error has been occured) and try to read again. There is no option on how to bypass read error and continue the Read operation in the case when an error occures.
  Reply With Quote
The Following User Says Thank You to Medusa Box For This Useful Post:
Old 10-25-2018, 13:04   #6 (permalink)
Junior Member
 
Join Date: Sep 2018
Location: FRANCE
Posts: 11
Member: 2865074
Status: Offline
Thanks Meter: 0
thank you very much for your answer and your help. I will try what you told me.
  Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 



All times are GMT +1. The time now is 09:34.



Powered by Searchlight © 2024 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2024 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2023 -
Page generated in 0.17197 seconds with 8 queries

SEO by vBSEO