Envelope-to: craig@sbc-85.com
Delivery-date: Sat, 10 Dec 2022 22:38:23 -0600
Subject: Re: MBM V1.0 Boards
To: craig@sbc-85.com
References: <de5bd6b6-a341-42bc-bf69-503467c91786@gmail.com>
 <1D73049A-08C3-4AC6-9D02-9E7E052B4BD5@sbc-85.com>
 <e4890a1a-8b8d-705f-eee8-2fea43acc200@gmail.com>
 <86b601d90d0d$6be1b3f0$43a51bd0$@sbc-85.com>
From: denverh <denverh2000@gmail.com>
Message-ID: <de355b9c-33d1-7a5b-ee47-a1e6e873818c@gmail.com>
Date: Sat, 10 Dec 2022 22:38:09 -0600
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101
 Firefox/68.0 SeaMonkey/2.53.13
MIME-Version: 1.0
In-Reply-To: <86b601d90d0d$6be1b3f0$43a51bd0$@sbc-85.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

craig@sbc-85.com wrote:
> Oh yea, I remember that.  It looks like I took a pair of pliers and put a 0.05" offset in each row of the socket.
>
> what was the problem getting it going?  if you want to send me some verbiage it would be great to add to the user's manual.
It wasn't anything special.  I had a poor connection at one of the port 
selection switches, so it was responding to a different port than the 
switches were set to.  Unusual, but at least it was easy to find.  A 
simple loop that reads from every possible port helps in situations 
where you're not sure what the port really is:
start:  lxi h, start+4
         in 00
         inr c
         mov m,c
         jmp start+5
It's pretty easy then to see what each address line is doing when /cs is 
active, or if /cs is even doing anything.  I still have a ways to go 
before I can say it's all working, but that point is getting closer.

Thanks,

Denver

> regards
>
> -----Original Message-----
> From: denverh <denverh2000@gmail.com>
> Sent: Saturday, December 10, 2022 5:55 PM
> To: SBC-85 <craig@sbc-85.com>
> Subject: Re: MBM V1.0 Boards
>
> Hi Craig,
>
> One more thing - what did you do on the V1.0 board about U6, the 7230, where the hole spacing is 0.1" too narrow?  So far everything is working and it's time to put the rest of the parts in, but that one stopped me.
>
> Thanks,
>
> Denver
>
>
>