By Andrew Davie (adapted by Duane Alan Hahn, a.k.a. Random Terrain)
As an Amazon Associate I earn from qualifying purchases. (I get commissions for purchases made through certain links on this page.)
Page Table of Contents
In tutorial 22, we learned that to horizontally position a sprite, we need to trigger the RESPx register at the appropriate position in the scanline, at which point the sprite will display immediately. To move to an arbitrary horizontal position, we need to trigger RESPx just before the TIA is displaying the appropriate color clock. Our solution has been to use the desired X-position of the sprite as the basis for a delay loop which starts at the beginning of a scanline, delays until roughly the correct position, adjusts the HMPx fine-tune horizontal position register and then 'hits' RESPx to immediately position the sprite.
Since the minimal time for a single loop iteration is 5 cycles (involving a register decrement, and a branch), and 5 cycles corresponds to 15 TIA color-clocks, it follows that our delay-loop approach can only position RESPx writes with an accuracy of 15 TIA color-clocks. This is fine, though, as the hardware capability of fine-positioning sprites by -8 to +7 pixels perfectly allows the correct position of the sprite to be established.
The approach taken previously has been to effectively divide the position by 15 (either through a table-lookup, or 'clever' code which simulated a divide by 15 using a divide by 16 (quick) + adjustment) and use that value as the iteration counter in a delay loop. This approach works, and has been fairly standard for a number of years. This is the approach presented in our earlier tutorial.
A posting to the [stella] list of an independent discovery of a 'new' method much improves on this technique. In actual fact, the technique was already known and documented in the list . . . but for various reasons these things don't always become well-known. The 'new' technique of horizontal positioning rolls the divide-by-15 and the delay loop into a single entity.
sec .Div15 sbc #15 ; 2 bcs .Div15 ; 3(2)
Now that may not look like much, but it's absolutely brilliant! Every iteration through the loop, the accumulator is decremented by 15. When the subtraction results in a carry, the accumulator has gone 'past' 0, and our loop ends. Each iteration takes exactly 5 cycles (with an extra 2 cycles added for the initial 'sec' and one less for the final branch not taken). The real beauty of the code is that we also, 'for free', get the correct -8 to +7 adjustment for the fine-tuning of the position (which with a little bit of fine-tuning can be used for the HMP0 register)! Read the relevant post on [stella] here. . .
For this brilliant bit of coding, our thanks go to R. Mundschau. . .
; Positions an object horizontally ; Inputs: A = Desired position. ; X = Desired object to be positioned (0-5). ; scanlines: If control comes on or before cycle 73 then 1 scanline is consumed. ; If control comes after cycle 73 then 2 scanlines are consumed. ; Outputs: X = unchanged ; A = Fine Adjustment value. ; Y = the "remainder" of the division by 15 minus an additional 15. ; control is returned on cycle 6 of the next scanline. PosObject SUBROUTINE sta WSYNC ; 00 Sync to start of scanline. sec ; 02 Set the carry flag so no borrow will be applied during the division. .divideby15 sbc #15 ; 04 Waste the necessary amount of time dividing X-pos by 15! bcs .divideby15 ; 06/07 11/16/21/26/31/36/41/46/51/56/61/66 tay lda fineAdjustTable,y ; 13 -> Consume 5 cycles by guaranteeing we cross a page boundary sta HMP0,x sta RESP0,x ; 21/ 26/31/36/41/46/51/56/61/66/71 - Set the rough position. rts ;----------------------------- ; This table converts the "remainder" of the division by 15 (-1 to -15) to the correct ; fine adjustment value. This table is on a page boundary to guarantee the processor ; will cross a page boundary and waste a cycle in order to be at the precise position ; for a RESP0,x write ORG $F000 fineAdjustBegin DC.B %01110000; Left 7 DC.B %01100000; Left 6 DC.B %01010000; Left 5 DC.B %01000000; Left 4 DC.B %00110000; Left 3 DC.B %00100000; Left 2 DC.B %00010000; Left 1 DC.B %00000000; No movement. DC.B %11110000; Right 1 DC.B %11100000; Right 2 DC.B %11010000; Right 3 DC.B %11000000; Right 4 DC.B %10110000; Right 5 DC.B %10100000; Right 6 DC.B %10010000; Right 7 fineAdjustTable EQU fineAdjustBegin - %11110001; NOTE: %11110001 = -15
One interesting aspect of this code is the access to the table with a (conceptual) negative index (-1 to -15 inclusive). Negative numbers are represented in two's complement form, so -1 is %11111111 which is *exactly* the same as 255 (%11111111). So how can we use negative numbers as indexes? We can't! All indexing is considered to be with positive numbers. So if our index was -1, we would actually index 255 bytes past the beginning of our table. The neat bit of code at the bottom sets the conceptual start of our table to 241 bytes BEFORE the start of the actual data so that when we attempt to access the -15th element of the table, we ACTUALLY end up at the very first byte of the 'fineAdjustBegin' table. Likewise, when accessing the -1th element, we ACTUALLY access the last element of the table. It's all very neat!
Finally, since we need to account for every cycle in this code very carefully (as the horizontal position depends on exactly where we write the RESP0 value), we need to take into account the possibility that an extra cycle is being thrown in when we access fineAdjustTable,y and that access crosses a page boundary. By positioning the table being accessed exactly on a page boundary, the code guarantees that every access incurs an extra cycle 'penalty' and is therefore consistent for all cases.
I don't take any credit for this, I just admire it. I consider this a BRILLIANT bit of coding, so hats-off to R. Mundschau and thanks for sharing!
Another 'BRILLIANT' bit of code, but this time from yours truly, is the 8-byte system clear. We touched on this earlier in Session 12, but I thought I'd give a quick run-down on exactly how that code works. . .
ldx #0 txa Clear dex txs pha bne Clear
We assume that when this code starts, the system is in a totally unknown state. Firstly, X and A are set to 0, and we enter the loop.
The loop begins: X-register is decremented (to 255) and this value is placed in the stack pointer (now $FF) the accumulator(0) is then pushed onto the stack, so memory/hardware location $FF is set to 0, and the stack pointer decrements to $FE since the txs and pha don't affect the flags, the branch will be based on the decrement of the x register if non-zero, then we repeat the loop. 0 will be written to 256 consecutive memory locations starting with $FF and ending with 0 (inclusive). Loop will terminate after 256 iterations. On the final pass through, x would be decremented to 0, and this placed in the stack pointer. We then push the accumulator (0) onto the stack (which effectively writes it to memory (TIA) location 0) and as a consequence the stack pointer decrements (and wraps!) back to $FF.
At the conclusion of the above, X = 0, A = 0, SP = $FF, a near-perfect init!
That could be the best 8-bytes ever written.
[This was the last session that Andrew Davie had time to work on. Maybe he'll find the time to finish these sessions in the future.]
Other Assembly Language Tutorials
Session 24: Some Nice Code
This book was written in English, not computerese. It's written for Atari users, not for professional programmers (though they might find it useful).
This book only assumes a working knowledge of BASIC. It was designed to speak directly to the amateur programmer, the part-time computerist. It should help you make the transition from BASIC to machine language with relative ease.
The 6502 Instruction Set broken down into 6 groups.
Nice, simple instruction set in little boxes (not made out of ticky-tacky).
This book shows how to put together a large machine language program. All of the fundamentals were covered in Machine Language for Beginners. What remains is to put the rules to use by constructing a working program, to take the theory into the field and show how machine language is done.
An easy-to-read page from The Second Book Of Machine Language.
A useful page from Assembly Language Programming for the Atari Computers.
Continually strives to remain the largest and most complete source for 6502-related information in the world.
By John Pickens. Updated by Bruce Clark.
Below are direct links to the most important pages.
Goes over each of the internal registers and their use.
Gives a summary of whole instruction set.
Describes each of the 6502 memory addressing modes.
Describes the complete instruction set in detail.
Cycle counting is an important aspect of Atari 2600 programming. It makes possible the positioning of sprites, the drawing of six-digit scores, non-mirrored playfield graphics and many other cool TIA tricks that keep every game from looking like Combat.
Atari 2600 programming is different from any other kind of programming in many ways. Just one of these ways is the flow of the program.
The "bankswitching bible." Also check out the Atari 2600 Fun Facts and Information Guide and this post about bankswitching by SeaGtGruff at AtariAge.
Atari 2600 programming specs (HTML version).
Links to useful information, tools, source code, and documentation.
Atari 2600 programming site based on Garon's "The Dig," which is now dead.
Includes interactive color charts, an NTSC/PAL color conversion tool, and Atari 2600 color compatibility tools that can help you quickly find colors that go great together.
Adapted information and charts related to Atari 2600 music and sound.
A guide and a check list for finished carts.
A multi-platform Atari 2600 VCS emulator. It has a built-in debugger to help you with your works in progress or you can use it to study classic games.
A very good emulator that can also be embedded on your own web site so people can play the games you make online. It's much better than JStella.
If assembly language seems a little too hard, don't worry. You can always try to make Atari 2600 games the faster, easier way with batari Basic.
Some people appear to have a mental illness because they have a vitamin B deficiency. For example, the wife of a guy I used to chat with online had severe mood swings which seemed to be caused by food allergies or intolerances. She would became irrational, obnoxious, throw tantrums, and generally act like she had a mental illness. The horrid behavior stopped after she started taking a vitamin B complex. I’ve been taking #ad Jarrow B-Right for many years. It makes me much easier to live with.
Unfermented soy is bad! “When she stopped eating soy, the mental problems went away.” Fermented soy doesn’t bother me, but the various versions of unfermented soy (soy flour, soybean oil, and so on) that are used in all kinds of products these days causes a negative mental health reaction in me that a vitamin B complex can’t tame. The sinister encroachment of soy has made the careful reading of ingredients a necessity.
If you are overweight, have type II diabetes, or are worried about the condition of your heart, check out the videos by William Davis and Ivor Cummins. It seems that most people should avoid wheat, not just those who have a wheat allergy or celiac disease. Check out these books: #ad Undoctored, #ad Wheat Belly, and #ad Eat Rich, Live Long.
Negative ions are good for us. You might want to avoid positive ion generators and ozone generators. Whenever I need a new air cleaner (with negative ion generator), I buy it from surroundair.com. A plain old air cleaner is better than nothing, but one that produces negative ions makes the air in a room fresher and easier for me to breathe. It also helps to brighten my mood.
Never litter. Toss it in the trash or take it home. Do not throw it on the ground. Also remember that good people clean up after themselves at home, out in public, at a campsite and so on. Leave it better than you found it.
Seems like more people than ever finally care about water, land, and air pollution, but the climate change cash grab scam is designed to put more of your money into the bank accounts of greedy politicians. Those power-hungry schemers try to trick us with bad data and lies about overpopulation while pretending to be caring do-gooders. Trying to eliminate pollution is a good thing, but the carbon footprint of the average law-abiding human right now is actually making the planet greener instead of killing it.
Watch these two YouTube videos for more information:
Hydrofracking is bad for you, your family, your friends, and the environment.
Although some people with certain conditions may not be able to take it, hydroxychloroquine is a cheap drug that has been prescribed by doctors since the 1950s and it seems to be helping many people who have COVID-19 when administered early enough. (Hydroxychloroquine is also supposedly safe and tolerable as an anti-cancer therapy.) Seems like most news sources are going out of their way to make it sound like hydroxychloroquine is the most dangerous drug in the world, but they also make it sound like it’s the greatest drug in the world for lupus and rheumatoid arthritis patients. They basically say that using hydroxychloroquine for COVID-19 patients would be taking that great and wonderful drug away from the other patients who need it. So which is it? Is hydroxychloroquine deadly or divine?
If you believe that a couple of Trump supporters took the medicine hydroxychloroquine and it’s President Trumps fault that the husband died, you’ve been duped. Watch this video. The wife was a prolific Democratic donor, it seems she hated her husband, she used fish tank cleaner (not the medicine hydroxychloroquine), and now she is the subject of a homicide investigation.
Some people claim that the reason so many news sources want to keep doctors from using hydroxychloroquine for COVID-19 is that they are desperate to keep everyone afraid to leave their homes since mail-in voting will make voter fraud much easier (the only way they could beat Trump). Others claim that the rabid anti-hydroxychloroquine campaign was to make way for the expensive new drug called remdesivir. Drug companies can’t make much money with old generic drugs, so new drugs must be pushed. Both claims could be true since remdesivir supposedly isn’t as good as hydroxychloroquine.
According to Dr. Shiva Ayyadurai, hydroxychloroquine does four things: (1) stops viral entry, (2) stops viral RNA replication, (3) stops viral particle assembly, and (4) stops cytokine storm. Remdesivir only stops viral RNA replication. Did you get that? Hydroxychloroquine does four things and remdesivir only does one. The doctor also said that nearly 70 percent of the people who took remdesivir had some type of adverse effect. If all of that is true and the more anemic medicine ends up being used by most doctors thanks to the smear campaign against hydroxychloroquine, the average American will beg to vote from home.
In case you didn’t know, Patrick Howley reported that one of the authors of the ‘study’ saying that hydroxychloroquine doesn’t work at VA hospitals got a research grant from Gilead (the company that makes remdesivir). Does that seem a little fishy to you?
Bryan Fischer said in an article that Dr. Fauci has known since 2005 that chloroquine is an effective inhibitor of coronaviruses. You might also want to check out the following three links:
“The Disruptive Physician” had this to say at Twitter: “Meanwhile, regular doctors like me are using HCQ + Azithromycin and Zinc to good effect. One nursing home in NE Ohio had 30 cases - started everyone on HCQ, no deaths. Quick recovery. Why would the MSM hide this? Why would twitter block people who question the WHO?” You might also want to check out Dr. Stephen Smith, Dr. Ramin Oskoui and Dr. Yvette Lozano.
In case you’re interested, here are a few COVID-19 patients who appear to claim that hydroxychloroquine saved their lives: elderly couple Louis Amen and Dolores Amen, Daniel Dae Kim, Rio Giardinieri, John McConnell, Margaret Novins, Jim Santilli, Billy Saracino, and Karen Whitsett (Democratic member of the Michigan House of Representatives).
View this page and any external web sites at your own risk. I am not responsible for any possible spiritual, emotional, physical, financial or any other damage to you, your friends, family, ancestors, or descendants in the past, present, or future, living or dead, in this dimension or any other.
Use any example programs at your own risk. I am not responsible if they blow up your computer or melt your Atari 2600. Use assembly language at your own risk. I am not responsible if assembly language makes you cry or gives you brain damage.