/explore
|
You are here 
|
danilafe.com | ||
| | | | |
multigesture.net
A multitouch and HCI research blog |
|
| | | | | ||
| | | | |
faizilham.github.io
It's been a while since I write emulator projects. While I do want to make more "serious" emulator like NES or GameBoy, I decided to do a warm up project by writing a Chip-8 emulator once more. Here are some interesting things I found and implemented during the development. |
|
| | | | | ||
| | | | |
jborza.com
CHIP-8 is one of the most popular target architectures for aspiring emulator writers. I'm planning to implement it in hardware, so I thought that writing a software emulator/interpreter would be enlightening. I was also looking for some practice before implementing CHIP-8 in hardware in Verilog :) CHIP-8 Virtual machine description: 64x32 pixel monochrome display 4K of 8-bit RAM 16 8-bit "variable" registers V0-VF I 16-bit address register Stack of 16-bit addresses for call/return 16-bit PC - program counter 8-bit delay timer (decremented at 60 Hz) until it reaches 0 8-bit sound timer (decremented at 60 Hz), beeps when it reaches 0 16- key keypad that sends scan codes 0x1-0xF Instruction set See https://en. |
|
| | | | | ||
| | | | |
patshaughnessy.net
[AI summary] The article discusses the process of learning to read x86 assembly language, focusing on how it can be a useful skill for understanding low-level operations of microprocessors. It outlines the challenges of reading assembly, especially in debugging scenarios, and provides an example of translating Ruby code into x86 assembly using Crystal. The article also explains the syntax and structure of x86 assembly, including register usage, instruction suffixes, and the differences between AT&T and Intel syntax. It highlights the complexity of x86 assembly due to its historical evolution and the need for understanding register sizes and operand notation. |
|
| | | |||
