make mruby more portable: Why and How
summary
A plan emerges: make mruby portable by building a mrbgems compatibility layer that wraps mbed/Arduino/CMSIS/STM HAL and RTOS calls, unify sensor APIs (value and detected) and accept some performance overhead. The team builds a Lego Sessalet Washlet model using EV3 (TOPPERS EV3RT), GR‑PEACH (Cortex‑A9) and Nucleo F412 (Cortex‑M4), uses IR and distance sensors plus different motors, and proves portability but hits real troubles: Nucleo F412 memory overflow, crashes during init, and a weak response to their mruby debugger, so work on ROM use and more samples continues.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:04What's Sessalet?
- 6:18mruby structue
- 7:55Why porting mruby app is difficult?
- 11:19making compatibility layer for mruby
- 12:30Unify peripheral API
- 13:01Application ported
- 15:50LEGO Mindstorms EV3
- 17:08Target boards' profile
- 18:40Sensors
- 19:34Motor
- 21:46Common Sensor API
- 25:44Arduino compatible headers
- 26:42Lesson Learned from Arduino
- 27:22Conclusion
- 27:43Future Plan
- 28:18porting into more boards
