 Okay, so a viewer has asked if I'd do a video on how to set up Visual Studio Code and the Commodore 64 debugger so that you can develop your own assembly programs the way I do. So I thought I'd make a quick video demonstrating how to do that. Now, I develop on a Mac, so just thinking through here, these, yeah, will be applicable to Windows as well and Linux, but you'll have to do your own, you know, if you use those systems, Windows or Linux, you'll need to vary things accordingly. So this is just going to focus on, you know, on, I'm doing it on a Mac, because that's what I have to hand. So here are the kick assembler website. A kick assembly is the assembler that I use that plugs into Visual Studio Code that outputs, turns the assembly into a binary that the Commodore 64 emulator that can then run or the debugger. And it automatically, once it's set up, it'll automatically, you can automatically assemble and launch the code in the debugger from Visual Studio Code, so that makes it quite an easy development cycle. So to find this website, this is what it should look like as of the date of this video. This is the latest version of kick assembler. So just Google kick assembler and it's the one at the web.dk. And it will look just like this. So kick assembler version 5.24 is currently the latest one. And this is the link you need download kick assembler. So I'm going to click that. Do you want to allow it to happen? Yes. And there we go. It's downloaded into my downloads folder. So I'm going to open up a terminal, which you would do, I hope you like. You know, if you can do this way, hit enter. It automatically unpacks the zip file for me. So if I CD into kick assembler, have a look. Yeah, we can see it's already unzipped in its own folder. And the file that we're interested in really here is the kickas.jar. It's the Java executable. You will also need the Java runtime environment installed and there's a link to that on the kick assembler website. So I won't be covering that. Yeah, this video will assume that you've already got that installed, but you'd click the link go through the install process for that. Okay, so we've got kick assembler downloaded in the kick assembler folder after unzipping the zip file. What we're going to do is copy that. We're going to just copy that into somewhere that is pathed. So it could be executed easier. Okay, so this is Visual Studio Code. It's available on Mac, Windows and Linux. It's pretty much the same editor on any platform. So it should be familiar, whichever version you're using. When we come to look into the settings in a minute, your paths will be slightly different on different operating systems. It should be able to work out what they should be. It's fairly straightforward. So what we're going to do is click here to get up the extensions, search for kickas. I've already got it installed, but if you didn't, this is the one that I use, the one you're looking for, kickas C64 by Captain Jinx. When you haven't got it installed, you'll have a little blue button with white install. So you'd click that to install it. Then you want to click the cog and go to extension settings. And you'll need to have downloaded the C64 debugger. If you just Google that, you'll find that it comes packaged with, I think it's a C65 and NES debugger. So yeah, when you Google it, it'll be one of the top results, C64 debugger. And also you want the vice emulator installed as well so that you can choose which one that you use. Once they're installed, I say installed, just unpacked and put wherever you want. Mine's on the desktop so you can see this is the full path to it for me, the C64 debugger binary. Users, username, that should actually have a username in it. And desktop, I've just got it in a folder called C64, 65, XC, NES debugger, blah, blah, blah, on my desktop. And then that's the full path to it. This should just say Java in there, because that should be accessible just by typing Java in a terminal. We now execute, we've tested that already. Here's the full path to the kickass.jar, where I copied it too, which is use a local bin to put it somewhere that was pathed. Now, I want to run a debugger and run with a C64 debugger. Once I'm happy with something, I'll then load up vice and run it in that if I want it to look just like a C64, but whilst I'm working on something, the debugger is very useful because you can pause the state, step through it, instruction by instruction to find out any problems or any quirks, anything that's not working out quite right. And down here is the full path, similar to the debugger binary, but to the vice emulator. So once you've got those set, you can close that and you can get to work on creating your first C64 assembly program and see if it works. Okay, so let's make sure everything's working and just create and run a very simple Commodore 64 assembly program. So I'm going to press Command N, helps me select that, Command N, and you can just start typing to get started. So the first thing I'm going to do is set the memory address on the Commodore 64 where I want program to be. So it's 1000 hex, which translates into 40096 hexadecimal. Why I'm telling you that will become clear shortly. So we do that. And then what we're going to do, or we're going to have a main loop label. And then in that, we are going to increment memory location D020. We're going to decrement D021. And then we are going to jump to the main loop. Lovely. Now let's save that. I'm going to just call it test, testprog. There we go. Right. And it's now, because it's an assembly file, I'll put the ASM extension, it recognizes the assembly language. And it's just colored certain things here, colored the instructions, you know, differently. And which is nice. It is helpful later when you've got lots of code to look at to be able to pick out things a bit easier. But anyway, if I press F5 now, so it loads the debugger. Ah, and nothing. That is loaded into memory. So that hexadecimal 1000 becoming decimal 4096 means we type sys 4096 percenter. There we go. It's a little too much to see on this screen here. But up here, you can see what we're doing is we're incrementing the values of the color for the border and the page. And it executes very, very quickly, quicker than the screen can be redrawn, in fact, which is why it looks like lots of different little lines. But there you go. So we know it's installed and it works. Hurrah. Thanks for watching. Please like, comment and subscribe.