Dobrica Pavlinušić's random unstructured stuff
HTC Dream G1 JTAG: Revision 9
openocdcompilationdpavlin@x200:/rest/cvs/openocd$ git remote -v origin git://openocd.git.sourceforge.net/gitroot/openocd/openocd (fetch) origin git://openocd.git.sourceforge.net/gitroot/openocd/openocd (push) dpavlin@x200:/rest/cvs/openocd$ ./configure --enable-verbose --enable-verbose-usb-io --enable-ft2232_libftdi dpavlin@x200:/rest/cvs/openocd$ make Debugginghttp://forum.xda-developers.com/showpost.php?p=6498820&postcount=621 That said before doing anything else take out your multi meter (and if you don't have one you are missing a tool for this type of work) and check the following: blue-light mode1) Put phone into blue light mode if serial is attached and power isn't: you will see bootmode 1 dpavlin@x200:/virtual/android$ ./neocon /dev/ttyUSB0 [Closed] [Open /dev/ttyUSB0] boot reason: PM_KPD_PWR_KEY_ON_RT_ST (PowerOn Status,Boot Reason)=(1,1) NAND_FLASH_READ_ID : SAMSUNG_256MB_FLASH_128MB_SDRAM ARM9_BOOT_MODE1 Invalid command : ? v-ref = 2.6v2) verify your v-ref is actually 2.6v (usually within 0.05v) when compared to the ground (any of the shielding) of the main board. You have one of the right points so there is an issue with the connection if its not. oprnocd, trst-n = 2.6vdpavlin@x200:/virtual/android/HTC-Dream-G1-JTAG$ sudo openocd Open On-Chip Debugger 0.4.0 (2010-02-23-17:04) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain dcc downloads are enabled fast memory access is enabled Info : clock speed 6000 kHz Info : JTAG tap: arm9.cpu tap/device found: 0xa01700e1 (mfg: 0x070, part: 0x0170, ver: 0xa) Info : Embedded ICE version 6 Info : arm9: hardware has 2 breakpoint/watchpoint units 3) now start open ocd: and check that trst-n is now also 2.6v when compared to ground. (if not your adapter is not working with the 2.6v.. very possible)
nTRST must be at high level (~2.6V) after openocd is launched.
Maybe you'll have to tweak the cfg file. There are several options for the behaviour of nTRST.
Maybe you'll have to tweak the cfg file. There are several options for the behaviour of nTRST. soldering4) with that done and you are still having problems as we said before check the soldering work.. Here there are two possibilities:
A) bridges - the wire is in contact with something in addition to the testpoint The tiniest bit of flux goes a long way here.. One quick thing you can test is that none of the 5 test points are connected to ground (disconnect rtck for now its one less variable) and that none are shorted to eachother. otherOther things to check:
softload radio ROMdpavlin@x200:~$ nc 127.0.0.1 4444 ��������Open On-Chip Debugger > halt halt cp15 read operation timed out cp15 read operation timed out cp15 read operation timed out cp15 read operation timed out cp15 read operation timed out cp15 read operation timed out cp15 write operation timed out target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x600000d3 pc: 0x00907aa0 MMU: disabled, D-Cache: enabled, I-Cache: enabled > > load_image /virtual/android/HTC-Dream-G1-JTAG/flash/radio-3.22.26.17_dream.img 0x103B5300 load_image /virtual/android/HTC-Dream-G1-JTAG/flash/radio-3.22.26.17_dream.img 0x103B5300 Target not halted no working area available, falling back to memory writes target not halted Command handler execution failed in procedure 'load_image' called at file "command.c", line 650 called at file "command.c", line 361 > |