Thanks for pointing out the ethernet IP.
Currently, I need to boot linux on a RISC-V based system and found lowrisc
to be simple and easy to follow.
I can do without the ethernet IP for now, login through the UART interface
and work on building a open-emdedded layer for the filesystem.
I did look at the v0.2, untethered version also, the main point being easy
to port to the Virtex 2000T boards that I have here.
The end goal would be to integrate with REDEFINE, a massively parallel many
core architecture (this work was presented at the RISC V Workshop 2016. Video
@ 7:40 mins <https://www.youtube.com/watch?v=PCzAOYJa-xY
Thanks & Regards,
On Tue, Jan 23, 2018 at 2:16 PM, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk>
I don't know whether the Ethernet is the primary capability of interest.
If so, you
need to be aware that our circuit design was specifically targeted at the
of the Nexys4-DDR. If you have a different system such as MII, GMII, or
XGMII then this
block would need quite a bit of adaptation, but there are some adaptor IPs
in the Vivado
library which may be a good starting point. You can also consult Alex
which has a number of IPs for different variations of Ethernet.
On 23/01/18 08:40, Anup Kini wrote:
> Hi Alex,
> Thank you for getting back.
> I am sorry, it was my mistake. The vivado tool ran out of memory and
> I was able to build it successfully on a bigger server.
> I have started with the port to V2000T, looking through the scripts to
> figure out the block design and the additional clocks required.
> Thanks & Regards,
> Anup Kini.
> On Tue, Jan 23, 2018 at 2:03 PM, Alex Bradbury <asb(a)lowrisc.org> wrote:
> On 19 January 2018 at 10:27, Anup Kini <anupkini(a)gmail.com> wrote:
>>> Hi All,
>>> I am trying to build the lowrisc 0.5 release for a custom Virtex 7 2000T
>>> To begin with I tried to build the nexus 4 ddr design, but the
>>> implementation fails.
>>> Has anyone been successfull in pulling the latest 0.5 release from
>>> and building it.
>>> I have attached the vivado log in this mail.
>>> Looking forward for any help.
>> Hi Anup. Thanks for trying our latest release. The log doesn't seem to
>> have made it through with your message - could you perhaps try to
>> share it again?