Wednesday, May 17, 2006
Thursday, March 09, 2006
H-JTAG Introduction
H-JTAG is a free jtag debug agent for arm mcu. From the view of function, H-JTAG is similar to multi-ice. H-JTAG supports SDT2.51, ADS1.2, RealView and IAR. With the help of H-JTAG, you can debug arm7/arm9 through wiggler or sdt-jtag.
1. Support RDI 1.5.0 and 1.5.1;
2. Support both ARM7 and ARM9;
3. Support both thumb and arm instructions;
4. Support both little-endian and big-endian;
5. Support semihosting;
6. Support wiggler, sdt-jtag and user defined interface;
7. Support WINDOWS 9.X/NT/2000/XP;
Download
Tuesday, August 23, 2005
H-JTAG Discussion Board
Twentyone
Friday, August 19, 2005
H-JTAG History
2006-10-16:
Released new version H-JTAG V0.4.0 (Build 20061015)
1.Improve the support to ARM9E-S and ARM9EJ-S.
2.Add TAP configuration to support complex TAP/JTAG
3.Add the support for initialization script, which can be used for auto initialization
4.Add the programming of NOR flash and AT91SAM. But only a few chips are supported currently. I will upgrade H-Flasher to support more NOR flash chip step by step. The programming of AT91SAM chips may have some problem. I am looking for some boards for testing. I will correct the problem asap.
5. To debug STR912X, please refer to this TAP configuration: config
2006-07-09:
Released new version H-JTAG V0.3.1 (Build 20060629)
1. Add auto flash download for LPC2000 on-chip flash. When auto-download is enabled, h-jtag server will call h-flasher to download program into on-chip flash automatically. This makes the debug in flash much more convenient.
2006-06-15:
Released new version H-JTAG V0.3.0 (Build 20060615)
1. In H-Flasher, added the calculation of checksum for the programming of LPC2000. For the programming of LPC2000, the content of 0x14 will be revised automatically to make the checksum of the vector table equal to zero.
2006-06-13:
Released new version H-JTAG v0.3.0 (Build 20060613)
1. Improve the processing of reset. The detection problem in v0.3.0 build 20060610 is fixed. Sorry for the inconvenience casued.
2006-06-10:
Released new version H-JTAG v0.3.0 (Build 20060610)
1. H-Flasher is inroduced. H-Flasher now supports the programming of LPC2000. I will upgrade H-Flasher to support the programming of external NOR flash step by step. Here, I would like to thank ZLGMCU for their support.
2. Please uninstall old version before install this new one.
3. For users of olimex wiggler, please configure JTAG according this picture;
4. Instructions for programming LPC2000:
A. Open H-JTAG and H-Flasher
B. In H-Flasher, select target flash in step 1;
C. Go to step 4;
D. Program/Erase ...
2006-04-02:
Released new version H-JTAG v0.2.1 Beta (Build 20060402)
1. Improved the management of breakpoints (Thank Christophe);
2. Enhanced the support for SWI SEMIHOSTING (Thank bluesky);
3. Improved the support for the debug of exception (Thank ZKR);
4. The flash programmer is still under development, because I am busy with something else recently. Sorry!
H-JTAG Q&A
Q: How to configure debugger (ADS/SDT/REALVIEW) ?
A: ADS/AXD -> options -> configure target -> add -> choose h-jtag.dll in the h-jtag installation directory. -> click OK
SDT/ADW -> options -> configuration debugger -> target-> add -> choose h-jtag.dll in the h-jtag installation directory -> click OK
RealView -> File -> Connection -> connect to target -> Right click on ARM -> Add/Remove/Edit Devices -> Add DLL -> Choose H-JTAG.DLL in the h-jtag installation directory -> Select H-JTAG.DLL and then click Configure
Q. How to configure KEIL?
A. KEIL->PROJECT->OPTIONS FOR TARGET->DEBUG->USE RDI Interface Driver->SETTING->BROWSER->Choose H-JTAG.DLL loacted in the installation folder.
Q. Unable to load h-jtag driver.
A. It means that the driver for h-jtag hasn't been installed properly. Please reinsrall h-jtag with the administrator's right.
Q. Too many breakpoints.
A. Normally, this is caused by vector catch/semihosting. Enable vector catch/semihosting will consume the breakpoint resource. If all the breakpoint resources are occupied, this message may be displayed. Please note that all the breakpoints set for vector catch and semihosting are unvisible to users. These breakpoints can't be removed by "delete all breakpoint" command. To remove this message, please disable the vector catch and semihosting in your debugger setting.
Q. The statement into which was stepped is singular (i.e. it has no exit).
A. This is caused by unvisible breakpoint set for vector catch/semihosting. To remove this message, please disable vector catch in your debugger setting.
Q. Execution stopped, because of an unknown breakpoint (this indicates an internal error).
A. This is caused by unvisible breakpoint set for vector catch/semihosting. To remove this message, please disable vector catch in your debugger setting.
Q. The processor is reset.
A. To remove this message, please disable vector catch in your debugger setting.
Q. Unrecognized swi.
A. To remove this message, please disable semihosting in your debugger setting.