Skip to content

PokéBridge v0.4.3 — Joybus debug screen

Choose a tag to compare

View all tags
@logdog2325 logdog2325 released this 27 May 02:23
· 9 commits to main since this release
v0.4.3
e33a047

Diagnostic-only release in response to ongoing link-cable testing where multiple GBAs sit on the GAME BOY splash without being detected.

Added: Joybus debug screen

Hold the Z trigger while selecting "Read GBA cart via link cable" from the main menu. Instead of the normal flow you'll get a live SI debug screen that prints the raw SI_GetTypeAsync response for all 4 controller ports, refreshed every frame.

What the values mean:

  • 0x00000000 — no device on this port, silent bus
  • 0x80 or bit 8 set — device responding but BIOS not ready (retry)
  • bit 0x40000 set — GBA detected!
  • 0x09000000 etc — GameCube controller

Plug your GBA in (no cart, powered on, official DOL-011 cable) and watch the values. If all 4 ports stay 0x00000000, the SI bus isn't seeing the cable at all. If a port toggles 0x80 / bit 8, the GBA is on the bus but its BIOS isn't reporting ready. Either way, the readings tell us exactly where to look.

Clarification on GBA splash behavior

Earlier release notes claimed the GBA should transition from the GAME BOY splash to a gradient/swirl multiboot wait screen — this was wrong. The GAME BOY splash IS the multiboot wait state for most BIOS revisions; the gradient/swirl is the loading screen during multiboot transfer (after packets have already arrived).

So "GBA sitting on GAME BOY" is the correct state to start the dump from. The bug PokéBridge is hitting is upstream of multiboot — we're not detecting that a GBA is on the bus at all.

Files

pokebridge-v0.4.3-release.dol — drop into sd:/apps/pokebridge/boot.dol.

No other changes from v0.4.2. All Gen 3 / XD / Colosseum read/edit/write paths unchanged.

Assets 3
Loading