From: Dwight Schauer <dschauer@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] Ocaml on an embedded arm system (no linux)
Date: Fri, 20 Sep 2013 09:13:26 -0500 [thread overview]
Message-ID: <CAKdt_-YTk2gfc6P2-jyLVzTbp7heueC+M3t=p_LJWaNMC_zR7Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
Hi,
I'm looking at the feasibility of targetting a couple ARM processeors in a
similar manner to ocapic at its core.
What I'm looking to end up with is a bytecode interpreter running
coopertatively multi-tasked ocaml apps, that I can feed in more bytecode at
runtime (start a new task, replace an existing task, or interpret a
bytecode sequence in an existing task.) The framework for this on the
embedded target would be in C (not assembly).
Ideally I'd also have a shell on the host development that I could used to
interactively compile and interpret ocaml code running on the target.
I would also like to crosscomple (including metacompilation) for the target
on the host machine, where I could have a sources file that switch between
host and target code to produce applications for the target.
Ideally the shell on the host would have access to the same environment
used for cross compilation.
I have not used OCaml all that much, so I don't know yet how how difficult
(or feasible) that this task would be.
Since the bare metal framework of the embedded target would be in C, I
would develop and test it first on the host system. (Linux on x86_64).
The ARM processors I'm looking to target are:
STM32F407ZGT6 ARM Cortex-M4, 1MB Flash, 196KB RAM (Has floating point)
STM32F103RB ARM Cortex-M3, 128 KB Flash, 20K RAM (No floating point)
On both I'd like to be able to run bytecode both out of Flash and RAM.
(Primarily flash, but RAM for debugging).
Speed is on overly important as long as I can control when the garbage
collection is run (could be done in C in the multitasker?).
Dwight
[-- Attachment #2: Type: text/html, Size: 1887 bytes --]
next reply other threads:[~2013-09-20 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 14:13 Dwight Schauer [this message]
2013-09-20 15:54 ` Gerd Stolpmann
2013-09-20 16:19 ` Dwight Schauer
2013-09-20 16:46 ` Gerd Stolpmann
2013-09-21 12:08 ` Jonathan Kimmitt
2013-09-23 12:30 ` Goswin von Brederlow
2013-09-23 21:10 ` Anil Madhavapeddy
2013-09-30 13:48 ` Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKdt_-YTk2gfc6P2-jyLVzTbp7heueC+M3t=p_LJWaNMC_zR7Q@mail.gmail.com' \
--to=dschauer@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox