Tokyo Bus Guide Decompilation

Introduction

This project focuses on decompiling the Sega Dreamcast game Tokyo Bus Guide. It prioritizes achieving identical behavior between the original and decompiled code, rather than traditional methods targeting byte-level matching. Key objectives include functional equivalence, scalable decompilation methods, and community collaboration in Dreamcast reverse engineering.

To the best of the author's knowledge, this is the first public Dreamcast game decompilation project.

Approach

Unlike traditional byte-level matching, this project uses a custom SH4 object simulator and testing framework. This tool tests decompiled functions against their original counterparts, ensuring exact behavioral replication.

Project Status

This is an ongoing project, the decompilation process will be regularly updated. While under development, the project allows building the game using the available decompiled functions.

Current Achivements:

Rebuilding the game binary with decompiled functions alongside original code.
Custom logs from decompiled C files, written to the Dreamcast serial interface and on-screen debug text: watch video, view code.
CI workflows with matching builds, non-matching builds and unit tests checks.

How to Contribute

Contributions to this project are encouraged and welcomed! Your expertise in code, testing, or documentation can significantly advance this decompilation effort. Detailed contribution guidelines will be available shortly.

Requirements

Operating System: Linux Mint or similar Ubuntu-based distributions (additional steps may be required for other distributions).
Wine 32.
Dreamcast SDK (Sega Library) Ver.1.55J (Google is your friend)

Project Setup

Ensure your SDK is organized as follows.

„¥„Ÿ„Ÿ bin (From disc Vol.1 dc_sdk/bin)
„    „¥„Ÿ„Ÿ binadj.exe
„    „¤„Ÿ„Ÿ ...
„¥„Ÿ„Ÿ shc (From disc Vol.2)
„    „¥„Ÿ„Ÿ bin
„    „¥„Ÿ„Ÿ include
„    „¤„Ÿ„Ÿ lib
„¤„Ÿ„Ÿ shinobi (From disc Vol.2)
   „¥„Ÿ„Ÿ driver
   „¥„Ÿ„Ÿ include
   „¥„Ÿ„Ÿ lib
   „¤„Ÿ„Ÿ sample

The Hitachi compiler suite expects some environments variables to be set. Create a copy of set_kt.example.sh named set_kt.sh and update the DK_SDK environment variable with your SDK location.
Source your set_kt.sh script to make the environment variables available in the current shell:
```
$ source set_kt.sh
```

Build the binary using the provided build.sh script.

$ ./build.sh

(...)

LINKAGE EDITOR COMPLETED
ELF2BIN: ELF -> binary converter Ver. 1.04
Copyright (c) 1998, Hitachi, Ltd.  All rights reserved.
Module  address: 8c008000 - 8c0fde20
Convert address: 8c010000 - 8c0fde20  size: 000ede20 (974368)

================
Project built :)
================

A successful build will display "Project built :)".

Docker Container Development

Open run_container.sh with your favorite text editor and update the SDK_PATH variable with the absolute path location of the SDK Files mentioned in the Project Setup
Run run_container.sh. you should be inside a bash shell inside /app (your current folder)
```
$ ./run_container.sh
```
Source your set_kt.docker.sh script to make the environment variables available in the current shell:
```
$ source ./scripts/set_kt.docker.sh
```