From: "Marko Mlinar" <Marko.Mlinar@campus.fri.uni-lj.si>
To: <gdb@sources.redhat.com>
Cc: <cores@opencores.org>
Subject: gdb port to or1k
Date: Thu, 26 Apr 2001 11:17:00 -0000 [thread overview]
Message-ID: <00a501c0ce7d$1fa4c5e0$bb4902c1@Javor> (raw)
Hi!
I am Marko Mlinar, member of OpenCores group.
OpenCores is very serious open HW developement group,
which is growing rapidly. More info can be obtained
at www.opencores.org
or1k is 32bit extendable processor architecture, and has many
new features, including better (more general) HW (conditional)
breapoints, watchpoints, catchpoint and pretty general HW trace.
or1k is published under GNU LGPL public license.
Detailed architecture description is available on opencores CVS.
GCC, BFD, disasembler and some other tools has already been ported.
We plan to port gdb to our processor OpenRisc 1000 architecture.
Our first plan is to prepare remote debugger using JTAG via parallel
port. First question - does anybody know if /dev/lp0 or such are
compatibile across platforms (including IOCTL function read_status
0x060b, I think).
or1k TAP (Test Access Port) document is still in preparation, but is
fully compatible with JTAG.
This project will probably extend to Linux native debugger and
also or1k gdb target port(?). We also have simulator, but it is
currently not compatible with gdb.
I am new to gdb community, so I would appreciate any kind of help,
especially coders ;)
We will try to follow your guidelines and to make this cooperation
fruitful for both communities.
Best regards,
Marko
next reply other threads:[~2001-04-26 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 11:17 Marko Mlinar [this message]
2001-04-26 15:04 ` J.T. Conklin
2001-04-27 0:04 ` Marko Mlinar
2001-04-27 12:56 ` Andrew Cagney
2001-04-27 23:07 ` Marko Mlinar
2001-04-30 9:45 ` Andrew Cagney
2001-04-30 10:44 ` J.T. Conklin
2001-04-30 10:13 ` J.T. Conklin
2001-04-30 10:49 ` Damjan Lampret
2001-04-30 18:07 ` Andrew Cagney
2001-04-30 22:15 ` Marko Mlinar
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='00a501c0ce7d$1fa4c5e0$bb4902c1@Javor' \
--to=marko.mlinar@campus.fri.uni-lj.si \
--cc=cores@opencores.org \
--cc=gdb@sources.redhat.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