Motorola 68k based CPUS
- 1 Introduction
- 2 Atari ST
- 3 Commodore Amiga
Wanting to start sizecoding on a Motorola 68k platform in this day and age can be tough.
So here is a bit of help to get you started:
The Motorola 68k processor
The Motorola 68k processor...
Note: Assigment direction is source,dest instead of dest,source !!!
To be added.
The number of cycles for each instruction is different depending of processor model in M68K family.
The Atari ST systems consists of the M68k system with custom hardware for graphics and sound.
Setting up your development platform for the Atari ST systems is quite easy, first get the following tools:
- Assembler: VASM - This assembler is able to assemble directly to a TOS executable
- Assembler: RMAC - Can assemble to TOS executable as well as a headerless absolute binary
- Emulator(s): -. Make sure to use the original TOS 1.62 Image for best compatibility.
Compiling to a TOS image
Vasm -Ftos source.s -o source.tos rmac -p -o source.tos source.s
ST executable format, and why you should write relocatable code
To be added
The Atari ST uses an interleaved planar memory layout to represent its paletted display modes (we'll concentrate on 320x200x16 colours here).
The Atari ST uses index values into a palette of colours. Index 0 is the background colour (that's also used for the border) and a maximum of 16 colours can be defined and indexed.
Every plane contains one bit of a pixel's colour index value. The bits of the binary representation of a colour index like %1010 (% Bit3,Bit2,Bit1,Bit0) will end up in 4 different planes (bits most significant to least significant aka left to right): Plane4 Plane3 Plane2 Plane1.
So basicly Plane1 contains all of the Bit0s of all pixels, Plane2 all Bit1s, Plane3 all Bit2s and Plabe4 all Bit3s.
The first pixel on a plane is described by the leftmost (aka most significant) bit in a word, the second one by the second-leftmost etc. - just like this %0123456789abcdef with 0-f=pixels 1-16. %1000000000000000=$8000=pixel 1 in a plane word set. The 16th pixel will use the leftmost bit of the next word in this plane. etc.
16 pixels worth of data are represented as a full graphicword, meaning all information to display 16 pixels are stored together, followed by the data to represent the next 16 pixels etc. One row worth of display data has 20 graphicwords (20*16 pixels=320 pixels).
16 pixels are stored in 4 words - which contain 4 of the aforementioned planes.
So a 320x200x16 colour display is a contiuous memory buffer containing:
Pixels 0-15, row 0:(Plane1.w Plane2.w Plane3.w Plane4.w) Pixels 16-31, row 0:(Plane1.w Plane2.w Plane3.w Plane4.w) Pixels 32-47, row 0:(Plane1.w Plane2.w Plane3.w Plane4.w) ...... Pixels 304-319, row 199:(Plane1.w Plane2.w Plane3.w Plane4.w)
To be refined soon.
Setting a palette
Here is some code that will help you setup a palette
pea palette(pc) move.w #6,-(sp) trap #14 ; Palette data palette: dc.w $000,$100,$200,$311,$422,$533,$644,$755 dc.w $575,$464,$353,$242,$131,$020,$010,$000
Getting something on screen
Here is a bit of code to get you started:
;----------------------- ; Line-A Initialization ;----------------------- ; After calling this function, data register D0 and address register A0 point to a table ; with the starting address of the Line A variables. ; Address register A1 points to a table with the starting addresses for the three system ; font headers, ; and address register A2 points to a table that specifies the starting addresses of the; 15 Line A opcodes. There's no parameter required for this function, so all you have ; to do is call the word opcode label that you specified for the $A000 (Initialize) ; function. dc.w $A000 movem.l (a0),a1-a4 ; A3=INTIN, A4=PTSIN ;--------- ; For X&Y ;--------- frameloop: move.w #200-1,d7 ; y yLoop: move.w #320-1,d6 ; x xLoop: ; Putpixel put_pixel: move.b d6,d0 ; d0=x eor d7,d0 ; d0=x^y lsr.b #2,d0 ; d0>>=4 and #42,d0 ; d0&42 move.w d0,(a3) ; a3=color(d0) movem.w d6/d7,(a4) ; a4=x,y` dc.w $A001 ; put pixel command dbra d6,xLoop ; decrease and branch dbra d7,yLoop ; Wait loop bra frameloop ; .s *
The Atari ST systems use the YM2149 chip to generate sound.\
For more information check out https://www.atarimagazines.com/v4n7/stsound.html
Make some noise
To be added soon.
Sizecoding on the Atari ST is not very huge yet, so resources are sparse.
Here is a writeup to porting of Mona to the Atari ST, containing many hints.
Here are some bytetros with source code:
And some for the Atari Falcon
The Commodore Amiga system consists of the M68k system with custom hardware for graphics and sound.
- Assembler: -
- Emulator(s): Linux: fs-uae, Windows: WinUAE
No information yet
No information yet