1,885
edits
Changes
→Experiments (Optional, Recommended)
* [[6502]] Wiki Page
* [[6502 Emulator]]
* [[Assembler Basics]]
* [[6502 Emulator Example Code]]
* Opcode/Instruction References
** On this Wiki*** [[6502 Instructions - Introduction]]*** [[6502 Addressing Modes]]** External*** [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]* [https://docs.google.com/spreadsheets/d/1a1-ZZ1opY8xcuUHNxj3YW75dxOPynSuP2-QGSvZGzYY/edit?usp=sharing Spreadsheet of bitmmapped bitmapped display memory locations]
== Lab 2 ==
1. Open the [[6502 Emulator]] at http://6502.cdot.systems in another tab or window, keeping this lab open.
{{Admon/important|Save Your Work|The emulator '''does not''' save your work automatically. Remember to periodically save it to a file (copy-and-paste the code or use the <code>Save</code> buttonto create local files). Recommendation: save your files to a directory, and use [https://git-scm.com/ git] to manage that directory.}}
=== Bitmap Code ===
2. The following code fills the emulator's bitmapped display with the colour yellow. Paste this code into the emulator:
lda #$00 ; set a pointer at in memory location $40 to point to $0200 sta $40 ; ... low byte ($00) goes in address $40 lda #$02 sta $41 ; ... high byte ($02) goes into address $41
lda #$07 ; colour number
ldy #$00 ; set index to 0
loop: sta ($40),y ; set pixel colour at the address (pointer)+Y
iny ; increment index
bne loop ; continue until done the page(256 pixels)
inc $41 ; increment the page
3. Test the code by pressing the Assemble button, then the Run button. If the there are any errors assembling (compiling) the code, they will appear in the message area at the bottom of the page. Make sure the code is running correctly and that you understands how it works. Don't be afraid to experiment!
=== Calculating Performance ===
4. Calculate how long it takes for the code to execute, assuming a 1 MHz clock speed(Watch [https://web.microsoftstream.com/video/ed7aedf1-fe6f-4b72-bbf1-c9b4e6e80af9 this video] if you would like a refresher on how to do this). Also calculate the total memory usage for the program plus any pointers or variables.
5. Consider ways to decrease the time taken to fill the screen with a solid colour. Calculate the execution time of the fastest version of this program that you can create.Challenge: the fastest version of this program is more than twice as fast as the original version shown above!
=== Modifying the Code ===
# Add this instruction after the <code>loop:</code> label and before the <code>sta ($40),y</code> instruction: <code>tya</code>
# What visual effect does this cause, and how many colours are on the screen? Why?
# Add this instruction after the <code>tya</code>: <code>lsalsr</code>
# What visual effect does this cause, and how many colours are on the screen? Why?
# Repeat the above tests with two, three, four, and five <code>lsr</code> instructions in a row. Describe and explain the effect in each case.
=== Challenges (Optional, Recommended) ===
# Set all of the display pixels to the same colour, except for the middle four pixels, which will be drawn in another colour.
# Write a program which draws lines at around the top and bottom edge of the display:
#* A red line across the top
#* A green line across the bottom
#* A blue line across the right side.
#* A purple line across the left size.
=== Write-Up ===
Post an entry on your blog describing your experiments in this lab. Follow the [[Blog Guidelines]]. Include code as text (and not screenshots), but feel free to include screenshots of the bitmapped display.
# The results of the Optional sections, if you performed them, and your explaination for each observed result.
# Your experiences with this lab -- your impressions of Assembly Language, what you learned, and your reflections on the process.
Remember that labs are marked on a scale of 0-3:
* 0 - Lab not completed, or significant errors.
* 1 - Very basic completion, or some small errors.
* 2 - Satisfactory completion of the lab.
* 3 - Lab completed with additional experiments, investigation, research, or explanation. For example, you could do some of the optional sections in this lab, and include those in your blog writeup -- or you could create your own experiments.
Remember to follow the [[Blog Guidelines]] as you write.
