prremote 0.2.1 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5c315e2104e35b23c87d7565249c2695f0bc8b9f7d0075564dda98b8fcc11491
-  data.tar.gz: 3e8ae2b89ca93b33f7830d45413dadef6f7c2d1d0a19d51499649214d626f1a6
+  metadata.gz: cfce7ce99a7bd04bbfde40aad5c53640f14f1ad90da41998c7399e6366d25198
+  data.tar.gz: d60e5701e6d42baf78a82a6d7d919d3bb5664cd34cb9cb02cdf7a2a749368121
 SHA512:
-  metadata.gz: 8bc5946b3d296fd7cfac88817b7e212f9713b13fa4a1f1748cacf84e278b0e269b0552f46b9eb0804e2ca319e50fd9e1bb48a4d81583c96f21bbcf468aa9d735
-  data.tar.gz: 8a467d706edf4600859d7563ab4dae1a29efd3eaaeff7d4f274d0be57412129eb44777fe099620733d0e773b0d17517751c7cb41e76714655803e038e8c5629a
+  metadata.gz: 5fd70f1266d67f8f41aef2018c102d4827c53cb103f304a16d40f78ee618c99556bc45fbc94447f66ff4e157f5318ff5b62956e8edf5dd1d1acda5a53ac1d94d
+  data.tar.gz: 70372664611e75517b6ea974ff85b222ecb6b53944ffdc345f423e6c15720b4daeedc84cdba20e5338c3c754f6090ac1aeb605ef34f498f1a4a6849236b62c31

data/README.md

