I'm becoming an expert at 6502 Assembly

We're almost a month into SPO600, and 6502 Assembly concepts are really starting to become second nature for me.

In this lecture, Chris spoke about characters, strings, and system routines.

Characters are usually represented in binary as a number which corresponds to an entry in a character set table. The most common table is ASCII.
Strings are groups of characters terminated with zeroes, much like C.

There are several ROM (read-only memory) system routines for the 6502 emulator:

  • SCINIT $ff81 - Initialize and clear the character display
  • CHRIN $ffcf - Input one character from keyboard (returns A)
  • CHROUT $ffdw - Outputs one character (A) to the screen at the current cursor position. Screen will wrap/scroll appropriately. Printable characters and cursor codes ($80/$81/$82/$83 for up/right/left/down) as well as RETURN ($0d) are accepted. Printable ASCII codes with the high bit set will be printed in reverse video.
  • SCREEN $ffed - Returns the character screen size in the X and Y registers.
  • PLOT $fff0 - gets (CARRY=1) or sets (CARRY=0) the cursor position

To use these routines, we need to copy the define directives.

CHROUT is particularly useful because it can be used to get automatic emulator window scrolling on new lines.

I'm looking forward to see what Chris has in store for us this week regarding the lab! The animation exercise last week was a lot of fun.
 

Comments

Post a Comment

Popular posts from this blog

The Difference of SVE2 (Project Stage 3)

Image
Hey everyone, and welcome to the final blog for SPO600. Objective ARMv9 is coming out soon, and it has improved SIMD implementation using a new technology titled Scalable Vector Extensions v2 (SVE2). This is an upgrade from SVE, an AArch64 extension used for flexible vector-length implementations. The idea for this final blog is to analyze how ffmpeg will be operating differently with the coming of SVE2 and describe the changes that will need to be extended to support SVE2. Definition Firstly, let's take a look at the official documentation for SVE2, taken straight from the ARM website. "SVE2 is a superset of SVE and Neon." This means that SVE2 will support all of the functionality of SVE and the Neon extension with extended features. By this logic, ffmpeg will require no necessary changes to support the new SVE2 overhaul. However; there's a couple of new features in SVE2 that should be utilized to improve the efficiency of ffmpeg. How do I write SVE code anyway? In
Read more

So I examined another open-source project... (Project Stage 2)

Image
For the second stage of the final SPO600 project, the objective is to select one open-source project of our choosing, locate the SIMD code and examine its purpose. Professor Chris provided many open-source project options for us; I decided to go with ffmpeg. ffmpeg is a multimedia library that is used for transcoding formats, video editing (trimming, concatenating, scaling, effects, etc.). This library has been in development since its release on December 20, 2000, with the most recent commit only being a few hours ago as shown below.   I decided to take a dive into their repository, searching for any sign of SIMD code. SIMD stands for Single Instruction, Multiple Data and is a parallel processing technique that is often used for 3D Graphics and multimedia applications. This makes sense because images have two dimensions, and videos even include time as an extra 'dimension' as well. Parallel processing is crucial to operate efficiently on multimedia like that. This is what
Read more

The World of Open Source! (Week 1 Lab)

In SPO600, we'll be submitting our own code for review. In order to learn more about this, Lab 1 is designed to explore the code review processes used in open source projects. I looked into two open source software packages - AForge.NET, a .NET computer vision library and YARP.it, a C++ robotics library. I took a closer look and found that AForge.NET has a public GitHub repo to accept pull requests. Interestingly, I found 10 pull requests. One of them, titled 'Added new solution and project files for .NET Standard' had four replies discussing specific technicalities I won't go over. On YARP.it, it was really easy to find their GitHub repo because it's on their main page. This time, there were 14 pull requests. The first one had 15 replies, in which they had an argument on whether or not the pull request is even beneficial or necessary. Although the pull request was made over 2 years ago, it's still in progress. It seems that there hasn't been a reply since M
Read more