GRiSP 2 – Erlang and Elixir on bare metal

Re:GRiSP 2 – Erlang and Elixir on bare metal by peerst on Monday March 11, 2019 @06:46PM (#19363626)

Its not really „on RTEMS“, its more side by side. RTEMS is not a layer between the BEAM and te hardware its just helping by providing threads, TCP stack and file access. From a Erlang NIF or port driver (thats what we use to access the outside world in Erlang and Elxir) you have direct access to hardware registers and e.g. CPU interrupts.

[ Parent | on HN ]

Re:GRiSP 2 – Erlang and Elixir on bare metal by TickleSteve on Tuesday March 12, 2019 @02:11AM (#19365809)

If RTEMS is controlling the execution of your code, your running on or in RTEMS.

Direct hardware access isn't really "bare metal" in the same manner as software running in DOS is not bare-metal. direct-hardware access is provided in both.

[ Parent | on HN ]

Re:GRiSP 2 – Erlang and Elixir on bare metal by e_proxus on Tuesday March 12, 2019 @05:14AM (#19366469)

RTEMS isn't "controlling" the execution of the code, it just supplies implementation for OS-specific utilities (effectively the POSIX API). The BEAM VM code is compiled to machine code and runs directly on the CPU. As peerst explained, if you write your own C code in an Erlang port driver for example, you don't have to use RTEMS at all.

[ Parent | on HN ]

Re:GRiSP 2 – Erlang and Elixir on bare metal by anonymousDan on Tuesday March 12, 2019 @07:07AM (#19366975)

Is there the ability to run multiple OS processes or is the BEAM VM the only thing running after boot?

[ Parent | on HN ]

Re:GRiSP 2 – Erlang and Elixir on bare metal by e_proxus on Tuesday March 12, 2019 @10:49AM (#19368653)

You can only run one process in RTEMS (hence the name The Real-Time Executive for Multiprocessor Systems), however you can simulate other processes via threads. This is how we run the network stack and Wi-Fi configuration tools among other things.

[ Parent | on HN ]