Skip to main content

Homebrew game for C64 - part 5: C64 / 6502 IDE for Mac

S
o far I've not written very much about the actual gameplay. That's mostly because I had done a bit of that before I started writing this blog. I will write some of that up 'retro'spectively. (geddit?)

But I've been choosing to do other things such as the music and whilst doing that I got hung up on writing a system for converting music notation to assembly.

I've been muddling by with a miscellany of tools (TMPx, an online sprite editor, XCode etc). This has been working pretty efficiently, with a few frustrations. So today I decided to begin work on an IDE for Mac, which AFAIK doesn't exist.
Not bad for a day's work.  The syntax colouring alone makes the assembly so much easier to read. The line numbering probably took more time than the rest put together. You never know what's going to go smoothly and what you'll be stuck on for hours.

But is this just displacement activity?? Am I avoiding getting on with the gameplay because I'm having doubts about the original concept? Maybe. But I'm reminded of this:

(image links to XKCD - go visit and spend time there.)

That seems very appropriate this evening.

If the IDE interests you, do let me know.

[update 28 Mar: Build / Run / Build+Run working, from menu or using same keyboard shortcuts as XCode. 'Build' uses tmpx and expects that to be installed, passes the resulting .prg (if build successful) to X64, Vice emulator]

Comments

  1. Great work. Do you know the Sublime text editor on the Mac? It has a Kick Assembler plugin which gives syntax highlighting. I'd be totally lost without syntax highlighting. The first time I saw it was in Turbo Pascal for DOS, I was amazed. Wish I'd had it when I was writing 6502 on the 64 back in the 80s...

    ReplyDelete
    Replies
    1. Thank you. I don't know Sublime but I'll take a look. I've done a little Z80 recently and found the TextMate editor and a plugin for the zasm assembler, which works well but doesn't appear to have a dark mode as far as I can see. The assembler I'm using for 6502 is Turbo Macro Pro and I've done quite a bit of work with that now and so I'm 'bought into' its syntax.

      Delete

Post a Comment

Popular posts from this blog

Driving NeoPixels with Z80

I 've long been thinking about a version two   RC2014 LED matrix module . I've had a matrix with a MAX 7219 on a module. It's a nice enhancement. But there's only so much you can do with a single-colour LED array right? Wouldn't it be cool to have RGB LEDs?  At Liverpool MakeFest I saw a wall-sized ping-pong ball NeoPixel display and picked up some NeoPixels with the intention of making one. Possibly driven by my RC2014.  I enjoy learning about protocols and have had some SPI devices working with the RC2014 - bit-banging SPI works really well because it doesn't care about timing. NeoPixels really do care about timing though. From Adafruit's web page about their 8x8  NeoPixel matrix: If there's one thing I want to get across in this blog post, it's don't just accept what you're told . Question everything. Learn about what's going on and find out why you're being told something isn't possible. Get creative with workarounds. I'

ZX81 reversible internal 16k upgrade

T his post is an upvote for Tynemouth Software's  ZX81 reversible Internal 16K RAM upgrade . Their instructions are easy enough for even me to follow and don't involve cutting tracks. This is the ZX81 I've had out on display and used whenever I wanted to. It's an issue 1 and was probably a kit judging by some very untidy assembly. It has a ZX8-CCB  composite video mod and an external keyboard fitted. On board it has two 1k x 4-bit chips.  The ZX81 originally came with 1k on board. Thanks to a trick with compressing the display in ram, that was enough to type and run a small program but you soon felt the limitations. Back in the early 80s, the solution was a 16k ram pack which plugged into the back[1] and this is the way I've been using this particular machine. These ram packs are notorious for 'ram pack wobble'. Even if fastened into place, you can still randomly find your work disappearing. This is a very reliable solution using a more modern 32k chip (half

Making new ROMs for the Vic20 / Vicky Twenty

M y Vicky Twenty is very nearly complete.  As things stand, the board and every single component is new*. The processor and VIAs are newly-manufactured (W65C02 and W65C22).  Obviously the Vic1 chip isn't manufactured today, but there is 'new old' stock about. I have been able to buy a Vic 1, date code 1987 (which seems very late). It obviously hasn't been in a computer before, passes the acetone test and works. The same goes for two of the ROMs - character and BASIC. But I haven't been able to buy a new-old Kernal ROM (901486-07). I am able to borrow one - all of the boards I have, have this particular ROM socketed. I don't know whether all of this indicates that the Kernal has proved less reliable than the other two. I recently bought a TL866 for another project. Of all the retro-computing hardware things I've had to learn to do, making ROMs has been one of the simplest. So far, everything has been very easy and worked first time.  I'm not sure that it&