Amiga Coders Club Source Codes

[Defender]

Hi,

As a newbie, I found Amiga Coders Club series is the Amiga hardware assembly tutorial I was looking for. However, whenever I try to run the example source codes either on VSCode (PC) or AsmPro (WinUAE), I'm receiving lots of different error messages, especially for the include files. (And yes, I corrected the folders) Has anyone ran those codes successfully please? Should I use another assembler for compatibility? It would be really good to able to run those examples.

Thanks in advance for your help.

[filou]

Hi,

I've found this:
https://archive.org/details/amiganut...scansalltested.

Very interesting.

Could you post a source code so we can test ?

What are the error messages ?

[Rock'n Roll]

this procedure works not for all but for the first some listings:

in ACC/Source5/Tutorials (Copper example 1) copper_eg1.s stands:
;opt o+,ow-,c- ; devpac, so I comment out this line because I use asmone

include source5:include/hardware.i
include source5:include/libs.i

I put asmone in the folder ACC/Source5
then in WinUAE: Hardware/CD & Harddrives --> Add directory or archive
Device name: DH1
Volume label: source5
Path: ../ACC/source5

Then start the emulation and then asmone and read and assemble the file: it works!

but this works not for the later files like 'eg_11.s' with this:
incdir 'Source5:include/'
include 'startup.i'
include 'macros.i'
include 'subroutines.i'

because in startup.i stands:
incdir "sys:include/"
include "exec/exec_lib.i"
include "exec/exec.i"
include "libraries/dos_lib.i"
include "libraries/dos.i"
include "libraries/dosextens.i

and asmone breaks up with errormessages here.

Maybe with devpac it is possible, but I have no experience with this.

[Defender]

Originally Posted by filou

Hi,

I've found this:
https://archive.org/details/amiganut...scansalltested.

Very interesting.

Could you post a source code so we can test ?

What are the error messages ?

Thanks, I tried to run the first sprite example in ACM3:
https://imgur.com/a/Z9GpPHL

Both VSCode and Asm-Pro v1.18 goes crazy about includes:
VSCode:
https://imgur.com/a/NrHRKDA

Asm-Pro:
https://imgur.com/a/GP8P0aQ

[Defender]

Originally Posted by Rock'n Roll

and asmone breaks up with errormessages here.

Maybe with devpac it is possible, but I have no experience with this.

Thanks, it seems the issue is with the include files for other sources too. When I remove the includes and put the definitions used in the source into the source code itself, it works fine for most of them.

[filou]

Hi, With the vscode extension there's a problem with the character "."

For example, you should replace in hardware.i:

CIAAE.LSB EQU $BFE801
CIAAE.MID EQU $BFE901
CIAAE.MSB EQU $BFEA01
by
CIAAE_LSB EQU $BFE801
CIAAE_MID EQU $BFE901
CIAAE_MSB EQU $BFEA01

or use the built in hardware/cia.i and hardware/custom.i



The vscode extension is also case sensitive.

[Defender]

Originally Posted by filou

Hi, With the vscode extension there's a problem with the character "."

For example, you should replace in hardware.i:

CIAAE.LSB EQU $BFE801
CIAAE.MID EQU $BFE901
CIAAE.MSB EQU $BFEA01
by
CIAAE_LSB EQU $BFE801
CIAAE_MID EQU $BFE901
CIAAE_MSB EQU $BFEA01

or use the built in hardware/cia.i and hardware/custom.i



The vscode extension is also case sensitive.

Very important knowledge, thank you!

[Defender]

And I didn't know there was built-in include files in VSCode extension! Trying hard to find them now

[Defender]

Any idea about this please?

https://imgur.com/a/MGYMtwY

[filou]

I think that the label \done should be renamed .done
Also "Be kind to the os" should be commented with ;
All the comments should appear in green : request bits , clear bits etc....

[Defender]

Seems like that backslash character has a special meaning so it can be re-used, probably in devpac:
https://imgur.com/a/QpNWkhG

[filou]

Maybe there are invisible characters between beq,s and \done.
Try to delete what's in between and replace by a regular space.

[Defender]

Originally Posted by filou

Maybe there are invisible characters between beq,s and \done.
Try to delete what's in between and replace by a regular space.

Checked, it's just spaces:
https://imgur.com/a/6SyOLti

[filou]

In previous post it said that _done is redefined.
a label is unique unless its name starts with "." , it then can be repeatedly used locally (till a rts or rte instruction)

You should rename _done to .done to avoid conflict.

Or differentiate each label done1, done2 for each subroutine ( rts (return from subroutine) instruction)

labels will be converted into instruction addresses by the assembler.

[a/b]

For asm-one&co:
- end of line comments may have to start with a semicolon, depending on your assembler prefs: (un)check the "; Comment" option
- local labels must start with a period, e.g. .local_lab
- local lables within other blocks are referenced with a backslash, e.g. Global3\.local_lab
That's why backslashes and periods have a special meaning when it comes to labels and symbols.

[phx]

Originally Posted by a/b

- local labels must start with a period, e.g. .local_lab
- local lables within other blocks are referenced with a backslash, e.g. Global3\.local_lab
That's why backslashes and periods have a special meaning when it comes to labels and symbols.

Backslashes are also used in macros to specify macro arguments (

\1

,

\2

, etc. or special macro replacements like

\@

(inserts a unique id)).
Periods are also used to define the size (

.b

,

.w

,

.l

) as in

move.l ExecBase.w,a6

or

(label.l,a0)

. Therefore you shouldn't use it within symbol names.

If you are refering to the VSCode extension based on vasm, then you can enable periods/dots within symbol names by the command line options:

-ldots

or

-devpac

(yes, Devpac seems to allow it).

[Defender]

Originally Posted by phx

If you are refering to the VSCode extension based on vasm, then you can enable periods/dots within symbol names by the command line options:

-ldots

or

-devpac

(yes, Devpac seems to allow it).

Oh that's great! It seems there are more to learn about that extension! Thanks

[Defender]

Am I doing it right?

\Programs\Microsoft VS Code>Code.exe -devpac

[filou]

On VsCode on the left tab "EXPLORER" you must edit the file task.json and add the arg -devpac to vasm. (expand .vscode folder)

"tasks": [
{
"type": "amigaassembly",
"vasm": {
"enabled": true,
"command": "${config:amiga-assembly.binDir}/vasmm68k_mot",
"args": [
"-m68000",
"-Fhunk",
"-devpac",
"-linedebug"
]
},

[Defender]

Originally Posted by filou

On VsCode on the left tab "EXPLORER" you must edit the file task.json and add the arg -devpac to vasm. (expand .vscode folder)

Ah, thanks!