User Tools

Site Tools


spo600:6502_program_lab

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
spo600:6502_program_lab [2024/09/24 19:31] – [Decide What to Write] chrisspo600:6502_program_lab [2025/02/04 22:07] (current) – [Examples] chris
Line 28: Line 28:
     *  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.     *  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>     *  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.+    *  Suggestion: Use fixed-point math for the rise/run (aka deltaY) value. 16-bit values with the radix point between the bytes is a good option.
  
 =====  Lab 3  ===== =====  Lab 3  =====
Line 74: Line 74:
 **Remember to save your work periodically**, either by pasting the text into a file, or using the Save button. Tip: the Save/Load/Chose File buttons work really well with a directory that is managed by Git. **Remember to save your work periodically**, either by pasting the text into a file, or using the Save button. Tip: the Save/Load/Chose File buttons work really well with a directory that is managed by Git.
  
-** 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 exactly which parts of the code you wrote__ (recommendation: colour-code your portion in the blog post). +** 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 exactly which lines of the code you wrote__ (recommendation: colour-code your portion in the blog post). **Do not** in any circumstances remove attribution, copyright, or license messages from the borrowed code.
  
 **__Important__: Failure to fully comply with the terms under which others have shared code with you, failure to fully acknowledge the source and license terms of all code which you incorporate from other sources, or failure to accurately identify exactly which portions of the code were written by you will be considered a violation of Seneca's [[https://www.senecapolytechnic.ca/about/policies/academic-integrity-policy.html|Academic Integrity Policy]].** **__Important__: Failure to fully comply with the terms under which others have shared code with you, failure to fully acknowledge the source and license terms of all code which you incorporate from other sources, or failure to accurately identify exactly which portions of the code were written by you will be considered a violation of Seneca's [[https://www.senecapolytechnic.ca/about/policies/academic-integrity-policy.html|Academic Integrity Policy]].**
Line 94: Line 94:
 For some examples of games and demos, see the [[#Resources]] section above, and also take a look at the http://txt3.de/ website - which uses an earlier version of the [[6502 Emulator|6502 emulator]] used in this course. The "Open Project" control on that page provides access to some interesting and inspiring code (check out "Skier", for example). You can copy-and-paste any of those examples into our SPO600 [[6502 Emulator]]. Be sure to check for permission (or licensing terms) before copying any code from that site (or any other source) and incorporating it into your code. For some examples of games and demos, see the [[#Resources]] section above, and also take a look at the http://txt3.de/ website - which uses an earlier version of the [[6502 Emulator|6502 emulator]] used in this course. The "Open Project" control on that page provides access to some interesting and inspiring code (check out "Skier", for example). You can copy-and-paste any of those examples into our SPO600 [[6502 Emulator]]. Be sure to check for permission (or licensing terms) before copying any code from that site (or any other source) and incorporating it into your code.
  
 +Another interesting example that pushes the emulator capability is the Peter Staley's Bad Apple video; see his [[https://www.youtube.com/watch?v=qsx5hKWRqpY|YouTube demo]] and [[https://github.com/pstaleystudent/|GitHub repo]]
spo600/6502_program_lab.1727206268.txt.gz · Last modified: 2024/09/24 19:31 by chris

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki