Editing Diagnostic Serial Console (section)

== Diagnostic Error Analysis and Hardware Troubleshooting ==

=== Memory Configuration Detection Patterns ===

The diagnostic system provides precise SIMM slot detection through specialized response codes that accurately reflect physical memory installation. When testing partial SIMM configurations, the <code>*R</code> command returns specific patterns indicating slot population status. With 1MB SIMMs installed in slots 1 and 2 only, the system reports <code>0000FFFF000E</code>, while installation in slots 3 and 4 only produces <code>FFFF000000E</code>. These codes provide immediate verification of physical SIMM installation and can diagnose installation errors or socket problems.

Memory addressing behavior reveals precise hardware functionality when writing test patterns to address 0x00000000. With 1MB SIMMs in slots 1 and 2 only, writing the pattern <code>11223344</code> reads back <code>xxxx3344</code>, indicating that slots 1-2 correspond to the lower 16 bits of the 32-bit data bus. Moving the SIMMs to slots 3 and 4 results in reading back <code>1122xxxx</code>, confirming that slots 3-4 handle the upper 16 bits. This demonstrates that the diagnostic interface can access each SIMM slot independently and reveals the precise relationship between physical slot positions and data bus bit assignments.

=== Address Boundary and Wrapping Analysis ===

Diagnostic testing reveals specific address boundary behavior that differs from normal operational limits. The system consistently reports end address <code>1003FFFC</code> for 4MB configurations, where the prefix <code>10</code> indicates diagnostic metadata while <code>03FFFC</code> represents the actual end address at 4MB (0x400000 - 4 = 0x3FFFC). This confirms accurate memory size detection for installed configurations.

However, algorithmic memory tests (T0002, T0005, T0006) consistently fail at address <code>800000</code> (8MB boundary) even when testing smaller ranges such as 64KB (0xFFFF). This indicates that these diagnostic routines are hardcoded to test up to 8MB address space regardless of installed memory or specified test parameters. The external addressing test failure (error code 0005) occurs because the diagnostic attempts to access the 8MB boundary when only 4MB is physically installed, representing normal diagnostic behavior rather than hardware failure.

=== Hardware Failure Mode Identification ===

Specific hardware failures produce characteristic diagnostic patterns that enable precise component identification. Data line failures manifest as consistent bit patterns in memory read operations, such as data line D3 constantly toggling while the system is idle, indicating signal integrity problems including floating data lines, bad buffer/driver ICs, power supply noise, PCB trace issues, clock crosstalk, or defective SIMM output drivers.

When algorithmic memory tests write 0xFF patterns successfully but fail when writing 0x00 patterns, reading back values like <code>00080000</code> instead of <code>00000000</code>, this indicates a stuck bit failure where specific bits can be pulled high but cannot be driven low. The second byte stuck at 0x08 suggests bit 3 failure in that data path, potentially caused by a specific SIMM with failing memory cells, buffer IC problems, socket contact issues, or motherboard trace failures.

=== Response Code Interpretation ===

The console returns hexadecimal response codes that provide detailed diagnostic information:

{| class="wikitable" style="width:100%; text-align:left;"
|+ '''Diagnostic Response Codes and Meanings'''
|-
! Response Code !! Meaning !! Technical Interpretation
|-
| <code>004000000000</code> || 4MB memory detected || 00400 = 4,194,304 bytes, trailing zeros = diagnostic metadata
|-
| <code>0000FFFF000E</code> || Slots 1-2 populated || Bit pattern indicating SIMM presence in Bank A front positions
|-
| <code>FFFF000000E</code> || Slots 3-4 populated || Bit pattern indicating SIMM presence in Bank A rear positions
|-
| <code>000000800000*R</code> || 8MB boundary access error || Attempt to access unmapped 8MB address space during testing
|-
| <code>FFFFFFFF0005*R</code> || External addressing test failed || Error code 0005 indicates addressing capability beyond installed memory
|-
| '''0F000D''' || NMI button pressed during boot || Normal indication of interrupt button activation
|}

=== Systematic Diagnostic Procedures ===

Comprehensive hardware validation requires systematic testing approaches that isolate specific failure modes. Individual bank isolation testing involves removing all SIMMs from Bank B, booting with Bank A only using 4 matched SIMMs, running comprehensive memory test suites, and documenting failures with specific SIMM slot positions. Bank B testing requires moving known-good SIMMs to Bank B positions, using diagnostic software for Bank B specific testing, and cross-referencing failures with physical SIMM locations.

For suspected SIMM failures, systematic replacement involves testing each SIMM individually in a known-good slot position, swapping SIMMs between slots to determine if failures follow specific memory modules or remain at fixed memory addresses, and using multiple test patterns to verify intermittent failures. Socket and motherboard issues require testing with known-good SIMMs to isolate socket problems, visual inspection of SIMM socket contacts for corrosion or damage, and verification of power delivery to each socket position.