> it is not board-dependent - two different boards give incorrect read
> data for the same write values!! ... I wonder if the board is storing
> wrong values a _lot_, and the ECC is normally catching them?
Anyone have any idea what might be going on here?
I ask because I'm fixing to r
> none of the other values used in that seemed to have a problem; but of
> course the program didn't include all 2^16 patterns. I suppose I should
> whip up a small program to try other values, and see if anything else
> does this...
And it does! Quite a few values come back wrong,
> I first have to tweak my 'scope loop program, to turn on memory mapping
So while doing that I just discovered what I _think_ (maybe I'm just not being
smart enough to see that it's somehow 'doing the right thing') is the wierdest
hardware bug I've ever seen.
Plug in an MSV11-J, disable ECC
> From: Glen Slick
> What signal were you probing on the M8186 KDF11-A board?
BDOUT; I'm triggering on that, and without any prints it wouldn't be easy to
find on the MSV11-J. Picking it up off the KDF11-A was the easy way to go.
> If you run the XXDP VMJAB0 diagnostic and there are
> From: Tor Arntsen
> So, here's how to see the updated page while not logged in:
Thanks for posting the 'fix'; the problem, and that workaround, are described
on the 'News' sidebar on the Main Page, but of course people going straight
to a URL won't see that - and since I'm always logged
On 6 July 2018 at 09:48, Tor Arntsen wrote:
> On 6 July 2018 at 05:29, Al Kossow via cctalk wrote:
>>
>>
>> On 7/5/18 8:20 PM, Glen Slick via cctalk wrote:
>>
>>> I don't see any chip info update at that #Technical_information page.
>>
>> The gunkies wiki is broken, none of his changes are gettin
On 6 July 2018 at 05:29, Al Kossow via cctalk wrote:
>
>
> On 7/5/18 8:20 PM, Glen Slick via cctalk wrote:
>
>> I don't see any chip info update at that #Technical_information page.
>
> The gunkies wiki is broken, none of his changes are getting out to the world.
Yes, that's very strange.. if I'm
On 7/5/18 8:20 PM, Glen Slick via cctalk wrote:
> I don't see any chip info update at that #Technical_information page.
The gunkies wiki is broken, none of his changes are getting out to the world.
On Thu, Jul 5, 2018 at 4:43 PM, Noel Chiappa via cctalk
wrote:
> >> I'll add the info to the MSV11-J page on the CHWiki, once I have it.
>
> > Alas, it's down at the moment ... but once it's back, I'll get them
> > right up.
>
> It's back, and I've added the chip info for the low 1MB b
>> I'll add the info to the MSV11-J page on the CHWiki, once I have it.
> Alas, it's down at the moment ... but once it's back, I'll get them
> right up.
It's back, and I've added the chip info for the low 1MB bank:
http://gunkies.org/wiki/MSV11-J_QBUS_memory#Technical_information
> I'm going to need this info real soon ... so I'll probably start on
> this later today if nobody has the info.
> ...
> write a two-instruction loop .. which writes a word with only a single
> '1' bit, hook up a 'scope ... to a DRAM input, and walk the bit through
> ... jus
> From: Glen Slick
> There are 88 41256 256Kx1 DRAMs on a 2MB MSV11-J. Each 512KB bank has
> 22 256Kx1 DRAMs organized as 16 data bits plus 6 ECC bits.
Umm, I think the internal organization is paired banks (one for even word
addresses, one for odd); the manual talks about doing doubl
On Mon, Jul 2, 2018 at 7:14 PM, Noel Chiappa via cctalk
wrote:
> Hi, I'm looking for engineering info on the MSV11-J. I was unable to find any
> prints online, or even a technical manual. (I have the User Manual, but it
> doesn't
> have much detail.)
> The main issue I'm after is working out whi
Hi, I'm looking for engineering info on the MSV11-J. I was unable to find any
prints online, or even a technical manual. (I have the User Manual, but it
doesn't
have much detail.)
The main issue I'm after is working out which bits go into which chips. I
have some other QBUS memory boards with no
14 matches
Mail list logo
