Hi,
I tested H-JTAG using wiggler clone and Olimex LPC2106 board.
H-JTAG detected the chip ( ARM7TDMI-S TAP ID CODE 0x4F1F0F0F).
I am unable to debug using ARM STD debugger and keil debugger.
Regards,
Marcio
--- In lpc2000@lpc2..., "derbaier" <dershu@s...> wrote:
>
> --- In lpc2000@lpc2..., "tsvetanusunov" <tusunov@m...>
wrote:
> >
> > I found yesterday this web site: http://twentyone.blogchina.com/
> > this guy with nick twentyone works on this RDI support for Wiggler
> > since year 2004 (the first project was called X-JTAG) and his last
> > release is made very recently 20/12/2005.
> > I'm going to check if it works with our ARM-JTAG today, if it
works
> > this means our ARM-JTAG (Wiggler) finally will be supported by all
> > debuggers who have RDI1.51 support, there are instruction how to
> > config Keil, IAR, STD, ADS to work with his DLL.
> > The best of all is that the source is opened and can be downloaded
> > freely from this web so support for other hardware can be implemented
> > easily.
> >
> > Merry Christmas and Happy New Year to all LPC2000 members!
> >
> > Tsvetan
> > ---
> > PCB prototypes for $26 at http://run.to/pcb
> > (http://www.olimex.com/pcb)
> > PCB any volume assembly (http://www.olimex.com/pcb/protoa.html)
> > Development boards for ARM, AVR, PIC, MAXQ2000 and MSP430
> > (http://www.olimex.com/dev)
> >
>
> Tsvetan, were you able to get H-JTAG to work in your setup?
>
> I followed your link and picked up the software to try out with the
> Olimex Wiggler clone that I have. I tried it with two different LPC
> chips and just got it's "Unable to find target" error
message.
> Sometimes it was able to reset the target and sometimes it could not.
> It never was able to work with the ARM SDT2.51 debugger.
>
> -- Dave
>
Wiggler and Keil
Started by ●December 26, 2005
Reply by ●December 28, 20052005-12-28
Reply by ●December 28, 20052005-12-28
--- In lpc2000@lpc2..., "atmelbr" <atmelbr@y...> wrote:
>
> Hi,
> This is a message from twentyone from H-JTAG:
>
> H-jtag can set hardware breakpoint in flash area. However, the
> inferface of KEIL has some problem. So, I don't recommend you debug
> your target using keil and h-jtag. The developer from keil says that
> they will handle the problem at about march 2006.I will try to upgrade
> h-jtag to support keilafter the problem of keil has been fixed.
>
> Thank you.
> twentyone
>
So far, H-JTAG does not work with ARM SDT2.51 either, so it's problem
is not JUST with Keil. Using an Olimex LPC2148 board and an Olimex
Wiggler clone, the H-JTAG server reports "Unable to find target", so
in this case, it can not work with ANY debugger. Earlier in this
thread Tsvetan said "the H-JTAG as is will not work with our ARM-JTAG
as it doesn't handle the JTAG-ENABLE pin we have on our JTAG". If
that is the ONLY problem with H-JTAG it should be simple fix to get it
going with the Olimex hardware??
FWIW, the H-JTAG.sys driver that provides direct port access under
Windows seems to be working fine. It is a derivative of Dale Robert's
GiveIO.sys driver, so I tested it with Dale Robert's TestIO code, and
it played the test tune on the PC speaker correctly. -- Dave
>
> Hi,
> This is a message from twentyone from H-JTAG:
>
> H-jtag can set hardware breakpoint in flash area. However, the
> inferface of KEIL has some problem. So, I don't recommend you debug
> your target using keil and h-jtag. The developer from keil says that
> they will handle the problem at about march 2006.I will try to upgrade
> h-jtag to support keilafter the problem of keil has been fixed.
>
> Thank you.
> twentyone
>
So far, H-JTAG does not work with ARM SDT2.51 either, so it's problem
is not JUST with Keil. Using an Olimex LPC2148 board and an Olimex
Wiggler clone, the H-JTAG server reports "Unable to find target", so
in this case, it can not work with ANY debugger. Earlier in this
thread Tsvetan said "the H-JTAG as is will not work with our ARM-JTAG
as it doesn't handle the JTAG-ENABLE pin we have on our JTAG". If
that is the ONLY problem with H-JTAG it should be simple fix to get it
going with the Olimex hardware??
FWIW, the H-JTAG.sys driver that provides direct port access under
Windows seems to be working fine. It is a derivative of Dale Robert's
GiveIO.sys driver, so I tested it with Dale Robert's TestIO code, and
it played the test tune on the PC speaker correctly. -- Dave
Reply by ●December 28, 20052005-12-28
Hi Dave,
I think you need to configure SDT debugger to work with H-JTAG.
The image is loaded ok and after SDT sends an error message "Too many
breakpoints"
To avoid this error you need to disable the vector
catch and semihosting in debugger setting.
I dont know how this can be done.
Regards,
Marcio
> So far, H-JTAG does not work with ARM SDT2.51 either, so it's problem
> is not JUST with Keil. Using an Olimex LPC2148 board and an Olimex
> Wiggler clone, the H-JTAG server reports "Unable to find target", so
> in this case, it can not work with ANY debugger. Earlier in this
> thread Tsvetan said "the H-JTAG as is will not work with our ARM-JTAG
> as it doesn't handle the JTAG-ENABLE pin we have on our JTAG". If
> that is the ONLY problem with H-JTAG it should be simple fix to get it
> going with the Olimex hardware??
>
> FWIW, the H-JTAG.sys driver that provides direct port access under
> Windows seems to be working fine. It is a derivative of Dale Robert's
> GiveIO.sys driver, so I tested it with Dale Robert's TestIO code, and
> it played the test tune on the PC speaker correctly. > -- Dave
>
I think you need to configure SDT debugger to work with H-JTAG.
The image is loaded ok and after SDT sends an error message "Too many
breakpoints"
To avoid this error you need to disable the vector
catch and semihosting in debugger setting.
I dont know how this can be done.
Regards,
Marcio
> So far, H-JTAG does not work with ARM SDT2.51 either, so it's problem
> is not JUST with Keil. Using an Olimex LPC2148 board and an Olimex
> Wiggler clone, the H-JTAG server reports "Unable to find target", so
> in this case, it can not work with ANY debugger. Earlier in this
> thread Tsvetan said "the H-JTAG as is will not work with our ARM-JTAG
> as it doesn't handle the JTAG-ENABLE pin we have on our JTAG". If
> that is the ONLY problem with H-JTAG it should be simple fix to get it
> going with the Olimex hardware??
>
> FWIW, the H-JTAG.sys driver that provides direct port access under
> Windows seems to be working fine. It is a derivative of Dale Robert's
> GiveIO.sys driver, so I tested it with Dale Robert's TestIO code, and
> it played the test tune on the PC speaker correctly. > -- Dave
>
Reply by ●December 28, 20052005-12-28
--- In lpc2000@lpc2..., "atmelbr" <atmelbr@y...> wrote:
>
> Hi Dave,
> I think you need to configure SDT debugger to work with H-JTAG.
> The image is loaded ok and after SDT sends an error message "Too many
> breakpoints"
> To avoid this error you need to disable the vector
> catch and semihosting in debugger setting.
> I dont know how this can be done.
> Regards,
> Marcio
>
Thank you very much for the reply, Marcio!
Unfortunately, I am not getting far enough for that error. :-(
When I start the H-JTAG server it displays "UNKNOWN 0x00000000", and
then "Unable to find target" if I click the "Detect Target" menu item.
If I disconnect the Olimex Wiggler from the PC cable the H-JTAG server
displays "UNKNOWN 0xFFFFFFFF".
If I just go ahead and try to run ADW in the SDT tools it produces the
error message "H-JTAG server is not ready. Please make sure the
hardware is properly connected and powered up". However, I know the
hardware is OK because the Olimex Wiggler works OK with the IAR demo
toolset.
I recall that Tsvetan said in an earlier post that "the H-JTAG as is
will not work with our ARM-JTAG as it doesn't handle the JTAG-ENABLE
pin we have on our JTAG." He also said it should be easy to fix, so I
am hoping that H-JTAG will work with the Wiggler real soon now. :-)
FWIW, I have several other debug options. It is just that it would be
really nice to have a nice low cost RDI debug setup for SDT2.51. I
have used SDT for nearly 10 years now with Lauterbach hardware, and I
am kind of attached to it! :-) Since I retired, I no longer have
access to the expensive Lauterbach hardware. :-( -- Dave
>
> Hi Dave,
> I think you need to configure SDT debugger to work with H-JTAG.
> The image is loaded ok and after SDT sends an error message "Too many
> breakpoints"
> To avoid this error you need to disable the vector
> catch and semihosting in debugger setting.
> I dont know how this can be done.
> Regards,
> Marcio
>
Thank you very much for the reply, Marcio!
Unfortunately, I am not getting far enough for that error. :-(
When I start the H-JTAG server it displays "UNKNOWN 0x00000000", and
then "Unable to find target" if I click the "Detect Target" menu item.
If I disconnect the Olimex Wiggler from the PC cable the H-JTAG server
displays "UNKNOWN 0xFFFFFFFF".
If I just go ahead and try to run ADW in the SDT tools it produces the
error message "H-JTAG server is not ready. Please make sure the
hardware is properly connected and powered up". However, I know the
hardware is OK because the Olimex Wiggler works OK with the IAR demo
toolset.
I recall that Tsvetan said in an earlier post that "the H-JTAG as is
will not work with our ARM-JTAG as it doesn't handle the JTAG-ENABLE
pin we have on our JTAG." He also said it should be easy to fix, so I
am hoping that H-JTAG will work with the Wiggler real soon now. :-)
FWIW, I have several other debug options. It is just that it would be
really nice to have a nice low cost RDI debug setup for SDT2.51. I
have used SDT for nearly 10 years now with Lauterbach hardware, and I
am kind of attached to it! :-) Since I retired, I no longer have
access to the expensive Lauterbach hardware. :-( -- Dave
Reply by ●December 28, 20052005-12-28
Dave your observations seem to comfirm what Tsvetan
reported.
I expect that Olimex will soon release an updated
version of H-JTAG that will work fine with Wiggler
clones.
Regards,
Viron.
...
> Unfortunately, I am not getting far enough for that
> error. :-(
> When I start the H-JTAG server it displays "UNKNOWN
> 0x00000000", and
> then "Unable to find target" if I click the "Detect
> Target" menu item.
> If I disconnect the Olimex Wiggler from the PC cable
> the H-JTAG server
> displays "UNKNOWN 0xFFFFFFFF".
>
> If I just go ahead and try to run ADW in the SDT
> tools it produces the
> error message "H-JTAG server is not ready. Please
> make sure the
> hardware is properly connected and powered up".
> However, I know the
> hardware is OK because the Olimex Wiggler works OK
> with the IAR demo
> toolset.
>
> I recall that Tsvetan said in an earlier post that
> "the H-JTAG as is
> will not work with our ARM-JTAG as it doesn't handle
> the JTAG-ENABLE
> pin we have on our JTAG." He also said it should be
> easy to fix, so I
> am hoping that H-JTAG will work with the Wiggler
> real soon now. :-)
>
> FWIW, I have several other debug options. It is just
> that it would be
> really nice to have a nice low cost RDI debug setup
> for SDT2.51. I
> have used SDT for nearly 10 years now with
> Lauterbach hardware, and I
> am kind of attached to it! :-) Since I retired, I
> no longer have
> access to the expensive Lauterbach hardware. :-( > -- Dave
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
reported.
I expect that Olimex will soon release an updated
version of H-JTAG that will work fine with Wiggler
clones.
Regards,
Viron.
...
> Unfortunately, I am not getting far enough for that
> error. :-(
> When I start the H-JTAG server it displays "UNKNOWN
> 0x00000000", and
> then "Unable to find target" if I click the "Detect
> Target" menu item.
> If I disconnect the Olimex Wiggler from the PC cable
> the H-JTAG server
> displays "UNKNOWN 0xFFFFFFFF".
>
> If I just go ahead and try to run ADW in the SDT
> tools it produces the
> error message "H-JTAG server is not ready. Please
> make sure the
> hardware is properly connected and powered up".
> However, I know the
> hardware is OK because the Olimex Wiggler works OK
> with the IAR demo
> toolset.
>
> I recall that Tsvetan said in an earlier post that
> "the H-JTAG as is
> will not work with our ARM-JTAG as it doesn't handle
> the JTAG-ENABLE
> pin we have on our JTAG." He also said it should be
> easy to fix, so I
> am hoping that H-JTAG will work with the Wiggler
> real soon now. :-)
>
> FWIW, I have several other debug options. It is just
> that it would be
> really nice to have a nice low cost RDI debug setup
> for SDT2.51. I
> have used SDT for nearly 10 years now with
> Lauterbach hardware, and I
> am kind of attached to it! :-) Since I retired, I
> no longer have
> access to the expensive Lauterbach hardware. :-( > -- Dave
__________________________________
Yahoo! for Good - Make a difference this year.
http://brand.yahoo.com/cybergivingweek2005/
Reply by ●December 29, 20052005-12-29
Hi again Dave,
H-JTAG is now working with ARM SDT2.51 debugger!!
Congratulations for twentyone.
You need to disable semihosting and vector catching.
Click on View->Debugger internals
On semihosting enable put 0x00000000
On vector_catching change the string
%RUsPDAifE to %ruspdaife
I am using a very simple home made wiggler.
See schematic on files area.
http://groups.yahoo.com/group/lpc2000/files/JTAG/
1. Put a jumper from pin 8 to pin 15 of DB25 connector.
2. Use 74HC244 chip.
Good luck and happy new year.
> > So far, H-JTAG does not work with ARM SDT2.51 either, so it's problem
> > is not JUST with Keil. Using an Olimex LPC2148 board and an Olimex
> > Wiggler clone, the H-JTAG server reports "Unable to find target", so
> > in this case, it can not work with ANY debugger. Earlier in this
> > thread Tsvetan said "the H-JTAG as is will not work with our ARM-JTAG
> > as it doesn't handle the JTAG-ENABLE pin we have on our JTAG". If
> > that is the ONLY problem with H-JTAG it should be simple fix to get it
> > going with the Olimex hardware??
> >
> > FWIW, the H-JTAG.sys driver that provides direct port access under
> > Windows seems to be working fine. It is a derivative of Dale Robert's
> > GiveIO.sys driver, so I tested it with Dale Robert's TestIO code, and
> > it played the test tune on the PC speaker correctly.
> >
> >
> > -- Dave
> >
>
H-JTAG is now working with ARM SDT2.51 debugger!!
Congratulations for twentyone.
You need to disable semihosting and vector catching.
Click on View->Debugger internals
On semihosting enable put 0x00000000
On vector_catching change the string
%RUsPDAifE to %ruspdaife
I am using a very simple home made wiggler.
See schematic on files area.
http://groups.yahoo.com/group/lpc2000/files/JTAG/
1. Put a jumper from pin 8 to pin 15 of DB25 connector.
2. Use 74HC244 chip.
Good luck and happy new year.
> > So far, H-JTAG does not work with ARM SDT2.51 either, so it's problem
> > is not JUST with Keil. Using an Olimex LPC2148 board and an Olimex
> > Wiggler clone, the H-JTAG server reports "Unable to find target", so
> > in this case, it can not work with ANY debugger. Earlier in this
> > thread Tsvetan said "the H-JTAG as is will not work with our ARM-JTAG
> > as it doesn't handle the JTAG-ENABLE pin we have on our JTAG". If
> > that is the ONLY problem with H-JTAG it should be simple fix to get it
> > going with the Olimex hardware??
> >
> > FWIW, the H-JTAG.sys driver that provides direct port access under
> > Windows seems to be working fine. It is a derivative of Dale Robert's
> > GiveIO.sys driver, so I tested it with Dale Robert's TestIO code, and
> > it played the test tune on the PC speaker correctly.
> >
> >
> > -- Dave
> >
>
Reply by ●December 29, 20052005-12-29
--- In lpc2000@lpc2..., "atmelbr" <atmelbr@y...> wrote:
>
> Hi again Dave,
> H-JTAG is now working with ARM SDT2.51 debugger!!
> Congratulations for twentyone.
> You need to disable semihosting and vector catching.
> Click on View->Debugger internals
> On semihosting enable put 0x00000000
> On vector_catching change the string
> %RUsPDAifE to %ruspdaife
>
> I am using a very simple home made wiggler.
> See schematic on files area.
> http://groups.yahoo.com/group/lpc2000/files/JTAG/
>
> 1. Put a jumper from pin 8 to pin 15 of DB25 connector.
> 2. Use 74HC244 chip.
> Good luck and happy new year. Thank you very much for this further information! Unfortunately, it
is not possible to get to the View->Debugger Internals menu with
H-JTAG selected as the debug channel. ADW displays the message "H-JTAG
server is not ready", and will not continue with ADW startup until
H-JTAG is responding correctly. Since IAR also reports the exact same
error message when the H-JTAG RDI debug channel is selected, I assume
the error message is generated by H-JTAG itself. The H-JTAG server
itself also generates an error message on startup, so everything comes
back to H-JTAG and the Olimex Wiggler. Since your Wiggler does seem
to work OK with H-JTAG, there must be a difference in these Wiggler
implementations causing the problem. Since Tsvetan has already
indicated that he knows what the problem is I hope that he and
twentyone can get together on a solution? It would be a great addition
to our community if H-JTAG and the Olimex Wiggler can be made to work
smoothly together. It would also be really great if H-JTAG would also
work with the EasyICE JTAG pod, since it is almost, but not exactly,
the same as the Wiggler. I tried to set up an EasyICE using H-JTAG's
user defined configuration option, but the correct pin assignments are
not available in H-JTAG's user defined menu. HAPPY NEW YEAR!!!
-- Dave
>
> Hi again Dave,
> H-JTAG is now working with ARM SDT2.51 debugger!!
> Congratulations for twentyone.
> You need to disable semihosting and vector catching.
> Click on View->Debugger internals
> On semihosting enable put 0x00000000
> On vector_catching change the string
> %RUsPDAifE to %ruspdaife
>
> I am using a very simple home made wiggler.
> See schematic on files area.
> http://groups.yahoo.com/group/lpc2000/files/JTAG/
>
> 1. Put a jumper from pin 8 to pin 15 of DB25 connector.
> 2. Use 74HC244 chip.
> Good luck and happy new year. Thank you very much for this further information! Unfortunately, it
is not possible to get to the View->Debugger Internals menu with
H-JTAG selected as the debug channel. ADW displays the message "H-JTAG
server is not ready", and will not continue with ADW startup until
H-JTAG is responding correctly. Since IAR also reports the exact same
error message when the H-JTAG RDI debug channel is selected, I assume
the error message is generated by H-JTAG itself. The H-JTAG server
itself also generates an error message on startup, so everything comes
back to H-JTAG and the Olimex Wiggler. Since your Wiggler does seem
to work OK with H-JTAG, there must be a difference in these Wiggler
implementations causing the problem. Since Tsvetan has already
indicated that he knows what the problem is I hope that he and
twentyone can get together on a solution? It would be a great addition
to our community if H-JTAG and the Olimex Wiggler can be made to work
smoothly together. It would also be really great if H-JTAG would also
work with the EasyICE JTAG pod, since it is almost, but not exactly,
the same as the Wiggler. I tried to set up an EasyICE using H-JTAG's
user defined configuration option, but the correct pin assignments are
not available in H-JTAG's user defined menu. HAPPY NEW YEAR!!!
-- Dave
Reply by ●December 30, 20052005-12-30
