#MicroBotics StarBoard
6 messages in this thread
Larry,
MicroBotics claims their board is a "zero wait state design", so I
assume it does mean 0 wait states. I'll check what Redmond Simonson says
though and let you know.
Todd
You may have spotted the message from Ed Lippert mentioning that the
Microbotics does wait when accessed during refresh.
Todd, this is a "no wait state" RAM, regardless of what you think about that
small percentage of waits. I would have no qualms about advertising it as such,
and believe me, I am a stickler when it comes to claims about a product.
Regards, Larry.
Larry,
I just spoke to Red Simonsen and he confirmed that it does cause a wait
state if there's a refresh conflict. I believe you. I'm just curious why it
timed out slower than chip ram. Chip ram has the same thing, no?
Thanks,
Todd
Todd,
One possible reason is that the program itself ends up loading into FAST
memory, and that will affect the timing. Might be worthwhile running it through
ATOM and specifying that it load to CHIP just to see what happens.
Regards, Larry.
Larry,
I'll do that and post the results.
Todd
Agreed Larry. That is universally accepted throughout the industry, minis
included (except for cache of course).