saji/blog
1
0
Fork 0
Code Actions Activity

formatting
All checks were successful
Build Blog / Build (push) Successful in 6m44s
Details

Browse source
This commit is contained in:
saji 2025-05-03 22:43:41 -05:00
parent 7575c06bfa
commit 669e0ef96c
4 changed files with 63 additions and 63 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.prettierignore Normal file
View file

@ -0,0 +1 @@
_includes/

35
_includes/base16-prism.css
View file

@ -10,7 +10,7 @@ code[class*="language-"],
pre[class*="language-"] {
color: var(--color-fg); /* base05 */
background: var(--color-black);
font-family: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
font-family: Consolas, Monaco, "Andale Mono", "Ubuntu Mono", monospace;
font-size: 1em;
text-align: left;
white-space: pre;
@ -29,15 +29,19 @@ pre[class*="language-"] {
hyphens: none;
}
pre[class*="language-"]::-moz-selection, pre[class*="language-"] ::-moz-selection,
code[class*="language-"]::-moz-selection, code[class*="language-"] ::-moz-selection {
pre[class*="language-"]::-moz-selection,
pre[class*="language-"] ::-moz-selection,
code[class*="language-"]::-moz-selection,
code[class*="language-"] ::-moz-selection {
color: inherit;
text-shadow: none;
background: var(--color-black-bright); /* base02 */
}
pre[class*="language-"]::selection, pre[class*="language-"] ::selection,
code[class*="language-"]::selection, code[class*="language-"] ::selection {
pre[class*="language-"]::selection,
pre[class*="language-"] ::selection,
code[class*="language-"]::selection,
code[class*="language-"] ::selection {
color: inherit;
text-shadow: none;
background: var(--color-black-bright); /* base02 */
@ -53,44 +57,44 @@ code[class*="language-"]::selection, code[class*="language-"] ::selection {
/* Code blocks */
pre[class*="language-"] {
padding: 1em;
margin: .5em 0;
margin: 0.5em 0;
overflow: auto;
}
:not(pre) > code[class*="language-"],
pre[class*="language-"] {
background: #{{base00-hex}}; /* base00 */
background: var(--color-bg); /* base00 */
}
/* Inline code */
:not(pre) > code[class*="language-"] {
padding: .1em;
border-radius: .3em;
padding: 0.1em;
border-radius: 0.3em;
white-space: normal;
}
.token.comment,
.token.prolog,
.token.cdata {
color: #{{base03-hex}}; /* base03 */
color: var(--color-white); /* base03 */
}
.token.entity,
.language-css .token.string,
.style .token.string {
color: #{{base04-hex}}; /* base04 */
background: #{{base01-hex}}; /* base01 */
color: var(--color-white-bright); /* base04 */
background: var(--color-black); /* base01 */
}
.token.punctuation {
color: #{{base05-hex}}; /* base05 */
color: var(--color-fg); /* base05 */
}
.token.variable,
.token.tag,
.token.operator,
.token.deleted {
color: var(--color-blue); /* base08 */
color: var(--color-blue-bright); /* base08 */
}
.token.property,
@ -149,6 +153,5 @@ pre[class*="language-"] {
}
.namespace {
opacity: .7;
opacity: 0.7;
}

4
content/blog/wy-60-repairs/wy-60-repairs.md
View file

@ -42,7 +42,6 @@ At this point we needed to test them out. And this is where I realized that,
despite picking the unit with the least yellowing, mine didn't work.
I saw the cursor, and a line for the status bar, but no characters in sight:
Thankfully, the scuffed one worked, so I was able to confirm that
I could interact with it. However, the geometry was bad and there seemed
to be some shaking in the text, meaning a power supply wasn't being stable
@ -81,7 +80,6 @@ alongside the character itself, or in a separate "Attribute RAM", which is read
![Functional block diagram, showing the attribute and character data pipelines](bus_architecture.png)
With my new test setup, I was able to find and probe pins from the underside of the board.
One of the challenges here is that there are multiple busses, each with potentially multiple masters.
Not only do you need to probe a data line, you also need to have a probe for whatever makes the chip
@ -98,13 +96,11 @@ Uh, guys?
![Image of more cold joints on a different chip](cold_joints_2.jpg)
It can't possibly be this, right? U17 and U15 are part of character storage,
and I did see the font RAM output non-zero, meaning it had to have rendered
something! I quickly cleaned up the joints and powered it on. I couldn't see it
at first, but it worked. Thankfully I found this before starting to replace other chips.
# Takeaway
This highlights the two styles of troubleshooting: