Hyper RAM Forum Discussions
There is an error in the DCARS footprint in the S70KS1282GABHB03 datasheet.
https://www.infineon.com/cms/en/search.html#!term=S70KS1282GABHB03&view=all
Section 12.2, Figure 37. The *DCARS*-capable part should have signals PSC and PSC# on pins B5 and C5, respectively. Those signals are not shown.
Can you please confirm that the footprint is wrong so that we can proceed forward with our board fabrication?
In the past we have used the 64Mbit DCARS-capable part which has the correct DCARS footprint pinout shown with the PSC/PSC# signals. We just want to make certain that the footprint is in error and that the PSC/PSC# pins are where we think they are.
Show LessWhy are there no HyperRAM parts with the DCARS feature in higher densities like 512Mbit?
The highest density hyperram with DCARS feature that I can find is 128Mbit.
The hyperram parts with the DCARS feature are a superior product in my opinion. Will higher density HyperRAMs w/ DCARS be released soon?
Show LessHello I'm looking for a verilog simulation model for the S70KL1281 (Hyper Ram).
Could you please point me the link to download it? (Prefer the model can be supported by xcelium and questasim)
** Note ** : I have been using the one provided in public (s27kl0642), but there is something more specific I would like to confirm with the exact variant in S70KL1281. Hope Infineon support team can help me with this.
Thanks a lot!
Regards,
SY
I am working on a HyperRAM controller in a MACHXO3 FPGA for this device.....
S27KS0642GABHI020
How is everyone handling the read cycle clock alignment? Variation over PVT is significant.
From the data sheet RWDS and DQout track each other tightly but they vary relative to the clock by a lot
1ns < tCKD < 5ns (clock to DQ valid)
0ns < tCKDI < 4.2ns (clock to DQ invalid)
My target clock is 125MHz (8ms)
At 125MHz the data valid window is....
3.0ns < tDV < 3.2ns
but the window center varies a LOT.
2.5ns < tCENTER < 6.6ns (delay from the clock edge)
For this to track over PVT is to use RWDS (edge aligned with the data) as the clock but RWDS is not free-running for a dynamic phase-lock.
A fixed delay from RWDS is possible but a known fixed clock period is required if guaranteed center alignment is desired.
What are your recommendations?
Show LessI was looking at the product page for the S80KS5122GABHA023. On the FAQ it states the following:
In Asynchronous SRAMs, the address pins (Ax) can be assigned in any bit order. For instance, pin A15 of CPU can be connected to A0 of SRAM, A10 of CPU to A1 of SRAM etc. Address assignment can be made as dictated by layout or other board-level constraints; there is no restriction from the internal SRAM-addressing standpoint, unless otherwise specified in the datasheet.
Likewise, data lines can be assigned in any order, within a specific byte. For instance, D0 of CPU can be connected to D4 of SRAM, D1 of CPU to D6 of SRAM etc. However, the data bit assignment should not cross byte boundaries if byte level accesses are made. For instance, a higher bit data of CPU connected to lower bit data line in SRAM could result in conflict when performing byte-specific (lower byte or higher byte) accesses. If such individual byte-level accesses are not made, routing can extend beyond byte boundaries also.
Does this actually apply to HyperRAM such as the S80KS5122, is the FAQ just some generic FAQ that gets placed on all the pages? Could anyone provide some info about how this could be implemented on the HyperRAM? Can I just connect any data line to any pin on the MCU? I'm still new to HyperRAM so I am confused about this.
Show LessHyper bus recognizes octal interfaces as standardized, is they compatible?
Can I put Hyper bus interface memory on an SoC that supports octal interfaces?
Show LessHi,
I have a TE0890 FPGA board (or S7 mini). There is Xilinx Spartan-7 and 64 Mbit HyperRAM. I want to use this HyperRAM so I need to HyperBus Controller IP but I cannot find it. Can anyone help me how can I find that IP?
Thanks,
Recep
When migrating from S27KS0641 to S27KS0642, in the attached PDF
On the 3rd page, it says "From a hardware point of view, no changes to the PCB are required."
S27KS0641 requires "differential clock", S27KS0642 "differential clock is optional", and "When CK# of S27KL0642 is not used,
Can be left floating. ”, there is a difference in the PIN specifications.
Therefore, the items to be confirmed are that the current board that uses the S27KS0641 is designed with a differential clock connected based on the ["HyperFlash™ and HyperRAM™ layout guide.pdf".] Is there any problem if I migrate (replace) to S27KS0642 without changing PCB?
Show LessHi,
I'm building various boards as a hobby. Recently I've built the board with Xilinx Artix-7 FPGA and two of HyperRAM ICs (here is what it looks like), and I wonder if it's possible for hobbyists like me to get access to your HyperBus Controller IP for FPGAs, and if so - what do I need to do to receive it. Thank you!
Show Less