Øyvind Harboe wrote: >> This is in contrast to Öyvinds preference that add_breakpoint should not >> touch the hardware. I would rather say that the meaning of add >> breakpoint is to touch the hardware as soon as possible. >> > > Let me refine that: any configuration that must happen in the target > configuration script must be possible with a powered down/disconnected > target. This is the crucial bit to me. > > Agreed !
I really don't want to split hairs but the crucial word here is "must". What must happen in a configuration script, is it necessary to add breakpoints in a configuration script ? Or is the right way to configure a startup script that should run when the target is actually powered up. There are several other target configurations that has been discussed, such as clock and mmu settings that can only be done on a live target. I think breakpoint configuration is an init script thing, not a config script thing. Default breakpoint type configuration on the other hand is more of a config option. Regards Magnus _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
