Lab - 1: Modifications and Experiments

 

Modifications and Experiments

Changing color to Light Blue

To change the color, I replaced lda #$07 (yellow) with lda #$06 (light blue). The emulator provides a full-color reference table, making this an easy modification.

Different Color for each page

To add variety, I used different colors for each quarter of the screen:


Randomizing Pixel Colors

By integrating a pseudo-random number generator (PRNG) from the 6502 Emulator page, I assigned a random color to each pixel, creating a vibrant, chaotic display.

Advanced Experiments

Adding TYA Before STA ($40), Y


Effect

  • The screen will show a gradient instead of a single color.
  • Since TYA loads Y into A, the stored value changes as Y increments.
  • This results in 256 different colors across a page, depending on how the emulator maps colors.

Adding LSR after TYA


Effect

  • The screen still shows a gradient but with fewer unique colors.
  • LSR reduces the range of stored values, making colors repeat more frequently.
  • The total number of colors is reduced to 128, since LSR halves each value.
Using Multiple LSR Instructions

Try 2, 3, 4, or 5 LSR in a row.

Effect

  • With 3 LSR, the color range is now 32 unique colors.
  • More shifts (e.g., 5 LSR) would reduce to 8 colors or even fewer.
Using ASL Instead of LSR



Effect

  • ASL increases the brightness range instead of reducing it.
  • The values overflow quickly, creating sharp transitions between colors.
  • This can result in more rapid color changes compared to LSR.
Testing Multiple INY Instructions

Try replacing INY with two, three, or five consecutive INY commands.


Effect

  • The pattern becomes less detailed, as pixels get skipped.
  • 3 INY results in every third pixel being colored, creating vertical stripes.
  • 5 INY makes the gaps even larger.

We pushed the boundaries of our 6502 assembly knowledge, tweaking code, testing new instructions, and seeing the magic happen in real-time. But are you ready for a challenge? In the next post, we’ll take things up a notch with a tricky but fun assembly problem to solve. Think you can crack it? Let’s find out!

Comments

Post a Comment

Popular posts from this blog

Project Stage 3: Enhancing GCC Pass for Multiple Function Clone Handling: Progress Update

In my earlier work, I developed a basic GCC pass for identifying and comparing function clones. For this latest phase, I focused on improving the pass to handle programs containing multiple cloned functions. Additionally, I wanted to enhance code organization by consolidating data storage, replacing multiple parallel vectors and maps with a structured approach using a dedicated struct to store characteristics of clone variants. Implementation Process Phase 1: Code Revision for Multi-Function Support I modified the pass to properly handle programs with multiple cloned functions in x86 server environments. The updated code includes all critical support files. The revised implementation's core is a specialized pass that processes GIMPLE representation data. This pass systematically identifies resolver functions and creates appropriate tracking structures for each function being cloned. The implementation uses maps and vectors to store function characteristics, including basic block co...
Read more

Lab - 1: Exploring 6502 Assembly

Image
Exploring 6502 Assembly: A Journey into Low-Level Programming  Introduction Assembly language has always been both fascinating and challenging for programmers. Unlike high-level languages where abstractions make coding easier, assembly requires a deep understanding of how the CPU processes instructions. In this lab, we explore the basics of 6502 Assembly Language through bitmap displays, code modifications, performance enhancements, and using the 6502 Emulator. This experience is the first step towards learning more complex architectures such as x86_64 and AArch64.
Read more

Project Stage 1: Troubleshooting a bit - Coming soon

  Procedure for Troubleshooting Debugging using the following method: First Error Analysis: I carefully reviewed the error logs after my initial build attempt failed. Copy ./pass-instances.def:47:23: error: expected ';' at end of member declaration 47 | NEXT_PASS_WITH_ARG (pass_mypass, 1, 1) This suggested an issue with my pass registration syntax. Examining Pass Declaration Conventions: I ran the following to examine the passes that were already included in the GCC source code: Copy cd ~/git/gcc/gcc grep -r "NEXT_PASS" passes.def This showed that NEXT_PASS (pass_name, number) was the proper format instead of NEXT_PASS_WITH_ARG. Function name Pattern Analysis: I looked at various pass implementations to learn more about the name conventions: Copy cd ~/git/gcc/gcc find . -name "tree-*.cc" | xargs grep "make_pass_" This demonstrated to me that the pattern make_pass_X, where X is the pass name without the "pass_" prefix, is what GCC ...
Read more