From: Mike Frysinger <vapier@gentoo.org>
To: Howard Chu <hyc@symas.com>
Cc: mx <mxmxmx0429@qq.com>, gdb <gdb@sourceware.org>
Subject: Re: Is it possible to remote debug a multicore system of which each core has different instruction set arch?
Date: Sat, 20 Feb 2021 01:54:54 -0500 [thread overview]
Message-ID: <YDCyPqPQzs22XTxV@vapier> (raw)
In-Reply-To: <acbc7e0b-bef1-bfd7-9153-d9b9abdd345d@symas.com>
On 20 Feb 2021 02:46, Howard Chu wrote:
> mx via Gdb wrote:
> > Is it possible to remote debug a multicore system of which each core has different instruction set arch? For example if I have a two core chip, one core is cortex-m3, the other is riscv-i32. Or if I can debug multiple chip at the same time, each of which is different arch? I think this feature is important, since in the future there will be more debug situations like this.
>
> If such a heterogeneous hardware system exists, the different cores will necessarily be running different
> OS images. So treat it as debugging two physically separate machines, nothing different from today.
fwiw, this situation isn't theoretical. TI makes an ARM + C6X SoC
combo where both run Linux.
https://en.wikipedia.org/wiki/Texas_Instruments_DaVinci
-mike
prev parent reply other threads:[~2021-02-20 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 2:31 mx
2021-02-20 2:46 ` Howard Chu
2021-02-20 6:54 ` Mike Frysinger [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=YDCyPqPQzs22XTxV@vapier \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=hyc@symas.com \
--cc=mxmxmx0429@qq.com \
/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).