Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] Understanding the LibreSOC core
From: Sanjay Menon @ 2020-06-08 18:03 UTC (permalink / raw)
  To: libre-riscv-dev

Hi,

Currently making a little progress on the nMigen tool.

Got to see some interesting things been discussed on the Alexa IOT pitch
for LibreSOC.

I have a few questions for you guys

1.Where do I start if I where to check into the LibreSoC source code?

2. Is this SoC in any way similar to the Xilinx ZYNQ architecture?.
Where the ARM embedded processor would be replaced by PowerPC and the
reconfigurable logic is converted to a GPU like entity, together forming a
heterogeneous SoC.

3. Do you plan to run the SoC on an FPGA for prototyping and testing
purposes?, or are you using some other methodologies?

Thanks and regards,
Sanjay
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Luke Kenneth Casson Leighton @ 2020-06-08 18:24 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAE_rhwaprF7wsHr8amwY3BZhVB=nj22xdRo0-D02MQFFsYYmmQ@mail.gmail.com>

On Mon, Jun 8, 2020 at 7:03 PM Sanjay Menon <sanjayamenon.mec@gmail.com> wrote:
>
> Hi,

hi! :)

> Currently making a little progress on the nMigen tool.

excellent. you understand gates (and verilog) already, so it should be
pretty straightforward.  Cesar i think got used to nmigen in around,
maybe 2 weeks?  it took me about that long.

> Got to see some interesting things been discussed on the Alexa IOT pitch
> for LibreSOC.
>
> I have a few questions for you guys
>
> 1.Where do I start if I were to check into the LibreSoC source code?

ha, ok, hum, bear in mind it's 75,000 lines, ok?  so i do recommend:
be patient, both with us and with yourself.  you've got nmigen already
(and yosys? and symbiyosys? - you only need symbiyosys and its
dependencies if running the formal proof tests)

have you followed the "quick peek at the code" on the frontpage?
https://libre-soc.org/ if so, you have the 3 key repositories, and you
could, for example, run the simple_core.py test that i posted about,
yesterday.  you *may* need to re-run pywriter.py though - see the
top-level Makefile

you can also just browse the source code directly online.  here's
core.py for example:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/simple/core.py;hb=HEAD

and its unit test:
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/simple/test/test_core.py;hb=HEAD

if you use vim, i recommend also "apt-get install exuberant-ctags",
then in each top-level directory where you work from, run "ctags -R".
you can then jump to any definition of any variable, class or
function, by putting the cursor on it and pressing "Ctrl-]"


> 2. Is this SoC in any way similar to the Xilinx ZYNQ architecture?.
> Where the ARM embedded processor would be replaced by PowerPC and the
> reconfigurable logic is converted to a GPU like entity, together forming a
> heterogeneous SoC.

ah no.  it *really is* an actual POWER9 core, where the plan is to
*extend* the POWER9 ISA (safely, and with careful mentoring from IBM
and the OpenPOWER Foundation), to add SimpleV vectorisation, YUV2RGB
instructions, Texture Interpolation instructions, and a shed-load
more.

those instructions *actually* run as *CPU* instructions, and we will
beef up the internal architecture to the point where it can cope with
the significant data and computational demands of executing GPU
workloads.  this is why we are going with a multi-issue OoO execution
engine, because it's the... "sane" way of dealing with the mixed
workloads of both sequential and parallel operations.

that is what being a "hybrid CPU-GPU-VPU" is all about.  it's very
much *not* about "farming off GPU workloads to elsewhere" - the
complete opposite is true.


> 3. Do you plan to run the SoC on an FPGA for prototyping and testing
> purposes?,

yes absolutely!  there is a EUR 10,000 budget allocated to this task:
https://bugs.libre-soc.org/show_bug.cgi?id=22

> or are you using some other methodologies?

i'd also like us to be able to use coriolis2 simulation.  this is
right at the gate level, about as close to the GDSII files as you can
get without actually paying for masks.

although it will be INSANELY slow, it will allow us to check that the
HDL has actually been properly translated into what we expect to be
executed.

