public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Vrany <jan@vrany.io>
To: "Schneider, Maximilian" <Maximilian.Schneider@Honeywell.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: openocd+gdb combo
Date: Fri, 25 Feb 2022 23:24:25 +0000	[thread overview]
Message-ID: <94769b26f03223bf419d31bc9f9218971d5874ca.camel@vrany.io> (raw)
In-Reply-To: <16d3c834b8c2567162e6326bf7bc6a4aa908d8e1.camel@vrany.io>

On Wed, 2022-02-23 at 21:16 +0000, Jan Vrany via Gdb wrote:
> On Wed, 2022-02-23 at 16:11 +0000, Schneider, Maximilian via Gdb wrote:
> > Hello,
> >
> > I have written a relatively complex but very useful external loader+gdb python script for a piece of memory connected to one of the many chips we use.
> > I can now use openocd to connect and subsequently gdb with the aforementioned loader and script to read/write/erase !
> >
> > However It is still a pain to have to start an openocd session before being able to launch the gdb command.
> >
> > Is there a known way to package openocd and gdb together so that I can get convenient calling conventions like bellow?
> > ./read_the_thing > memory_dump.bin
> >
> > How would you recommend creating portable installations of gdb so that they can be shipped quickly to the unfortunate windows users?
> > I can imagine writing an extra tool that manages the sequencing of openocd+gdb but I would need executables I can run without installation to make it palatable for my colleagues.
> >
> I was facing similar problem a year ago. Took me a bit to figure
> out how to make a .zip you can download, unpack wherever you want 
> and use, including working python.
>
> If you think it would help, I can try to extract the build script 
> from my CI and share some time later this or next week.

You may find the script here: https://github.com/janvrany/binutils-gdb-devscripts

HTH, Jan


>
> Jan
>
> > Best Regards,
> > Maximilian Schneider
>
>



      reply	other threads:[~2022-02-25 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 16:11 Schneider, Maximilian
2022-02-23 21:16 ` Jan Vrany
2022-02-25 23:24   ` Jan Vrany [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=94769b26f03223bf419d31bc9f9218971d5874ca.camel@vrany.io \
    --to=jan@vrany.io \
    --cc=Maximilian.Schneider@Honeywell.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).