Lab 2

 For this post I will be discussing lab 2 of SPO600,

This is lab is testing and modifying some code based on the 6502 assembler which can be found on this link http://6502.cdot.systems/. 

I will be testing the performance on the code and seeing how much memory it takes and the total run time.


Calculating Performance








I used a spread sheet in order to calculate the total time it will take to execute the program in ms and sec. The total time is not to long but it could be cut down. The fastest way I am thinking would be to cut down on the loops but I could not get it to work with out an error.

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
bne loop ; continue until done all pages

I was able to decrease the team by removing the first pointer, the low byte, getting rid of the current page number and the compare. This cuts down the time but now in half it wont make to much of difference. I tried to make it work with just one loop by thinking I could get the page and index to increment in the same loop but I could not figure out how. 




Modifying the Code



Change the code to fill the display with light blue instead of yellow. (Tip: you can find the colour codes on the 6502 Emulator page)

lda #$00 ; set a pointer 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 #$e ; colour number Set to blue.

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
ldx $41 ; get the current page number
cpx #$06 ; compare with 6
bne loop ; continue until done all pages

Comments

Post a Comment

Popular posts from this blog

SPO600 Lab1

Image
 Lab 1 for SPO600: I have picked node.js and openSSL, the reason I have picked both of these is that I have had the chance to work with Node in the past and found openSSL to be kind of cool never learned about it till I researched it. 1.) Node.js is an open software package that uses permissive MIT license for the main library. More information can be found here \ https://snyk.io/learn/node-js-licensing-and-security-risks/ . Node.js accepts contributions from developers by using Github, here developers can add patches to the software. This link will redirect to the Github page  https://github.com/nodejs/node . There is a total 3,131 contributors to this software, a user by the name mhdawson  seems to be the lead of the project and others can post and patch as well. There is a link here  https://github.com/nodejs/node/blob/main/CONTRIBUTING.md#pull-requests  that will allow you to apply to become a contributor to the project.     One of the code patches that I found was by as user named
Read more

SPO600(Project 3.2 FInal Post and thoughts on project and course)

Please Read 3.0 and 3.1 post as well!!  Thoughts on the tool and project. I believe that this can be very useful if expanded, what I mean by this is that I limited this tool just taking in C code using Python, That can be incredibly useful in the sense that if I only had an IDE such as Vs code (Made up example) that only was able to execute python that could become an issue if I need to execute a C style file or code bloc. This tool that I made was able to take that C and still give the desired output using Python language and syntax. This could be done in principial with any kind of code coming to the tool such as C++, Java and all other kinds. This tool could also be put onto other soft ware and is very modular in design.  This tool can be used very well to choose specific architecture, for my tool it was for aarch64 SME, SME2 and ASIMD, Proving the tool worked for choosing the methods was done in my 3.0 post and it shows we can choose a function using the tool that I had made.  The
Read more

SPO600(Project Part 2.1)

Image
My code can be found here:  https://github.com/a-martin94/Spo600/blob/main/tool.py As part two of the project I needed to put my plan in action and so that required a bit revision. Instead of writing in the code in C++ or Node I opted to pick python instead as this was a recommendation from our professor if we had used the language before because it is very good at parsing which is essentially what this project needs to do the most in order to get the expected output. I sadly had never used python before so I found myself learning a lot on the fly, luckily python is some what of an easy language to grasp but having to learn some new syntax and and other tools that python offers was some what harder to do. I do like python in the sense that you can just start coding not really to much third party installs required. I found part two of this project to be very hard. I started off with the idea that I was going to take some tester code that our professor has provided for us and dissect the
Read more