On Wed, 2009-12-02 at 13:47 -0800, Zach Welch wrote: > On Wed, 2009-12-02 at 15:42 +0100, Yegor Yefremov wrote: > > I found some short description about TFTP support in OpenOCD but it > > seems to be restricted to eCOS or ZY1000 debugger. > > > > Are there any plans to implement such a feature? The usage were for > > example following: I have my Linux development host where I compile > > the firmware and I also run an TFTP daemon there. My production host > > has an FTDI based board attached to it to flash the embedded device. > > So the only alternatives a have now are either to copy the image to > > this production host or to use CIFS to mount the related directory on > > the development host. I'd like to be able to fetch the file directly > > through OpenOCD commands with the syntax provided in the manual: > > > > flash write_image erase /tftp/ip/file.bin bin > > I think this would be better done as a general-purpose mechanism.... > Personally, I think a 'tftp fetch <var> <file>' command would be both > easy to implement and use. It would store the contents of the remote > file in the named variable. > > Then, you could pass that to write_image instead of a file name. This > then allows folks to write all sorts of mechanisms to produce images > that can be written... not just TFTP. > > The catch: it cannot require new library dependencies, and it must be > portable to all platforms supported by OpenOCD. However, I would push > for this to be included, if implemented in the manner I suggested.
One caveat to the catch: if you make these commands fully configurable through --enable-net-tftp (or something), then the library and portability requirements _might_ be relaxed. Nevertheless, a portable and dependency-free solution should be preferred whenever possible, and this seems eminently possible for this particular situation. --Z _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
