I didn't think your question got properly answered, so I'm going to add a few comments and a few off-topic links.

gforth, as I see it, would best be described as a hosted forth. So, if you want to use it as an embedded system, you'll need to put at least glib (thus, ulib, as Edward mentioned) underneath it.

Or, if you have a few megabytes of flash and RAM to keep a full host OS, you might try a stripped-down Linux or BSD underneath gforth. (netBSD and openBSD have small footprints, and then there are "Damn Small Linux" and "Puppy Linux" and similar. If you check around those communities, they can point you to even smaller unix-ish host OSses.

I'm not sure what Bernd and David are doing, didn't take the time to check, but it would be theoretically possible to go the other direction, and replace the parts of glib that gforth is dependent on with your own code. I don't think gforth uses all that much of glib, so it may just be a matter of a few primitive routines.

Other places you might want to look for more information on using FORTH as the embedded OS -- forth.org is back up, and has a number of very small models of the old fig-FORTHs:

http://forth.org
http://forth.org/fig-forth/contents.html

The fig-FORTH model listings are partial image-to-pdf conversions, you'll need to be able to view large graphical PDF files. But, for all that the pdfs are huge downloads (12M), the actual listings are on the order of 40 ~ 80 pages of assembly language language, and not very dense, at that. Definitely possible for a single person to read and understand within a month or so.

Your question moved me to blog yesterday about my experience porting a fig model to the 6809 many moons ago, see http:// reiisi.blogspot.com . If you're interested in the 6809 source and my annotations, and can't (don't want to?) find the tools to get them out of the .hqx, let me know off-list. (I think I'll eventually re- organize my site and put those back up as tarballs, but I'm working on something else today.)

OpenFirmware might be interesting, or might be confusing overkill. You can search on, say, google, for "openfirmware arm".

Finally, have you seen comp.lang.forth, accessible at many newsgroup portals, for instance, google's groups at http://groups.google.com ?

On 平成 20/07/26, at 0:04, Jelle de Jong wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everybody,

My name is Jelle and I'm new to this mailinglist, so let me first thank
~ you all for the development of gforth.

In all my years of collage I never heard of the forth language. So when I was reading through a "designing embedded hardware" book i came across
a forth chapter and read it with some surprises.

gforth looks interesting and I would like to know if I can build an
embedded "system on chip system" with an ARM9 or ARM7 and create a
firmware programmed in gforth for the device? I need to be able to
control all the hardware, create interrupt routines and all the other
stuff normally possible in embedded systems.

Are there people here that have programmed arm systems with gforth? If
possible and the opportunity arises I could create a training module for
gforth and ARM systems for some Dutch universities.

Best regards,

Jelle

The gnu gforth website does not work very well on my system:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1) Gecko/2008071618
Iceweasel/3.0.1 (Debian-3.0.1-1)
http://www.gnu.org/software/gforth/#introduction
http://www.gnu.org/software/gforth/#downloading
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkiJ62sACgkQ1WclBW9j5HkY0AP/TxuUpq3IA9AoKfl73qJF0cOl
cU/FqslrtAkrNX5H0bSAAqmEFixJByvLQY9Rs+QEiH/yRjrGMvkc8hyHYQN93MvD
XQUEtl8g+3mrl3xpK19kbYr1xhqIXaqMdA7U/rFWZKyRsPhTHlH/UB+jG3z2q0E2
mCeLkM8YrLGOAux2puw=
=Zp07
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Joel Rees
(waiting for a 3+GHz ARM processor to come out,
to test Steve's willingness to switch again.)



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to