jamesbowman / 8051forth Goto Github PK

I know this project is no longer maintained but perhaps a hint or two would help.

I don't see how the resulting hex file is run to validate the build.

1. The instructions are to run the command: 8051emu/emu generic camel51.hex But the simulator doesn't accept an argument called generic.
2. The emulator is supposed to produce output which is captured in the file actual and compared with the file golden. But the emulator uses ncurses and generates screen output which looks nothing like the console output in golden.

I tried using an updated version of 8051emu from Github but the updates are minor and again there is no sign of console output, only ncurses output.

Wait, I think I get it. You defined aother main program called mymain.c which is a wrapper for the core simulator and this is the one that should be used.

Like in another issue reporter, I was wondering if this forth could be put inside a CH552.

Hello,

I'd like to ask your advice. Do you know a 8051 part which is easy to use for a beginner? Preferrably one which can be programmed with a command-line tool in Linux, and is simple to connect to a PC (USB?).

Thanks!

Hi James, I realise that this is not an active project, and a vanishingly small chance of you being interested but anyway...

Since I see you used a CH559, Can you comment on whether this forth can run on CH552?
i.e. is the memory map / flash self-programming workable, or is there a show stopper?

It would be fantastic to have a small forth on this as it is both minimal and cheap with USB.

https://hackaday.io/project/171543-chusbie552-ch552-development-board

It would be nice to have that little board with the default power-on function being a USB<->Serial adaptor,
that drops into the Forth command line when an escape sequence is seen (e.g. "+++")

The CH552 is cheap enough to be used instead of CH340 serial adaptor, but allowing with built in Forth control and automation. It would be a winner for very simple projects , both stand alone as as pc controlled interfaces.

Howdy,

I've tried several times to get my head around this, but failed each time.

Can you point me to some info on how to get started applying this from first principles. I'm used to running forth as a native application, and talking via a terminal session to the interpreter/compiler and loading code via terminal text uploads, with the appropriate time delay to let the embedded Forth understand the code... This is a different kettle of fish.

Thank you!