rabbit-slide-hasumikin-RubyConfPoland2019-Workshop 2019.05.15

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: b405d2e727e9bdf9a97abafa789721d74b6745a8778e39c3f0eb67ce9062120f
+  data.tar.gz: d39e0fb8abf7e62826bbbaac065e06229efd7882fe96f3270dee51674b07219e
+SHA512:
+  metadata.gz: b4ed7960e3725d6d00ae33b9d1cf8f54d54dd31a01ef93109d06f08a04cf3cea575a854b2c0b52016b2cd02983217abfbe8f38b2e78d91caff82c062673085c5
+  data.tar.gz: cc059e8425cc13e5830883835d71ca8dc18209fcaba186f40500eac71509d9acd15b62d265d012be1cac9527caf7b2f3339775493ad14387756bcdee5ef3f879

data/.rabbit

@@ -0,0 +1 @@
+IoT-workshop-for-firmware-programming-with-ESP32-and-mrubyc.rab

data/IoT-workshop-for-firmware-programming-with-ESP32-and-mrubyc.rab

@@ -0,0 +1,558 @@
+= IoT workshop for firmware programming with ESP32 and mruby/c
+
+#    サブタイトル
+: author
+   HASUMI Hitoshi (@hasumikin)
+: institution
+   Monstar Lab, Matsue
+# : content-source
+#    イベント名
+: date
+   March 16, 2019 in Matsue, Japan
+: date
+   May 6, 2019 in Warszawa, Polska
+: date
+   May 15, 2019 in Kraków, Polska
+: allotted-time
+   3h
+: theme
+   theme
+
+= hide-title
+(('tag:center'))\n\n\n\n((*(('tag:xx-large:Cześć!'))*))
+== プロパティ
+: hide-title
+   true
+
+= about me
+  * HASUMI Hitoshi\n@hasumikin
+  * Ruby ((*💎*))\nSake 🍶\nSoba 🍜\nCoffee ☕
+  # image
+  # src = images/hasumi.jpg
+  # align = right
+  # relative-height = 80
+
+= about me
+== prop
+: background-image
+   images/monstarlab.png
+: background-image-relative-height
+   100
+
+= about me
+== prop
+: background-image
+   images/m2.png
+: background-image-relative-height
+   100
+
+= about me
+== prop
+: background-image
+   images/松江城_Matsue.rb.jpg
+: background-image-relative-width
+   100
+
+= message from Matz
+  # # video
+  # # src = images/matz.mp4
+
+= agenda
+  * we will learn how to start to make IoT product with Ruby
+  * assumed attendees are software programmers
+  * ESP32 microcontroller as the platform
+  * mruby/c (and C) as the firmware language
+  * we will iterate some combinations of lecture and hands-on
+
+= agenda
+  * we have 3 to 4 hours 😨
+    * no worry, we will take several breaks
+
+= break
+\n\n\n(('tag:center'))a short break
+== prop
+: hide-title
+   true
+: background-image
+   images/annie-spratt-330560-unsplash.jpg
+: background-image-relative-height
+   100
+
+= enquête
+
+= enquête
+(('tag:center'))\n\n\n\n✋ please raise your hand ✋\n✋ if you are a ✋\n✋ firmware programming ((*newbie*)) ✋
+
+= enquête
+(('tag:center'))\n\n\n\n✋ please raise your hand ✋\n✋ if you don't have ✋\n✋ ((*any*)) experience of mruby  ✋
+
+= enquête
+(('tag:center'))\n\n\n\n✋ please raise your hand ✋\n✋ if you don't have ✋\n✋ ((*much*)) experience of C language ✋
+
+= setup your laptop
+* we have to install ESP-IDF and some dependent tools in order to develop mruby/c firmwares for ESP32
+* the most important thing will be ((*USB*)). we will write our firmware into ESP32 through USB cable
+
+= setup your laptop - Linux or macOS
+* using ((*Linux distributions*)) or ((*macOS*)) (as a host machine) is the easiest way
+  * less USB problem
+* I'm not sure but docker will not work because of USB problem
+
+= setup your laptop - Windows
+* you can choose both ((*Windows Subsystem for Linux*)) (WSL) and ((*MSYS2*))
+  * I recommend you to use WSL if your OS is Windows10 (64 bit) as compiling on WSL is much faster than MSYS2
+* ((*WSL*))
+  * you should use WSL if your OS is 64bit of Win10 Pro
+
+= setup your laptop - Windows
+* ((*MSYS2*))
+  * strongly recommended of using zipped one which Espressif Systems maintenances
+  * besides, note that only 32 bit version of MSYS2 is available regardless of whether your Windows is 64 bit or 32 bit
+* Docker for Windows
+  * it appears not to work so far
+  * but please tell me if it works
+
+= setup your laptop - VM
+* I (hasumi) use Linux Mint with VirtualBox on Windows 10 Professional
+  * but some people say that virtual environments tend to have problems around USB
+
+= setup your laptop
+\n\n
+(('tag:center'))more information on
+\n\n
+https://github.com/hasumikin\n/IoT_workshop
+
+= setup your laptop
+\n\n\n\n
+(('tag:center'))please tell me if you have any doubt
+\n
+during the hands-on
+
+= Hands On 01
+\n
+(('tag:center'))Hello mruby/c World!
+\n\n
+open the URL
+\n
+(('tag:center'))github.com/hasumikin/IoT_workshop
+\n\n
+and find the link
+\n
+(('tag:center'))((*Hands on 01*))
+== prop
+: background-image
+   images/black-background.png
+: background-image-relative-width
+   100
+: background-image-relative-height
+   100
+
+= what is microcontroller?
+* if you are not familiar with microcontroller, this section is very important to grab overview what we do in this workshop
+
+= one-chip microcontroller
+  * a single IC chip\nconsists of CPU(MPU),\nRAM, ROM and\nprogrammable GPIOs
+  * `programmable`\nmeans user can\nconfigure the role\nof the pins
+
+  # image
+  # src = images/esp32_onechip.png
+  # align = right
+  # relative-height = 90
+
+= moduled microcontroller
+  * additional instruments\nlike WiFi communication\nmodule combined\nwith one-chip\nmicrocontroller
+
+  # image
+  # src = images/esp32_module.png
+  # align = right
+  # relative-height = 90
+
+= moduled microcontroller
+  # image
+  # src = images/esp32_module_block_diagram.png
+  # align = center
+  # relative-height = 90
+
+(('tag:left'))(('tag:xx-small:"esp32_hardware_design_guidelines_en.pdf  esp32_datasheet_en.pdf"'))
+
+= development board (devkit)
+  * useful equipments like\nUSB adaptor and power\nregulator combined\nwith microcontroller\nfor experimental work
+  * generally has 2.54mm\n(=1/10inch) pitch pins\nto be fit with\nbreadboard
+
+  # image
+  # src = images/esp32_devboard.png
+  # align = right
+  # relative-height = 90
+
+= what is microcontroller?
+* what we call as `microcontroller` depends on the situation
+* I call the development board as `microcontroller` in this workshop
+* you may have to treat `one-chip microcontroller` as `microcontroller` if you plan for producing an IoT hardware
+
+= Hands On 02
+\n
+(('tag:center'))Hello ESP32 World!
+\n\n
+open the URL
+\n
+(('tag:center'))github.com/hasumikin/IoT_workshop
+\n\n
+and find the link
+\n
+(('tag:center'))((*Hands on 02*))
+== prop
+: background-image
+   images/black-background.png
+: background-image-relative-width
+   100
+: background-image-relative-height
+   100
+
+= break
+\n\n\n\n\n\n\n(('tag:center'))a short break
+== prop
+: hide-title
+   true
+: background-image
+   images/andrew-santellan-311033-unsplash.jpg
+: background-image-relative-height
+   100
+
+= peripherals
+* ((*peripheral*)) is an important concept of microcontroller
+* high-end microcontroller has rich peripherals and low-end one has less
+
+= peripherals
+  # image
+  # src = images/esp32_block_diagram-2.png
+  # align = center
+  # relative-height = 90
+
+(('tag:center'))(('tag:xx-small:"esp32_datasheet_en.pdf"'))
+
+= peripherals
+* GPIO (General Purpose Input/Output)
+  * GPIO is a defining characteristic of microcontroller
+  * GPIO basically has values of only 0 and 1 (digital value)
+    * analog value will be mentioned later
+  * usecases of Input:
+    * switch as an user interface, getting sensor value
+  * usecases of Output:
+    * LED as a display, sending message to modem
+
+= peripherals
+* ADC (analog to digital converter) and\nDAC (vice versa)
+  * ADC converts analog value such as microphone input into digital value that computer can deal with
+  * DAC converts digital value such as sound data of MP3 into analog output in order to play back the music on loud speaker
+
+= peripherals
+  * Raspberry Pi does neither have ADC nor DAC
+  * we can add an independent ADC part if we need it
+  # image
+  # src = images/mcp3002.jpg
+  # align = center
+  # relative-height = 90
+
+(('tag:center'))(('tag:xx-small:from "http://akizukidenshi.com/catalog/g/gI-02584/"'))
+
+= today's parts
+  * breadboard
+  * resistor
+  * LED
+  * thermistor
+
+= breadboard (protoboard)
+  * wired internally by 2.54 mm pitch so that we can experiment without soldering
+
+  # image
+  # src = images/bb_wiring_01.png
+  # align = center
+  # relative-height = 90
+
+(('tag:center'))(('tag:xx-small:from "https://ht-deko.com/arduino/breadboard.html"'))
+
+= registor & Ohm's law
+  * if the voltage across the both ends of 10kOhm resistor is 3V, the current will be 0.3mA
+
+(('tag:center'))3 / 10k = 3 / 10000 = 0.0003A = 0.3mA
+
+  # image
+  # src = images/resistor.jpg
+  # align = center
+  # relative-height = 100
+
+= LED
+  # blockquote
+  # title = WIKIPEDIA
+  A light-emitting diode (LED) is a semiconductor light source that emits light when current flows through it.
+
+   # image
+   # src = images/LED.png
+   # align = center
+   # relative-height = 100
+
+= LED - datasheet
+  # image
+  # src = images/led_datasheet.png
+  # align = center
+  # relative-height = 90
+
+(('tag:center'))(('tag:xx-small:from "http://akizukidenshi.com/download/ds/optosupply/OSXXXX3Z74A_VER_A1.pdf"'))
+
+= LED & Ohm's law
+(('tag:center'))(3.3 - 2.1) / 330 = 0.0036A = 3.6mA
+
+  # image
+  # src = images/led_circuit.png
+  # align = center
+  # relative-height = 100
+
+= LED & GPIO
+  * small LED can be lighten by GPIO
+  * but instruments like huge LED which requires high current can not be driven even if its nominal voltage is less than 3.3V
+  * because microcontroller has some limit of supplying amount of electric current
+  * incorrect usage may break your microcontroller
+
+= Hands On 03
+\n
+(('tag:center'))Blinking LED
+\n\n
+open the URL
+\n
+github.com/hasumikin/IoT_workshop
+\n\n
+and find the link
+\n
+((*Hands on 03*))
+\n\n
+hint: you should use a ((*blue*)) resistor
+== prop
+: background-image
+   images/black-background.png
+: background-image-relative-width
+   100
+: background-image-relative-height
+   100
+
+= break
+\n\n\n\n\n(('tag:center'))a short break
+== prop
+: hide-title
+   true
+: background-image
+   images/jj-ying-230105-unsplash.jpg
+: background-image-relative-height
+   100
+
+= today's parts (again)
+  * breadboard
+  * resistor
+  * LED
+  * thermistor
+
+= thermistor
+  # blockquote
+  # title = WIKIPEDIA
+  A thermistor is a type of resistor whose resistance is dependent on temperature, more so than in standard resistors.
+\n
+  # image
+  # src = images/thermistor.jpg
+  # align = center
+  # relative-height = 110
+
+= thermistor
+  # image
+  # src = images/Corleto_thermistor1.jpg
+  # align = left
+  # relative-height = 90
+
+(('tag:center'))(('tag:xx-small:from "https://www.allaboutcircuits.com/projects/measuring-temperature-with-an-ntc-thermistor/"'))
+
+#= thermistor - approximation
+#  # LaTeX
+#
+#  $\;$
+#
+#  $R=R_{ref} \times e^{(B(\frac{1}{T+273}-\frac{1}{T_{o}+273}))}$
+#
+#  hence,
+#
+#  $T=\frac{1}{\frac{1}{B}\log \frac{R}{R_{ref}}+\frac{1}{T_{o}+273}}-273$
+
+= thermistor - approximation
+  # image
+  # src = images/thermistor_approximation.png
+  # relative_width = 80
+  # relative_margin_top = 10
+
+= thermistor - datasheet
+  # image
+  # src = images/thermistor_datasheet.png
+  # relative_width = 100
+
+(('tag:center'))(('tag:xx-small:from "https://www.mouser.com/datasheet/2/362/semitec_atthermistor-1202913.pdf"'))
+
+= thermistor - approximation
+  # enscript ruby
+  # this is CRuby
+  include Math
+
+  # according to the datasheet
+  B    = 3_435  # from datasheet
+  To   = 25     # from datasheet
+  Rref = 10_000 # arbitrary but fixed
+
+  def temperature(r)
+    1.to_f / ( 1.to_f / B * log(r.to_f / Rref)
+      + 1.to_f / (To + 273) ) - 273
+  end
+
+  # if resistance of thermistor is 12kOhm
+  puts temperature(12_000)
+
+  => 20.35988998853088
+
+#= thermistor - circuit
+#  # LaTeX
+#
+#  $R=\frac{V-V_{ref}}{\frac{V_{ref}}{R_{ref}}}$
+
+= thermistor & Ohm's law
+  # image
+  # src = images/thermistor_circuit_resistance.png
+  # relative-height = 100
+
+= Hands On 04
+\n
+(('tag:center'))Taking temperature
+\n\n
+open the URL
+\n
+github.com/hasumikin/IoT_workshop
+\n\n
+and find the link
+\n
+((*Hands on 04*))
+\n\n
+hint: you should use a ((*brown*)) resistor
+== prop
+: background-image
+   images/black-background.png
+: background-image-relative-width
+   100
+: background-image-relative-height
+   100
+
+= break
+\n\n\n\n\n\n(('tag:center'))a short break
+== prop
+: hide-title
+   true
+: background-image
+   images/mnm-all-551345-unsplash.jpg
+: background-image-relative-height
+   100
+
+= what is mruby/c?
+  * github.com/mrubyc/mrubyc
+  * yet another implementation of mruby
+  * `/c` symbolizes compact,\nconcurrent and capability
+  * especially dedicated to\none-chip microcontroller
+
+= mruby and mruby/c
+  # RT
+
+  mruby, mruby/c
+
+  v1.0.0 in Jan 2014, v1.0 in Jan 2017
+  for general embedded software, for one-chip microcontroller
+  RAM < 400KB, RAM < 40KB
+
+* sometimes mruby is still too big to run on microcontroller
+
+= ((*both*)) mruby and mruby/c
+  * bytecodes are compiled by `mrbc` and VM executes the bytecode
+  # image
+  # src = images/mruby_and_mrubyc.png
+  # align = center
+  # relative-height = 100
+
+= bytecode
+  * a kind of intermediate representation
+  * virtual machine dynamically interprets the bytecode and processes the program
+  # image
+  # src = images/bytecode.png
+  # align = center
+  # relative-width = 100
+
+= mruby on microcontroller
+  * RTOS (Real-Time OS) manages mruby VMs. RTOS has features like multi tasking
+  # image
+  # src = images/mruby_and_mrubyc-mruby.png
+  # align = center
+  # relative-height = 100
+
+= mruby/c on microcontroller
+  * mruby/c has its own mechanism to manage the runtime: ((*rrt0*))
+  # image
+  # src = images/mruby_and_mrubyc-mrubyc.png
+  # align = center
+  # relative-height = 100
+
+= mruby/c - virtual machine (VM)
+  * much smaller than mruby's one
+    * that's why mruby/c runs on smaller RAM
+  * accordingly, mruby/c has ((*less*)) functionality than mruby
+
+= how ((*less*))?
+
+= how ((*less*))? - for example
+  * mruby/c doesn't have module, hence there is no Kernel module
+  * then you must wonder how can you `#puts`?
+  * in mruby/c, `#puts` is implemented in Object class
+
+= how ((*less*))? - for example
+  * mruby/c doesn't have #send, #eval, nor #method_missing
+  * moreover, mruby/c neither have your favorite features like TracePoint nor Refinements 😞
+
+= how ((*less*))? - actually
+  * the full list of mruby/c's classes
+    * Array,   FalseClass,   Fixnum,   Float,   Hash,   Math,   Mutex,   NilClass,   Numeric,   Object,   Proc,   Range,   String,   Symbol,   TrueClass,   VM
+
+= despite the fact,
+  * no problem in practical use of microcontroller
+  * as far as IoT go, mruby/c is enough Ruby as I expect
+  * we can fully develop firmwares with features of mruby/c
+
+= Hands On 05
+\n
+(('tag:center'))Multi-tasking with mruby/c
+\n\n
+open the URL
+\n
+(('tag:center'))github.com/hasumikin/IoT_workshop
+\n\n
+and find the link
+\n
+(('tag:center'))((*Hands on 05*))
+== prop
+: background-image
+   images/black-background.png
+: background-image-relative-width
+   100
+: background-image-relative-height
+   100
+
+= conclusion
+
+= conclusion
+\n\n\n\n
+(('tag:center'))(('tag:large:All you need is')) ((*(('tag:large:Ohm's law'))*))
+
+= ((' '))
+\n\n\n\n
+(('tag:center'))(('tag:xx-large:Thank you!'))
+== プロパティ
+: hide-title
+   true
+