Friday, August 19, 2005

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.