FAQ

Something is wrong after a version update

Please look at the breaking changes page.

Disable FS-UAE mouse capture

To disable the mouse capture by FS-UAE add the launch option (.vscode/launch.json):

{
    "configurations": [
        {
            "type": "fs-uae",
            ...
            "options": [
                ...
                "--automatic_input_grab=0"
            ],
            ...
        }
    ]
}

The debugger does not hit a breakpoint

Please verify:

• You have at least a 0.7 version extension installed
• FS-UAE Or WinUAE is a custom build with the remote debugger (try with the prebuilt binaries).

The copper debugger does not stop in each line

This is due to the way the emulator deals with the copper emulation.

The copper breakpoint is hit on a wrong line

This is due to the way the emulator deals with the copper emulation.

The message "Build aborted: there are compile errors" appears, what's happening ?

Go to the "output" tab (menu: view/Output), if you select "Amiga Assembly" in the combo (in the Output tab view) you will see all the errors from vasm / vlink.

The breakpoints are not resolved

If you use a binary compiled from files in another workspace directory, the debug info may point to an unknown path. In this case, you'll have to set the replacement expressions in the launch configuration.

    "configurations": [
        {
...
            "sourceFileMap": {
                "my/old/path": "my/new/path/"
            }
...
        },
    ]

Gray screen and the debugger does not start

The first section of the executable must be a code section. Please verify that the first object added to vlink contains your entry point. You may try some vlink options like -mrel to automatically merge sections, when there are PC-relative references between them.

    "amiga-assembly.vlink": {
        "enabled": true,
...
        "options": [
...
            "-mrel"
        ]
    }
}

The output binary is not updated when I run or debug my program

Please verify in the launch configuration that you have this options set:

    "buildWorkspace": true

When starting, the FS-UAE runs "twice" before returning to the ide

i.e. after clicking left mouse button to exit gencop, it reboots and runs gencop, and I have to click left mouse button again.

This is due to the difference between the debug and release launch.

In Run mode there is no injection so the binary is launched by the Startup-Sequence. In the fs-uae Debug mode the binary is injected in fs-uae at initialization before the Startup-Sequence started. So when it's done the normal amiga emulation start with a startup-sequence and re-runs the gencop binary.

If you don't want it in debug, remove the gencop line in Startup-Sequence file and keep UAEquit call (to have a gentle exit).

This does not apply to WinUAE.

Since 0.21 the run configuration does not work

In 0.21 the run configuration type changed from fs-uae-run to uae-run.

Please check the type in the .vscode/launch.json:

                "type": "uae-run",

I try to build / run and nothing happens

• If you are on linux please check the authorizations of the binary files.
• Select the "OUTPUT" tab and in the combo select "Amiga Assembly" you will get some logs that might be interesting.

Home can I print the custom register values

For the custom registers you can add to the watch:

• m $dff180,4

or

• m ${COLOR00},4

For all the registers at once:

• m $dff000,512,4,1

000002f0 | ...ð
00dff000: 000002f0 | ...ð
00dff004: a0001cca | ...Ê
...
00dff1f0: 00000000 | ....
00dff1f4: 00000000 | ....
00dff1f8: 00008000 | ....
00dff1fc: 0000ff3a | ..ÿ:

vasmm68k_mot not found on Osx

Error :

Cannot find bin/vasmm68k_mot : spawn bin/vasmm68k_mot ENOENT
Source: Amiga Assembly (Extension)

Edit the *.code-workspace file and set absolute paths to the binaries.

	"folders": [
		{
			"path": "."
		}
	],
	"settings": {
        ...
		"amiga-assembly.vasm": {
			"file": "bin/vasmm68k_mot",
		},
        ...
	}
}

}

So instead e.g.

"file": "bin/vasmm68k_mot",

put e.g. (where ever your project is located) for all tools in bin

"file": "/Users/myuser/myproject/bin/vasmm68k_mot",

Credits: gljubojevic for this workaround.

Binaries not working on Osx

The binaries are downloaded and not signed so they are in quarantine for osx until you accept the risk. In a terminal type :

cd to_my_bin_diretory_with_fsuae_vasm_etc
find . | xargs xattr -r -d com.apple.quarantine 

Otherwise to download and prepare the binaries :

# download osx tools for Amiga Assembly extension
echo "Downloading bin tools..."
echo "NOTE: No need to set osx unknown developer attributes when bin tools downloaded like this"
[ -d "bin" ] && rm -rf bin
mkdir -p bin
curl https://github.com/prb28/vscode-amiga-assembly/releases/download/0.21.1/osx.zip -L -o bin/osx.zip
unzip -d ./bin ./bin/osx.zip
rm ./bin/osx.zip

Credits: asimilion and gljubojevic for this workaround.