On Monday 29 June 2009, Øyvind Harboe wrote:
> On Mon, Jun 29, 2009 at 7:21 PM, David Brownell<davi...@pacbell.net> wrote:
> > On Monday 29 June 2009, Ųyvind Harboe wrote:
> >> The point is that the target configuration script would define
> >> a tcl proc that would use e.g. play svf file.
> >
> > There's a missing hook too. No way for a non-target to
> > invoke "svf file.name" or "xsvf tap.name file.name" during
> > the reset process.
>
> With an FPGA there is a step which brings the CPU into existence.
>
> Resetting the CPU is much like resetting any normal CPU.
... that's *IF* one task of that FPGA is implementing a CPU.
(And if it's not one of the FPGAs with on-chip storage for
that particular config bitstream.)
> I'm not sure that configuring the FPGA(bringing the CPU into existence)
> should be done during the reset CPU tcl procedure....
If it's implementing a CPU, then one of the post-reset event
handlers should _be able_ to handle that. Whether that's the
best place for it is another issue.
I happen to think the problems here would become a lot more
clear if one just took CPUs ("debug targets", the stuff that
GDB understands) out of the picture entirely and just looked
at what's missing from the JTAG facilities.
- Dave
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
