2024-07-06 14:19:47 Wow - hurricane Beryl's predicted path now looks like it's headed right at us here in Houston. It will be a much weaker storm by then than it was, though. 2024-07-06 17:27:05 Hey, for this "three instruction" interface, the line I'm thinking on right now is to have that interface run on ASCII characters. The target will have a small stack (not the eventual Forth stack - this one's dedicated and doesn't have to be very deep). Each incoming character that is a hex digit will just get "accumulated" into the TOS. Then we'll have four other characters, that basically run @, !, 2024-07-06 17:27:07 "call," and "send." Send will deliver the TOS value to the host. 2024-07-06 17:27:38 That's enough to function in the sense described in that three instruction paper. 2024-07-06 17:29:02 Send will also send the value back as a hex character string. No binary data in the interface. 2024-07-06 17:30:42 So with that running I then see going through a process kind of like that PlanckForth system we kicked around here once. Just steadily bootstrap up a full Forth interface. 2024-07-06 17:40:10 Oh, yeah - you also need a command to push a new 0 onto the stack. Like the ENTER key on an RPN calculator. 2024-07-06 17:40:17 So you can do multiple numbers in a row. 2024-07-06 21:27:24 What's the appeal of the three instruction interface in this case? I see the point when you want to take as little space on the target as possible and keep everything on the host 2024-07-06 21:49:07 Just the simplest possible starting point. The least code I'd have to get in and working before I started working in "my own" ecosystem.