Amiga Assembly extension for Visual Studio Code

[prb28]

@Steve, the VASM binary configuration is set in the .vscode/settings.json file.

    "amiga-assembly.vasm": {
        "enabled": true,
        "file": "bin\\windows_x64\\vasmm68k_mot.exe",
        "options": [
            "-m68000",
            "-Fhunk",
            "-linedebug"
        ]
    }

The "enabled" parameter must be "true" and the "file" parameter must have the path to the vasm executable.

VASM is used to check errors in the assembly and to build the binaries to run and debug in FS-UAE.
It may not be mandatory, if you do not want to build the amiga executable, so if there is errors while vasm configuration is set to "false", tell me.

[Steve]

Okay thanks. Do I have to rename the files like this to get it to work properly:

`.vscode\settings-windows_x64.json -> .vscode\settings.json`

`.vscode\launch-windows_x64.json -> .vscode\launch.json`

Can the rest of the settings files then be deleted?

[prb28]

@Steve if you have downloaded this zip file vscode-amiga-wks-example-windows_x64.zip it is already done for Windows 10.

[Steve]

Originally Posted by prb28

@Steve if you have downloaded this zip file vscode-amiga-wks-example-windows_x64.zip it is already done for Windows 10.

Oh thanks, you're right. I was already using that zipped setup. Just a bit confused as to why when I run the debugger it keeps asking me 'Please configure the VASM compiler'. Also it doesn't seem to take any notice of the breakpoint and just goes ahead and runs the program.

Actually I'm not sure what its executing but it certainly isn't compiling the code. I deleted a big chunk of code to break it and it still ran fine. Hmmm, somethings not right.

EDIT: Oops it looks like I haven't setup a correct path in the workspace settings. No that didn't fix it.

[prb28]

My test machine is the same that I used to compile the binaries, it may have some special configuration due to all the build tools... I will test it tomorrow in a empty window 10 install.

Are you sure you selected the debug configuration in the debug launch drop box ? You can choose between run and debug (run is selected by default).

Could you try these steps :

• run the vasm executable (vasmm68k_mot.exe) in a dos box, just to see if it is functional
• set absolute paths in the .vscode/settings.json
• delete all the "*.o" files in the build directory
• delete the fs-uae/hd0/gencop file
• click on the build word in the bottom status bar of vscode and verify that the fs-uae/hd0/gencop file has been generated

Hope this helps,
I will try to add some error reporting in the next release to help to diagnose the configuration problems.

[Steve]

Originally Posted by prb28

My test machine is the same that I used to compile the binaries, it may have some special configuration due to all the build tools... I will test it tomorrow in a empty window 10 install.

Are you sure you selected the debug configuration in the debug launch drop box ? You can choose between run and debug (run is selected by default).

Could you try these steps :

• run the vasm executable (vasmm68k_mot.exe) in a dos box, just to see if it is functional
• set absolute paths in the .vscode/settings.json
• delete all the "*.o" files in the build directory
• delete the fs-uae/hd0/gencop file
• click on the build word in the bottom status bar of vscode and verify that the fs-uae/hd0/gencop file has been generated

Hope this helps,
I will try to add some error reporting in the next release to help to diagnose the configuration problems.

Thanks for your help. I managed to run vasm in the windows CLI okay. It just complained about no file being selected but it seemed to be working. I added the absolute paths like so:

{
    //"[m68k]": {
    //    "files.encoding": "iso88591"
    //},
    "amiga-assembly.cstool": "F:\\TEMPS\\vscode-amiga-wks-example\\bin\\windows_x64\\cstool.exe",
    "amiga-assembly.vasm": {
        "enabled": true,
        "file": "F:\\TEMPS\\vscode-amiga-wks-example\\bin\\windows_x64\\vasmm68k_mot.exe",
        "options": [
            "-m68000",
            "-Fhunk",
            "-linedebug"
        ]
    },
    "amiga-assembly.vlink": {
        "enabled": true,
        "file": "F:\\TEMPS\\vscode-amiga-wks-example\\bin\\windows_x64\\vlink.exe",
        "includes": "*.s",
        "excludes": "",
        "exefilename": "..\\fs-uae\\hd0\\gencop",
        "options": [
            "-bamigahunk",
            "-Bstatic"
        ]
    }
}

