Arria10 HPS Fpga to Sdram cannot be configured above 64 bits

do you use qsys to configure your HPS? you have to add a HPS component

in this component are parameter for ram width and ram protocol

as far as i know, hps ram can be up to 64 bit and you can add a fpga-to-hps-interface axi interface with up to 256 bit width

don't mix up ram data witdh and axi interface width

i use cyclone v fpga to hps interface with 150 MHz, Arria 10 should be more powerful

Lars_g,

Thanks for the reply. Actually I am working on Arria10. When I instantiate a HPS component in Qsys, it does not have any options related to the DDR protocol or the DDR memory width like it has in Arria 5 (under SDRAM tab. The only option it gives me is to enable a conduit to EMIF.

2. You are right. In arria 5 or cyclon 5, you can have a width of upto 256 bits for Fpga-2-HPS-Sdram port, but in Arria10 the maximum width available for selection is 64 bit AXI.

In Arria5 or Cyclon, you don't have to manually instantiate the DDR PHY, but what I am thinking is probably in Arria 10, I will have to manually instantiate the external memory PHY. Probably that's why, when I instantiate HPS, its parameter editor does not have any option related to DDR protocol or DDR memory width selection.

Now, my real problem is, if I have only 64 bit AXI interafce to the HPS(FPGA-2-HPS-SDRAM interface), I will have to clock it at 500 Mhz to match the bandwidth of my master port(coming from a third party IP 256bit @ 125 Mhz). I am very uncomfortable with such a high frequency(even though this path is really in a hard IP).

I don't understand why I cannot have a 256 bit port to HPS sdram interface like I can have in Arria 5. Why altera is limiting bandwidth on this fpga-2-sdram interface to the HPS!!!

Let me know what you think.

--- Quote Start ---

Lars_g,

Thanks for the reply. Actually I am working on Arria10. When I instantiate a HPS component in Qsys, it does not have any options related to the DDR protocol or the DDR memory width like it has in Arria 5 (under SDRAM tab. The only option it gives me is to enable a conduit to EMIF.

2. You are right. In arria 5 or cyclon 5, you can have a width of upto 256 bits for Fpga-2-HPS-Sdram port, but in Arria10 the maximum width available for selection is 64 bit AXI.

In Arria5 or Cyclon, you don't have to manually instantiate the DDR PHY, but what I am thinking is probably in Arria 10, I will have to manually instantiate the external memory PHY. Probably that's why, when I instantiate HPS, its parameter editor does not have any option related to DDR protocol or DDR memory width selection.

Now, my real problem is, if I have only 64 bit AXI interafce to the HPS(FPGA-2-HPS-SDRAM interface), I will have to clock it at 500 Mhz to match the bandwidth of my master port(coming from a third party IP 256bit @ 125 Mhz). I am very uncomfortable with such a high frequency(even though this path is really in a hard IP).

I don't understand why I cannot have a 256 bit port to HPS sdram interface like I can have in Arria 5. Why altera is limiting bandwidth on this fpga-2-sdram interface to the HPS!!!

Let me know what you think.

--- Quote End ---

I think this is more complicated-- just because the upstream bandwidth is a wider bridge does not mean that the SDRAM controller is running any quicker. I believe the way it worked in the Arria V or Cyclone V was by linking together multiple ports to get increased bandwidth. You could probably do the same here and drive multiple ports, but I haven't messed with it yet. Also, the HPS on the Arria 10 does have an EMIF connection, if you want to play around with that.

Thanks Derim for the reply.

You are right. The FPGA-to-HPS SDRAM interface supports six command ports each 64 bit, allowing up to six Avalon-MM interfaces or three AXI interfaces. Each command port can be used to implement either a read or write command port for AXI, or be used as part of an Avalon-MM interface. The AXI and Avalon-MM interfaces can be configured to support 32-, 64-, 128-, and 256-bit data. Since there are 4 data ports each 64bit. Look at the attached picture. What happens is, you cannot configure the FPGA2SDRAm port in HPS for a width above 64bit. This applies to following Arria10 device. 10as066n3f40I2sges. I am not sure if the tool will allow me to configure a higher data width if I use another FPGA. I am using the arria10 soc development kit and it has this device.

I checked with Altera and they said that this device has some problem(probably some ECO is done) and that why this width is limited to 64 bits only. but theoretically, it can go upto 256bit.

Now, 64 bit is ok, but I need a bandwidth of 32gbps on this port and to get that i will have to clock it at 500Mhz. That would be impossible for the logic which does conversion from 256bit@125Mhz to 64bit@500Mhz. Anyways, now Instead of using this port, I am using the FPGA2HPS port to access sdram through L3 interconnect. L3 interconnect works at half of cpu speed and has a 64bit interface to sdram scheduler in sdram l3 interconnect. The good thing is fpga-to-hps port can be configured as 128 bits. So my conversion logic needs to run only at 250 Mhz, which I think I will be able to manage.

Let me know what you think.

--- Quote Start ---

are you using ES1 chip?

--- Quote End ---

I am sorry,but how do you identify that?

ganeshmirajkar -

You're talking about the three FPGA to HPS SDRAM interfaces, correct? If you select Port Configuration 3 in the HPS parameter editor then the F2SDRAM 0 and F2SDRAM 2 interfaces are both 128 bits wide, and F2SDRAM 1 is disabled. If you select Port Configuration 4 then F2SDRAM 0 is 128 bits, F2SDRAM 1 is 32 bits, and F2SDRAM 2 is 64 bits. So you're correct that you can't get 256 wide on one port, but you can get 128 wide. And if using two ports will work for your application then you can get 256 wide by using F2SDRAM 0 and F2SDRAM 2 in Port Configuration 3.

By the way, the ES1 marking should be on the device package if you can see it.

Bob

--- Quote Start ---

ganeshmirajkar -

You're talking about the three FPGA to HPS SDRAM interfaces, correct? If you select Port Configuration 3 in the HPS parameter editor then the F2SDRAM 0 and F2SDRAM 2 interfaces are both 128 bits wide, and F2SDRAM 1 is disabled. If you select Port Configuration 4 then F2SDRAM 0 is 128 bits, F2SDRAM 1 is 32 bits, and F2SDRAM 2 is 64 bits. So you're correct that you can't get 256 wide on one port, but you can get 128 wide. And if using two ports will work for your application then you can get 256 wide by using F2SDRAM 0 and F2SDRAM 2 in Port Configuration 3.

By the way, the ES1 marking should be on the device package if you can see it.

Bob

--- Quote End ---

Yes. You are right, But the thing is I cannot select port3 or port1 configuration for this device. It is disabled. This is because there is some problem with that device and they have disabled all option which allow you to go above 64bit.

Hi All,

Thanks for the replies. I have come to a conclusion that the FPGA2SDRAM path cannot go above 64 bit for 10AS066N3F40I2sGes device that is there oon the Arria10 Soc development Kit. So as of now I will be using FPGA2HPS path. I think this will give me the same performance as a 128bit FPGA2SDRAM path. Later if atera comes up with another version of board which has a problem free device, I will update my design accordingly. I also checked the design that are available on Rocket boards and you will see that eve if they say that this design is for Arroa10 soc development board, they don't use the correct device number to make those designs. You can check this design for example http://rocketboards.org/foswiki/view/projects/arria10pcierootportwithmsi.

So the FPGA on this Arria10 SOC development board will never get programmed if you directly use the sd/card image that they provide.

ganeshmirajkar -

How did you get a dev kit with ES silicon (vs. ES2)? All of the A10 SoC dev kit designs on rocketboards.org target ES2 silicon as far as I can tell. I've been working with the GHRD project from rocketboards, which has the F2SDRAM interface in port configuration 3 with F2SDRAM 2 connected at 128 bits wide to a JTAG to Avalon master bridge.

We ordered an A10 SoC dev kit and have been waiting patiently to receive it. Ours will have ES2 silicon and I was not even aware that earlier kits with ES silicon had ever been released to the public.

Sounds like you were a very early adopter and are paying the inevitable price for that. Altera should definitely step up and get you a new kit with ES2 silicon as soon as they're available (in a few weeks so we've been promised).

Bob