On Saturday 24 October 2009, Timo Boettcher wrote: > openocd -f openocd/openocd.cfg -f openocd/olimex-arm-usb-ocd.cfg -f > openocd/openocd-sam7s256.cfg -c "mt_flash_bin glow_flash.bin" > I get: > > ===== begin openocd output ===== > Warn : use 'sam7se256.cpu' as target identifier, not '0' > Unknown command: mww 0xfffffd44 0x00008000 > ====== end openocd output ====== > > What am I missing there?
An "init" command before running your script. (Plus I'll guess your flash config is where that "0" needs to become "sam7se256.cpu"...) See the User's Guide ... the first thing in the chapter on "Daemon Configuration" covers the "configuration stage". You use the "init" to force exit from that stage into the state where commands like "mww" are available. Come to think of it, the doc doesn't cover two points: (a) some name for the stage after the configuration stage! (b) commands like "mww" will not be available until entry to that unnamed stage. Your programming script would be a good example to clarify those... - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
