Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 15jun2020
Date: Mon, 15 Jun 2020 20:58:53 +0100
Message-ID: <CAPweEDx1hevEgNrMvEdORv3cLmFyBqgrA4eAK5Z4Vuo0f=SqcA@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDy+jJ6ifvjMSOrn51v-Bs6qdXa6ZELT_r8TDRH7qx8uyQ@mail.gmail.com>

On Mon, Jun 15, 2020 at 4:11 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> * look at why the 2nd LD/ST instruction remains "busy" in test_core.py
> where in the test_ldst_compunit.py it is fine

found it quickly.  turns out that you must not link signals together
*after* you create a nmigen Simulator instance.  the nmigen
Simulator(m) instance must be the last thing done.

now the LD/ST unit tests also work in test_core.py as well.  this is a
significant step because with LD/ST, branch, and add (etc.) all
confirmed working, simple loops can be created once we have
instruction read/feed in place.

> * if that's found quickly, continue investigating the next step which
> is to first add in an instruction "reader" (I-Cache path) and second
> to point the PC at it and actually get instructions from an actual
> I-Cache / SRAM.

this is now the next high priority task: getting an SRAM that's on the
other side of a wishbone bus operational (and properly unit tested)
then dropping it into place on the L0CacheBuffer.

on a separate path an instruction queue can also be added... however
agaaain, that needs to be reading from a Memory, preferably via a
wishbone interface.

what i might do for now is just drop in a small SRAM just to get
something working.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 15:11 Luke Kenneth Casson Leighton
2020-06-15 19:58 ` Luke Kenneth Casson Leighton [this message]
2020-06-15 20:03   ` Yehowshua
2020-06-15 21:12     ` Cole Poirier
2020-06-15 21:21       ` Luke Kenneth Casson Leighton
2020-06-15 21:20     ` Luke Kenneth Casson Leighton
2020-06-16  3:08 ` Jacob Lifshay
2020-06-16 10:52   ` Luke Kenneth Casson Leighton

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='CAPweEDx1hevEgNrMvEdORv3cLmFyBqgrA4eAK5Z4Vuo0f=SqcA@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git