Honored Contributor
Honored Contributor--- quote start ---
we completely support so-dimm's, but do not at all support i2c -- our sdram controller only does static so-dimm configurations (set up in the wizard, pre-quartus compile). this should be reasonably well described in the sopcbuilder sdr-sdram documentation.[/b]
--- quote end ---
yes, it was quite obvious in the documentation. i was just wondering if you guys were thinking of adding such a feature.
<!--quotebegin-kerri@Jul 14 2004, 11:56 AM i'm guessing that the user wants to have their system dynamically self-configure sdram at power-up, via i2c, to be able to talk to whatever (potentially new) so-dimm it happens to find. i believe that (aside from the fact that the controller can't do it) putting in a different so-dimm might change the address space requirements of the system, which the cpu and other system components can't deal with anyway. since a rebuild would be required to change memory size/capacity anyway, you can reconfig your controller to match the new so-dimm at the same time. --- Quote End --- The user just wants a lot of RAM. We could design around some SDRAM chips, but then we're at the mercy of some company keeping those chips in production. An SO-DIMM would be easier to deal with over the long haul, plus they're easier to route. Static worst-case timings are acceptable, as long as I can determine what such timings should be. Or I'll just spec some timings and see how well it does. I'm running PC133 memory at PC66 speeds anyway, so it should be a bit more lenient. As for memory size detection, I figured we'd just set up SOPC builder for the maximum and then detect how much is really there (if any) at boot time. Will this approach fail?
