Discussion:
[N8VEM: 15820] ColorVDU Jumpers
J. Alexander Jacocks
2013-04-11 04:23:25 UTC
Permalink
All,

I must be completely blind, but I can't find the jumper reference for the
Color VDU board. I know JP1 needs to be set, but I'm not at all sure about
others.

Help?

Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-11 08:28:20 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
P5 selects the high nibble of the device code;&nbsp; 0xE? is suggested;
i.e., jumper 7-8 only.<br>
<br>
K1, K2, K3 select interrupts.&nbsp; AFAIK, none are used.&nbsp; No jumpers.<br>
<br>
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.<br>
This may take some experimentation to get right for your monitor.&nbsp;
Start with both 1-2.<br>
<br>
JP1 must be in place.<br>
<br>
P32 is an external connector.&nbsp; Leave all pins open.<br>
<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
On 04/10/2013 09:23 PM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y2Qm_dCU=Y=fn0hJi5kMm_PHHzj1iLsr=HyrLrOUVmNWQ-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">All,
<div><br>
</div>
<div style="">I must be completely blind, but I can't find the
jumper reference for the Color VDU board. &nbsp;I know JP1 needs to
be set, but I'm not at all sure about others.</div>
<div style="">
<br>
</div>
<div style="">Help?</div>
<div style=""><br>
</div>
<div style="">Thanks!</div>
<div style="">- Alex</div>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
J. Alexander Jacocks
2013-04-12 03:49:41 UTC
Permalink
OK, I think I have the board set correctly. However, whenever I install it
to the ECB backplane, I don't get any output, anymore, from the serial
console on the N8VEM SBC V2 board. I do get a keyboard LED flash, at power
on, if I connect a PS/2 keyboard. I take that to be a good sign that the
keyboard controller is at least initializing.

I have tried installing the ColorVDU ROM, and also the standard ROM, with
the ColorVDU test programs added. Neither seems to help things.

I have checked my soldering, and I don't see any obvious shorts or missing
connectivity.

I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?

Thanks!
- Alex
**
P5 selects the high nibble of the device code; 0xE? is suggested; i.e.,
jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Wayne Warthen
2013-04-12 06:11:29 UTC
Permalink
Hi Alex,

You will need to apply all of the documented patches even when using the
board with an N8VEM SBCv2.

-Wayne
Post by J. Alexander Jacocks
OK, I think I have the board set correctly. However, whenever I install
it to the ECB backplane, I don't get any output, anymore, from the serial
console on the N8VEM SBC V2 board. I do get a keyboard LED flash, at power
on, if I connect a PS/2 keyboard. I take that to be a good sign that the
keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM, with
the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or missing
connectivity.
I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?
Thanks!
- Alex
**
P5 selects the high nibble of the device code; 0xE? is suggested; i.e.,
jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-12 16:13:03 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Alex,<br>
<br>
Are you using 16K DRAM chips or 64K chips?&nbsp; The SBC-188 BIOS was
written using 64K chips; I have been unable to test with 16K chips
(at a reasonable price).<br>
<br>
Wayne would have to comment on whether this might affect SBC v2
operation.&nbsp; There is a bit in the initialization parameters which
tells the 8563 what size chips are in use.&nbsp; I know the '188 says
"64K."<br>
<br>
#1 priority:&nbsp; get those board mods into the circuit
[ConstructionNotes.txt].<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
On 04/11/2013 11:11 PM, Wayne Warthen wrote:
<blockquote
cite="mid:84ebc378-5faa-42eb-9ed7-97a7a4615041-/***@public.gmane.org"
type="cite">Hi Alex,
<div><br>
</div>
<div>You will need to apply all of the documented patches even
when using the board with an N8VEM SBCv2.</div>
<div><br>
</div>
<div>-Wayne<br>
<br>
On Thursday, April 11, 2013 8:49:41 PM UTC-7, Alexander wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div dir="ltr">
<div>OK, I think I have the board set correctly. &nbsp;However,
whenever I install it to the ECB backplane, I don't get
any output, anymore, from the serial console on the N8VEM
SBC V2 board. &nbsp;I do get a keyboard LED flash, at power on,
if I connect a PS/2 keyboard. &nbsp;I take that to be a good
sign that the keyboard controller is at least
initializing.<br>
</div>
<div><br>
</div>
<div>I have tried installing the ColorVDU ROM, and also the
standard ROM, with the ColorVDU test programs added.
&nbsp;Neither seems to help things.</div>
<div><br>
</div>
<div>I have checked my soldering, and I don't see any
obvious shorts or missing connectivity.</div>
<div><br>
</div>
<div>I did not perform any of the fixups that are listed in
the Construction Notes, as I was not planning to use the
board with a SBC-188 board. &nbsp;Are there any that I should
particularly do?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex<br>
<br>
<div class="gmail_quote">On Thu, Apr 11, 2013 at 4:28 AM,
John Coffman <span dir="ltr">&lt;<a
moz-do-not-send="true" href="javascript:"
target="_blank" gdf-obfuscated-mailto="hl6nv-m18V4J">john...-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt
0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> P5 selects the
high nibble of the device code;&nbsp; 0xE? is suggested;
i.e., jumper 7-8 only.<br>
<br>
K1, K2, K3 select interrupts.&nbsp; AFAIK, none are
used.&nbsp; No jumpers.<br>
<br>
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3
is neg.<br>
This may take some experimentation to get right for
your monitor.&nbsp; Start with both 1-2.<br>
<br>
JP1 must be in place.<br>
<br>
P32 is an external connector.&nbsp; Leave all pins open.<br>
<br>
<br>
--John
<div>
<div><br>
<br>
<br>
<br>
<br>
On 04/10/2013 09:23 PM, J. Alexander Jacocks
wrote: </div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">All,
<div><br>
</div>
<div>I must be completely blind, but I can't
find the jumper reference for the Color
VDU board. &nbsp;I know JP1 needs to be set,
but I'm not at all sure about others.</div>
<div> <br>
</div>
<div>Help?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex</div>
</div>
</div>
</div>
<span><font color="#888888"> -- <br>
You received this message because you are
subscribed to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop
receiving emails from it, send an email to <a
moz-do-not-send="true" href="javascript:"
target="_blank"
gdf-obfuscated-mailto="hl6nv-m18V4J">n8vem+un...@<wbr>googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true" href="javascript:"
target="_blank"
gdf-obfuscated-mailto="hl6nv-m18V4J">n8...-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en" target="_blank">http://groups.google.com/<wbr>group/n8vem?hl=en</a>.<br>
For more options, visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/<wbr>groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
<span><font color="#888888"> </font></span></div>
<span><font color="#888888">
-- <br>
You received this message because you are
subscribed to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
moz-do-not-send="true" href="javascript:"
target="_blank"
gdf-obfuscated-mailto="hl6nv-m18V4J">n8vem+un...@<wbr>googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true" href="javascript:"
target="_blank"
gdf-obfuscated-mailto="hl6nv-m18V4J">n8...-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/<wbr>group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/<wbr>groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
J. Alexander Jacocks
2013-04-12 17:42:03 UTC
Permalink
John,

I am using TMS4416-12 ICs, so they are 16K DRAMs. Should I change them
out? The BoM wasn't specific, so I wasn't aware that the extra capacity
was used. I'd be happy to do some testing, for you, if you want.

