Fritz @daremo@fosstodon.org

I think we are feature- and bug-complete for the first part of the #vtracker UI, which is the pattern editor. I'll get this ready for release and push master.

This makes vtracker a bit more usable, but it still needs an instrument editor and track editor before it has a complete user interface.

New post on the motivation behind my vale8x64 #homebrewcomputer project, and an overview of its technical details: http://www.mahnke.tech/blog/2019-04-09-introducing-the-vale8x64-computer.html

Good morning.

Just registered for and plan to attend Cactuscon 2019: https://www.cactuscon.com/

I finished this small assembly language LCD demo in time for our #phxcompeng meeting this past Tuesday. The next thing to do is add RAM so programs can use a stack. After that, I want to make the computer load its start program from my desktop over serial port; reprogramming EEPROM every time is too cumbersome.

65C02, 65C22, and LCD are presumably wired correctly and a test program is assembled. My EEPROM programmer isn't correctly writing some memory locations, though. I noticed I'm not quite meeting the timing requirements for the write procedure, so I'm working on a new EEPROM programmer circuit now.

Working on address decoding and getting some wire paths cleaned up today. Optimistically, I'd like to be able to show off controlling the LCD display with assembly language programs at my #phx-com-eng meetup on Tuesday.

Good morning #supercon . Looking forward to striking up #homebrewcomputer conversations with people sitting next to me.

Working on the Arduino-based keyboard controller I'll use for my 65C02 computer. I'll start very simple. The controller will have a small internal buffer of keys that have been typed. It will deliver the scan code for each typed key to the processor, one by one, as the processor requests them.

@vertigo I also noticed the Wikipedia entry has a very nice overview of the internals https://en.wikipedia.org/wiki/Forth_(programming_language). And the Forth-79 standard seems pretty digestible, at 50 pages https://pages.physics.wisc.edu/~lmaurer/forth/Forth-79.pdf.

Regarding implementing a Forth, that is still some months away, but I've started to look into it. I've been reading the source code for JonesForth, and intend to take notes on the fig-forth source code as well. @vertigo, any other recommended material on understanding Forth's internals?

The last thing I want to emulate before moving back to the breadboard is a keyboard controller. Once I have a program to echo user keystrokes on the display in the emulator, it'll be time to move back to the hardware and bring it to parity with the emulator.

I have enough of the 65C22 emulated to drive the character LCD from an assembly language program: https://privatebin.net/?47c2cc0bea08e32a#2vLoq8E6VRZazTrHwekmjRUet5HTjdQyp4TwqxuKNJNH

Time to wrap up a few small things and quit for the day.

I don't know of such a standard, but I'd be interested if one exists. I'm gluing them together in C code.

I'm emulating a hardware computer I'm building around the 65C02 processor. The goal in this case is to be able to test ideas as thoroughly as possible in the software emulator before moving them to the hardware.

Character LCD emulation is working. Now I'll work on emulating the 6522.

I want to experiment with some interrupt and I/O routines before trying them on the hardware, so I'm looking for a 6502 core to use in an emulator. Here are a couple candidates I'll look into:

https://github.com/redcode/6502
https://github.com/DavidBuchanan314/6502-emu

6502 primer shows a circuit to extend the number of input bits for the 65C22 shift register, which is just what I need to handle 11-bit PS/2 keyboard scan codes. After I integrate this and the LCD with the 65C02, all the hardware is in place for a complete user I/O loop.

Then I'll start work on my first piece of software for this new machine: a forth environment. I've begun reading through JonesForth to prepare.

Who is going to Hackaday con?

I have 2 keyboards that fall back to PS/2 compatibility when connected through a USB-to-PS/2 adapter, which I happened to have. I confirmed they are sending their make/break signals.

Next is to communicate with the keyboard using the 65C22. It seems using the VIA's shift register is the best way to do that.

Got familiar with the 65C22 VIA. Testing the LCD display through it went fine.

Now to try to talk to a keyboard. Not sure whether or not any of the ones I have are PS/2 compatible.