horrorhub.club is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for Horror fans.

Server stats:

77
active users

#rc2014

4 posts2 participants0 posts today
Replied in thread

@feoh thank you! still needs that little extra though.

but it's fun working out how those old chips are working.

as for soldering: you don't have to - @etchedpixels has written a very good #rc2014 #emulator which also emulates the #tms9928a - I use it on my @VoidLinux laptop while abroad.

Maybe that is an option for you to get some taste of rc2014?!

you can find it here:

github.com/EtchedPixels/Emulat

A collection of emulators mostly of retrobrew style systems - EtchedPixels/EmulatorKit
GitHubGitHub - EtchedPixels/EmulatorKit: A collection of emulators mostly of retrobrew style systemsA collection of emulators mostly of retrobrew style systems - EtchedPixels/EmulatorKit

Here are the latest news regading my #TMSnake #game for #rc2014 and #TMS9918a #graphics.

The video below shows the current state of affairs, and I've just added some limited #sfx to the game - however the recording below did not capture the beepy beeps for some reason.

There is one last tweak I need to add in terms of gameplay but the final release is "coming soon" ™️ 😏

#retrocomputing
#retroprogramming
#gamedev
#forth
#dxforth

Continued thread

Oh bugger! It didn't turn out to be such a happy JCLPCB Day after all.

Glad that I found the error though, and thankfully camouflaged bodge wire makes for an invisible fix!

I don't get excited about Christmas. However, on days like today when I know that two big boxes with #JLCPCB stamped on them will be arriving, I can imagine the excitement that some people get in December. Even though I know what #RC2014 stuff is going to be inside, I can't help but keep looking out the window for the UPS truck!

Of course, dear Spidey, that with great power comes great responsibility, creating too many stacks can be overkill for some resource-constrained systems. But this is becoming less of a problem with new multi-core MCUs running at hundreds of Mhz, and with several megabytes of RAM.

What #ual says is: if your machine is not very powerful, we may be able to make it less painful to program highly optimised code for it. If your target machine is powerful, we may help to speed up your development cycles, and you may construct more nuanced, sophisticated, and reliable software with less effort.

Continued thread

New #ual programmers can start coding following most ideas they would assume to work using Lua, and progressively adopt the ual-specific stacked mode when it makes sense. For example, in resource-constrained systems where an algorithm using a Forth-like stack can be more efficient for certain tasks.

The > operator indicates a line that operates on the stack system, using a vocabulary for the most part similar to Forth's.

The @stackname > expression allows the programmer to select on which stack the operations are executed. The system comes with a data stack (@dstack) and a return stack (@rstack) built-in, but you can instantiate new ones, since stacks are first class objects in ual.

Take for example this implementation of Dijkstra's shortest path algorithm, uses its own separate stack to perform its computation.
github.com/ha1tch/ual/blob/mai

Hope you like it!

Continued thread

Other ideas in the works:

  • Adding the zxa assembler as one additional backend, to produce Z80 binaries.
    github.com/ha1tch/zxa
    in the future this could allow ual programs to target the ZX Spectrum and the RC2014.

  • Adding a uxntal backend to produce uxn roms.

Introducing the concept of transmutation

  • Write ual, or Z80 assembler, then send uxn or Z80 binaries to an ESP32 system, and have the binaries transmuted into Xtensa or RISC-V binaries as sort of shaders that run in-mcu.
A simple Z80 assembler for the ZX Spectrum written in Go - ha1tch/zxa
GitHubGitHub - ha1tch/zxa: A simple Z80 assembler for the ZX Spectrum written in GoA simple Z80 assembler for the ZX Spectrum written in Go - ha1tch/zxa

The soldering iron has been busy here at #RC2014 Towers today. 3 new/updated PCB designs for testing.

First one worked perfect first go. Yay!

Second one only worked when I went back and soldered the row of pins that I missed the first time around. So that is a win too!

Third one - Well, it works, although the pin order on the connectors needs swapping around for the final board. Luckily I only ordered 5 of these prototypes.

Looking forward to sharing these with you later next month. #NoSpoilers

... spent half the weekend trying to find out why I wasn't able to play a musical scale on the #ay89xx despite having all the formulae for caluclating the tone period implemented correct. some notes were played correctly 🎶 , others sounded like a fart ... 💨

turns out that I did 8 bit masking when I should have done 16 bit masking for the 12 bit of the coarse tune/fine tune registers ... *doh* ... 🤦‍♂️

#retrocoding
#soundchip
#forth
#rc2014
#ym2149f

Continued thread

Good news! JLCPCB have caved in and admitted that non-Euclidean geometry can be applied to their PCBs. So, subject to some negative temporal paradoxes being applied, there might be an exciting new Limited Edition #RC2014 available in the future. Or the past. Depending on when you are now.

+++ Sysop News +++ Sysop News +++

So I'm still investigating the connectivity issues I witnessed with #rc2014bbs and here are my current findings:

1.) while the telnet listener of the #Zimodem firmware is no longer open on port 2014, the #wifi of the #esp8266 itself is still active and the reserved ip is responding to ping requests.

2.) once the firmware gets reset via ATZ it sometimes restarts /re-opens the listener on port 2014

3.) the listener dies a few hours after initial powerup of the system

4.) my memory may be failing me but those issues began somewhere around autumn last year when I updated the firmware to version 3.7.1

As a result of these findings, I have reverted the firmware on the esp8266 to Zimodem version 3.6.5. It's not an official release - I checked it out using the corresponding commit hash.

The BBS was powered up with that version yesterday at 09:00 am and it is still running about 24 hours later, which was never the case with the 3.7.1 version of the firmware. I've also noticed a few other glitches not being present with the 3.6.5 version.

It is still a little too soon to call the problem solved, but there's movement here.

Also keep in mind that RC-BOX BBS (the world's first and - currently - only #rc2014 based #bbs) is using a wifi connection so other sources of influence may also have an effect on connectivity (although they never were *that* worse before 3.7.1).

Continued thread

I've had some great feedback, and I've done some more investigation.

It seems the #RC2014 SID-Ulator module is continuously outputting a 125Khz wave, even when no other sounds are being output.

This is exactly the SwinSID's 32Mhz clock divided by 256. Could this be an artifact of the emulation?