Differences

This shows you the differences between two versions of the page.

--- spo600:6502_math_and_strings_lab [2024/01/25 08:05] – [Write it!] chris
+++ spo600:6502_math_and_strings_lab [2024/09/24 15:30] (current) – chris
@@ Line 1: / Line 1: @@
-======  6502 Math and Strings Lab  ======
+#REDIRECT [[6502 Program Lab]]
-In this lab, you will write code with arithmetic/math and strings in [[6502]] assembly language, including text output, graphical output, and keyboard input, in preparation for learning more complex x86_64 and AArch64 assembly language.
-=====  Resources  =====
-  *  [[6502]]
-  *  [[6502 Emulator]]
-  *  [[6502 Math]]
-  *  [[6502 Jumps, Branches, and Procedures]]
-  *  [[6502 Emulator Example Code]] - Specifically:
-    *  [[6502_Emulator_Example_Code#Place_a_Graphic_on_the_Screen|Place a Graphic on the Screen]] - for an example of defining a graphic using DCB, and copying a graphic to the screen
-    *  [[6502_Emulator_Example_Code#Etch-a-Sketchtm_Style_Drawing|Etch-a-Sketch Style Drawing]] - for an example of converting (ROW,COL) co-ordinates to a screen address, and reading the keyboard
-  *  [[https://github.com/ctyler/6502js-code/|6502js-code]] repo on GitHub - Specifically:
-    *  Wordle-like example (wordle-6502)
-  *  Opcode/Instruction References
-    *  [[http://www.6502.org/tutorials/6502opcodes.html|6502 Opcodes with Register Definitions]]
-    *  [[https://www.masswerk.at/6502/6502_instruction_set.html|6502 Opcodes with Detailed Operation Information]]
-=====  Techniques  =====
-  *  Bouncing Object
-    *  To bounce an object around the screen:
-      * Use two variables for deltaX and deltaY values -- the amount that the object will move in each direction for each update. Add these values to the X,Y position of the object on the screen each time you update the position.
-      * These values can simply be -1 or +1 if the object is going to bounce at 45-degree angles.
-      * These values will need to include a fractional component for angles other than 45 degrees. This can be handled by using two bytes for each element of the X,Y position and for the deltaX and deltaY values, where one byte represents the integer portion and one byte represents the fractional portion (fixed-point representation).
-    *  Detect when the object has collided with the edge of the screen or other objects, and reverse the sign of the deltaX or deltaY value (or both). For example, when bouncing off the top or bottom of the display, set ''deltaY = -deltaY''
-  *  Keyboard
-    *  Access the keyboard using the CHRIN [[6502_Emulator#ROM_Routines|ROM routine]].
-  *  Random number generator
-    *  A random byte is available at memory location $FE.
-  *  Drawing a Line
-    *  To draw a line between two arbitrary points (X<sub>1</sub>,Y<sub>1</sub>)(X<sub>2</sub>,Y<sub>2</sub>) where X<sub>2</sub>-X<sub>1</sub> > Y<sub>2</sub>-Y<sub>1</sub> and all coordinates are positive, calculate the rise/run, then set Y=Y<sub>1</sub> and iterate for X=X<sub>1</sub>>X<sub>2</sub> incrementing Y by the rise/run each step.
-    *  Do something similar with run/rise where X<sub>2</sub>-X<sub>1</sub> < Y<sub>2</sub>-Y<sub>1</sub>
-    *  Suggestion: Use fixed-point math for the rise/run (aka deltaY) value.
-=====  Lab 2  =====
-====  Decide What to Write  ====
-For this lab, write a program that meets these criteria:
-  -  Your program must work in the [[6502 Emulator]]
-  -  You must output to the character screen as well as the graphics (bitmapped) screen.
-  -  You must accept user input from the keyboard in some form.
-  -  You must use some arithmetic/math instructions (to add, subtract, do bitwise operations, or rotate/shift)
-For example, you could write a simple game:
-  *  [[https://en.wikipedia.org/wiki/Pong|Pong]]
-  *  [[https://en.wikipedia.org/wiki/Breakout_(video_game)|Breakout]]
-  *  [[https://en.wikipedia.org/wiki/Mastermind_(board_game)|Mastermind]]
-  *  A drawing program
-  *  A maze
-  *  A number guessing game (try to guess a random number in the shortest number of tries, getting feedback of "too high" or "too low" for each wrong guess)
-  *  Or any other type of game...
-Or a calculator/converter:
-  *  An adding or subtracting calculator
-  *  A decimal-to-binary or hexidecimal-to-decimal converter
-  *  A inches-and-feet to centimeter converter
-  *  A [[https://en.wikipedia.org/wiki/Electronic_color_code|resistor colour band]] calculator
-  *  A program to draw bar or line graphs based on user input
-  *  Or any other type of calculator or converter...
-**Or anything else that meets the criteria above**
-You can interact with the user using either display. For example:
-  *  The main interaction could be on the graphical display, and instructions could be printed on the text display (which keys to use to move, for example); or
-  *  The main interaction could be on the text display, and an appropriate pattern could be shown on the bitmap display (for example, a version of Wordle could display the words on the text display and the scoring of the guesses on the graphical display), or a calculator could use the text display for input and show a binary representation or a colour code on the graphical display (such as green for positive numbers, yellow for negative numbers, red for bad input).
-**Tip:** Keep it simple! Assembly language is hard. Start simple, you can always add features later.
-====  Write it!  ====
-Write the code for your selected program in the [[6502 Emulator]].
-It can be helpful and fun to write this code with one or two other people in a live session. Acknowledge each person's input, and add your own customizations or tweaks.
-** Acknowledge Other's Code ** - Feel free to incorporate other people's code into your program __with their permission__, but you **must** __acknowledge the source of any incorporated code__ (include a link to the source(s)), identify __how you attained permission__ to use the code (for example, if the code is distributed under an open source license, show which license applies) and __clearly identify which parts of the code you wrote__ (recommendation: colour-code your portion in the blog post).
-** You must write __at least 75% of the code__ in this lab. ** Don't take an existing program and just make minor changes to messages or colours.
-====  Blog it  ====
-Write up your adventures in your blog. Remember to include the source code, some narrative about how it went, perhaps a screenshot of the program running, a reflection on the experience, and some ideas for further enhancement of the program.
-Ensure that your program works and is free from major bugs. Document any limitations or remaining minor bugs.
-Make sure that others (including your prof!) can run you code by pasting it into the [[6502 Emulator|emulator]] or loading it from a file (e.g., public git repository or downloadable file).
-Remember to follow the [[Blog Guidelines]] as you write.
-====  Examples  ====
-For some examples of games and demos, take a look at the http://txt3.de/ website - which uses an earlier version of the 6502 emulator. The "Open Project" control on that page provides access to some interesting and inspiring code. You can copy-and-paste any of those examples into the SPO600 [[6502 Emulator]]. However, check for permission before borrowing any code from that site (or any other source) and incorporating it into your code.