l.

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 368] Need one example unit test of how to run some assembly code "qemu vs simulator" rather than "qemu vs hardware"
From: bugzilla-daemon @ 2020-06-08 18:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-368-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=368

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://docs.cocotb.org/en/latest/quickstart.html
should allow us to also include microwatt in the mix.
TODO later.  thank you michael for getting this started.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 370] New: need a way to co-simulate hardware, qemu, microwatt, simulator, side-by-side
From: bugzilla-daemon @ 2020-06-08 18:34 UTC (permalink / raw)
  To: libre-riscv-dev

https://bugs.libre-soc.org/show_bug.cgi?id=370

            Bug ID: 370
           Summary: need a way to co-simulate hardware, qemu, microwatt,
                    simulator, side-by-side
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Mac OS
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

see bug #368 - we need a way to run different POWER9 cycle-accurate execution 
environments side-by-side, in order to be able to compare them and see if they
produce the same results.  this would include native program execution on the
Raptor sponsored TALOS-II server, using gdb (native) rather than gdb (to
qemu-ppc)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 369] missing XER SO/OV/32 check in test_pipe_caller.py
From: bugzilla-daemon @ 2020-06-08 18:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-369-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=369

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
soc/simple/test/test_core.py now passes, with XER SO/OV/OV32 checking enabled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-06-08 18:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=305
Bug 305 depends on bug 369, which changed state.

Bug 369 Summary: missing XER SO/OV/32 check in test_pipe_caller.py
https://bugs.libre-soc.org/show_bug.cgi?id=369

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 339] create POWER9 ROTATE (SHIFTROT) pipeline
From: bugzilla-daemon @ 2020-06-08 18:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-339-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=339
Bug 339 depends on bug 369, which changed state.

Bug 369 Summary: missing XER SO/OV/32 check in test_pipe_caller.py
https://bugs.libre-soc.org/show_bug.cgi?id=369

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Yehowshua @ 2020-06-08 18:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDz5XeFCXTzhJ0j6WyWe=3FbZb2nb29QXr2yRvseJhZQZA@mail.gmail.com>



> On Jun 8, 2020, at 2:24 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> yes absolutely!  there is a EUR 10,000 budget allocated to this task:
> https://bugs.libre-soc.org/show_bug.cgi?id=22 <https://bugs.libre-soc.org/show_bug.cgi?id=22>
Hey Luke! I totally forgot about this.
I should have my thesis done by end of June - crossing fingers.

I would like to work on that - popping LibreSOC ontop of LiteX and stuffing it
in my VersaECP5 - hope it fits - I’m a LiteX veteran at this point.
This would be at the beginning of July.

Can we get a gate count for this: http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/007828.html

Here’s to hoping its below 400k - otherwise - yeah…

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 370] need a way to co-simulate hardware, qemu, microwatt, simulator, side-by-side
From: bugzilla-daemon @ 2020-06-08 18:52 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-370-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=370

Michael Nolan <mtnolan2640@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mtnolan2640@gmail.com

--- Comment #1 from Michael Nolan <mtnolan2640@gmail.com> ---
Cycle accurate - as in checking that the results are the same after every step?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Luke Kenneth Casson Leighton @ 2020-06-08 18:55 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A1761A3D-5C92-4A5C-88A7-D544068D8523@gatech.edu>

On Mon, Jun 8, 2020 at 7:46 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
>
>
> > On Jun 8, 2020, at 2:24 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> >
> > yes absolutely!  there is a EUR 10,000 budget allocated to this task:
> > https://bugs.libre-soc.org/show_bug.cgi?id=22 <https://bugs.libre-soc.org/show_bug.cgi?id=22>
> Hey Luke! I totally forgot about this.

:)

> I should have my thesis done by end of June - crossing fingers.
>
> I would like to work on that - popping LibreSOC ontop of LiteX

*great*.  by then that _should_ - as long as the wishbone interfaces
are up - be pretty straightforward to do.

