Re: Remote Flashing w/ Window Client & OpenOCD

linnix wrote:
Yes, I didn't bother to post the .h, just add the .mode member to it.

I tried contacting you through the form at http://linnix.com/ocd/ but maybe
that didn't work. Could you please make sure that the complete source code
used to create the binary you're distributing is available, including the
COPYING file?

My remote client (on Window) first upload data into target sram, then
issue a command to flash it. Problem with existing code is that the
file must be on the server first.

[snip]
Telnet interface is not as easy as GDB. Packet size and format are
easier to control in GDB, where Telnet can be anything. My Window
client already have GDB and I hate to add another protocol to it.

[snip]
No, the remote client dumps into the target memory directly.

Ah, I never thought of such a scenario. I suppose you're using the GDB
protocol's M or X packet to write target memory, and all you now want to do
is trigger a copy from memory to flash.

The "clean" approach would be the use of the new vFlash command (I mixed
that up with the "$f,..." you wrote about), but when using a "real" GDB
client that would also require the use of an XML description file that
tells the GDB when to use memory access (M, X) and when to use flash access
(vFlash).

A simpler alternative that's still usefull for other uses would be a "flash
copy <bank> <source-address> <destination-address>" command, if you're
interested in getting these changes upstream. If what you want is a private
fork that's only meant to work with your own Windows client then you can of
course use whatever is easiest for you to implement.

Regards,

Dominic
.

Relevant Pages

  • Re: Remote Flashing w/ Window Client & OpenOCD
    ... Telnet interface is not as easy as GDB. ... the remote client dumps into the target memory directly. ... is trigger a copy from memory to flash. ... a write command as well as a erase command. ...
    (comp.arch.embedded)
  • Re: rpc.lockd(8) seg faults on 5.2-RELEASE
    ... But it seldomly crashes with segfault, ... The server hosts home directories for about 400k users. ... this is probably because the client ... I'm not really proficient with gdb, so if more is needed let me ...
    (freebsd-current)
  • Re: Remote Flashing w/ Window Client & OpenOCD
    ... My remote client first upload data into target sram, ... Telnet interface is not as easy as GDB. ... the remote client dumps into the target memory directly. ...
    (comp.arch.embedded)
  • Re: SIGSEGV informations
    ... The idea would be to get a core dumped on your client. ... fetch it back to your developpment platform and analyse it with gdb as ...
    (comp.os.linux.misc)
  • Re: SIGSEGV informations
    ... The idea would be to get a core dumped on your client. ... fetch it back to your developpment platform and analyse it with gdb as ...
    (comp.os.linux.questions)