On Fri, Jul 25, 2008 at 2:51 AM, Dominic Rath <[EMAIL PROTECTED]> wrote:

> On Thursday 24 July 2008 21:37:41 Brian Hutchinson wrote:
> > Hi,
> >
> > Could someone point me in the right direction so I don't go in the weeds
> > too far?
> >
> > I know this is mostly for ARM but I would really like to take a interface
> > line the Amontec JAGKey Tiny and make an adaptor to match the pinouts of
> an
> > AMD Elan SC520 (Soekris net4526 board to be more specific).
> >
> > I'd like to know how to take the BSDL file I have for the SC520 and what
> > all I would need to do to get a JTAG interface working with it and what I
> > would need to do in order to use OpenOCD tools with it.
>
> Boundary scan does not offer any debugging features. It gives you control
> over
> the external pins of the device.


I've used commercial debuggers that use the 4 JTAG signals in order to
establish a debugging session and I know the ARM guys have gdbserver going
so I know it is possible ... I just don't know how to go about learning it.

That is why I'm posting ... so you guys can "show me the way".

Right now I would be just happy being able to flash the Soekris board I'm
using as I would like to port a different bios to it but I would like to
learn how to get gdb to work over the jtag link in the future.



>
> > I would also like to use GDB in order to debug the target so would
> looking
> > at the ARM GDB Server be a start to figure out how to port such a thing
> to
> > the SC520?
>
> Debugging requires support from dedicated on-chip debug circuitry.
> Apparently
> the Elan SC520 has something they call "AMDebug", which probably does what
> you want, but I'm not sure if the necessary information is publicly
> available.


AMDebug is a propritery AMD thing that I'm not interested in.

>
>
> > I've always been a user of commercial JTAG products and now want to learn
> > how this all really works so I can tinker with boards at home on a low
> cost
> > basis.
> >
> > Thank you!
> >
> > Brian
>
> Best regards,
>
> Dominic
> _______________________________________________
> Openocd-development mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/openocd-development
>
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to