Hi, Duane, thank you for your feedback, you raise very interesting points and I believe OpenOCD should really get rid of the hardcoded assumptions to attract those professionals who have less common ARM configurations to work on.
On Thu, May 01, 2014 at 12:21:46PM -0700, Duane Ellis wrote: > duane>> And associated configure commands at the generic target level to > configure this manually? > > Freddie> But if the distinction is related only to memory type (flash/RAM) > there is no need for a new commands - OpenOCD knows where the flash is… > > I don’t see where OpenOCD knows this. I guess what Freddie means is that when you work on a target with supported flash you already have "flash bank ..." commands in the target config which tell OpenOCD specifics about the said flash. So cortex_m code can use get_flash_bank_by_addr and if that succeeds, assume the region is flash, and if not, RAM. What do you think, do you see any downsides with this? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
