Hi Jonathan,
I have setup the lowRISC environment and went through some of debugging
tutorial.I used release version v0.3. Still I am running on bare metal mode
(only behavioral and RTL simulations) and hopefully I can start debugging
with FPGA once my nexys4 board is here. Now I am trying to get some
insight into lowRISC architecture. I went through release v0.4. I
appreciate any advice to proceed further. Thanks in advance.
regards,
Mahesh.
On Thu, Jun 29, 2017 at 12:28 PM, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk>
wrote:
Take a look at the comments here:
http://www.lowrisc.org/docs/minion-v0.4/environment/
and then, if you have further difficulty, write explicitly as to the error
message you get or give further detail.
Also have regard to the following:
https://www.xilinx.com/support/answers/54242.html
The difficulty is, commercial software takes a long time to write and
porting to a new machine requires resources. The chief
difficulty is that Vivado incorporates certain old copies of O/S libraries
for its own use. This breaks standard O/S utilities if they accidentally
make use of those old libraries. This is controlled by the LD_LIBRARY_PATH
environment variable. I recommend a wrapper script that sets the
environment, but Vivado initialization scripts set this variable in the top
level environment. Obviously his is a big problem when many incompatible
CAD vendors coexist on one machine.
Also, if you have an Intel Skylake processor, you could have problems with
microcode bugs (disable hyperthreading in this case).
On 29/06/17 06:46, Mahesh Dananjaya wrote:
Hi Jonathan,
What is the recommended operating system for the LowRISC? I have both
Ubuntu 14.04 and 16.04. I am currently using 16.04. Seems to be I have some
issues.Thank you.
regards,
Mahesh.
On Tue, Apr 25, 2017 at 2:39 PM, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk>
wrote:
> Dear Mahesh,
>
> The zed-board support was contributed by a third-party. I do not have one
> to try at the moment. My expectation is that the FPGA portion of the
> zed-board design is smaller, bearing in mind the ARM portion, so I do not
> know if the Minion core from our new release would fit in addition to the
> Rocket. The new release documentation including Minions is in review and
> due to be released real soon now. In any case the ARM SD-card is not
> accessible from the SD fabric so you need to provide a separate one.
> Probably these are the extra components you referred to.
> Jonathan
>
>
> On 04/25/2017 09:59 AM, Mahesh Dananjaya wrote:
>
> Hi Jonathan,
> Thank you. BTW, I have a one Zed board with me. so I am planning to
> continue with it, but it take some time to receive additional component.
> Hope Zed board will work fine. Will try another option later. I went
> through couple of your documentation and I forked the project. Hope to run
> some testing and debugging in next couple of days. Are there any other
> reading materials for minions? Cheers.
> regards,
> Mahesh.
>
> On Mon, Apr 17, 2017 at 2:02 PM, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk>
> wrote:
>
>> Dear Mahesh,
>>
>> This is the most economic board that we support or plan to support. When
>> you are more experienced you can attempt the advanced task of porting our
>> design or parts of it to a newer and potentially more economical board.
>> This has already been done for the Zedboard and our debug-v0.3 release. You
>> can read about it here:
>>
>>
https://github.com/furkanturan/lowrisc-zed
>>
>> Remember this is not an easy task. You need to consider the FPGA size
>> and manufacturer, the data sheets for the peripherals, clocking,
>> constraints, testing, simulation, synthesis, and software changes, as well
>> documenting what you have done and merging with other ports in a compatible
>> manner (not to mention discovering and correcting the information you are
>> given if necessary).
>>
>> Regards,
>>
>> Jonathan
>>
>> On 17/04/17 08:48, Mahesh Dananjaya wrote:
>>
>> Hi Jonathan,
>> Thank you very much. I am going through them. Is that the only board
>> currently support minions? I will let you know the progress. I have
>> discussed with Alex as well. Thank you.Cheers.
>> regards,
>>
>> On Thu, Apr 13, 2017 at 1:49 PM, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk>
>> wrote:
>>
>>> Dear Mahesh,
>>>
>>> The best way forward would depend on whether you can get access to a
>>> suitable FPGA board:
>>>
>>>
https://reference.digilentinc.com/reference/programmable-log
>>> ic/nexys-4-ddr/start
>>>
>>> through your school or by personal purchase. This would allow you to go
>>> through the install procedure
>>>
>>> and examples for our previous release
http://www.lowrisc.org/docs/de
>>> bug-v0.3/
>>>
>>> By the time you have exhausted this resource, the next release,
>>> including minion, will be ready.
>>>
>>> The overall repository structure and instructions will only change
>>> where necessary,
>>>
>>> and the above hardware platform will still be used.
>>>
>>> If you only have access to a Linux PC, you can still simulate the
>>> behaviour and learn according to the above instructions.
>>> Regards,
>>> Jonathan
>>>
>>>
>>> On 04/13/2017 09:03 AM, Mahesh Dananjaya wrote:
>>>
>>> Hi Jonathan,
>>> Thank you for your response. I am planning to contribute to the LowRISC
>>> project in long term. I am going through some of your resources like [1]
>>> and I would like to discuss and support the project. As Alex suggested,
>>> minion concept for high performance applications seems to be a good
>>> starting point, since it involve many things. I am working on some
>>> fundamentals in RISC-V and LowRISC. Can you please tell me, what are the
>>> relevant repos for me to be cloned to start this (I have seen lots of repos
>>> there including minions subsystem). I am going through the tutorials [2],
>>> but I think its good for me to learn them from the experts. Therefore, I am
>>> willing to have a meeting and discuss about the further work. Specially, I
>>> like the research kind of work. Thank you.
>>> regards,
>>> Mahesh.
>>>
>>> [1]
http://www.lowrisc.org/downloads/lowRISC-memo-2014-001.pdf
>>> [2]
http://www.lowrisc.org/docs/tagged-memory-v0.1/
>>>
>>> On Thu, Apr 13, 2017 at 12:21 PM, Dr Jonathan Kimmitt
<jrrk2(a)cam.ac.uk>
>>> wrote:
>>>
>>>> Hi Mahesh,
>>>> It's Jonathan Kimmitt here. I'm in charge of the minion
subsystem.
>>>> This is going to be part of our forthcoming release but the tutorial
isn't
>>>> ready yet. For test purposes it's possible to use the minion by
itself but
>>>> most users will expect to use it as part of a larger system where the
>>>> minion acts as an SD-card controller as well as other tasks. A unique
>>>> aspect of our work is that all our repositories are open source, whether
or
>>>> not they are ready for release.
>>>>
>>>> Regards,
>>>> Jonathan
>>>>
>>>> Sent from my iPhone
>>>>
>>>> > On 13 Apr 2017, at 07:17, Mahesh Dananjaya <
>>>> dananjayamahesh(a)gmail.com> wrote:
>>>> >
>>>> > Hi Alex,
>>>> > Any further information on this?. [1] Is this the relevant
>>>> repo?.Thankz.
>>>> > regards,
>>>> > [
1]https://github.com/lowRISC/minion_subsystem
>>>> >
>>>> > On Thu, Apr 6, 2017 at 6:01 PM, Mahesh Dananjaya <
>>>> dananjayamahesh(a)gmail.com>
>>>> > wrote:
>>>> >
>>>> >> Hi Alex,
>>>> >> Thank you very much for the information. I am planning to
contribute
>>>> >> LowRISC and RISC-V in long term, particularly for next few
years.
>>>> Yeah, I
>>>> >> have a good experience in SDN, but with a particular emphasis
on
>>>> hardware
>>>> >> architecture. But most of my research are focusing on
>>>> >> multi-core/multi-processor architecture and high performance
>>>> computing
>>>> >> areas. But I am not limited to these areas and willing to learn
new
>>>> areas.
>>>> >> Therefore lets meet and decide what is good for both lowRISC
and
>>>> myself.
>>>> >> BTW, I am reading some tutorials and try to get some ground
>>>> understanding.
>>>> >> I am very happy to contribute to the project. Lets hangout (or
>>>> skype). It
>>>> >> will be really helpful. Let me know any convenient time for you.
I
>>>> will be
>>>> >> free for couple of days (for 7 days) after 8th of this month.
>>>> Thankz.
>>>> >> Cheers!!
>>>> >> BR,
>>>> >> Mahesh.
>>>> >>
>>>> >>
>>>> >>> On Thu, Apr 6, 2017 at 1:44 PM, Alex Bradbury
<asb(a)asbradbury.org>
>>>> wrote:
>>>> >>>
>>>> >>> On 5 April 2017 at 08:45, Mahesh Dananjaya <
>>>> dananjayamahesh(a)gmail.com>
>>>> >>> wrote:
>>>> >>>> Hi,
>>>> >>>> I am happy to contribute to LowRISC if there is a
chance.
>>>> Currently I am
>>>> >>>> getting familiar with RISC-V. I have seen some projects
in your
>>>> GSOC
>>>> >>>> idealist. But i couldn't participate this time. And
also can
>>>> someone
>>>> >>> give a
>>>> >>>> idea of where to start?. I have seen lots of project in
your
>>>> github
>>>> >>> page. I
>>>> >>>> am very familiar with computer architecture and system
design. Any
>>>> >>>> information regarding this is highly appreciated. I am
looking
>>>> forward
>>>> >>> to
>>>> >>>> contribute to the lowRISC in long term. Thankz.
Cheers.!!
>>>> >>>> regards,
>>>> >>>
>>>> >>> Hi Mahesh, many many thanks for getting in touch and for
your
>>>> interest
>>>> >>> in contributing. The GSoC ideas list obviously gives a
sampling of
>>>> >>> possible projects, but lowRISC is a huge project so
there's no
>>>> >>> shortage of potential topics.
>>>> >>>
>>>> >>> Looking at our documentation
<
http://www.lowrisc.org/docs/> should
>>>> >>> give you a good idea of what we have now - we're very
close to
>>>> >>> releasing the 0.4 point release which will update that
>>>> documentation
>>>> >>> and add tag cache optimisations, a way of enforcing rules on
tags,
>>>> and
>>>> >>> an initial integration of minion cores.
>>>> >>>
>>>> >>> It partly depends what size project you're looking for.
We've
>>>> recently
>>>> >>> thought about experimenting with the minion concept for
higher
>>>> speed
>>>> >>> protocols (e.g. Ethernet), and there's obviously a huge
amount of
>>>> work
>>>> >>> there in terms of determining what custom accelerators or
>>>> instruction
>>>> >>> set extensions might be necessary to support that sort of
use case.
>>>> >>> Given your interest in software defined networking, perhaps
you
>>>> have
>>>> >>> ideas in this area? It all depends of course if you have
other
>>>> goals
>>>> >>> in contributing, e.g. some people are specifically looking
to
>>>> branch
>>>> >>> out into an area they're less familiar with.
>>>> >>>
>>>> >>> I'd be happy to set up a skype/hangout to discuss
potential ways of
>>>> >>> contributing further, if you think that would be helpful.
>>>> >>>
>>>> >>> Thanks again!
>>>> >>>
>>>> >>> Alex
>>>> >>>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >>
>>>> >>
>>>> >> *Mahesh Dananjaya*
>>>> >> Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo,
Sri
>>>> Lanka,
>>>> >> email | mahesh(a)paraqum.com
>>>> >> web |
www.paraqum.com
>>>> >> Tel | +94717586199
<
http://linkedin.com/in/dananjayamahesh>
>>>> >>
>>>> >> Department of Electronic and Telecommunication Engineering
>>>> >> University of Moratuwa
>>>> >> email | 110089(a)uom.lk
>>>> >> web |
www.ent.mrt.ac.lk
>>>> >>
>>>> >> skype | dananjaya.mahesh1 (Mahesh Dananjaya)
>>>> >>
>>>> >>
>>>> >> [image:
https://github.com/dananjayamahesh]
>>>> >> <
https://github.com/dananjayamahesh>
>>>> >> <
http://linkedin.com/in/dananjayamahesh>[image:
>>>> >>
https://twitter.com/DRAtapattu]
<
https://twitter.com/mahesh91uom
>>>> >[image:
>>>> >>
https://www.facebook.com/dulaj.atapattu]
>>>> >> <
https://www.facebook.com/dananjaya.mahesh.9>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> > *Mahesh Dananjaya*
>>>> > Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo, Sri
>>>> Lanka,
>>>> > email | mahesh(a)paraqum.com
>>>> > web |
www.paraqum.com
>>>> > Tel | +94717586199 <
http://linkedin.com/in/dananjayamahesh>
>>>> >
>>>> > Department of Electronic and Telecommunication Engineering
>>>> > University of Moratuwa
>>>> > email | 110089(a)uom.lk
>>>> > web |
www.ent.mrt.ac.lk
>>>> >
>>>> >
>>>> > [image:
https://github.com/dananjayamahesh]
>>>> > <
https://github.com/dananjayamahesh>
>>>> > <
http://linkedin.com/in/dananjayamahesh>[image:
>>>> >
https://twitter.com/DRAtapattu] <
https://twitter.com/mahesh91uom
>>>> >[image:
>>>> >
https://www.facebook.com/dulaj.atapattu]
>>>> > <
https://www.facebook.com/dananjaya.mahesh.9>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Mahesh Dananjaya *
>>> Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo, Sri
>>> Lanka,
>>> email | mahesh(a)paraqum.com
>>> web |
www.paraqum.com
>>> Tel | +94717586199 <
http://linkedin.com/in/dananjayamahesh>
>>>
>>> Department of Electronic and Telecommunication Engineering
>>> University of Moratuwa
>>> email | 110089(a)uom.lk
>>> web |
www.ent.mrt.ac.lk
>>>
>>>
>>> [image:
https://github.com/dananjayamahesh]
>>> <
https://github.com/dananjayamahesh>
>>> <
http://linkedin.com/in/dananjayamahesh>[image:
>>>
https://twitter.com/DRAtapattu]
<
https://twitter.com/mahesh91uom>[image:
>>>
https://www.facebook.com/dulaj.atapattu]
>>> <
https://www.facebook.com/dananjaya.mahesh.9>
>>>
>>>
>>>
>>
>>
>> --
>>
>>
>> *Mahesh Dananjaya *
>> Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo, Sri Lanka,
>> email | mahesh(a)paraqum.com
>> web |
www.paraqum.com
>> Tel | +94717586199 <
http://linkedin.com/in/dananjayamahesh>
>>
>> Department of Electronic and Telecommunication Engineering
>> University of Moratuwa
>> email | 110089(a)uom.lk
>> web |
www.ent.mrt.ac.lk
>>
>>
>> [image:
https://github.com/dananjayamahesh]
>> <
https://github.com/dananjayamahesh>
>> <
http://linkedin.com/in/dananjayamahesh>[image:
>>
https://twitter.com/DRAtapattu] <
https://twitter.com/mahesh91uom>[image:
>>
https://www.facebook.com/dulaj.atapattu]
>> <
https://www.facebook.com/dananjaya.mahesh.9>
>>
>>
>>
>
>
> --
>
>
> *Mahesh Dananjaya *
> Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo, Sri Lanka,
> email | mahesh(a)paraqum.com
> web |
www.paraqum.com
> Tel | +94717586199 <
http://linkedin.com/in/dananjayamahesh>
>
> Department of Electronic and Telecommunication Engineering
> University of Moratuwa
> email | 110089(a)uom.lk
> web |
www.ent.mrt.ac.lk
>
>
> [image:
https://github.com/dananjayamahesh]
> <
https://github.com/dananjayamahesh>
> <
http://linkedin.com/in/dananjayamahesh>[image:
>
https://twitter.com/DRAtapattu] <
https://twitter.com/mahesh91uom>[image:
>
https://www.facebook.com/dulaj.atapattu]
> <
https://www.facebook.com/dananjaya.mahesh.9>
>
>
>
--
*Mahesh Dananjaya *
Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo, Sri Lanka,
email | mahesh(a)paraqum.com
web |
www.paraqum.com
Tel | +94717586199 <
http://linkedin.com/in/dananjayamahesh>
Department of Electronic and Telecommunication Engineering
University of Moratuwa
email | 110089(a)uom.lk
web |
www.ent.mrt.ac.lk
[image:
https://github.com/dananjayamahesh]
<
https://github.com/dananjayamahesh>
<
http://linkedin.com/in/dananjayamahesh>[image:
https://twitter.com/DRAtapattu] <
https://twitter.com/mahesh91uom>[image:
https://www.facebook.com/dulaj.atapattu]
<
https://www.facebook.com/dananjaya.mahesh.9>
--
*Mahesh Dananjaya*
Electronic Engineer | Paraqum Technologies (pvt) ltd, Colombo, Sri Lanka,
email | mahesh(a)paraqum.com
web |
Department of Electronic and Telecommunication Engineering
University of Moratuwa
email | 110089(a)uom.lk
web |