On Mon, Jun 29, 2009 at 9:32 PM, David Brownell<davi...@pacbell.net> wrote: > On Monday 29 June 2009, Ųyvind Harboe wrote: >> Really what is required is a target .cfg file for *each* FPGA bit >> file, just like a .cfg file is required for each target. > > You mean, to handle cases like the config bitstream > linking in more TAPs to the one provided by the FPGA > vendor?
Even simpler than that: an FPGA could implement one or more CPUs. The only way to *know* what to write in a target configuration file is to embed some knowledge about the # of CPUs and how to set them up in the target configuration script. > should solve the technical problem. And it could be > made properly conditional, so that bitstream_file_1 > and bitstream_file_1 enable different TAPs, and are > chosen based on the task at hand. Note that a bitstream and the target configuration file will be unique to a single company or even developer, so I'm not a believer in a generic scheme to "discover" how to set up a target configuration script. Really each bitstream would be a different board+target configuration under the current OpenOCD thinking. -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
