little-things-gb - GitLite

KO | EN

gitlite — search

#csharp #git #python #kotlin #video #ai #pdf #mcp #claude #dotnet

little-things-gb

(★ 10)

Small test ROMs and experiments for Gameboy.

little-things-gb 최신버젼 다운로드

ZIP 다운로드

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일 경로 직접 입력

링크

예시

명령어 용어집

이 문서에서 사용된 명령어를 모아봤습니다. 낯선 명령어가 있다면 펼쳐서 확인해보세요.

🔍

`halt`

설명 보기 ▼

시스템을 중지합니다.
더 많은 정보: <https://manned.org/halt>.

halt

시스템 중지:

halt {{[-p|--poweroff]}}

시스템 전원 끄기 (`poweroff`와 동일):

halt --reboot

시스템 재부팅 (`reboot`와 동일):

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Small test ROMs and experiments for Gameboy made by nitro2k01. Inspired by [PinoBatch's repo](https://github.com/pinobatch/little-things-gb) with the same name and concept.

## Building
Prerequisite: some recent version of RGBDS. Under Linux and presumably macOS, just run `./m.sh`. No Makefile, sorry. Maybe one day. Under Windows it should not be too hard to make a `m.bat` file that executes the same commands as `./m.sh`.

## Download
If you are just looking for the ROMs, go to [releases](https://github.com/nitro2k01/little-things-gb/releases/).

# List of projects

## Whichboot.gb (2022)

Whichboot.gb is a research tool for identifying Gameboy consoles and emulators through software running on the machine/emulator. It is similar in concept to [Matt Currie's which.gb](https://github.com/mattcurrie/which.gb) but it's using different detection mechanisms and is geared toward detecting different aspects of the running machine than which.gb. Whereas which.gb is trying to detect which SoC revision the ROM is running on by triggering various hardware quirks, whichboot.gb is trying to detect which boot ROM was executed. It does this by detecting the CPU register values left by the boot ROM, as well as the timing of the boot process using `DIV` and `LY`, and the logo data left in VRAM.

The initial purpose of this tool was to provide a non-intrusive way of detecting any undumped boot ROMs that may exist in Gameboy clones. However, it also turned out to be a powerful tool for finding out interesting information about the design process and internal workings of various emulators. I have run whichboot.gb on a wide range of new and old emulators, and using just the methods described below, it can accurately detect many of the older emulators exactly.

Originally destined for little-things-gb, this project now has [its own repo](https://github.com/nitro2k01/whichboot.gb).

## Windesync-validate (2022)

![Windesync-validate running in BGB screenshot](https://raw.githubusercontent.com/nitro2k01/little-things-gb/main/windesync-validate/images/screenshot.png)

An emulator validation test ROM for a hardware quirk on pre-GBC Gameboys where activating the window, then turning it off on a later scanline inserts a glitch pixel and offsets the rest of the scanline, depending on the values of `SCX` and `WX`. Recently (re-)discovered because a graphical element in the game Star Trek 25th Anniversary was misaligned by one pixel in emulators. At the time of writing, the only emulators known to emulate this quirk are [BGB](https://bgb.bircd.org/) and [SameBoy](https://sameboy.github.io/).

## Double-halt-cancel (2022)

![Double-halt-cancel running in BGB screenshot](https://raw.githubusercontent.com/nitro2k01/little-things-gb/main/double-halt-cancel/images/bgb-dmg.png)

A test ROM that tests what happens if a program executes a double `halt` instruction with interrupts disabled, then changes the data at the location in question. It is conventionally assumed that executing a double `halt` will permanently lock up the CPU. What actually happens on hardware though, is that the CPU keep reading the second `halt` instruction over and over. If the CPU would theoretically read a different value all of a sudden, this code would be allowed to run instead. This could be done using a custom cartridge that can switch ROM banks automatically in the background. However, this test ROM uses VRAM inaccessibility to execute a `rst $38` instruction when VRAM becomes inaccessible and reads `$FF`.