KuttyPy -- Visual Programming & C IDE

// JS code updates as you edit blocks

Connect USB, build a program, then Run.

Connect USB, upload firmware that prints CSV lines, then Launch.

Connect USB, upload firmware that replies to a poll command with CSV lines, then Launch.

No channels yet — start polling to detect columns

Chart.js polled logger. Upload oneshot firmware, Launch, then Start.

Opening dumps flash from address 0…

Upload cro.c (ATmega32) or cro_atmega328p.c (Nano), Launch, then Capture (sends READBLOCK=1).

Step 1

Prepare Arduino ISP

Flash ArduinoISP onto the KuttyPy that is connected over USB. This board becomes the programmer for the next step. Choose the MCU family that matches this board.

Uploads atmega32_uisp.hex or atmega328p_uisp.hex via the bootloader
After success, tie RST → 5V on this programmer so it cannot self-program

Step 2

Prepare another KuttyPy

Wire the programmer (ArduinoISP board) to a blank or target board, then use the buttons below in order. Port stays open at 38400 — no reopen / baud change. Opening this page jumps from the KuttyPy monitor into the already-flashed ArduinoISP sketch (same as C IDE Run).

Connect 5V–5V, GND–GND, MISO–MISO, MOSI–MOSI, SCK–SCK
Connect programmer pin 10 → RST of the target board
Keep programmer RST tied to 5V after ArduinoISP is running
If Probe fails after jump, use step 1 to Flash ArduinoISP first
Probe = STK sync + ArduinoISP version + target signature (few bytes)
Burn fuses = chip-erase + lfuse/hfuse/(efuse) for the selected MCU
Flash bootloader = write/verify rgbboot_*.hex (run Burn fuses first on a blank chip)

Visual Programming

C Programming

DATA LOGGER

POLLED LOGGER

POLLED LOGGER 2

READ FLASH

OSCILLOSCOPE

Spawn KuttyPy

Prepare Arduino ISP

Prepare another KuttyPy