Erlang 28 on GRiSP Nano using only 16 MB

Re:Erlang 28 on GRiSP Nano using only 16 MB by signa11 on Tuesday July 22, 2025 @01:42AM (#44643566)

quick-question: why go the `rtems` route ? would 'isolcpus' not work in this case ?

thanks !

[ Parent | on HN ]

Re:Erlang 28 on GRiSP Nano using only 16 MB by plainOldText on Tuesday July 22, 2025 @05:38AM (#44644909)

I am not associated with the project, so I cannot answer that.

[ Parent | on HN ]

Re:Erlang 28 on GRiSP Nano using only 16 MB by peerst on Tuesday July 22, 2025 @09:15AM (#44646483)

With Linux we can only run on larger embedded CPUs that support virtual memory well enough. With RTEMS we can go towards much smaller platforms.

[ Parent | on HN ]

Re:Erlang 28 on GRiSP Nano using only 16 MB by peerst on Tuesday July 22, 2025 @09:21AM (#44646540)

Addendum: we have Buildroot and Yocto based platforms too. Not clear on the website right now but we have three platforms actually:

* GRiSP Metal - aka just GRiSP (Erlang/Elxiir + RTEMS)

* GRiSP Alloy - Buildroot Linux based, starts the Erlang/Elixir runtime as process 1 similar to Nerves but more language agnostic (Nerves is for Elixir only) and we support RT Linux and running multiple Erlang Runtimes at different priorities

* GRiSP Forge - Similar to alloy but Yocto based.

The idea is that from the high level language level they are more or less interchangeable.

[ Parent | on HN ]

Re:Erlang 28 on GRiSP Nano using only 16 MB by signa11 on Friday July 25, 2025 @11:14PM (#44691024)

ah ! indeed it can. do such platforms have 18m of memory and then some ?

[ Parent | on HN ]