Temat: UrJTAG 0.10 #1502 vs tjtag 3.0.1 (EJTAG)
Przeprowadziłem testy odczytywania bootloadera CFE do pliku na urządzeniu vodafone HG553 za pomocą kabla unbuffered bezpośrednio do portu LPT (4 rezystory 100om). Procesor Broadcom BCM6358.
UrJTAG
=====
jtag> cable ea253 parallel 0x3bc
jtag> detectflash 0x1e000000
jtag> readmem 0x1e000000 0x00020000 cfe.binzgrał CFE do pliku w 4 min 30 sek
tjtag (EJTAG):
==========
tjtag3 -backup:custom /start:1e000000 /length:20000 /window:1e000000 /swap_endian /silent /noreset /nobreakzgrał w 1 min 36 sek
wbudowana opcja -backup:cfe zgrywa za dużo bo 256 bajtów dlatego lepiej używać start length window
swap_endian aby nie odwracał wartości HEX
silent aby pokazywał procent postępu w jednej linii
noreset, nobreak aby procesor się nie zatrzymał, bez tego właśnie się zatrzymuje gdzieś przy 80% odczytu i przez to pojawiają się błędy w pliku
Wychodzi na to iż tjtag 3.0.1 jest szybszy albo ja nie umiem używać UrJTAG
==============================================
EJTAG Debrick Utility v3.0.1 Tornado-MOD
==============================================
Probing bus ... Done
Instruction Length set to 5
CPU Chip ID: 00000110001101011000000101111111 (0635817F)
*** Found a Broadcom BCM6358 Rev 1 CPU chip ***
- EJTAG IMPCODE ....... : 00000000100000011000100100000100 (00818904)
- EJTAG Version ....... : 1 or 2.0
- EJTAG DMA Support ... : Yes
- EJTAG Implementation flags: R4k MIPS16 MIPS32
Issuing Processor / Peripheral Reset ... Skipped
Enabling Memory Writes ... Done
Halting Processor ... Skipped
Clearing Watchdog ... Done
Probing Flash at (Flash Window: 0x1e000000) ...
Done
Flash Vendor ID: 00000000000000000000000101111110 (0000017E)
Flash Device ID: 00000000000000000010000100000001 (00002101)
*** Found a Spansion S29GL128P U (16MB) Flash Chip ***
- Flash Chip Window Start .... : 1e000000
- Flash Chip Window Length ... : 01000000
- Selected Area Start ........ : 1e000000
- Selected Area Length ....... : 00020000
*** You Selected to Backup the CUSTOM.BIN ***
=========================
Backup Routine Started
=========================
Saving CUSTOM.BIN.SAVED_20160801_125704 to Disk...
Done (CUSTOM.BIN.SAVED_20160801_125704 saved to Disk OK)
bytes written: 131072
=========================
Backup Routine Complete
=========================
elapsed time: 96 seconds
*** REQUESTED OPERATION IS COMPLETE ***Jest nowsza wersja tjtag 3.0.2.1 i niby zgrywa ale pokazuje błędy DMA:
Clearing Watchdog ... Done
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Chip ID 8032
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Chip Rev 11
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Package Options 1
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Number of Cores 12
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Core Revision 15
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Core Type 8030
DMA Read Addr = 18000000 Data = (3C1B8032)ERROR ON READ
Core Vendor ID 3c1b0000
DMA Read Addr = 18000004 Data = (3C1B8032)ERROR ON READ
Flash Type 0
Flash Type = FLASH_NONE
DMA Read Addr = 18000128 Data = (3C1B8032)ERROR ON READ
DMA Read Addr = 18000004 Data = (3C1B8032)ERROR ON READ
Dest is bits 16
DMA Read Addr = 18000128 Data = (3C1B8032)ERROR ON READ
Flash is byteswapped 32
DMA Read Addr = 18000004 Data = (3C1B8032)ERROR ON READ
Endian Type is LE 0
DMA Read Addr = 18000004 Data = (3C1B8032)ERROR ON READ
PLL Type 00038000
Enter Flash Probei 1000 linii polecenia IDCODE for device:
Detected IR chain length = 5
Number of device(s) = 1000
IDCODE for device 1 is 0x0635817F
IDCODE for device 2 is 0x0635817F
IDCODE for device 3 is 0x0635817F
IDCODE for device 4 is 0x0635817F
IDCODE for device 5 is 0x0635817F...Opisujcie swoje doświadczenia z programami JTAG, może znacie inne, szybsze, lepsze?