FWIW: The 0x10 indication of "appFull" in this context means that the underlying memory controller in not ready to accept any commands. This is typically observed in the interval after bitstream load and reset. but before the MIG has initialized and trained. -Shep
On Tue, Apr 3, 2012 at 11:10 AM, Albert Kwon <[email protected]> wrote: > Hi Jim, > > So to initialize the DRAM controller in the DramServer, do I have to > use the swctl? > Right now, I am calling dram.start() in the c++ code where dram is the > 12th worker, but when I read dramStatus, I still read 16 (i.e. 10000, and > initComplete.read was 0). > > Thanks, > Albert > > > > On 04/03/2012 11:01 AM, James Kulp wrote: > > Hi Albert, > > Some "workers" in the bitstream are not considered "application workers", > and thus are not accessible through the C++ API (a.k.a. Application Control > API, or ACI). They should be somehow. Other workers in this category are > the "DP" workers (the DMA streaming engines), the "SMA" workers > (stream-to-message adapters), and the ICAP worker. These "infrastructure" > workers are presently only really accessible via swctl. Allowing the ACI > to access these workers is of course a good idea. They are in fact > accessed (started, and configured) "under the covers", otherwise nothing > would work, but there is no C++ API for this yet. > > Jim > > > > > > > > > On 4/3/12 10:03 AM, Albert Kwon wrote: > > What is the equivalent of this when I'm using the c++ code (a code like > testRpl)? Do I have to use swctl? > > Thanks, > Albert > > > On 04/03/2012 07:11 AM, Shepard Siegel wrote: > > See lines 133-135 > https://github.com/ShepardSiegel/ocpi/blob/master/bsv/wrk/DramServer_v6.bsv > > The only bit that matters is bit 0. > The rest are for debug and may or may not be present based upon > hasDebugLogic > > Be sure to wait a second or two after the > reset->unreset->initialize->start sequence before looking, as read-capture > training takes a while and we have not yet made that long wait built into > initialize (as it should be). > > Look at testSeq9* if you are unsure of the sequence, e.g. > https://github.com/ShepardSiegel/ocpi/blob/master/bin/testSeq9b2 > > Please let me know if that was your issue. > > -Shep > > > > On Tue, Apr 3, 2012 at 1:05 AM, Albert Kwon <[email protected]>wrote: > >> Hi Shep, >> >> I have a quick question about dramStatus variable in >> DramServer_v6.bsv: is initComplete.read supposed to be 1 when DRAM is ready? >> When I get the value for dramStatus, it is always 16, which seems like >> it means appFull = 1, and everything else is 0. >> If so, how can I make sure that it is 1? >> >> Thanks, >> Albert >> > > > > > _______________________________________________ > opencpi_dev mailing > [email protected]http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org > > > >
_______________________________________________ opencpi_dev mailing list [email protected] http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
