From: Sergey Belyashov via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] [gdb] Add Z80 CPU basic support
Date: Fri, 25 Sep 2020 15:40:37 +0300 [thread overview]
Message-ID: <CAOe0RDxcm+cooUW0TGP+SMMtRyNdOye-Rqtcxw3N+3AViD4Z=w@mail.gmail.com> (raw)
In-Reply-To: <5a120c4d-630a-08f5-fb81-d35237267adb@simark.ca>
> GCC is not required, it is possible to write a board file that specifies
> another compiler. It would be good to have a board file that allows a
> developer to test a change against Z80. A bit like
> testsuite/boards/simavr.exp for AVR.
There is no gdb-compatible simulator yet.
> So, do we need to mention eZ80 at all? Can't we just talk about Z80 and
> never talk about eZ80?
eZ80 in Z80 mode has additional instructions. Theoretically, GDB may
support eZ80 in ADL mode too, but I do not test it (I have no
simulator and device).
> Ok, it would be good to give an example of how to use it, otherwise it's
> pretty much dead code (like all other files in this directories are).
I will add a small instruction on how to embed it to the project to
the stub source.
> Most people won't actually have a device and setup to play with. Would
> it be possible to provide some explicit/clear steps for somebody to run
> and debug an hello world program using any simulator? Either using the
> stub you have provided, or I see there's a qemu Z80 port, does it work
> to debug against that?
There is a modified version required: https://github.com/b-s-a/qemu-z80
but it is based on a qemu snapshot from 2012 year and does not work for me.
Best regards,
Sergey Belyashov
prev parent reply other threads:[~2020-09-25 12:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 9:21 [PATCH] Add Zilog Z80 CPU (and derivatives) support Sergey Belyashov via Gdb-patches
2020-09-24 2:55 ` Simon Marchi
2020-09-24 2:57 ` Simon Marchi
2020-09-24 8:26 ` [PATCH] [gdb] Add Z80 CPU basic support sergey.belyashov--- via Gdb-patches
2020-09-24 14:08 ` Simon Marchi
2020-09-24 15:21 ` Sergey Belyashov via Gdb-patches
2020-09-24 15:42 ` Simon Marchi
2020-09-24 15:22 ` [PATCH v3] " Sergey Belyashov via Gdb-patches
2020-09-24 15:44 ` Simon Marchi
2020-09-25 11:40 ` [PATCH v4] [gdb] Add basic Z80 CPU support Sergey Belyashov via Gdb-patches
2020-10-06 10:17 ` Sergey Belyashov via Gdb-patches
2020-10-07 3:07 ` Simon Marchi
2021-05-24 19:13 ` Joel Brobecker
2021-07-12 21:37 ` Simon Marchi via Gdb-patches
2021-07-13 5:42 ` Sergey Belyashov via Gdb-patches
2021-07-13 13:01 ` Simon Marchi via Gdb-patches
2021-07-13 13:28 ` Sergey Belyashov via Gdb-patches
2021-07-15 2:23 ` Simon Marchi via Gdb-patches
2021-07-15 2:29 ` [PATCH v5] " Simon Marchi via Gdb-patches
2021-07-15 7:19 ` Sergey Belyashov via Gdb-patches
2020-09-25 12:40 ` Sergey Belyashov via Gdb-patches [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='CAOe0RDxcm+cooUW0TGP+SMMtRyNdOye-Rqtcxw3N+3AViD4Z=w@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=sergey.belyashov@gmail.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