@@ -18,9 +18,9 @@ Inspired by [mpremote](https://docs.micropython.org/en/latest/reference/mpremote
 
 - Ruby 3.4 or later
 - Supported boards:
-  - Raspberry Pi Pico W / Pico
-  - ESP32 (classic) — e.g. M5GO / M5Stack Core gen1, generic dev boards
-  - ESP32-C6 (RISC-V) — e.g. Seeed Studio XIAO ESP32C6
+  - [Raspberry Pi Pico W](https://www.raspberrypi.com/products/raspberry-pi-pico-w/) / [Pico](https://www.raspberrypi.com/products/raspberry-pi-pico/)
+  - ESP32 (classic) — e.g. [M5GO / M5Stack Core gen1](https://docs.m5stack.com/en/core/m5go), generic [ESP32](https://www.espressif.com/en/products/socs/esp32) dev boards
+  - ESP32-C6 (RISC-V) — e.g. [Seeed Studio XIAO ESP32C6](https://wiki.seeedstudio.com/xiao_esp32c6_getting_started/)
 - `mrbc` (mruby 4.x) for `run`, `deploy`, and `eval`
   - macOS: `brew install mruby`
   - Linux: build from source — [github.com/mruby/mruby/releases](https://github.com/mruby/mruby/releases)
@@ -74,7 +74,11 @@ The firmware is downloaded from GitHub Releases on first use and cached in `~/.p
 
 Pico boards: put the device into BOOTSEL mode (hold BOOTSEL, connect USB, release) when prompted.
 
-ESP32 / ESP32-C6 boards: no button dance and no extra tools needed — the firmware is written over the serial port by prremote's pure-Ruby implementation of the Espressif bootloader protocol (the chip is reset into its boot ROM automatically, and the write is verified with an on-chip MD5). Reflashing the runtime does not erase a deployed script.
+ESP32 (classic): no button dance and no extra tools needed — the firmware is written over the serial port by prremote's pure-Ruby implementation of the Espressif bootloader protocol (the chip is reset into its boot ROM automatically, and the write is verified with an on-chip MD5).
+
+ESP32-C6: flashing is delegated to [esptool](https://docs.espressif.com/projects/esptool/en/latest/), because the C6 boot ROM rejects the direct write the classic ESP32 accepts. Install it first (`brew install esptool`, or `pip3 install esptool`), and put the board into bootloader mode when prompted — on the XIAO ESP32C6, hold **BOOT**, press **RST**, then release both.
+
+Reflashing the runtime does not erase a deployed script on either chip.
 
 ---
 
@@ -128,7 +132,7 @@ Evaluate a Ruby one-liner on the device.
 
 ```bash
 prremote eval "puts 1 + 1"
-prremote eval "CYW43.init; CYW43::GPIO.new(CYW43::GPIO::LED_PIN).write 1"
+prremote eval "GPIO.led.write 1"
 ```
 
 ---
@@ -172,8 +176,8 @@ Show the gem version, mrbc version, and the connected device's runtime version.
 
 ```bash
 prremote version
-# prremote: 0.2.1
-# runtime:  0.2.1 (/dev/tty.usbmodem101)
+# prremote: 0.3.0
+# runtime:  0.3.0 (/dev/tty.usbmodem101)
 # mrbc: mruby 4.0.0 (2026-04-20) (/opt/homebrew/bin/mrbc)
 ```
 
@@ -218,7 +222,7 @@ prremote flashes a minimal C firmware (built on mruby/c) onto the Pico W. The fi
    - `DPLY` + `.mrb` bytecode → save to flash and confirm with `DEPLOYED` (`deploy`)
 3. Waits for the next command
 
-Scripts saved via `deploy` are stored in flash and run automatically on every boot. GPIO / ADC / PWM / I2C / SPI bindings are available on all boards; WiFi (CYW43) on the Pico W; an `LCD` class (ILI9342C) on ESP32 / M5Stack.
+Scripts saved via `deploy` are stored in flash and run automatically on every boot. GPIO / ADC / PWM / I2C / SPI bindings are available on all boards; a `WiFi` module on boards with a radio (Pico W and ESP32); an `LCD` class (ILI9342C) on ESP32 / M5Stack.
 
 ---
 
@@ -284,8 +288,4 @@ bundle exec rake test
 
 - [mruby/c](https://github.com/mrubyc/mrubyc) — Lightweight mruby implementation used in the runtime
 - [picotool](https://github.com/raspberrypi/picotool) — Official Raspberry Pi tool for inspecting and managing Pico devices; useful for checking what's on flash or force-rebooting outside of prremote
-- [mpremote](https://docs.micropython.org/en/latest/reference/mpremote.html) — MicroPython equivalent (inspiration)
-
-https://wiki.seeedstudio.com/ja/xiao_esp32c6_getting_started/
-
-brew install esptool
+- [mpremote](https://docs.micropython.org/en/latest/reference/mpremote.html) — MicroPython equivalent (inspiration)

data/VERSION

@@ -1 +1 @@
-0.2.1
+0.3.0

data/lib/prremote/esp_flasher.rb

@@ -104,21 +104,42 @@ module Prremote
         MSG
       end
 
+      ctx = { esptool: esptool, port: port, image_path: image_path, board: board, verbose: verbose }
+
+      # USB-Serial/JTAG chips (e.g. XIAO ESP32C6) can be dropped into the
+      # download ROM over USB, so esptool's usb-reset flashes hands-free — no
+      # BOOT/RST button dance. --after hard-reset then reboots straight into the
+      # freshly flashed firmware. Verified on a physical XIAO ESP32C6.
+      return if esptool_write(ctx, before: 'usb-reset', after: 'hard-reset', connect_attempts: 7)
+
+      # Fallback for hosts/boards where usb-reset doesn't take: enter the
+      # bootloader by hand and let esptool retry forever. --before no-reset never
+      # resets the chip, so each attempt just re-sends SYNC until the manual
+      # BOOT/RST lands the board in download mode — no timeout to race against.
       warn ''
-      warn 'Put the board in bootloader mode while "Connecting..." is shown:'
+      warn "Couldn't reset #{board} automatically. Put it in bootloader mode by hand:"
       warn '  XIAO ESP32C6: hold BOOT, press RST, release both.'
-
-      cmd = [*esptool,
-             '--chip', board, '--port', port,
-             '--before', 'no-reset', '--after', 'no-reset',
-             'write-flash', '0x0', image_path]
-      warn "[flash] #{cmd.join(' ')}" if verbose
-      system(*cmd) or raise Error, 'esptool exited with an error'
+      warn 'No rush — esptool keeps retrying the SYNC handshake until it connects.'
+      esptool_write(ctx, before: 'no-reset', after: 'no-reset', connect_attempts: 0) or
+        raise Error, 'esptool exited with an error'
 
       warn ''
       warn 'Flash complete. Press RST to start the firmware.'
     end
 
+    # Runs one `esptool write-flash 0x0 <image>` pass, returning esptool's
+    # success boolean.  connect_attempts 0 = retry the connect forever.
+    # `ctx` carries the fixed invocation context (esptool/port/image_path/board/verbose).
+    def self.esptool_write(ctx, before:, after:, connect_attempts:)
+      cmd = [*ctx[:esptool],
+             '--chip', ctx[:board], '--port', ctx[:port],
+             '--connect-attempts', connect_attempts.to_s,
+             '--before', before, '--after', after,
+             'write-flash', '0x0', ctx[:image_path]]
+      warn "[flash] #{cmd.join(' ')}" if ctx[:verbose]
+      system(*cmd)
+    end
+
     def self.find_esptool
       dirs = ENV.fetch('PATH', '').split(File::PATH_SEPARATOR)
       %w[esptool esptool.py].each do |exe|

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: prremote
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.3.0
 platform: ruby
 authors:
 - ITO Yosei