On Tue, Nov 10, 2009 at 7:27 AM, Freddie Chopin <freddie_cho...@op.pl> wrote: > David Brownell pisze: >> The stm32.cfg shouldn't specify a reset type at all, since >> the right configuration depends on what the *board* wires up. >> Send a patch in ... :) > > I think this policy should be changed... IMHO all /board and /target > should be merged and the problem would be gone. > > Another way is to use only the LAST command. When a target.cfg file > specifies some default reset, the board.cfg (which includes the > target.cfg) can override that and the problem is also gone.
You mean that "reset_config" should ignore any previous invocations of "reset_config", right? I have to agree with you on this one and I've posted to that effect in the past. I just feel that the idea that reset_config(as it is today) could somehow be used to let the target define half of the reset config and the board config to do the rest is more trouble than it's worth. Such communication could be handled in tcl + it could then handle more cases than the narrow reset_config case. Is this feature used *at all* today? It's such a marginal benefit(IMHO) and it precludes target files being useful standalone. I think *preventing* target config files from being used standalone is the wrong way to go. Sometimes all that is needed is a generic target config and it's not necessary to configure the specific flash or DRAM, etc. on the board. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
