Hi John,
There is a few parts to this:
The first thing is that the phy programming infrastructure is built into
the new tcpborphserver with the "?phyprog" katcp command. This version of
tcpborphserver is contained in the romfs image. This can be extracted by
mounting the romfs image as a loop dev
Folks
After reverse engineering the dram on ROACH2 here is what one should know.
1. The dram on roach2 is different from roach1.
On roach1, the user can read and write 144 size words to the dram with the
buss set not to 288 bits.
On roach2, the data buss is always 288 bits, regardless of th
Thanks, Robin! This should do it.
John
> Hi John,
>
> There is a few parts to this:
>
> The first thing is that the phy programming infrastructure is built into
> the new tcpborphserver with the "?phyprog" katcp command. This version of
> tcpborphserver is contained in the romfs image. This can
Hi Tim,
If you don't mind sharing your design, I'll put it up on the Casper wiki,
where i think it would be useful for others trying to use the dram.
Cheers,
Jack
On Thu, 16 Apr 2015 7:19 am Madden, Timothy J. wrote:
> Folks
>
> After reverse engineering the dram on ROACH2 here is what one sh
I will get on github soon. Argonne and Nist are sharing stuff already.
T
From: Jack Hickish [jackhick...@gmail.com]
Sent: Thursday, April 16, 2015 10:08 AM
To: Madden, Timothy J.; casper@lists.berkeley.edu
Subject: Re: [casper] Regarding dram: Moving from ROACH1 t
5 matches
Mail list logo
