By using this site, you agree to our Privacy Policy and our Terms of Use. Close
darkknightkryta said:
HappySqurriel said:
KungKras said:
darkknightkryta said:
 

Machine code isn't all that hard to read :D.  Both consoles don't have a C compiler, everything is done through assembly.

NES tutorials: http://www.patater.com/nes-asm-tutorials

Genesis Start (Not necessarily a tutorial, but will give you a start for searching): http://www.gamedev.net/topic/575801-making-a-game-for-the-sega-genesis/

I was talking about the code that looks like a mish mash of ASCII symbols.

Reading hex numbers in memory registers is much more doable though :)

EDIT: Now that I think about it, I might have gotten my definition of machine code wrong. If the hex numbers in register thing is called machine code, what's that code that just looks like a clusterfuck of ASCII signs called?


I think you're thinking of a memory dump, but I can't be sure

Machine code is just a representation of assembly.  So for instance ADD  1 1 would represented as 110 for ADD 0001 for one in byte representation, so the full machine code would be 11000010001.  Now that's me simplifying it and assigning 110 for ADD.  It's a bit more complex, but each portion of the bit number represents something, so the first few digits would be your actual op, and the last 8 bits would be something, a memory address, direct numbers, registers, etc.  Higher the percision, so let's say a 64 bit processor vs 32 bit processor would let you have more complex ops and to represent bigger numbers.

I see. So machine code is the assembly commands when translated into binary numbers and stored in the registers? That's similar to how I remember it from digital technology class. Only, since we used a training processor with 8-bit registers, the command filled an entire register, and the adress came from the register after.



I LOVE ICELAND!