> and stuffing it in my VersaECP5

oo i want one of those.

> - hope it fits - I’m a LiteX veteran at this point.

:)

> This would be at the beginning of July.
>
> Can we get a gate count for this: http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-June/007828.html
>
> Here’s to hoping its below 400k - otherwise - yeah…

ok so i ran the following yosys commands:

$ python soc/simple/core.py
$ yosys
read_ilang non_production_core.py
proc
opt
flatten
synth

and it produced this:

=== top ===

   Number of wires:              40844
   Number of wire bits:          93864
   Number of public wires:        5816
   Number of public wire bits:   58836
   Number of memories:               0
   Number of memory bits:            0
   Number of processes:              0
   Number of cells:              42932
     $_ANDNOT_                   11780
     $_AND_                        399
     $_DFF_P_                     3542
     $_MUX_                      11446
     $_NAND_                      3272
     $_NOR_                        567
     $_NOT_                       2751
     $_ORNOT_                      419
     $_OR_                        8622
     $_XNOR_                        35
     $_XOR_                         99


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

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Yehowshua @ 2020-06-08 18:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzO-kQpz=gDHSFJpqy-gcnfikiVKymgAZ=QnoL5rguc3Q@mail.gmail.com>

Those look like reasonable numbers.

I think it should fit. At minimum, I can get it running
inside the LiteX Verilator environment.

Yehowshua

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Sanjay Menon @ 2020-06-08 19:01 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <878934CF-C5C0-40DA-8299-140ADD4EAA79@gatech.edu>

Thanks for replying Luke.Would be looking into some of the things you
mentioned.

Yehowshua, if it does not fit you could try Partial dynamic reconfiguration
:)

Regards,
Sanjay

On Tue, 9 Jun 2020, 00:28 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.
>
> Yehowshua
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Luke Kenneth Casson Leighton @ 2020-06-08 19:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A1761A3D-5C92-4A5C-88A7-D544068D8523@gatech.edu>

https://www.mouser.co.uk/ProductDetail/Lattice/LFE5UM-45F-VERSA-EVN?qs=J7VcZjJ3Z9cK61xZC6pcWg%3D%3D

is that the one?  LFE5UM-45F_VERSA-EVN?  it makes sense for me to get
one as well.

l.

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Yehowshua @ 2020-06-08 19:05 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyTLTB=mVU4FUYzBQ_o8P2e+J5uMG8iWMFRvxwoM_WaGA@mail.gmail.com>


> 
> is that the one?  LFE5UM-45F_VERSA-EVN?  it makes sense for me to get
> one as well.

Yes - do hurry as there are only six left.
A fantastic alternative is the ulx3s.
The ulx3s uses SDR however, which LiTeX supports just fine.
The lead times of the ulx3s is two to three months however.
https://www.crowdsupply.com/radiona/ulx3s

> 
> l.
Yehowshua

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Yehowshua @ 2020-06-08 19:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAE_rhwbBd5Y9=TgbpWNsu+S5Yxm4VeVvrdHCNKNcE3gk4B3Dmg@mail.gmail.com>

> 
> Yehowshua, if it does not fit you could try Partial dynamic reconfiguration

That is an interesting suggestion. Unfortunately, I’m pretty 
sure NextPnr does not support this at the moment.

https://github.com/YosysHQ/nextpnr

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Yehowshua @ 2020-06-08 19:14 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <878934CF-C5C0-40DA-8299-140ADD4EAA79@gatech.edu>



> 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.

Two ways to approach this:
1. I can strip the LiteX BIOS down to bare essentials for initializing DDR3 on the Versa, and the build that.
Once built, I can comb through the assembled binary looking for any instructions we don’t 
currently support.
2. We can use SDR on the ulx3s which requires no CPU intervention.

Yehowshua


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

^ permalink raw reply

* [libre-riscv-dev] daily kan-ban update 08jun2020
From: Luke Kenneth Casson Leighton @ 2020-06-08 20:08 UTC (permalink / raw)
  To: Libre-RISCV General Development

