> Rather than changing this for current commands I might favor adding a > new command (or option, or subcommand) for flashing, which first sets > up PLLs where possible, then does the flash operating, and then does > a reset.
We can use "gdb-flash-write-start" hook to enable the PLL and up the speed, then in "gdb-flash-write-end" hook the chip can be reset or just some things disabled. It would be better to add a generic "flash-write-start/-end" hooks so that it could be done also for telnet commands, not just GDB. > Yes, it's important that when the target executes code it will see > documented reset state for the chip. Do you see a way for this > requirement to not conflict with the desire for OpenOCD to use as > high speed as possible for debug communication? Only adaptive clock (RCLK) comes in mind... You'd need a data breakpoint on clock control registers to know exactly when the clock changes /; Anyway - during "normal" debugging (a few variables, stepping, breakpoints) the frequency of JTAG clock doesn't make much difference (in my opinion)... 4\/3!! ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