I deleted the object files and ran build but I keep getting the same response:

'Please configure VASM compiler'

No object files were generated.

[prb28]

That's weird...

This message only appears when the configuration is not found or vasm is disabled.

It must be looking for the settings file in another location than the .vscode directory, maybe are you using workspaces ? (I never tried it)

So could you please try to edit the settings using the dedicated gui of vscode ?
https://code.visualstudio.com/docs/getstarted/settings

[Steve]

Originally Posted by prb28

That's weird...

This message only appears when the configuration is not found or vasm is disabled.

It must be looking for the settings file in another location than the .vscode directory, maybe are you using workspaces ? (I never tried it)

So could you please try to edit the settings using the dedicated gui of vscode ?
https://code.visualstudio.com/docs/getstarted/settings

It's strange, I've looked at those settings but it does seem to be using the external JSON settings files. The internal settings are set to read-only. I didn't install Visual Studio Code in the usual C:/Program files etc. I installed it onto my F: partition. Maybe that has something to do with it? It could be looking in the User folder?

[prb28]

You are right, it can be a user/security problem.
Microsoft has a new installer in user mode it may help :
https://code.visualstudio.com/docs/?dv=win64user

[Steve]

Originally Posted by prb28

You are right, it can be a user/security problem.
Microsoft has a new installer in user mode it may help :
https://code.visualstudio.com/docs/?dv=win64user

Thanks tried that but still the same issue. Maybe this screen could be the culprit?

Notice it says 'enabled: false'

[prb28]

Thanks for the screenshot it helps !

You are using a workspace in vscode - I never used it, I will try to fix it for the next release
I shouldn't have called the project 'workspace' - sorry about that, it's confusing.

Please use a new window and the "file"/"open Folder" option to open the folder containing the sources.

[Steve]

Originally Posted by prb28

Thanks for the screenshot it helps !

You are using a workspace in vscode - I never used it, I will try to fix it for the next release
I shouldn't have called the project 'workspace' - sorry about that, it's confusing.

Please use a new window and the "file"/"open Folder" option to open the folder containing the sources.

Yep, that was the problem alright! Thanks for getting it fixed in the next release.

Good work by the way - I've been looking for something like this for a while.

[prb28]

Happy to ear that !

I will fix it in the next release thanks !

[Steve]

I'm just wondering why, when the code is assembled by vasm and the debugger starts, how come it seems to always pause on line 25 even though I haven't set a break point?

Line 25:   clr.l      d0

Can I prevent it from pausing at the start every time the debugger is run?

[prb28]

By default the stop on entry option is set in the .vscode/launch.json file :

{
    "version": "0.2.0",
    "configurations": [
        {
...
        {
            "type": "fs-uae",
            "request": "launch",
            "name": "Debug",
            "stopOnEntry": true,
...
        }
    ]
}

Set it to false :

{
...
            "stopOnEntry": false,
...
}

and the program will run until you press pause.

[Steve]

Originally Posted by prb28

By default the stop on entry option is set in the...and the program will run until you press pause.

So it does, thanks again!

[yesplease]

This extension is totally great! Merci beaucoup. Just tried it on my old aztec Asm code. I mounted a macos folder as a harddrive in FSUAE and started visual code with AmigaAssembly extension on that folder. Now I have a very cool editor with syntax highlighting and all the modern comforts. It even shows the semantics of the custom chip registers. Very cool!

[prb28]

Danke ! Happy you like it.
I'm working on the copper debugger, it will be in the next release (still some bugs to fix...).

[MartinW]

Just wanted to say thank you too for this extension. I've not used it all that much yet but I did try it out and thought it was particularly awesome. I especially like the fact that you have bundled up the required EXE's which make it a nice relatively small and self-contained package.

[arcanist]

How did I not know about this, and why does this thread only have 2 pages?

That's some crazy good integration! I love VS Code, will definitely be playing with this.