yesterday:

* worked with Cole on TRAP
* fixed the Condition Register MFCR bug
* started on XER testing
* reviewed the IoT pitch

today:

* dealt with yet another massive headache.
* fixed XER SO/OV/OV32 handling (simulator and test_core)

going to take it easy for the rest of the day, return to LDST CompUnit
testing tomorrow.

l.

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Michael Nolan @ 2020-06-08 20:11 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDzO-kQpz=gDHSFJpqy-gcnfikiVKymgAZ=QnoL5rguc3Q@mail.gmail.com>

On 6/8/20 2:55 PM, Luke Kenneth Casson Leighton wrote:
>
> ok so i ran the following yosys commands:
>
> $ python soc/simple/core.py
> $ yosys
> read_ilang non_production_core.py
> proc
> opt
> flatten
> synth
>
> and it produced this:
>
> === top ===
>
>     Number of wires:              40844
>     Number of wire bits:          93864
>     Number of public wires:        5816
>     Number of public wire bits:   58836
>     Number of memories:               0
>     Number of memory bits:            0
>     Number of processes:              0
>     Number of cells:              42932
>       $_ANDNOT_                   11780
>       $_AND_                        399
>       $_DFF_P_                     3542
>       $_MUX_                      11446
>       $_NAND_                      3272
>       $_NOR_                        567
>       $_NOT_                       2751
>       $_ORNOT_                      419
>       $_OR_                        8622
>       $_XNOR_                        35
>       $_XOR_                         99

It should fit. Running synth_ecp5 instead of the generic asic synth 
above gives me this:

3.52. Printing statistics.

=== top ===

    Number of wires:              24216
    Number of wire bits:          72752
    Number of public wires:       24216
    Number of public wire bits:   72752
    Number of memories:               0
    Number of memory bits:            0
    Number of processes:              0
    Number of cells:              22710
      CCU2C                          72
      L6MUX21                      1203
      LUT4                        14962
      PFUMX                        3454
      TRELLIS_FF                   3019

--Michael


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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Yehowshua @ 2020-06-08 20:12 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <24d818ee-0882-e21f-4d8b-e33c85ee338c@gmail.com>



> On Jun 8, 2020, at 4:11 PM, Michael Nolan <mtnolan2640@gmail.com> wrote:
> 
> LUT4                        14962

Yeah easily - we have an 85k LUT budget.
Awesome!

Yehowshua

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Luke Kenneth Casson Leighton @ 2020-06-08 20:31 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <F24179DB-0461-4863-BCCA-2D4CC61FB1BB@gatech.edu>

On Mon, Jun 8, 2020 at 9:12 PM Yehowshua <yimmanuel3@gatech.edu> wrote:

> > On Jun 8, 2020, at 4:11 PM, Michael Nolan <mtnolan2640@gmail.com> wrote:
> >
> > LUT4                        14962

is that a lot?  i have no idea of "scale" if you know what i mean.
someone compiled microwatt for spartan-7 and got 11k LUTs
https://hackaday.com/2019/08/23/joining-the-risc-v-ranks-ibms-power-isa-to-become-free/

> Yeah easily - we have an 85k LUT budget.

the VersaECP5 from mouser is sadly only 45k LUTs, it does however have
the advantage of actually being available immediately.

> Awesome!

:)

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Luke Kenneth Casson Leighton @ 2020-06-08 20:38 UTC (permalink / raw)
  To: Libre-RISCV General Development
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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Luke Kenneth Casson Leighton @ 2020-06-08 20:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzwpCAndDnTtgWCex-f7kRWJDquQN=kixjmawwVHxtFBQ@mail.gmail.com>

https://github.com/enjoy-digital/litex/issues/245

okaaay, interesting.  later comments on that also explain some of the
commits i saw (changing xics)  overall it looks really exciting, and,
again, that they're trail-blazing for us.

l.

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

^ permalink raw reply

* [libre-riscv-dev] [Bug 325] create POWER9 TRAP pipeline
From: bugzilla-daemon @ 2020-06-08 21:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-325-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=325

