From: Gopi Kumar Bulusu <gopi@sankhya.com>
To: Michael Eager <eager@eagercon.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] MicroBlaze: Update software breakpoint machine code as per MicroBlaze ISA
Date: Tue, 9 Sep 2025 17:53:26 +0530 [thread overview]
Message-ID: <CAL1P33ysVBSqE+pmL3UC-WtdCVzmTfRtLR5zzyR_k2De-Z2r-A@mail.gmail.com> (raw)
In-Reply-To: <430e84f1-b960-45e7-a617-8f88c083a800@eagercon.com>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
namaskaaram
On Tue, Sep 9, 2025 at 5:26 PM Michael Eager <eager@eagercon.com> wrote:
> On 9/9/25 12:16 AM, Gopi Kumar Bulusu wrote:
> > namaskaaram,
> > The macro MICROBLAZE_BREAKPOINT is set to an instruction opcode that
> > does not meet the criteria for software breakpoint instruction as set
> > forth in the AMD MicroBlaze ISA. This patch addresses the problem.
> >
> > This simple patch concludes a series of patches that add AMD MicroBlaze
> > gdbserver target support for GNU/Linux.
> >
> > Updated NEWS to include MicroBlaze gdbserver target.
> >
> > Build/Test - tested by building microblazeel-linux-gdb and verifying
> > that software breakpoint works
> > using gdbserver as target.
>
>
> Has this patch been tested with bare metal targets?
>
>
1. Yes, This patch has been part of the AMD/Xilinx git sources (Yocto
builds) for many many years. Breakpoints
work with bare metal (qemu). From what I understand - the bare-metal case
when using QEMU does not use a
software breakpoint.
2. No, I have not checked Baremetal - real target, but when using BDM/JTAG
this may not matter. However I don't see
currently JTAG supported from gdb for MicroBlaze (does it ?).
3. I also don't see any indication that gdb for MicroBlaze includes support
for a remote debug monitor for bare metal targets
that may use software breakpoint.
Approved ?
dhanyavaadaaha
gopi
> --
> Michael Eager
>
>
[-- Attachment #2: Type: text/html, Size: 2214 bytes --]
next prev parent reply other threads:[~2025-09-09 13:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 7:16 Gopi Kumar Bulusu
2025-09-09 11:56 ` Michael Eager
2025-09-09 12:23 ` Gopi Kumar Bulusu [this message]
2025-09-09 13:35 ` Michael Eager
2025-09-09 15:31 ` Simon Marchi
2025-09-09 15:34 ` Simon Marchi
2025-09-09 16:05 ` Gopi Kumar Bulusu
2025-09-09 16:22 ` Simon Marchi
2025-09-09 16:39 ` Gopi Kumar Bulusu
2025-09-09 16:29 ` Michael Eager
2025-09-09 16:41 ` Gopi Kumar Bulusu
2025-09-10 5:14 ` [pushed] " Gopi Kumar Bulusu
2025-09-10 13:27 ` Michael Eager
2025-09-10 15:09 ` Simon Marchi
2025-09-09 15:34 ` [PATCH] " Michael Eager
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=CAL1P33ysVBSqE+pmL3UC-WtdCVzmTfRtLR5zzyR_k2De-Z2r-A@mail.gmail.com \
--to=gopi@sankhya.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@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