mruby on the minimal embedded resource
summary
mruby on small MCUs requires about ~100KB RAM to run and a typical build uses ~150KB ROM, so cheap 128KB-class boards lack headroom. an stm32f4 reference board uses QSPI/SPI to map external memory; experiments count memset/memcpy operations and show string handling (hello world, fibonacci) drives most writes while pure number crunching does not. proposal: keep hot data in internal SRAM and combine a small SPI SRAM with NOR Flash as RAM cache (100k writes limit), spreading writes to extend life.
AI-written summary · about
chapters (8)
- 0:00Introduction to mruby
- 3:32Embedded benefits of mruby
- 10:11Why adopt mruby
- 17:25Minimum specs required
- 21:45Memory shortage challenges
- 25:26Flash memory usage
- 30:1016-bit mruby development
- 32:43Summary and future
related talks
27mROM: the final frontier of mruby
33mmruby/c: Running on Less Than 64KB RAM Microcontroller
15mA Managed Memory System for micro controllers with NOR flash memory
36m(m)Ruby on small devices
34mEmbedding Ruby into your Daily Life
29mWhat's happening when initializing mruby?
29mmake mruby more portable: Why and How
31mBuilding a Standalone Ruby Programming Environment