--- Comment #88 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #86)
> hi michael, apologies i couldn't help it, i did some of the TODO
> comments on trap main_stage:
> 
> -        # TODO: MSR (into srr1)
> +        # take a copy of the current MSR in SRR1
> +        comb += msr_copy(srr1_o.data, msr_i) # old MSR
> +        comb += srr1_o.ok.eq(1)
>  
> also i wandered through the 3.0B PDF and found the section that
> covers "Program Interrupts" - Book III 7.5.9
> 
> i therefore added these defines:
> 
> PI_TRAP = (63 - 46)    # 1 if exception is "trap" type
> 
> and changed the setting of the relevant SRR1 bit to use that definition:
> 
>                     self.trap(0x700, cia_i)
>                     comb += srr1_o.data[PI_TRAP].eq(1)
> 
> now we have words instead of numbers when it comes to reading through the
> code.  we can see, in two lines of code:
> 
> 1. "it's a trap" (self.trap - duh). 
> 2. execution continues at address 0x700
> 3. the trap handler (in software) can read SRR1 and know exactly what to do

(In reply to Luke Kenneth Casson Leighton from comment #87)
> (In reply to Luke Kenneth Casson Leighton from comment #86)
> > hi michael,
> 
> cole!  gaah :)   names... massive headache (again) at the moment.

Hehe no problem :) I took a look at this yesterday evening, and I was going to
ask you for help because I was stuck, so, so much the better!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 08jun2020
From: Cole Poirier @ 2020-06-08 21:17 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDyeAQzR=R3EkAKHnKmHwQmHOmZCokyFN=WxKxCr2tFvRQ@mail.gmail.com>

On Jun 8 2020, at 1:08 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> yesterday:
> 
> * worked with Cole on TRAP
> * fixed the Condition Register MFCR bug
> * started on XER testing
> * reviewed the IoT pitch

Thank you so much for this Luke, the discussion you had on-list with our
less frequently commenting members (because they have full time jobs),
who are incredibly technically capable was phenomenally helpful.
 
> today:
> 
> * dealt with yet another massive headache.
> * fixed XER SO/OV/OV32 handling (simulator and test_core)
> 
> going to take it easy for the rest of the day, return to LDST CompUnit
> testing tomorrow.
> 
> l.

I'm very sorry to hear you're suffering from massive headaches, several
of my family members suffer from migraines, I know it's very unpleasant.

Today I think I need to focus exclusively on the pitch because the
deadline is so close and there is currently so much missing info.

I'm planning on taking the discussion on list, and the comments on the
pitch on the wiki and coming up with a new pitch specific to these
discussions. 

I'm going to spend the next two hours trying to take all of the
technical aspects of the pitch and put them into a coherent form with my
understanding of the technical aspects. Then I'll send this to the list
so that you and others can reply and correct inline.

I'll try to put just a few very specific questions (such as the
advantages/high level summary of Simple-V) for you and other technical
project members to answer. I would try answer this myself given your
present state, but unfortunately I don't think I can understand and
explain something like Simple-V on my own in a day.

Can I ask you to see if you're able to answer some of these questions
today, if your illness permits? I hate to ask you while you're sick, but
I think the pitch will really suffer without your technical input...


Thank you,

Cole

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

^ permalink raw reply

* Re: [libre-riscv-dev] Understanding the LibreSOC core
From: Michael Nolan @ 2020-06-08 21:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDzwpCAndDnTtgWCex-f7kRWJDquQN=kixjmawwVHxtFBQ@mail.gmail.com>

On 6/8/20 4:38 PM, Luke Kenneth Casson Leighton wrote:
> 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.
>
We were going to need to do something like this anyway though, the 
actual SOC will need some low level boot code in rom right? For initial 
testing the 45f has 216kiB of bram, which is plenty for running test 
code and whatnot (granted, we will need some of that ram for other 
purposes).

--Michael


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

^ permalink raw reply

page:   latest

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