MAC/65 Assembler Editor and Atari 8-bit Machine Language Programming - Part 9.2
ฝัง
- เผยแพร่เมื่อ 18 ก.ย. 2024
- The 12th in a series of videos in programming in Assembly Language for the Atari 8-bit computers using the MAC/65 Assembler Editor cartridge.
This video covers:
I complete the last major portion of coding logic for checking a joystick and moving a character around on the screen in assembly language. I introduce four new instructions and demonstrate how to code nested IF-THEN statements in Assembly. I also explain a potential memory issue that can happen during assembly on a 48K machine with MAC/65.
Unfortunately, I also make a typo 6 1/2 minutes in that leads to a 30 minute debugging session in DDT. Not totally a bad thing because I get to show how to debug in MAC/65 DDT by setting single and multiple breakpoints in DDT and how to work them.
Code for my videos are at my GitHub at GitHub.com/Davi.... Expect a couple days lag for each videos code to be uploaded since they will be more heavily commented.
Atari Books referenced in this video and where you can download them:
MAC/65 and DDT Manual:
www.atarimania...
Mapping the Atari by Ian Chadwick:
www.atarimania...
Compute's Machine Language for Beginners by Richard Mansfield:
www.atarimania...
Compute's Second Book of Machine Language by Richard Mansfield:
www.atarimania...
Atari Roots by Mark Andrews:
www.atarimania...
SAMS Programmer's Reference Guide for the Atari 400/800 Computers:
www.atarimania...
Your Atari Computer by Poole, McNiff, and Cook:
www.atarimania...
Tom Hudson's Machine Language Boot Camp Series Analog Magazine (starting in Issue 13):
archive.org/de...
OK the good news is I finish up the coding logic to move a character around on the screen with a joystick in assembly code. I also show four new instructions and how to do nested IF-THEN logic in assembly. The bad news (sort of) is that I make a typing mistake in the first 6 1/2 minutes that leads to a 30 minute DDT debugging session at the end. Not that is totally a bad thing because I show in this video more real life examples of debugging assembly code including how to set breakpoints inside of DDT and how to use them, including setting a single breakpoint and then setting multiple breakpoints.
It's just super annoying because my mistake is something I look at right in front of my face 15 seconds after I make it and MULTIPLE times after that and never see it. And when I finally DO see it, I still can't seem to get it typed in right. Very embarrassing as well as annoying but welcome to real life. :)
The text on the new monitor looks pretty sharp. Looking forward to the next video!
I'm really enjoying this series. Glad to see I'm not the only one that makes mistakes like that! I usually sleep on them, and when I come back I spot the mistake almost instantly.
@@nickfolino8228 That happens a lot for me too! In the morning the brain is clear! In this case, I actually had already set up an intentional mistake to show DDT breakpoints and then didn't even have to use it because of the real mistake! LoL
Write out 100 times 'I must press enter after editing'
Right? Except even then I'd probably forget to hit Enter on 50 of them! 😊
8 bit is better than 1 bit 😂 Imagine you have to use 8 instruction to build one byte.