Hi Michael, it's great to see the first meaty questions on this new init structure. :-)
On Fri, Dec 31, 2010 at 12:49 PM, Michael Trensch <[email protected]> wrote: > Hiho, > > I was just trying to port the netX scripts to the new target script > structure with the "setup_target" proc. I remarked that the script > changes seem to be fitted to "real" embedded processors with all > peripherals on the die. But this chip does not own an internal flash > memory and the flash / ram configuration is board dependent. > > So what to do in this case? Is the number of parameters for the proc > "setup_target" set in stone, or am I free to adjust it? I presume you mean init_targets. init_targets takes no arguments. It is a procedure that sets up the configuration for the config script that is loaded. init_targets invokes a target/board/architecture specific procedure with fixed default arguments. The arguments to the procedure that init_targets calls have no defined structure. It is entirely up to the configuration script for the target/PCB family. If someone wants to set up a different pcb/target, they load the config file in question, then define a new init_targets proc specific to their PCB. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
