On Mon, Jan 11, 2010 at 4:44 PM, David Brownell <[email protected]> wrote: > On Monday 11 January 2010, Edgar Grimberg wrote: >> index 9cddb50..75c8152 100644 >> --- a/src/flash/nor/str9x.c >> +++ b/src/flash/nor/str9x.c >> @@ -679,7 +679,7 @@ COMMAND_HANDLER(str9x_handle_flash_config_command) >> >> static const struct command_registration str9x_config_command_handlers[] = { >> { >> - .name = "disable_jtag", >> + .name = "flash_config", > > This bug was already fixed ...
Ah, great. The plan was to test on a release candidate and gather a bunch of problems. Of course, errors in the configuration scripts are show stoppers. I'll get the latest and give it another try. > >> .handler = &str9x_handle_flash_config_command, >> .mode = COMMAND_EXEC, >> .help = "configure str9x flash controller", > > ... though I'm not sure how many other commands accidentally got > renamed like that. Catching that particular goof was just a side > effect of auditing the usage messages, since that was so clearly > incorrect. I'm doing target tests according to a test plan. I want to test the basic functionality of OpenOCD: * Connectivity: telnet, GDB * Reset, using the provided configuration scripts, on targets with blank flash: reset init, reset halt * JTAG speed: MHz values and return clock * debugging: load into RAM, software breakpoint, single step in RAM, hardware breakpoint, single step in ROM * RAM access: writing simple patterns to RAM and reading back * FLASH: probe, fill, erase, program using GDB load The list is open and I welcome any additions.. Regards, Edgar -- Edgar Grimberg System Developer Zylin AS ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html Phone: (+47) 51 63 25 00 _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
