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] Understanding the LibreSOC core
Date: Mon, 8 Jun 2020 21:38:10 +0100
Message-ID: <CAPweEDzwpCAndDnTtgWCex-f7kRWJDquQN=kixjmawwVHxtFBQ@mail.gmail.com> (raw)
In-Reply-To: <9D061BD0-3FD9-4A05-A070-745C82482CAF@gatech.edu>

On Mon, Jun 8, 2020 at 8:14 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
>
> > On Jun 8, 2020, at 2:58 PM, Yehowshua <yimmanuel3@gatech.edu> wrote:
> >
> > Those look like reasonable numbers.
> >
> > I think it should fit. At minimum, I can get it running
> > inside the LiteX Verilator environment.
> >
>
> Also do keep in mind that LiteX **requires the CPU to
> initialize the DDR3 present on the Versa.

microwatt i believe did something like that (recently).

> Two ways to approach this:
> 1. I can strip the LiteX BIOS down to bare essentials for initializing DDR3 on the Versa, and then build that.

there's a BIOS??  oink :)

if there's a BIOS, it means that at least some instructions can be
loaded (into something - probably an on-board SRAM) and executed, and
that at least means we can test _something_ before getting to that
stage.

(meaning: the instructions to initialise DDR3 have to execute _from_
somewhere, they can't be executed from thin air)

btw we were planning to put in a "Board Support Package" NLNet Grant Request.

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: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 18:03 Sanjay Menon
2020-06-08 18:24 ` Luke Kenneth Casson Leighton
2020-06-08 18:46   ` Yehowshua
2020-06-08 18:55     ` Luke Kenneth Casson Leighton
2020-06-08 18:58       ` Yehowshua
2020-06-08 19:01         ` Sanjay Menon
2020-06-08 19:09           ` Yehowshua
2020-06-08 19:14         ` Yehowshua
2020-06-08 20:38           ` Luke Kenneth Casson Leighton [this message]
2020-06-08 20:46             ` Luke Kenneth Casson Leighton
2020-06-08 21:19             ` Michael Nolan
2020-06-08 22:17               ` Luke Kenneth Casson Leighton
2020-06-08 22:18                 ` Luke Kenneth Casson Leighton
2020-06-08 20:11       ` Michael Nolan
2020-06-08 20:12         ` Yehowshua
2020-06-08 20:31           ` Luke Kenneth Casson Leighton
2020-06-08 19:02     ` Luke Kenneth Casson Leighton
2020-06-08 19:05       ` Yehowshua

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='CAPweEDzwpCAndDnTtgWCex-f7kRWJDquQN=kixjmawwVHxtFBQ@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