Durango POST-Code reader via RasPi Pico

This software flashed to the Raspberry Pi Pico allows for monitoring of POST codes, which is useful for fault diagnosis on the hardware.

• Durango POST-Code reader via RasPi Pico
  • Supported consoles
  • Technical infos:
  • Usage
    • How to interact ?
  • Videos / Tutorials
  • Connection diagram
    • Optional: 0.91" OLED Display (SSD1306)
  • Screenshots
  • Develop
    • VS Code
    • Zed Editor

Supported consoles

Via FACET connector

• ✅ Xbox One PHAT
• ✅ Xbox One S
• ✅ Xbox One X

Via AARDVARK connector

• ✅ Xbox Series S
• ✅ Xbox Series X

Technical infos:

• POST bus on Xbox One - Wiki page

• List of error codes

Usage

• Download latest release
• Flash the firmware onto the Pi Pico (Pi Pico: durango_post_monitor.uf2, Pi Pico 2: *_pico2.uf2)
  • Disconnect Pi Pico from your PC
  • Hold the BOOTSEL button
  • Plug in Pi Pico to the PC again
  • Release the BOOTSEL button
  • A removable storage device should appear in your file explorer
  • Drag the extracted *.uf2 file onto the Removable storage medium
  • The removable storage should automatically disappear
  • You are ready to go!

• Listen on the exposed USB Serial interface, Baudrate: 115200 via Serial monitor software
  • XboxPostcodeMonitor is recommended
    • Has errorcode auto-updating from https://errors.xboxresearch.com
    • Multi-console compatibility
  • PuTTY or any other generic serial monitor software
    • PuTTy: Check this Link
    • Tip: Make use of Saving a session configuration, no need to re-type Serial-port and baudrate each time!
    • Downside: No multi-console functionality, no errorcode updating

How to interact ?

Check Screenshots to see how the sofware output looks.

Generally:

• On Startup, it directly goes into POST monitoring mode.
• If you hit "CTRL+C" you will be brought into the REPL-menu.
• Here you can set various options
• Check out the "help" command.

Jump to the Connection diagram

Videos / Tutorials

Check out the videos from @craftbenmine

and @ACE Console Repairs

Connection diagram

Pi Pico -> FACET / AARDVARK

• SDA: Pi Pico Pin 1 (GP0) -> FACET Pin 26 (AARDVARK Pin 3 on Series S/X)
• SCL: Pi Pico Pin 2 (GP1) -> FACET Pin 25 (AARDVARK Pin 1 on Series S/X)
• GND -> GND

Thx to @ACE-AU for the new diagram

ESP32 (env esp32) -> FACET / AARDVARK

• SDA: ESP32 GPIO21 -> FACET Pin 26 (AARDVARK Pin 3 on Series S/X)
• SCL: ESP32 GPIO22 -> FACET Pin 25 (AARDVARK Pin 1 on Series S/X)
• GND -> GND

ESP32-S3 (env esp32s3) -> FACET / AARDVARK

• SDA: ESP32-S3 GPIO8 -> FACET Pin 26 (AARDVARK Pin 3 on Series S/X)
• SCL: ESP32-S3 GPIO9 -> FACET Pin 25 (AARDVARK Pin 1 on Series S/X)
• GND -> GND

Teensy 4.0 / 4.1 (envs teensy40 / teensy41) -> FACET / AARDVARK

• SDA: Teensy Pin 18 (Wire, fixed in hardware) -> FACET Pin 26 (AARDVARK Pin 3 on Series S/X)
• SCL: Teensy Pin 19 (Wire, fixed in hardware) -> FACET Pin 25 (AARDVARK Pin 1 on Series S/X)
• GND -> GND

Optional: 0.91" OLED Display (SSD1306)

Model: SSD1306 0.91" 128x32 pixels, monochrome

SSD 1306 module photo

Pi Pico:

• Pi Pico 3V3 -> Display VCC
• SDA: Pi Pico Pin 9 (GP6) -> Display Pin SDA
• SCL: Pi Pico Pin 10 (GP7) -> Display Pin SCL
• GND -> GND

ESP32:

• ESP32 3V3 -> Display VCC
• SDA: ESP32 GPIO18 -> Display Pin SDA
• SCL: ESP32 GPIO19 -> Display Pin SCL
• GND -> GND

ESP32-S3:

• ESP32-S3 3V3 -> Display VCC
• SDA: ESP32-S3 GPIO4 -> Display Pin SDA
• SCL: ESP32-S3 GPIO5 -> Display Pin SCL
• GND -> GND

Teensy 4.0 / 4.1:

• Teensy 3V3 -> Display VCC
• SDA: Teensy Pin 17 (Wire1, fixed in hardware) -> Display Pin SDA
• SCL: Teensy Pin 16 (Wire1, fixed in hardware) -> Display Pin SCL
• GND -> GND

NOTE: This image is showing firmware v0.2.3 - starting with v0.3.0 POST code names are not shown on display anymore, see note in Usage.

Screenshots

This is showing the output of firmware v0.2.0.

NOTE: This screenshot is showing firmware v0.2.3 - starting with v0.3.0 POST code names are not shown via serial anymore, see note in Usage.

Develop

VS Code

• Use VS Code as your IDE / Code Editor
• Install the extension PlatformIO
• Edit the code
• Change to the PlatformIO-tab in VS Code and choose Upload and Monitor to compile and upload the code

Zed Editor

• Use Zed as your IDE / Code Editor
• Install PlatformIO Core (CLI)
• Generate a compilation database so clangd can resolve includes: pio run -e pico -t compiledb
• Add a .zed/settings.json pointing clangd at the ARM toolchain so it picks up the cross-compiler's built-in headers:

  {
    "lsp": {
      "clangd": {
        "binary": {
          "arguments": [
            "--query-driver=<path-to-.platformio>/packages/toolchain-rp2040-earlephilhower/bin/*"
          ]
        }
      }
    }
  }
  

• Edit the code
• Compile and upload with pio run -e pico -t upload, monitor with pio device monitor -b 115200
• Re-run the compiledb command whenever platformio.ini deps/envs change, since the database goes stale otherwise