Skip to main content

'Setting Forth' with Forth on the RC2014

T

his adventure started a few weeks ago when Spencer included an item in his RC2014 newsletter about James Bowman's port of CamelForth for RC2014.

I was intrigued by the arithmetic using double-length numbers and as James gives a few bits of example code in his article, it looked like a good opportunity to have a little foray into Forth. (I love the Jupiter Ace. I wish more had been sold so that they're a little less pricey today.)

I found several versions for CP/M. (I like using Compact Flash storage and CP/M on my RC2014.) Like BASIC, generic Forth sometimes doesn't work on the version you have without modification. Some versions contain more words or stick to the standard more closely than others. I tried Forth80, DXForth and UniForth as well as CamelForth and the one I like best is DXForth (I'm not recommending it over the others, it just worked best for me as I worked through some examples. I'd encourage anyone to try all of these and make up their own mind.)

The last thing I needed in my life was a new language. I use an object-orientated version of C in my day job, and assembly language with retro-computers. You can't beat the speed and efficiency of assembly. I wouldn't have considered using a higher-level language* for 8-bit computing.  Yet there was something about Forth that really appealed. 

It produces a compiled executable, which is pretty efficient and runs at close to assembly speeds. You can even write blocks of assembly in your Forth. Developing is very neat and efficient and it's easy to do it directly on the RC2014. If you buy into the way that Forth works, it forces you to think and program in a different way. 

I could write pages about this. But this is where the dice program comes in. Once I'd learned how to store and read bitmap data in Forth (hint: 'unindexed array'), send data to my OLED screen and read the buttons on my digital i/o module, building those things into a program was very quick and simple. 

Useful 'getting started' links:

Ed has provided me with this Google drive link which contains latest versions of DXForth

Archived copy of Ed's DXForth page 

Learn X in Y minutes where X = Forth (a beautifully straightforward 'getting started' page)

Thinking Forth by Leo Brodie - download and find Appendix A for more inroads. The rest of the book is a great read.


* it's arguably not a higher-level language, see "But Is It a High-Level Language?" page 27 of Leo Brodies' book.

Labels:

Comments

  1. Cuvtixo2 January 2021 at 15:49

    I'm really surprised you didn't mention Tynemouth's 4th Minstrel - Jupiter Ace replica. I got a kit from thefuturewas8bit.com but haven't had time to put it together. It's RC2014 bus compatible! I first heard of FORTH when I had a PowerPC iBook, and I briefly toyed with the idea of learning for that reason. The boot firmware for PowerPC Macs was written in that language when PCs just had humble BIOS and UEFI wasn't yet invented. It has a long history in the embedded world, and is ideal for that purpose, although I never got around to actually learning any, hopefully I'll learn when my Minstrel4 gets put together!

    ReplyDelete
  2. peahen2 January 2021 at 16:42

    I'm quite envious. My first Tynemouth kit was the Mini Pet and I was really impressed with the kit & documentation. I have always loved the look of the Ace, it's such a shame that original ones are silly money now. Since starting to learn about Forth I've been even more interested in that computer, and when I finally made the decision to grab a Minstrel Fourth kit from tfw8bit, they'd all gone. It's important with this 'new old stuff' to buy it when you see it, stuff tends to be produced in batches. I didn't know that fact about Macs. I've been a Mac person for a long time and have a number of powerPC macs and an iBook. One more reason to love them! Enjoy building and using your kit.

    ReplyDelete

Post a Comment

Popular posts from this blog

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
Post a Comment
Read more

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'
Post a Comment
Read more

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&
4 comments
Read more