Thanks!
- Alex
**
Alex,
Are you using 16K DRAM chips or 64K chips? The SBC-188 BIOS was written
using 64K chips; I have been unable to test with 16K chips (at a reasonable
price).
Wayne would have to comment on whether this might affect SBC v2
operation. There is a bit in the initialization parameters which tells the
8563 what size chips are in use. I know the '188 says "64K."
#1 priority: get those board mods into the circuit
[ConstructionNotes.txt].
--John
Hi Alex,
You will need to apply all of the documented patches even when using the
board with an N8VEM SBCv2.
-Wayne
Post by J. Alexander Jacocks
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested;
i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/**group/n8vem?hl=en<http://groups.google.com/group/n8vem?hl=en>
.
For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/**group/n8vem?hl=en<http://groups.google.com/group/n8vem?hl=en>
.
For more options, visit https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-13 00:00:17 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Long term, I'd like to be able to test the DRAM size on the CVDU to
know what can and cannot be supported.&nbsp; 64K chips will definitely be
needed to use the device in monochrome graphics mode; likewise, to
support multiple character pages as on an IBM-PC.&nbsp; But for a single
page of text, 16K is definitely sufficient:&nbsp; IF ...&nbsp;&nbsp; if the setup
is for 16K, not 64K.<br>
<br>
No matter the 16K/64K initialization setting, you should see video
output, even if it is garbage.&nbsp; The first time I got garbage on the
screen in bringing the board up I was happy to know I was on the
right track.<br>
<br>
Q1:&nbsp; What kind of monitor are you using, and how are you
connecting?&nbsp; A strictly VGA monitor will not sync to the slower
output of this old chip.&nbsp; The SBC-188 setup uses exact EGA timing
with a 16.257Mhz oscillator (see my board pix on the Wiki), so a
"multisync" type of monitor must be used with the VGA connector.&nbsp;
Dan originally connected with a CGA to VGA external board, and must
have used quite different timing parameters.&nbsp; Unfortunately, the
8563 is too old and slow to operate at the higher VGA frequencies.<br>
<br>
Q2:&nbsp; Are you working with Dan's "M8563 Test Programs.zip" yet?&nbsp; They
are on the Wiki on the second page of the CVDU postings.&nbsp; One level
to get to is to be able to read &amp; write registers/memory on the
8563, and print out the correct values.<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
<br>
On 04/12/2013 10:42 AM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y3n3=EN=f7Uf+GfQSOh209QLrC7aELKtaF=x5hRpa-FLw-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">
<div>
<div>John,<br>
<br>
</div>
I am using <font><span>TMS4416-12 ICs, so they are 16K
DRAMs.&nbsp; Should I change them out?&nbsp; The BoM wasn't
specific, so I wasn't aware that the extra capacity was
used.&nbsp; I'd be happy to do some testing, for you, if you
want.<br>
<br>
Thanks!<br>
</span></font></div>
<font><span>- Alex</span></font></div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Apr 12, 2013 at 12:13 PM, John
Coffman <span dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:johninsd-***@public.gmane.org" target="_blank">johninsd-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Alex,<br>
<br>
Are you using 16K DRAM chips or 64K chips?&nbsp; The SBC-188
BIOS was written using 64K chips; I have been unable to
test with 16K chips (at a reasonable price).<br>
<br>
Wayne would have to comment on whether this might affect
SBC v2 operation.&nbsp; There is a bit in the initialization
parameters which tells the 8563 what size chips are in
use.&nbsp; I know the '188 says "64K."<br>
<br>
#1 priority:&nbsp; get those board mods into the circuit
[ConstructionNotes.txt].<span class="HOEnZb"><font
color="#888888"><br>
<br>
--John</font></span>
<div>
<div class="h5"><br>
<br>
<br>
<br>
<br>
On 04/11/2013 11:11 PM, Wayne Warthen wrote:
<blockquote type="cite">Hi Alex,
<div><br>
</div>
<div>You will need to apply all of the documented
patches even when using the board with an N8VEM
SBCv2.</div>
<div><br>
</div>
<div>-Wayne<br>
<br>
On Thursday, April 11, 2013 8:49:41 PM UTC-7,
Alexander wrote:
<blockquote class="gmail_quote" style="margin: 0pt
0pt 0pt 0.8ex; border-left: 1px solid rgb(204,
204, 204); padding-left: 1ex;">
<div dir="ltr">
<div>OK, I think I have the board set
correctly. &nbsp;However, whenever I install it
to the ECB backplane, I don't get any
output, anymore, from the serial console on
the N8VEM SBC V2 board. &nbsp;I do get a keyboard
LED flash, at power on, if I connect a PS/2
keyboard. &nbsp;I take that to be a good sign
that the keyboard controller is at least
initializing.<br>
</div>
<div><br>
</div>
<div>I have tried installing the ColorVDU ROM,
and also the standard ROM, with the ColorVDU
test programs added. &nbsp;Neither seems to help
things.</div>
<div><br>
</div>
<div>I have checked my soldering, and I don't
see any obvious shorts or missing
connectivity.</div>
<div><br>
</div>
<div>I did not perform any of the fixups that
are listed in the Construction Notes, as I
was not planning to use the board with a
SBC-188 board. &nbsp;Are there any that I should
particularly do?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex<br>
<br>
<div class="gmail_quote">On Thu, Apr 11,
2013 at 4:28 AM, John Coffman <span
dir="ltr">&lt;<a moz-do-not-send="true">john...-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204, 204,
204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
P5 selects the high nibble of the
device code;&nbsp; 0xE? is suggested; i.e.,
jumper 7-8 only.<br>
<br>
K1, K2, K3 select interrupts.&nbsp; AFAIK,
none are used.&nbsp; No jumpers.<br>
<br>
K4, K5 select H, V sync polarity; 1-2
is pos., 2-3 is neg.<br>
This may take some experimentation to
get right for your monitor.&nbsp; Start
with both 1-2.<br>
<br>
JP1 must be in place.<br>
<br>
P32 is an external connector.&nbsp; Leave
all pins open.<br>
<br>
<br>
--John
<div>
<div><br>
<br>
<br>
<br>
<br>
On 04/10/2013 09:23 PM, J.
Alexander Jacocks wrote: </div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">All,
<div><br>
</div>
<div>I must be completely
blind, but I can't find the
jumper reference for the
Color VDU board. &nbsp;I know JP1
needs to be set, but I'm not
at all sure about others.</div>
<div> <br>
</div>
<div>Help?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex</div>
</div>
</div>
</div>
<span><font color="#888888"> -- <br>
You received this message
because you are subscribed to
the Google Groups "N8VEM" group.<br>
To unsubscribe from this group
and stop receiving emails from
it, send an email to <a
moz-do-not-send="true">n8vem+un...-/***@public.gmane.org</a>.<br>
To post to this group, send
email to <a
moz-do-not-send="true">n8...-/***@public.gmane.org</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
<span><font color="#888888"> </font></span></div>
<span><font color="#888888"> -- <br>
You received this message because
you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and
stop receiving emails from it, send
an email to <a
moz-do-not-send="true">n8vem+un...-/***@public.gmane.org</a>.<br>
To post to this group, send email to
<a moz-do-not-send="true">n8...-/***@public.gmane.org</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
-- <br>
You received this message because you are subscribed
to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
moz-do-not-send="true"
href="mailto:n8vem+unsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org"
target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</div>
</div>
</div>
<div class="HOEnZb">
<div class="h5">
-- <br>
You received this message because you are subscribed to
the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails
from it, send an email to <a moz-do-not-send="true"
href="mailto:n8vem%2Bunsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org" target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
J. Alexander Jacocks
2013-04-13 11:10:16 UTC
Permalink
John,

Currently, I am connecting to a Dell 19" Trinitron monitor, via VGA. That
monitor is capable of doing quite a few different sync frequencies, but I'm
not completely sure where it's lower bounds are. I'll check on that.

I also have a Commodore 1080 monitor, which supports digital RGB, so it
should be a good fallback, if the Dell won't scan low enough.

I have loaded Dan's test programs onto the ROM disk, in my custom RomWBW
config. However, since the machine does not seem to POST (no output on
serial console) when the ColorVDU is installed, I haven't been able to test
much, yet.

And Wayne, I'll try changing the config for the RAM size, but I'm not too
hopeful that's the issue, since the machine should POST, no matter the ROM
config, when I load the N8VEM_SBC standard ROM, which has no support for
Color VDU, right?

Thanks!
- Alex
**
Long term, I'd like to be able to test the DRAM size on the CVDU to know
what can and cannot be supported. 64K chips will definitely be needed to
use the device in monochrome graphics mode; likewise, to support multiple
character pages as on an IBM-PC. But for a single page of text, 16K is
definitely sufficient: IF ... if the setup is for 16K, not 64K.
No matter the 16K/64K initialization setting, you should see video output,
even if it is garbage. The first time I got garbage on the screen in
bringing the board up I was happy to know I was on the right track.
Q1: What kind of monitor are you using, and how are you connecting? A
strictly VGA monitor will not sync to the slower output of this old chip.
The SBC-188 setup uses exact EGA timing with a 16.257Mhz oscillator (see my
board pix on the Wiki), so a "multisync" type of monitor must be used with
the VGA connector. Dan originally connected with a CGA to VGA external
board, and must have used quite different timing parameters.
Unfortunately, the 8563 is too old and slow to operate at the higher VGA
frequencies.
Q2: Are you working with Dan's "M8563 Test Programs.zip" yet? They are
on the Wiki on the second page of the CVDU postings. One level to get to
is to be able to read & write registers/memory on the 8563, and print out
the correct values.
--John
John,
I am using TMS4416-12 ICs, so they are 16K DRAMs. Should I change them
out? The BoM wasn't specific, so I wasn't aware that the extra capacity
was used. I'd be happy to do some testing, for you, if you want.
Thanks!
- Alex
Alex,
Are you using 16K DRAM chips or 64K chips? The SBC-188 BIOS was written
using 64K chips; I have been unable to test with 16K chips (at a reasonable
price).
Wayne would have to comment on whether this might affect SBC v2
operation. There is a bit in the initialization parameters which tells the
8563 what size chips are in use. I know the '188 says "64K."
#1 priority: get those board mods into the circuit
[ConstructionNotes.txt].
--John
Hi Alex,
You will need to apply all of the documented patches even when using
the board with an N8VEM SBCv2.
-Wayne
Post by J. Alexander Jacocks
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the
Construction Notes, as I was not planning to use the board with a SBC-188
board. Are there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested;
i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor.
Start with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-13 15:32:24 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The loss of the serial output suggests that some signal on the
backplane is corrupted by the CVDU board.&nbsp; The jumper settings I
suggested earlier disconnect all "INT" signals, so this should not
be an issue.&nbsp; As you know, there should be no change in SBC v2
behavior w/ or w/out the CVDU.<br>
<br>
In running the test programs, I would suggest using a RomWBW image
without the CVDU; just use straight serial output.&nbsp; The test program
should be the only s/w addressing the CVDU.&nbsp; The wr/rd of the
registers does not depend on any monitor.&nbsp; <br>
<br>
--John<br>
<br>
<br>
<br>
<br>
On 04/13/2013 04:10 AM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y1=vXJav7kR58c7NcfmmpNcd8v9m7EhMS_hzQP7_aARZw-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr"><span style="color: rgb(0, 0, 0); font-family:
arial,sans-serif; font-size: 13px;">John,</span><br
style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">
<br style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">Currently, I am connecting to a Dell 19"
Trinitron monitor, via VGA. &nbsp;That</span><br style="color:
rgb(0, 0, 0); font-family: arial,sans-serif; font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">monitor is capable of doing quite a few
different sync frequencies, but I'm</span><br style="color:
rgb(0, 0, 0); font-family: arial,sans-serif; font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">not completely sure where it's lower bounds
are. &nbsp;I'll check on that.</span><br style="color: rgb(0, 0,
0); font-family: arial,sans-serif; font-size: 13px;">
<br style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">I also have a Commodore 1080 monitor, which
supports digital RGB, so it</span><br style="color: rgb(0, 0,
0); font-family: arial,sans-serif; font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">should be a good fallback, if the Dell won't
scan low enough.</span><br style="color: rgb(0, 0, 0);
font-family: arial,sans-serif; font-size: 13px;">
<br style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">I have loaded Dan's test programs onto the
ROM disk, in my custom RomWBW</span><br style="color: rgb(0,
0, 0); font-family: arial,sans-serif; font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">config. &nbsp;However, since the machine does not
seem to POST (no output on</span><br style="color: rgb(0, 0,
0); font-family: arial,sans-serif; font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">serial console) when the ColorVDU is
installed, I haven't been able to test</span><br style="color:
rgb(0, 0, 0); font-family: arial,sans-serif; font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">much, yet.</span>
<div><br>
</div>
<div>And Wayne, I'll try changing the config for the RAM size,
but I'm not too hopeful that's the issue, since the machine
should POST, no matter the ROM config, when I load the
N8VEM_SBC standard ROM, which has no support for Color VDU,
right?<br style="color: rgb(0, 0, 0); font-family:
arial,sans-serif; font-size: 13px;">
<br style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family:
arial,sans-serif; font-size: 13px;">Thanks!</span><br
style="color: rgb(0, 0, 0); font-family: arial,sans-serif;
font-size: 13px;">
<span style="color: rgb(0, 0, 0); font-family:
arial,sans-serif; font-size: 13px;">- Alex</span><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Apr 12, 2013 at 8:00 PM, John
Coffman <span dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:johninsd-***@public.gmane.org" target="_blank">johninsd-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Long term, I'd like
to be able to test the DRAM size on the CVDU to know what
can and cannot be supported.&nbsp; 64K chips will definitely be
needed to use the device in monochrome graphics mode;
likewise, to support multiple character pages as on an
IBM-PC.&nbsp; But for a single page of text, 16K is definitely
sufficient:&nbsp; IF ...&nbsp;&nbsp; if the setup is for 16K, not 64K.<br>
<br>
No matter the 16K/64K initialization setting, you should
see video output, even if it is garbage.&nbsp; The first time I
got garbage on the screen in bringing the board up I was
happy to know I was on the right track.<br>
<br>
Q1:&nbsp; What kind of monitor are you using, and how are you
connecting?&nbsp; A strictly VGA monitor will not sync to the
slower output of this old chip.&nbsp; The SBC-188 setup uses
exact EGA timing with a 16.257Mhz oscillator (see my board
pix on the Wiki), so a "multisync" type of monitor must be
used with the VGA connector.&nbsp; Dan originally connected
with a CGA to VGA external board, and must have used quite
different timing parameters.&nbsp; Unfortunately, the 8563 is
too old and slow to operate at the higher VGA frequencies.<br>
<br>
Q2:&nbsp; Are you working with Dan's "M8563 Test Programs.zip"
yet?&nbsp; They are on the Wiki on the second page of the CVDU
postings.&nbsp; One level to get to is to be able to read &amp;
write registers/memory on the 8563, and print out the
correct values.<span class="HOEnZb"><font color="#888888"><br>
<br>
--John</font></span>
<div>
<div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
On 04/12/2013 10:42 AM, J. Alexander Jacocks wrote:
<blockquote type="cite">
<div dir="ltr">
<div>
<div>John,<br>
<br>
</div>
I am using <font><span>TMS4416-12 ICs, so they
are 16K DRAMs.&nbsp; Should I change them out?&nbsp;
The BoM wasn't specific, so I wasn't aware
that the extra capacity was used.&nbsp; I'd be
happy to do some testing, for you, if you
want.<br>
<br>
Thanks!<br>
</span></font></div>
<font><span>- Alex</span></font></div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Apr 12, 2013 at
12:13 PM, John Coffman <span dir="ltr">&lt;<a
moz-do-not-send="true"
href="mailto:johninsd-***@public.gmane.org"
target="_blank">johninsd-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:
0pt 0pt 0pt 0.8ex; border-left: 1px solid
rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Alex,<br>
<br>
Are you using 16K DRAM chips or 64K chips?&nbsp;
The SBC-188 BIOS was written using 64K
chips; I have been unable to test with 16K
chips (at a reasonable price).<br>
<br>
Wayne would have to comment on whether this
might affect SBC v2 operation.&nbsp; There is a
bit in the initialization parameters which
tells the 8563 what size chips are in use.&nbsp;
I know the '188 says "64K."<br>
<br>
#1 priority:&nbsp; get those board mods into the
circuit [ConstructionNotes.txt].<span><font
color="#888888"><br>
<br>
--John</font></span>
<div>
<div><br>
<br>
<br>
<br>
<br>
On 04/11/2013 11:11 PM, Wayne Warthen
wrote:
<blockquote type="cite">Hi Alex,
<div><br>
</div>
<div>You will need to apply all of the
documented patches even when using
the board with an N8VEM SBCv2.</div>
<div><br>
</div>
<div>-Wayne<br>
<br>
On Thursday, April 11, 2013 8:49:41
PM UTC-7, Alexander wrote:
<blockquote class="gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204,
204, 204); padding-left: 1ex;">
<div dir="ltr">
<div>OK, I think I have the
board set correctly. &nbsp;However,
whenever I install it to the
ECB backplane, I don't get any
output, anymore, from the
serial console on the N8VEM
SBC V2 board. &nbsp;I do get a
keyboard LED flash, at power
on, if I connect a PS/2
keyboard. &nbsp;I take that to be a
good sign that the keyboard
controller is at least
initializing.<br>
</div>
<div><br>
</div>
<div>I have tried installing the
ColorVDU ROM, and also the
standard ROM, with the
ColorVDU test programs added.
&nbsp;Neither seems to help things.</div>
<div><br>
</div>
<div>I have checked my
soldering, and I don't see any
obvious shorts or missing
connectivity.</div>
<div><br>
</div>
<div>I did not perform any of
the fixups that are listed in
the Construction Notes, as I
was not planning to use the
board with a SBC-188 board.
&nbsp;Are there any that I should
particularly do?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex<br>
<br>
<div class="gmail_quote">On
Thu, Apr 11, 2013 at 4:28
AM, John Coffman <span
dir="ltr">&lt;<a
moz-do-not-send="true">john...-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote
class="gmail_quote"
style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px
solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff"
text="#000000"> P5
selects the high nibble
of the device code;&nbsp;
0xE? is suggested; i.e.,
jumper 7-8 only.<br>
<br>
K1, K2, K3 select
interrupts.&nbsp; AFAIK, none
are used.&nbsp; No jumpers.<br>
<br>
K4, K5 select H, V sync
polarity; 1-2 is pos.,
2-3 is neg.<br>
This may take some
experimentation to get
right for your monitor.&nbsp;
Start with both 1-2.<br>
<br>
JP1 must be in place.<br>
<br>
P32 is an external
connector.&nbsp; Leave all
pins open.<br>
<br>
<br>
--John
<div>
<div><br>
<br>
<br>
<br>
<br>
On 04/10/2013 09:23
PM, J. Alexander
Jacocks wrote: </div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">All,

<div><br>
</div>
<div>I must be
completely
blind, but I
can't find the
jumper
reference for
the Color VDU
board. &nbsp;I know
JP1 needs to
be set, but
I'm not at all
sure about
others.</div>
<div> <br>
</div>
<div>Help?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex</div>
</div>
</div>
</div>
<span><font
color="#888888">
-- <br>
You received this
message because
you are subscribed
to the Google
Groups "N8VEM"
group.<br>
To unsubscribe
from this group
and stop receiving
emails from it,
send an email to <a
moz-do-not-send="true">n8vem+un...-/***@public.gmane.org</a>.<br>
To post to this
group, send email
to <a
moz-do-not-send="true">n8...-/***@public.gmane.org</a>.<br>
Visit this group
at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en" target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options,
visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
<span><font
color="#888888"> </font></span></div>
<span><font
color="#888888"> -- <br>
You received this
message because you
are subscribed to the
Google Groups "N8VEM"
group.<br>
To unsubscribe from
this group and stop
receiving emails from
it, send an email to <a
moz-do-not-send="true">n8vem+un...-/***@public.gmane.org</a>.<br>
To post to this group,
send email to <a
moz-do-not-send="true">n8...-/***@public.gmane.org</a>.<br>
Visit this group at <a
moz-do-not-send="true" href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options,
visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out" target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
-- <br>
You received this message because you
are subscribed to the Google Groups
"N8VEM" group.<br>
To unsubscribe from this group and
stop receiving emails from it, send an
email to <a moz-do-not-send="true"
href="mailto:n8vem+unsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org"
target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</div>
</div>
</div>
<div>
<div> -- <br>
You received this message because you are
subscribed to the Google Groups "N8VEM"
group.<br>
To unsubscribe from this group and stop
receiving emails from it, send an email to
<a moz-do-not-send="true"
href="mailto:n8vem%2Bunsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org"
target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
-- <br>
You received this message because you are subscribed
to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
moz-do-not-send="true"
href="mailto:n8vem+unsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org"
target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</div>
</div>
</div>
<div class="HOEnZb">
<div class="h5">
-- <br>
You received this message because you are subscribed to
the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails
from it, send an email to <a moz-do-not-send="true"
href="mailto:n8vem%2Bunsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org" target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
Wayne Warthen
2013-04-13 16:02:57 UTC
Permalink
Hi Alex,

I think that John generally covered it, but just to make sure I am
answering the question... Yes, the N8VEM standard ROM should run fine with
the CVDU card installed regardless of the memory config/setup of the CVDU
card itself. As John said, seems like the CVDU is somehow corrupting a
signal on the backplane.

I don't remember if you mentioned it previously, but what other cards (if
any) are on your backplane? Just to rule it out, you should try alternate
slots on the backplane and removing any other cards.

I don't have any great ideas on how to isolate bus corruption by the CVDU.
I guess I would start by pulling out the bus interface chips on the CVDU
and see if the SBC then boots successfully.

-Wayne
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Wayne Warthen
2013-04-13 04:21:17 UTC
Permalink
Hi Alex,

Regarding the 16/64K RAM chips. In RomWBW, the VDU chip is configured with
the bit set for 64K RAM chips. Note that the code only uses the first 16K.
I am not quite sure what will happen if the VDU is configured for 64K RAM
and 16K RAM chips are used.

If you are doing your own ROM builds (pretty easy), you can make the
following change in the file cvdu.asm in the Source directory:

Near the end of the file, find the line that reads:

.DB $20+(1<<4) ; 28: char set addr; RAM size (64/16)

and change it to:

.DB $20 ; 28: char set addr; RAM size (64/16)

Thanks,

Wayne
Alex,
Are you using 16K DRAM chips or 64K chips? The SBC-188 BIOS was written
using 64K chips; I have been unable to test with 16K chips (at a reasonable
price).
Wayne would have to comment on whether this might affect SBC v2
operation. There is a bit in the initialization parameters which tells the
8563 what size chips are in use. I know the '188 says "64K."
#1 priority: get those board mods into the circuit
[ConstructionNotes.txt].
--John
Hi Alex,
You will need to apply all of the documented patches even when using the
board with an N8VEM SBCv2.
-Wayne
Post by J. Alexander Jacocks
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested;
i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-25 07:45:50 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Resurrecting an old thread ...<br>
<br>
RE:&nbsp; Color VDU with 4416 DRAMs vs 4464 DRAMs<br>
<br>
I just got my hands on some reasonably priced 4416's (16K x 4)
DRAMs.&nbsp; After a little experimentation:<br>
<br>
&nbsp;&nbsp;&nbsp; 1.&nbsp; If the current SBC-188 BIOS is configured for 16K chips
instead of 64K, the BIOS only uses 16K of memory, so either size
DRAM chip will work.&nbsp; However, this requires re-compiling the
initialization routine with "DRAMSize" set to 16 instead of 64.&nbsp;
"DRAMSize" is a "#define" in "ega9a.h".&nbsp; This is suggested as an
immediate workaround.<br>
<br>
&nbsp;&nbsp;&nbsp; 2.&nbsp; Dynamically determining the DRAM size is easy, and will be a
part of the next BIOS update.&nbsp; The procedure consists of:<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; a.&nbsp; Set the DRAM size to 64K.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; b.&nbsp; Write zero to address 0x0000.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; c.&nbsp; Write non-zero to address 0x0100.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; d.&nbsp; Check the value in address 0x0000.&nbsp; If it changed,
you have 16K DRAM chips; if not, you have 64K DRAM chips.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; e.&nbsp; If you have the smaller chips, reset the DRAM size
to 16K.<br>
<br>
16K chips will support alpha mode 3 (16 colors) with 2 pages.&nbsp; Only
1 page is used as of now.<br>
<br>
64K chips will be used in the future to support alpha mode 3 with 8
pages.&nbsp; I have yet to experiment with graphics mode, but this
requires at least 32K of memory; hence, the larger chips.&nbsp; With
dynamic determination of the chip size, it is possible to know
whether the graphic mode will be available.<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
On 04/11/2013 08:49 PM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y2XdK9Q6W9QwQWvFTxYUTq+HhkE1J2tA5kU4ocHNk=h2Q-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">
<div>OK, I think I have the board set correctly. &nbsp;However,
whenever I install it to the ECB backplane, I don't get any
output, anymore, from the serial console on the N8VEM SBC V2
board. &nbsp;I do get a keyboard LED flash, at power on, if I
connect a PS/2 keyboard. &nbsp;I take that to be a good sign that
the keyboard controller is at least initializing.<br>
</div>
<div><br>
</div>
<div style="">I have tried installing the ColorVDU ROM, and also
the standard ROM, with the ColorVDU test programs added.
&nbsp;Neither seems to help things.</div>
<div style=""><br>
</div>
<div style="">I have checked my soldering, and I don't see any
obvious shorts or missing connectivity.</div>
<div style=""><br>
</div>
<div style="">I did not perform any of the fixups that are
listed in the Construction Notes, as I was not planning to use
the board with a SBC-188 board. &nbsp;Are there any that I should
particularly do?</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Thanks!</div>
<div class="gmail_extra">- Alex<br>
<br>
<div class="gmail_quote">On Thu, Apr 11, 2013 at 4:28 AM, John
Coffman <span dir="ltr">&lt;<a moz-do-not-send="true"
href="mailto:johninsd-***@public.gmane.org" target="_blank">johninsd-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> P5 selects the high
nibble of the device code;&nbsp; 0xE? is suggested; i.e.,
jumper 7-8 only.<br>
<br>
K1, K2, K3 select interrupts.&nbsp; AFAIK, none are used.&nbsp; No
jumpers.<br>
<br>
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is
neg.<br>
This may take some experimentation to get right for your
monitor.&nbsp; Start with both 1-2.<br>
<br>
JP1 must be in place.<br>
<br>
P32 is an external connector.&nbsp; Leave all pins open.<br>
<br>
<br>
--John
<div>
<div class="h5"><br>
<br>
<br>
<br>
<br>
On 04/10/2013 09:23 PM, J. Alexander Jacocks wrote:
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">All,
<div><br>
</div>
<div>I must be completely blind, but I can't
find the jumper reference for the Color VDU
board. &nbsp;I know JP1 needs to be set, but I'm
not at all sure about others.</div>
<div> <br>
</div>
<div>Help?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex</div>
</div>
</div>
</div>
<span class="HOEnZb"><font color="#888888"> -- <br>
You received this message because you are
subscribed to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
moz-do-not-send="true"
href="mailto:n8vem+unsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org"
target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
<span class="HOEnZb"><font color="#888888"> </font></span></div>
<span class="HOEnZb"><font color="#888888">
-- <br>
You received this message because you are subscribed
to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
moz-do-not-send="true"
href="mailto:n8vem%2Bunsubscribe-/***@public.gmane.org"
target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:n8vem-/***@public.gmane.org" target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
J. Alexander Jacocks
2013-04-25 11:24:01 UTC
Permalink
Interesting. Wayne, could you add something similar to RomWBW?

I'm thinking that I should source a pair of 4464s, but I need to figure out
why my board is killing the bus, first. I haven't made any progress on
that front, yet.

Thanks!
- Alex
Post by John Coffman
**
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
I just got my hands on some reasonably priced 4416's (16K x 4) DRAMs.
1. If the current SBC-188 BIOS is configured for 16K chips instead of
64K, the BIOS only uses 16K of memory, so either size DRAM chip will work.
However, this requires re-compiling the initialization routine with
"DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in
"ega9a.h". This is suggested as an immediate workaround.
2. Dynamically determining the DRAM size is easy, and will be a part
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you
have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1 page
is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8
pages. I have yet to experiment with graphics mode, but this requires at
least 32K of memory; hence, the larger chips. With dynamic determination
of the chip size, it is possible to know whether the graphic mode will be
available.
--John
OK, I think I have the board set correctly. However, whenever I install
it to the ECB backplane, I don't get any output, anymore, from the serial
console on the N8VEM SBC V2 board. I do get a keyboard LED flash, at power
on, if I connect a PS/2 keyboard. I take that to be a good sign that the
keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested; i.e.,
jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Wayne Warthen
2013-04-25 14:13:17 UTC
Permalink
Absolutely. Now that John has documented the detection process so clearly,
I can easily implement this in RomWBW. I will publish an updated Beta
release in the next day or two.

--Wayne
Post by J. Alexander Jacocks
Interesting. Wayne, could you add something similar to RomWBW?
I'm thinking that I should source a pair of 4464s, but I need to figure
out why my board is killing the bus, first. I haven't made any progress on
that front, yet.
Thanks!
- Alex
Post by John Coffman
**
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
I just got my hands on some reasonably priced 4416's (16K x 4) DRAMs.
1. If the current SBC-188 BIOS is configured for 16K chips instead
of 64K, the BIOS only uses 16K of memory, so either size DRAM chip will
work. However, this requires re-compiling the initialization routine with
"DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in
"ega9a.h". This is suggested as an immediate workaround.
2. Dynamically determining the DRAM size is easy, and will be a part
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you
have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1
page is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8
pages. I have yet to experiment with graphics mode, but this requires at
least 32K of memory; hence, the larger chips. With dynamic determination
of the chip size, it is possible to know whether the graphic mode will be
available.
--John
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested; i.e.,
jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Wayne Warthen
2013-04-29 20:41:06 UTC
Permalink
Just wanted to follow-up and say that I have implemented the dynamic VDU
RAM size handling in the latest Beta of RomWBW.

--Wayne
Post by Wayne Warthen
Absolutely. Now that John has documented the detection process so
clearly, I can easily implement this in RomWBW. I will publish an updated
Beta release in the next day or two.
--Wayne
Post by J. Alexander Jacocks
Interesting. Wayne, could you add something similar to RomWBW?
I'm thinking that I should source a pair of 4464s, but I need to figure
out why my board is killing the bus, first. I haven't made any progress on
that front, yet.
Thanks!
- Alex
Post by John Coffman
**
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
I just got my hands on some reasonably priced 4416's (16K x 4) DRAMs.
1. If the current SBC-188 BIOS is configured for 16K chips instead
of 64K, the BIOS only uses 16K of memory, so either size DRAM chip will
work. However, this requires re-compiling the initialization routine with
"DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in
"ega9a.h". This is suggested as an immediate workaround.
2. Dynamically determining the DRAM size is easy, and will be a
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you
have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1
page is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8
pages. I have yet to experiment with graphics mode, but this requires at
least 32K of memory; hence, the larger chips. With dynamic determination
of the chip size, it is possible to know whether the graphic mode will be
available.
--John
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the
Construction Notes, as I was not planning to use the board with a SBC-188
board. Are there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested;
i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-29 23:03:59 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 04/29/2013 01:41 PM, Wayne Warthen wrote:
<blockquote
cite="mid:77a3931c-5ebe-48fa-b289-c3ba9cda99e0-/***@public.gmane.org"
type="cite">Just wanted to follow-up and say that I have
implemented the dynamic VDU RAM size handling in the latest Beta
of RomWBW.</blockquote>
<br>
Wayne,<br>
<br>
Great!<br>
<br>
The DRAM size is a nice little bit of information to know if one
wants to begin playing with the 8563 in graphics mode.&nbsp; This idea is
way down there on my "I'd like to try it" list.<br>
<br>
--John<br>
<br>
<br>
<br>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />

John Coffman
2013-04-25 17:51:41 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alex,<br>
<br>
Sorry to hear that you still have the trouble.&nbsp; The following may be
old ideas, but here are some:<br>
<br>
1.&nbsp; B_/INT not pulled low all the time.&nbsp; One of the board updates
fixed a polarity problem in the interrupt request output from the
8242.<br>
2.&nbsp; On the SBC-188, use of the CVDU suppresses all serial output,
unless the video is reset to mode 7.&nbsp; The wiki has a tiny utility to
do this; but DOS must be running to use it.&nbsp; There is also a utility
to return to [color] video mode 3.<br>
3.&nbsp; Each bus signal will need to be checked:&nbsp; /RD, /WR, /MREQ,
/IORQ, /M1, ... to make sure it is not stuck.&nbsp; Although, these
mentioned are all inputs to the CVDU board.<br>
<br>
Make sure all the board updates, per the ConstructionNotes.txt have
been installed correctly.&nbsp; There are pix of the top and bottom of
the modified board with orange wires.<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
<br>
On 04/25/2013 04:24 AM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y33+A=hiBYJVFGe1S_bfacd5hrpTpbd26yEaJiXVk0XGQ-JsoAwUIsXosN+***@public.gmane.org"
type="cite">Interesting. &nbsp;Wayne, could you add something similar
to RomWBW?
<div><br>
</div>
<div>I'm thinking that I should source a pair of 4464s, but I need
to figure out why my board is killing the bus, first. &nbsp;I haven't
made any progress on that front, yet.</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex<span></span><br>
<br>
On Thursday, April 25, 2013, John Coffman wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Resurrecting an old
thread ...<br>
<br>
RE:&nbsp; Color VDU with 4416 DRAMs vs 4464 DRAMs<br>
<br>
I just got my hands on some reasonably priced 4416's (16K x
4) DRAMs.&nbsp; After a little experimentation:<br>
<br>
&nbsp;&nbsp;&nbsp; 1.&nbsp; If the current SBC-188 BIOS is configured for 16K
chips instead of 64K, the BIOS only uses 16K of memory, so
either size DRAM chip will work.&nbsp; However, this requires
re-compiling the initialization routine with "DRAMSize" set
to 16 instead of 64.&nbsp; "DRAMSize" is a "#define" in
"ega9a.h".&nbsp; This is suggested as an immediate workaround.<br>
<br>
&nbsp;&nbsp;&nbsp; 2.&nbsp; Dynamically determining the DRAM size is easy, and
will be a part of the next BIOS update.&nbsp; The procedure
consists of:<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; a.&nbsp; Set the DRAM size to 64K.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; b.&nbsp; Write zero to address 0x0000.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; c.&nbsp; Write non-zero to address 0x0100.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; d.&nbsp; Check the value in address 0x0000.&nbsp; If it
changed, you have 16K DRAM chips; if not, you have 64K DRAM
chips.<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; e.&nbsp; If you have the smaller chips, reset the
DRAM size to 16K.<br>
<br>
16K chips will support alpha mode 3 (16 colors) with 2
pages.&nbsp; Only 1 page is used as of now.<br>
<br>
64K chips will be used in the future to support alpha mode 3
with 8 pages.&nbsp; I have yet to experiment with graphics mode,
but this requires at least 32K of memory; hence, the larger
chips.&nbsp; With dynamic determination of the chip size, it is
possible to know whether the graphic mode will be available.<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
On 04/11/2013 08:49 PM, J. Alexander Jacocks wrote:
<blockquote type="cite">
<div dir="ltr">
<div>OK, I think I have the board set correctly.
&nbsp;However, whenever I install it to the ECB backplane,
I don't get any output, anymore, from the serial
console on the N8VEM SBC V2 board. &nbsp;I do get a
keyboard LED flash, at power on, if I connect a PS/2
keyboard. &nbsp;I take that to be a good sign that the
keyboard controller is at least initializing.<br>
</div>
<div><br>
</div>
<div>I have tried installing the ColorVDU ROM, and also
the standard ROM, with the ColorVDU test programs
added. &nbsp;Neither seems to help things.</div>
<div><br>
</div>
<div>I have checked my soldering, and I don't see any
obvious shorts or missing connectivity.</div>
<div><br>
</div>
<div>I did not perform any of the fixups that are listed
in the Construction Notes, as I was not planning to
use the board with a SBC-188 board. &nbsp;Are there any
that I should particularly do?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex<br>
<br>
<div>On Thu, Apr 11, 2013 at 4:28 AM, John Coffman <span
dir="ltr">&lt;<a moz-do-not-send="true">johninsd-***@public.gmane.org</a>&gt;</span>
wrote:<br>
<blockquote style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> P5 selects
the high nibble of the device code;&nbsp; 0xE? is
suggested; i.e., jumper 7-8 only.<br>
<br>
K1, K2, K3 select interrupts.&nbsp; AFAIK, none are
used.&nbsp; No jumpers.<br>
<br>
K4, K5 select H, V sync polarity; 1-2 is pos.,
2-3 is neg.<br>
This may take some experimentation to get right
for your monitor.&nbsp; Start with both 1-2.<br>
<br>
JP1 must be in place.<br>
<br>
P32 is an external connector.&nbsp; Leave all pins
open.<br>
<br>
<br>
--John
<div>
<div><br>
<br>
<br>
<br>
<br>
On 04/10/2013 09:23 PM, J. Alexander Jacocks
wrote: </div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">All,
<div><br>
</div>
<div>I must be completely blind, but I
can't find the jumper reference for
the Color VDU board. &nbsp;I know JP1 needs
to be set, but I'm not at all sure
about others.</div>
<div> <br>
</div>
<div>Help?</div>
<div><br>
</div>
<div>Thanks!</div>
<div>- Alex</div>
</div>
</div>
</div>
<span><font color="#888888"> -- <br>
You received this message because you are
subscribed to the Google Groups "N8VEM"
group.<br>
To unsubscribe from this group and stop
receiving emails from it, send an email to
<a moz-do-not-send="true">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a
moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</font></span></blockquote>
<span><font color="#888888"> </font></span></div>
<span><font color="#888888"> -- <br>
You received this message because you are
subscribed to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop
receiving emails from it, send an email to </font></span></blockquote>
</div>
</div>
</div>
</blockquote>
</div>
-- <br>
You received this message because you are subscribed to the
Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from
it, send an email to <a moz-do-not-send="true"
href="javascript:_e({}, 'cvml',
'n8vem%2Bunsubscribe-/***@public.gmane.org');" target="_blank">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true" href="javascript:_e({}, 'cvml',
'n8vem-/***@public.gmane.org');" target="_blank">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en"
target="_blank">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out"
target="_blank">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</div>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem+unsubscribe-/***@public.gmane.org">n8vem+unsubscribe-/***@public.gmane.org</a>.<br>
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:n8vem-/***@public.gmane.org">n8vem-/***@public.gmane.org</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br>
&nbsp;<br>
&nbsp;<br>
</blockquote>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
J. Alexander Jacocks
2013-04-28 21:49:28 UTC
Permalink
I'm using my ColorVDU with the SBCv2 board, so the SBC-188 fixes shouldn't
be necessary.

I have board revision 1.0-005, so I think I have the most updated board
currently available, so I don't think that's the issue.

I was checking all of my soldering (again!), and I noticed something,
though. The 16MHz oscillator socket is a 14-pin socket, though only a
half-can oscillator is used, for clearance reasons. I noticed, though,
that pin 11 is connected to 8563 pin 2. Since I am using an oscillator
socket, though, only pins 1, 7, 8, and 14 have pins soldered to the board.
It looks like the 8563 is not getting a DCLK signal.

Would this be enough to kill the bus?

- Alex
**
Alex,
Sorry to hear that you still have the trouble. The following may be old
1. B_/INT not pulled low all the time. One of the board updates fixed a
polarity problem in the interrupt request output from the 8242.
2. On the SBC-188, use of the CVDU suppresses all serial output, unless
the video is reset to mode 7. The wiki has a tiny utility to do this; but
DOS must be running to use it. There is also a utility to return to
[color] video mode 3.
3. Each bus signal will need to be checked: /RD, /WR, /MREQ, /IORQ, /M1,
... to make sure it is not stuck. Although, these mentioned are all inputs
to the CVDU board.
Make sure all the board updates, per the ConstructionNotes.txt have been
installed correctly. There are pix of the top and bottom of the modified
board with orange wires.
--John
Interesting. Wayne, could you add something similar to RomWBW?
I'm thinking that I should source a pair of 4464s, but I need to figure
out why my board is killing the bus, first. I haven't made any progress on
that front, yet.
Thanks!
- Alex
Post by John Coffman
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
I just got my hands on some reasonably priced 4416's (16K x 4) DRAMs.
1. If the current SBC-188 BIOS is configured for 16K chips instead
of 64K, the BIOS only uses 16K of memory, so either size DRAM chip will
work. However, this requires re-compiling the initialization routine with
"DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in
"ega9a.h". This is suggested as an immediate workaround.
2. Dynamically determining the DRAM size is easy, and will be a part
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you
have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1
page is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8
pages. I have yet to experiment with graphics mode, but this requires at
least 32K of memory; hence, the larger chips. With dynamic determination
of the chip size, it is possible to know whether the graphic mode will be
available.
--John
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the Construction
Notes, as I was not planning to use the board with a SBC-188 board. Are
there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested; i.e.,
jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Wayne Warthen
2013-04-29 00:04:56 UTC
Permalink
Hi Alex,

The documented fixes are required when using the ColorVDU 1.0-005 with
SBCv2. The fixes are not specific to the SBC-188, they apply regardless of
the host CPU used.

Pin 11 of P24 (16 MHz oscillator) is intended to be connected to pin 2 of
the 8563. The DIP-14 footprint on the PCB is specifically routed to allow
for the use of either a half or full can oscillator. I am using a half-can
just as you are with no issues.

Suggest you focus on the patches... :-)

--Wayne
Post by J. Alexander Jacocks
I'm using my ColorVDU with the SBCv2 board, so the SBC-188 fixes shouldn't
be necessary.
I have board revision 1.0-005, so I think I have the most updated board
currently available, so I don't think that's the issue.
I was checking all of my soldering (again!), and I noticed something,
though. The 16MHz oscillator socket is a 14-pin socket, though only a
half-can oscillator is used, for clearance reasons. I noticed, though,
that pin 11 is connected to 8563 pin 2. Since I am using an oscillator
socket, though, only pins 1, 7, 8, and 14 have pins soldered to the board.
It looks like the 8563 is not getting a DCLK signal.
Would this be enough to kill the bus?
- Alex
**
Alex,
Sorry to hear that you still have the trouble. The following may be old
1. B_/INT not pulled low all the time. One of the board updates fixed a
polarity problem in the interrupt request output from the 8242.
2. On the SBC-188, use of the CVDU suppresses all serial output, unless
the video is reset to mode 7. The wiki has a tiny utility to do this; but
DOS must be running to use it. There is also a utility to return to
[color] video mode 3.
3. Each bus signal will need to be checked: /RD, /WR, /MREQ, /IORQ,
/M1, ... to make sure it is not stuck. Although, these mentioned are all
inputs to the CVDU board.
Make sure all the board updates, per the ConstructionNotes.txt have been
installed correctly. There are pix of the top and bottom of the modified
board with orange wires.
--John
Interesting. Wayne, could you add something similar to RomWBW?
I'm thinking that I should source a pair of 4464s, but I need to figure
out why my board is killing the bus, first. I haven't made any progress on
that front, yet.
Thanks!
- Alex
Post by John Coffman
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
I just got my hands on some reasonably priced 4416's (16K x 4) DRAMs.
1. If the current SBC-188 BIOS is configured for 16K chips instead
of 64K, the BIOS only uses 16K of memory, so either size DRAM chip will
work. However, this requires re-compiling the initialization routine with
"DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in
"ega9a.h". This is suggested as an immediate workaround.
2. Dynamically determining the DRAM size is easy, and will be a
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you
have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1
page is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8
pages. I have yet to experiment with graphics mode, but this requires at
least 32K of memory; hence, the larger chips. With dynamic determination
of the chip size, it is possible to know whether the graphic mode will be
available.
--John
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the
Construction Notes, as I was not planning to use the board with a SBC-188
board. Are there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested;
i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start
with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Max Scane
2013-04-29 00:13:58 UTC
Permalink
Hi Alex,

If you are using a half can oscillator, then you need to replace the oscillator socket with a proper socket with all pins.

The one you have will only work with a full can oscillator.

Cheers,

Max

Sent from my iPad
I'm using my ColorVDU with the SBCv2 board, so the SBC-188 fixes shouldn't be necessary.
I have board revision 1.0-005, so I think I have the most updated board currently available, so I don't think that's the issue.
I was checking all of my soldering (again!), and I noticed something, though. The 16MHz oscillator socket is a 14-pin socket, though only a half-can oscillator is used, for clearance reasons. I noticed, though, that pin 11 is connected to 8563 pin 2. Since I am using an oscillator socket, though, only pins 1, 7, 8, and 14 have pins soldered to the board. It looks like the 8563 is not getting a DCLK signal.
Would this be enough to kill the bus?
- Alex
Alex,
1. B_/INT not pulled low all the time. One of the board updates fixed a polarity problem in the interrupt request output from the 8242.
2. On the SBC-188, use of the CVDU suppresses all serial output, unless the video is reset to mode 7. The wiki has a tiny utility to do this; but DOS must be running to use it. There is also a utility to return to [color] video mode 3.
3. Each bus signal will need to be checked: /RD, /WR, /MREQ, /IORQ, /M1, ... to make sure it is not stuck. Although, these mentioned are all inputs to the CVDU board.
Make sure all the board updates, per the ConstructionNotes.txt have been installed correctly. There are pix of the top and bottom of the modified board with orange wires.
--John
Post by J. Alexander Jacocks
Interesting. Wayne, could you add something similar to RomWBW?
I'm thinking that I should source a pair of 4464s, but I need to figure out why my board is killing the bus, first. I haven't made any progress on that front, yet.
Thanks!
- Alex
Post by John Coffman
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
1. If the current SBC-188 BIOS is configured for 16K chips instead of 64K, the BIOS only uses 16K of memory, so either size DRAM chip will work. However, this requires re-compiling the initialization routine with "DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in "ega9a.h". This is suggested as an immediate workaround.
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1 page is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8 pages. I have yet to experiment with graphics mode, but this requires at least 32K of memory; hence, the larger chips. With dynamic determination of the chip size, it is possible to know whether the graphic mode will be available.
--John
OK, I think I have the board set correctly. However, whenever I install it to the ECB backplane, I don't get any output, anymore, from the serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash, at power on, if I connect a PS/2 keyboard. I take that to be a good sign that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM, with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or missing connectivity.
I did not perform any of the fixups that are listed in the Construction Notes, as I was not planning to use the board with a SBC-188 board. Are there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested; i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for the Color VDU board. I know JP1 needs to be set, but I'm not at all sure about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
J. Alexander Jacocks
2013-04-29 00:49:19 UTC
Permalink
Thanks, Max. I indeed just did that. I now get a cycling orange/green
light (improper sync, most likely), on my test monitor. So, that's good to
see.

I'll concentrate on applying the fixes. How do you all suggest doing the
leg-type fixes? Direct-soldering to an IC leg, bent outside of the socket?

Thanks!
- Alex
Post by Wayne Warthen
Hi Alex,
If you are using a half can oscillator, then you need to replace the
oscillator socket with a proper socket with all pins.
The one you have will only work with a full can oscillator.
Cheers,
Max
Sent from my iPad
I'm using my ColorVDU with the SBCv2 board, so the SBC-188 fixes shouldn't be necessary.
I have board revision 1.0-005, so I think I have the most updated board
currently available, so I don't think that's the issue.
I was checking all of my soldering (again!), and I noticed something,
though. The 16MHz oscillator socket is a 14-pin socket, though only a
half-can oscillator is used, for clearance reasons. I noticed, though,
that pin 11 is connected to 8563 pin 2. Since I am using an oscillator
socket, though, only pins 1, 7, 8, and 14 have pins soldered to the board.
It looks like the 8563 is not getting a DCLK signal.
Would this be enough to kill the bus?
- Alex
**
Alex,
Sorry to hear that you still have the trouble. The following may be old
1. B_/INT not pulled low all the time. One of the board updates fixed a
polarity problem in the interrupt request output from the 8242.
2. On the SBC-188, use of the CVDU suppresses all serial output, unless
the video is reset to mode 7. The wiki has a tiny utility to do this; but
DOS must be running to use it. There is also a utility to return to
[color] video mode 3.
3. Each bus signal will need to be checked: /RD, /WR, /MREQ, /IORQ,
/M1, ... to make sure it is not stuck. Although, these mentioned are all
inputs to the CVDU board.
Make sure all the board updates, per the ConstructionNotes.txt have been
installed correctly. There are pix of the top and bottom of the modified
board with orange wires.
--John
Interesting. Wayne, could you add something similar to RomWBW?
I'm thinking that I should source a pair of 4464s, but I need to figure
out why my board is killing the bus, first. I haven't made any progress on
that front, yet.
Thanks!
- Alex
Post by John Coffman
Resurrecting an old thread ...
RE: Color VDU with 4416 DRAMs vs 4464 DRAMs
I just got my hands on some reasonably priced 4416's (16K x 4) DRAMs.
1. If the current SBC-188 BIOS is configured for 16K chips instead
of 64K, the BIOS only uses 16K of memory, so either size DRAM chip will
work. However, this requires re-compiling the initialization routine with
"DRAMSize" set to 16 instead of 64. "DRAMSize" is a "#define" in
"ega9a.h". This is suggested as an immediate workaround.
2. Dynamically determining the DRAM size is easy, and will be a
a. Set the DRAM size to 64K.
b. Write zero to address 0x0000.
c. Write non-zero to address 0x0100.
d. Check the value in address 0x0000. If it changed, you
have 16K DRAM chips; if not, you have 64K DRAM chips.
e. If you have the smaller chips, reset the DRAM size to 16K.
16K chips will support alpha mode 3 (16 colors) with 2 pages. Only 1
page is used as of now.
64K chips will be used in the future to support alpha mode 3 with 8
pages. I have yet to experiment with graphics mode, but this requires at
least 32K of memory; hence, the larger chips. With dynamic determination
of the chip size, it is possible to know whether the graphic mode will be
available.
--John
OK, I think I have the board set correctly. However, whenever I
install it to the ECB backplane, I don't get any output, anymore, from the
serial console on the N8VEM SBC V2 board. I do get a keyboard LED flash,
at power on, if I connect a PS/2 keyboard. I take that to be a good sign
that the keyboard controller is at least initializing.
I have tried installing the ColorVDU ROM, and also the standard ROM,
with the ColorVDU test programs added. Neither seems to help things.
I have checked my soldering, and I don't see any obvious shorts or
missing connectivity.
I did not perform any of the fixups that are listed in the
Construction Notes, as I was not planning to use the board with a SBC-188
board. Are there any that I should particularly do?
Thanks!
- Alex
P5 selects the high nibble of the device code; 0xE? is suggested;
i.e., jumper 7-8 only.
K1, K2, K3 select interrupts. AFAIK, none are used. No jumpers.
K4, K5 select H, V sync polarity; 1-2 is pos., 2-3 is neg.
This may take some experimentation to get right for your monitor. Start with both 1-2.
JP1 must be in place.
P32 is an external connector. Leave all pins open.
--John
All,
I must be completely blind, but I can't find the jumper reference for
the Color VDU board. I know JP1 needs to be set, but I'm not at all sure
about others.
Help?
Thanks!
- Alex
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-29 02:44:58 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 04/28/2013 05:49 PM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y0G71sdnu5bVos6d=VmD=YFFBuURm=q0nCqSmqC5zVzag-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">Thanks, Max. &nbsp;I indeed just did that. &nbsp;I now get a
cycling orange/green light (improper sync, most likely), on my
test monitor. &nbsp;So, that's good to see.</div>
</blockquote>
<br>
Very encouraging.<br>
<br>
Dan's original intent was CGA to VGA daughter-board output, all
monitor timing being determined by the third party daughter-board.<br>
<br>
If the VGA connector is used, then this board <u>requires</u> a
multi-sync monitor that supports EGA timing.&nbsp; MDA timing, and EGA
timing, are very similar; both are derived from a 16.257Mhz
oscillator.<br>
<br>
<blockquote
cite="mid:CAF-r0Y0G71sdnu5bVos6d=VmD=YFFBuURm=q0nCqSmqC5zVzag-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>I'll concentrate on applying the fixes. &nbsp;How do you all
suggest doing the leg-type fixes? &nbsp;Direct-soldering to an IC
leg, bent outside of the socket?</div>
</div>
</blockquote>
<br>
See photo of modified board top.<br>
<br>
With bent leg fixes, I have a lot of old wire-wrapping tools, so I
tend to use that approach.&nbsp; There is nothing wrong with soldering,
as long as you are careful to avoid static discharge.<br>
<br>
--John<br>
<br>
<br>
<br>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
J. Alexander Jacocks
2013-04-29 11:35:54 UTC
Permalink
Post by J. Alexander Jacocks
**
Thanks, Max. I indeed just did that. I now get a cycling orange/green
light (improper sync, most likely), on my test monitor. So, that's good to
see.
Very encouraging.
Dan's original intent was CGA to VGA daughter-board output, all monitor
timing being determined by the third party daughter-board.
If the VGA connector is used, then this board *requires* a multi-sync
monitor that supports EGA timing. MDA timing, and EGA timing, are very
similar; both are derived from a 16.257Mhz oscillator.
I'll concentrate on applying the fixes. How do you all suggest doing
the leg-type fixes? Direct-soldering to an IC leg, bent outside of the
socket?
See photo of modified board top.
With bent leg fixes, I have a lot of old wire-wrapping tools, so I tend to
use that approach. There is nothing wrong with soldering, as long as you
are careful to avoid static discharge.
John,

Thanks for the notes. I do, indeed, need to replace my testing CRT (a 17"
Dell Trinitron), with a monitor that syncs to a greater variety of
frequencies.

For testing this board, I will probably use my Commodore 1080, which can do
CGA/EGA. I need to make a cable, though, from the VDU's digital output
connector.

- Alex
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/n8vem?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
John Coffman
2013-04-29 17:47:53 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 04/29/2013 04:35 AM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y1=8e5niMsTWswyw8O8ksEZzHKWCTeZ9GMpJL9B-Q+WfA-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div style="">For testing this board, I will probably use my
Commodore 1080, which can do CGA/EGA. &nbsp;I need to make a cable,
though, from the VDU's digital output connector.</div>
</blockquote>
<br>
The VGA connector needs a monitor input impedance of 75 ohms.&nbsp; This
input impedance value is assumed by the D-A network resistors (390
&amp; 820 ohms).&nbsp; I think 75 ohms is the most common monitor input
impedance, but if you have brightness issues, the resistor network
values may need tweaking.<br>
<br>
VGA uses TTL level signals for Hsync &amp; Vsync.&nbsp; With the two
jumper blocks, K4 &amp; K5, polarity is easily changed, if
necessary.<br>
<br>
--John<br>
<br>
<br>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
John Coffman
2013-04-29 02:29:59 UTC
Permalink
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 04/28/2013 02:49 PM, J. Alexander Jacocks wrote:
<blockquote
cite="mid:CAF-r0Y3_UFDPOeWLx0R95059jS9GZekUfTjo=S13p+uGUyfsKg-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">I'm using my ColorVDU with the SBCv2 board, so the
SBC-188 fixes shouldn't be necessary.</div>
</blockquote>
<br>
None of the Mar-2013 corrections to the SBC-188 CPU board would be
applicable in this case.&nbsp; However, ...<br>
<br>
<br>
<blockquote
cite="mid:CAF-r0Y3_UFDPOeWLx0R95059jS9GZekUfTjo=S13p+uGUyfsKg-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">
<div style="">I have board revision 1.0-005, so I think I have
the most updated board currently available, so I don't think
that's the issue.</div>
</div>
</blockquote>
<br>
There are a number of corrections to the 1.0-005 ColorVDU board
which must be applied.&nbsp; They are detailed in the
ConstructionNotes.txt file and the accompanying photos.<br>
<br>
Corrections are made to both the top of the board and the bottom.&nbsp;
Luckily, only one trace needs to be cut.&nbsp; Note that a 14-pin socket
is added into the 20-pin spare DIP location.<br>
<br>
<br>
<blockquote
cite="mid:CAF-r0Y3_UFDPOeWLx0R95059jS9GZekUfTjo=S13p+uGUyfsKg-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">
<div style=""><br>
</div>
<div style="">I was checking all of my soldering (again!), and I
noticed something, though. &nbsp;The 16MHz oscillator socket is a
14-pin socket, though only a half-can oscillator is used, for
clearance reasons. &nbsp;I noticed, though, that pin 11 is
connected to 8563 pin 2. &nbsp;Since I am using an oscillator
socket, though, only pins 1, 7, 8, and 14 have pins soldered
to the board. &nbsp;It looks like the 8563 is not getting a DCLK
signal.</div>
</div>
</blockquote>
<br>
The board layout accommodates either a full-can or half-can
oscillator.&nbsp; In either case, pin 1 must be inserted into pin 1 on
the board.&nbsp; On the 14-pin footprint, pins 4,5,6,&amp;7 are GND, and
pins 8,9,10,&amp;11 are oscillator output.&nbsp; When using a full can
oscillator, just watch out for the clearance problem noted in the
photo.&nbsp; Use of an insulating strip is suggested for insurance.<br>
<br>
<blockquote
cite="mid:CAF-r0Y3_UFDPOeWLx0R95059jS9GZekUfTjo=S13p+uGUyfsKg-JsoAwUIsXosN+***@public.gmane.org"
type="cite">
<div dir="ltr">
<div style=""><br>
</div>
<div style="">Would this be enough to kill the bus?</div>
</div>
</blockquote>
<br>
If the keyboard interrupt is connected, you may have a problem:&nbsp; the
1.0-005 layout gets the keyboard-mouse interrupt polarity
backwards.&nbsp; This is one of the board updates.<br>
<br>
Without an updated 1.0-005 board, B_/INT asserted all the time might
be the problem.&nbsp; To test, disconnect the interrupt jumper K3
entirely.<br>
<br>
--John<br>
<br>
<br>
<br>
</body>
</html>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;N8VEM&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
To post to this group, send email to n8vem-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org<br />
Visit this group at <a href="http://groups.google.com/group/n8vem?hl=en">http://groups.google.com/group/n8vem?hl=en</a>.<br />
For more options, visit <a href="https://groups.google.com/groups/opt_out">https://groups.google.com/groups/opt_out</a>.<br />
&nbsp;<br />
&nbsp;<br />
Loading...