Comments

LBPHacker 11th Jul 2016

But it's a terribly old, buggy version. Don't mind it.
LBPHacker 11th Jul 2016

Or if you just spark Resume instead of Start. Sparking start is what copies the new ROM into the RAM, Resume only resumes execution (doh). Yep, left the P1 demo code in there.
drunk_tv1 11th Jul 2016

If you spark the INST above the running light, it activates the Rterm P1 tech demo!
LBPHacker 11th Jul 2016

It's actually in the P1 forum thread. The keyboard just sends character codes (not keycodes).
LBPHacker 11th Jul 2016

Nope, it uses sends, although it could be made to first bump and then send the character when queried. It might be useful if you manage to hook up more peripherals to the computer than just the terminal.
zaccybot2 11th Jul 2016

what is the protocol for communication with the kb, does it use bumps on the port or anything?
LBPHacker 11th Jul 2016

The screen is already capable of printing a character (or setting cursor position or text color or scrolling) every frame. It's the computer's fault for not being able to churn out characters that fast :P Without a buffer (that is, something that increments some pointer AND outputs a character at the same time) it's impossible to send characters in every frame.
handicraftsman 11th Jul 2016

(screen's bus, to increase screen's speed)
LBPHacker 11th Jul 2016

There are several of both of those in there, which ones do you mean?
handicraftsman 11th Jul 2016

@LBPHacker, try increasing bus size and ROM reader's speed.

The Powder Toy