Difference between revisions of "6502 Assembly Language Lab (Old Version)"

From CDOT Wiki
Jump to: navigation, search
Line 5: Line 5:
 
* [[6502 Emulator]]
 
* [[6502 Emulator]]
 
* [[6502 Emulator Example Code]]
 
* [[6502 Emulator Example Code]]
 +
* 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]
  
 
== Lab 1 ==
 
== Lab 1 ==
Line 10: Line 13:
 
=== Setup ===
 
=== Setup ===
 
1. Organize a group of 4-6 students around one of the monitor/whiteboard groups in the classroom. Arrange the furniture so that everyone has a comfortable view of the display.
 
1. Organize a group of 4-6 students around one of the monitor/whiteboard groups in the classroom. Arrange the furniture so that everyone has a comfortable view of the display.
 +
 
2. Gather these supplies:
 
2. Gather these supplies:
 
* HDMI cable
 
* HDMI cable
 
* Whiteboard markers
 
* Whiteboard markers
3. Select one person to be the "Driver". That person should connect a device (laptop, table) to the HDMI display and open the [[6502 Emulator]] at [http://6502.cdot.systems] as well as this page.
+
 
 +
3. Select one person to be the "Driver", who will type/operate the computer for the group. That person should connect a device (laptop, table) to the HDMI display and open the [[6502 Emulator]] at [http://6502.cdot.systems] as well as this page.
 +
 
 +
4. Decide how group results will be shared between the members of the group. (Suggestion: consider using a git repository).
  
 
{{Admon/important|Save Your Work|The emulator '''does not''' save your work. Remember to periodically save it to a file (copy-and-paste the code).}}
 
{{Admon/important|Save Your Work|The emulator '''does not''' save your work. Remember to periodically save it to a file (copy-and-paste the code).}}
  
 
=== Bitmap Code ===
 
=== Bitmap Code ===
# Paste this code into the emulator:
+
4. Paste this code into the emulator:
 
+
 
  lda #$00 ; set a pointer at $40 to point to $0200
 
  lda #$00 ; set a pointer at $40 to point to $0200
 
  sta $40
 
  sta $40
Line 38: Line 45:
 
  cpx #$06 ; compare with 6
 
  cpx #$06 ; compare with 6
 
  bne loop ; continue until done all pages
 
  bne loop ; continue until done all pages
 +
 +
 +
5. 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 everyone in your group understands how it works.
  
4. 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 everyone in your group understands how it works.
+
6. Add this instruction after the <code>loop:</code> label and before the <code>sta ($40),y</code> instruction:
5. Add this instruction after the <code>loop:</code> label and before the <code>sta ($40),y</code> instruction:
 
 
   tya
 
   tya
6. What visual effect does this cause, and how many colours are on the screen? Why?
+
 
7. Add this instruction after the <code>tya</code>:
+
7. What visual effect does this cause, and how many colours are on the screen? Why?
 +
 
 +
8. Add this instruction after the <code>tya</code>:
 
   lsr
 
   lsr
8. What visual effect does this cause, and how many colours are on the screen? Why?
+
 
9. 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.
+
9. What visual effect does this cause, and how many colours are on the screen? Why?
10. Repeat the tests using <code>asl</code> instructions instead of <code>lsr</code> instructions. Describe and explain the effect in each case.
+
 
11. Remove the <code>tya</code> and all <code>asl</code> and <code>lsr</code> instructions.
+
10. 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.
12. Test with one to five <code>iny</code> instructions. Describe and explain the effect in each case. '''Note:''' ensure that the Speed slider is on its lowest setting (left) for these experiments.
+
 
 +
11. Repeat the tests using <code>asl</code> instructions instead of <code>lsr</code> instructions. Describe and explain the effect in each case.
 +
 
 +
12. Remove the <code>tya</code> and all <code>asl</code> and <code>lsr</code> instructions.
 +
 
 +
13. The original code includes one <code>iny</code> instruction. Test with one to five consecutive <code>iny</code> instructions. Describe and explain the effect in each case. '''Note:''' ensure that the Speed slider is on its lowest setting (left) for these experiments.
  
 
=== Writing Code, Part 1 ===
 
=== Writing Code, Part 1 ===
Write code to draw a green line across the top of the bitmap screen and a blue line across the bottom.
+
14. Write code to draw a green line across the top of the bitmap screen and a blue line across the bottom.
  
 
=== Writing Code, Part 2 ===
 
=== Writing Code, Part 2 ===
Write code to draw a yellow line down the left side of the screen and a purple line down the right side.
+
15. Write code to draw a yellow line down the left side of the screen and a purple line down the right side.
 +
 
 +
 
  
 
== Write-Up ==
 
== Write-Up ==
 
Post an entry on your blog describing your experiments in this lab. Include:
 
Post an entry on your blog describing your experiments in this lab. Include:
1. An introduction, so that someone who happens across your blog will understand the context of what you're writing about.
+
# An introduction, so that someone who happens across your blog will understand the context of what you're writing about.
2. The results from the ''Bitmap Code'' portion of the lab, describing what happened in each case and the reasons for it.
+
# The results from the ''Bitmap Code'' portion of the lab, describing what happened in each case and the reasons for it.
3. The results from the two ''Writing Code'' portions of the lab, including the code, a description of how the code works, and the results produced.
+
# The results from the two ''Writing Code'' portions of the lab, including the code, a description of how the code works, and the results produced.
4. Your experiences with this lab -- your impressions of the Assembly Language, what you learned, and your reflections of the process.
+
# Your experiences with this lab -- your impressions of the Assembly Language, what you learned, and your reflections of the process.
 +
 
 +
Remember to follow the [[Blog Guidelines]] as you write.

Revision as of 11:18, 13 January 2020

Lab icon.png
Purpose of this Lab
In this lab, you will learn some of the basics of 6502 assembly language, in preparation for learning more complex x86_64 and AArch64 assembly language.

Resources

Lab 1

Setup

1. Organize a group of 4-6 students around one of the monitor/whiteboard groups in the classroom. Arrange the furniture so that everyone has a comfortable view of the display.

2. Gather these supplies:

  • HDMI cable
  • Whiteboard markers

3. Select one person to be the "Driver", who will type/operate the computer for the group. That person should connect a device (laptop, table) to the HDMI display and open the 6502 Emulator at [1] as well as this page.

4. Decide how group results will be shared between the members of the group. (Suggestion: consider using a git repository).

Important.png
Save Your Work
The emulator does not save your work. Remember to periodically save it to a file (copy-and-paste the code).

Bitmap Code

4. Paste this code into the emulator:

	lda #$00	; set a pointer at $40 to point to $0200
	sta $40
	lda #$02
	sta $41

	lda #$07	; colour

	ldy #$00	; set index to 0

loop:	sta ($40),y	; set pixel

	iny		; increment index
	bne loop	; continue until done the page

	inc $41		; increment the page
	ldx $41		; get the page
	cpx #$06	; compare with 6
	bne loop	; continue until done all pages

5. 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 everyone in your group understands how it works.

6. Add this instruction after the loop: label and before the sta ($40),y instruction:

 tya

7. What visual effect does this cause, and how many colours are on the screen? Why?

8. Add this instruction after the tya:

 lsr

9. What visual effect does this cause, and how many colours are on the screen? Why?

10. Repeat the above tests with two, three, four, and five lsr instructions in a row. Describe and explain the effect in each case.

11. Repeat the tests using asl instructions instead of lsr instructions. Describe and explain the effect in each case.

12. Remove the tya and all asl and lsr instructions.

13. The original code includes one iny instruction. Test with one to five consecutive iny instructions. Describe and explain the effect in each case. Note: ensure that the Speed slider is on its lowest setting (left) for these experiments.

Writing Code, Part 1

14. Write code to draw a green line across the top of the bitmap screen and a blue line across the bottom.

Writing Code, Part 2

15. Write code to draw a yellow line down the left side of the screen and a purple line down the right side.


Write-Up

Post an entry on your blog describing your experiments in this lab. Include:

  1. An introduction, so that someone who happens across your blog will understand the context of what you're writing about.
  2. The results from the Bitmap Code portion of the lab, describing what happened in each case and the reasons for it.
  3. The results from the two Writing Code portions of the lab, including the code, a description of how the code works, and the results produced.
  4. Your experiences with this lab -- your impressions of the Assembly Language, what you learned, and your reflections of the process.

Remember to follow the Blog Guidelines as you write.