freddie_chopin wrote: > > 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.
I agree, anything new must not be restricted to only one interface. Adding generic flash hooks should not be very difficult in itself, and the existing gdb hooks could call into them. In several cases OpenOCD is only used for flashing, which should not require GDB for good performance, rather the opposite: if possible to reduce the number of components involved then all the better. Leaving the debug speed discussion aside. I agree the clock is not as important for debug. //Peter ------------------------------------------------------------------------------ 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
